issue_comments: 362951129
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/1388#issuecomment-362951129 | https://api.github.com/repos/pydata/xarray/issues/1388 | 362951129 | MDEyOklzc3VlQ29tbWVudDM2Mjk1MTEyOQ== | 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 } |
224878728 |