issue_comments
15 rows where author_association = "MEMBER" and issue = 84127296 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- add average function · 15 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
485456780 | https://github.com/pydata/xarray/issues/422#issuecomment-485456780 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDQ4NTQ1Njc4MA== | dcherian 2448579 | 2019-04-22T15:52:15Z | 2019-04-22T15:52:15Z | MEMBER |
I would do the same i.e. take inspiration from the groupby / rolling / resample modules. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
484470656 | https://github.com/pydata/xarray/issues/422#issuecomment-484470656 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDQ4NDQ3MDY1Ng== | rabernat 1197350 | 2019-04-18T11:47:08Z | 2019-04-18T11:48:03Z | MEMBER | @pgierz - Our documentation has a page on contributing which I encourage you to read through. ~Unfortunately, we don't have any "developer documentation" to explain the actual code base itself. That would be good to add at some point.~ Edit: that was wrong. We have a page on xarray internals. Once you have your local development environment set up and your fork cloned, the next step is to start exploring the source code and figuring out where changes need to be made. At that point, you can post any questions you have here and we will be happy to give you some guidance. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
483715005 | https://github.com/pydata/xarray/issues/422#issuecomment-483715005 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDQ4MzcxNTAwNQ== | dcherian 2448579 | 2019-04-16T15:37:37Z | 2019-04-16T15:37:37Z | MEMBER | @pgierz take a look at the "good first issue" label: https://github.com/pydata/xarray/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
482737161 | https://github.com/pydata/xarray/issues/422#issuecomment-482737161 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDQ4MjczNzE2MQ== | dcherian 2448579 | 2019-04-12T22:03:27Z | 2019-04-12T22:03:27Z | MEMBER |
hmm.. the intent here would be that the weights are broadcasted against the input array no? Not sure that a warning is required. e.g. @shoyer's comment above:
Are we going to require that the argument to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
482393543 | https://github.com/pydata/xarray/issues/422#issuecomment-482393543 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDQ4MjM5MzU0Mw== | spencerkclark 6628425 | 2019-04-12T00:48:09Z | 2019-04-12T10:28:59Z | MEMBER | It would be great to have some progress on this issue! @mathause, @pgierz, @markelg, or @jbusecke if there is anything we can do to help you get started let us know. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
218520080 | https://github.com/pydata/xarray/issues/422#issuecomment-218520080 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDIxODUyMDA4MA== | shoyer 1217238 | 2016-05-11T16:51:10Z | 2016-05-11T16:51:10Z | MEMBER | Yes, +1 for
This is a fair point, I haven't looked in to the details of these implementations yet. But I expect there are still at least a few picks of logic that we will be able to share. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
218513335 | https://github.com/pydata/xarray/issues/422#issuecomment-218513335 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDIxODUxMzMzNQ== | jhamman 2443309 | 2016-05-11T16:26:55Z | 2016-05-11T16:26:55Z | MEMBER | @mathause - I would think you want the latter ( ``` Python
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
218413377 | https://github.com/pydata/xarray/issues/422#issuecomment-218413377 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDIxODQxMzM3Nw== | mathause 10194086 | 2016-05-11T09:51:29Z | 2016-05-11T09:51:29Z | MEMBER | Do we want
or
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
218403213 | https://github.com/pydata/xarray/issues/422#issuecomment-218403213 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDIxODQwMzIxMw== | mathause 10194086 | 2016-05-11T09:06:49Z | 2016-05-11T09:07:24Z | MEMBER | Sounds like a clean solution. Then we can defer handling of NaN in the weights to We may still end up implementing all required methods separately in
i.e. we use
However, I think this can not be generalized to a Additionally, |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
218360875 | https://github.com/pydata/xarray/issues/422#issuecomment-218360875 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDIxODM2MDg3NQ== | shoyer 1217238 | 2016-05-11T04:47:46Z | 2016-05-11T04:47:46Z | MEMBER | I would suggest not using keyword arguments for |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
218358372 | https://github.com/pydata/xarray/issues/422#issuecomment-218358372 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDIxODM1ODM3Mg== | jhamman 2443309 | 2016-05-11T04:24:05Z | 2016-05-11T04:24:05Z | MEMBER | @MaximilianR has suggested a ``` Python da.weighted(weights=ds.dim).mean() or maybeda.weighted(time=days_per_month(da.time)).mean() ``` I really like this idea, as does @shoyer. I'm going to close my PR in hopes of this becoming reality. |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
140823232 | https://github.com/pydata/xarray/issues/422#issuecomment-140823232 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDE0MDgyMzIzMg== | mathause 10194086 | 2015-09-16T18:02:39Z | 2015-09-16T18:02:39Z | MEMBER | Thanks - that seems to be the fastest possibility. I wrote the functions for Dataset and DataArray ``` python def average_da(self, dim=None, weights=None): """ weighted average for DataArrays
-----------------------------------------------------------------------------def average_ds(self, dim=None, weights=None): """ weighted average for Datasets
``` They can be combined to one function: ``` python def average(data, dim=None, weights=None): """ weighted average for xray objects
``` Or a monkey patch:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
140797623 | https://github.com/pydata/xarray/issues/422#issuecomment-140797623 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDE0MDc5NzYyMw== | shoyer 1217238 | 2015-09-16T16:40:20Z | 2015-09-16T16:40:20Z | MEMBER | Possibly using where, e.g., |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
140794893 | https://github.com/pydata/xarray/issues/422#issuecomment-140794893 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDE0MDc5NDg5Mw== | mathause 10194086 | 2015-09-16T16:29:22Z | 2015-09-16T16:29:32Z | MEMBER | This is has to be adjusted if there are Is there a better way to get the correct weights than:
It should probably not be used on a Dataset as every DataArray may have its own |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 | |
108118570 | https://github.com/pydata/xarray/issues/422#issuecomment-108118570 | https://api.github.com/repos/pydata/xarray/issues/422 | MDEyOklzc3VlQ29tbWVudDEwODExODU3MA== | shoyer 1217238 | 2015-06-02T22:41:22Z | 2015-06-02T22:41:22Z | MEMBER | Module error checking, etc., this would look something like:
This is pretty easy to do manually, but I can see the value in having the standard method around, so I'm definitely open to PRs to add this functionality. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
add average function 84127296 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 6