-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix optimize for chunked DataArray #4432
Conversation
Previously we generated in invalidate Dask task graph, becuase the lines removed here dropped keys that were referenced elsewhere in the task graph. The original implementation had a comment indicating that this was to cull: https://github.com/pydata/xarray/blame/502a988ad5b87b9f3aeec3033bf55c71272e1053/xarray/core/variable.py#L384 Just spot-checking things, I think we're OK here though. Something like `dask.visualize(arr[[0]], optimize_graph=True)` indicates that we're OK. Closes pydata#3698
Thanks @TomAugspurger ! |
with the merge we have a test failure:
does anyone know why that happens? |
This reverts commit 9a8a62b.
Huh, I'm able to reproduce locally. Looking into it now. |
Might be best to proceed with #4434 for now. I'll need to give this a bit of thought. |
OK, as you wish, I'll merge if that passes. But your change did pass before the merge. Could it be a conflict (in functionality, not git) with recent changes on master? |
I'm not sure, but I don't think so. It's strange that it didn't fail on the
pull request.
…On Thu, Sep 17, 2020 at 8:51 PM Maximilian Roos ***@***.***> wrote:
Might be best to proceed with #4434
<#4434> for now. I'll need to give
this a bit of thought.
OK, as you wish, I'll merge if that passes.
But your change did pass before the merge. Could it be a conflict (in
functionality, not git) with recent changes on master?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4432 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKAOISNY5A5N2A44YR2ZMLSGK4JTANCNFSM4RQ6OP2Q>
.
|
Edit: sorry, you're right, the first commit should have also failed. Not sure why that happened, and we can't really check because the build logs were already deleted. |
…pagate-attrs * 'propagate-attrs' of github.com:dcherian/xarray: (22 commits) silence sphinx warnings about broken rst (pydata#4448) Xarray open_mfdataset with engine Zarr (pydata#4187) Fix release notes formatting (pydata#4443) fix typo in io.rst (pydata#4250) Fix typo (pydata#4181) Fix release notes typo New whatsnew section Add notes re doctests (pydata#4440) Fixed dask.optimize on datasets (pydata#4438) Release notes for 0.16.1 (pydata#4435) Small updates to How-to-release + lint (pydata#4436) Fix doctests (pydata#4439) add a ci for doctests (pydata#4437) preserve original dimension, coordinate and variable order in ``concat`` (pydata#4419) Fix for h5py deepcopy issues (pydata#4426) Keep the original ordering of the coordinates (pydata#4409) Clearer Vectorized Indexing example (pydata#4433) Revert "Fix optimize for chunked DataArray (pydata#4432)" (pydata#4434) Fix optimize for chunked DataArray (pydata#4432) fix doc dataarray to netcdf (pydata#4424) ...
Previously we generated in invalidate Dask task graph, becuase the lines
removed here dropped keys that were referenced elsewhere in the task
graph. The original implementation had a
comment indicating that this was to cull:
xarray/xarray/core/variable.py
Line 384 in 502a988
Just spot-checking things, I think we're OK here though. Something like
dask.visualize(arr[[0]], optimize_graph=True)
indicates that we're OK.isort . && black . && mypy . && flake8
whats-new.rst
api.rst