issues: 333312849
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
333312849 | MDU6SXNzdWUzMzMzMTI4NDk= | 2237 | why time grouping doesn't preserve chunks | 1197350 | closed | 0 | 30 | 2018-06-18T15:12:38Z | 2022-05-15T02:44:06Z | 2022-05-15T02:38:30Z | MEMBER | Code Sample, a copy-pastable example if possibleI am continuing my quest to obtain more efficient time grouping for calculation of climatologies and climatological anomalies. I believe this is one of the major performance bottlenecks facing xarray users today. I have raised this in other issues (e.g. #1832), but I believe I have narrowed it down here to a more specific problem. The easiest way to summarize the problem is with an example. Consider the following dataset
One non-dimension coordinate ( Now let's do a trivial groupby operation on Problem descriptionWhen grouping over a non-contiguous variable ( Expected OutputWe would like to preserve the original chunk structure of Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/2237/reactions", "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |