issue_comments
7 rows where author_association = "MEMBER" and issue = 224878728 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- argmin / argmax behavior doesn't match documentation · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
656361865 | https://github.com/pydata/xarray/issues/1388#issuecomment-656361865 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDY1NjM2MTg2NQ== | dcherian 2448579 | 2020-07-09T21:32:52Z | 2020-07-09T21:32:52Z | MEMBER | I think this is fixed now thanks to @johnomotani |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
362951129 | https://github.com/pydata/xarray/issues/1388#issuecomment-362951129 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDM2Mjk1MTEyOQ== | shoyer 1217238 | 2018-02-04T23:54:10Z | 2018-02-04T23:54:10Z | MEMBER | I think it would be fine to add a special case to preserve coordinates corresponding to min/max values with xarray's I agree that it does not make sense to preserve coordinates along aggregated dimensions for argmin/argmax, but we can preserve other coordinates. So I like @fujiisoup's example behavior above. I suppose we now have two candidate APIs for returning multiple indices from a method like argmin/argmax:
1. Add an additional dimension, e.g., I think my favorite option is (2) with My concern with adding an additional dimension is that it is always a little surprising and error-prone when we invent new dimension names not supplied by the user (for example, this can lead to conflicting names). Also, consolidating indices will not work as well with Either way, I would like a separate dedicated method for returning multiple indexing arrays. It's convenient (and what users expect) for argmax to return a single array if taking the max only over one dimension. However, if we switch to add an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
362902669 | https://github.com/pydata/xarray/issues/1388#issuecomment-362902669 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDM2MjkwMjY2OQ== | fujiisoup 6815844 | 2018-02-04T12:20:33Z | 2018-02-04T12:52:29Z | MEMBER | @gajomi Sorry for my late response and thank you for the proposal. But aside from my previous proposal, I was thinking whether such aggregation methods (including Such specific rules may be confusing and bring additional complexity. I think the rule we do not track coordinates after aggregations would be much simpler and easier to understand. If we adopt the above rule, I think the In [4]: da.argmin(dim='x') Out[4]: <xarray.DataArray (y: 3)> array([0, 1, 0]) Coordinates: * y (y) <U1 'a' 'b' 'c' In [3]: da.isel(x=da.argmin(dim='x')) Out[3]: <xarray.DataArray (y: 3)> array([0, 1, 2]) Coordinates: x (y) int64 1 2 1 * y (y) <U1 'a' 'b' 'c' ``` I think your logic would be useful even we do not track the coordinate. I would appreciate any feedback. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
338397633 | https://github.com/pydata/xarray/issues/1388#issuecomment-338397633 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDMzODM5NzYzMw== | fujiisoup 6815844 | 2017-10-21T13:51:04Z | 2017-10-21T13:51:04Z | MEMBER | I am thinking again how (We discussed the name for this new method in #1469 but here I just use For example with a three dimensional array with The above proposal for ii (and iii) is not quite clean, as if it is used as an argument of Any thoughts are welcome. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
309280411 | https://github.com/pydata/xarray/issues/1388#issuecomment-309280411 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDMwOTI4MDQxMQ== | fujiisoup 6815844 | 2017-06-18T14:18:40Z | 2017-06-19T12:56:03Z | MEMBER | I'm working to fix this and I would like to make some design decisions;
Edit:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
298256260 | https://github.com/pydata/xarray/issues/1388#issuecomment-298256260 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDI5ODI1NjI2MA== | shoyer 1217238 | 2017-04-30T20:50:49Z | 2017-04-30T20:50:49Z | MEMBER | I agree that The main downside of returning a tuple or dict from
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
297845435 | https://github.com/pydata/xarray/issues/1388#issuecomment-297845435 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDI5Nzg0NTQzNQ== | shoyer 1217238 | 2017-04-27T21:33:06Z | 2017-04-27T21:33:06Z | MEMBER | Agreed, the current implementation of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 |
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 3