issue_comments: 1162833362
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/6709#issuecomment-1162833362 | https://api.github.com/repos/pydata/xarray/issues/6709 | 1162833362 | IC_kwDOAMm_X85FT23S | 74916839 | 2022-06-22T08:54:18Z | 2022-06-22T09:10:04Z | NONE | Hi @TomNicholas I've reduced the original dataset to 11 chunks over the time dimension so that we can see the graph properly. I also replaced the .compute operation by a to_zarr(compute=False) because I don't know how to visualize xarray operations without generating a Delayed object (comments are welcomed on this point !) Anyway here are the files, first one is the graph where the means are built from dask.ones arrays Second one is the graph where the means are built from the same arrays but opened from a zarr store I am quite a newbie in dask graphs debug but everything seems ok in the second graph, apart from the open_dataset tasks that are linked to a parent task. Also, I noticed that Dask have fused the 'ones' operations in the first graph. Would it help if I generated another arrays with zeros instead ? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1277437106 |