-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Dask-friendly nan check in xr.corr() and xr.cov() #5284
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
b8d6daf
initial changes
AndrewILWilliams 227b622
Using map_blocks to lazily mask input arrays, following #4559
AndrewILWilliams 6619a6c
Adding lazy corr cov test with `raise_if_dask_computes`
AndrewILWilliams 637ab80
adding test for one da without nans
AndrewILWilliams fff4556
checking ordering of arrays doesnt matter
AndrewILWilliams 2756488
adjust inputs to test
AndrewILWilliams 58c441d
add test for array with no missing values
AndrewILWilliams a9bd723
added whatsnew
AndrewILWilliams 8f50b09
Merge branch 'master' into dask_corr_cov
AndrewILWilliams ccb5f67
fixing format issues
AndrewILWilliams File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AndrewWilliams3142 .
Unfortunately I don't think you can avoid this for dask arrays. Fundamentally
bool(dask_array)
will call compute. So this lineif not _are_there_nans
will call compute.I think the only solution here is to special case this optimization for non-dask DataArray, and always call
.where(valid_values)
for dask arrays but maybe someone else has an idea.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I guess you could stick the
in a helper function and
map_blocks
that.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, ok. Silly question but does it matter that
_are_there_nans
is a scalar reduction ofvalid_values
? Sovalid_values
is still left uncomputed. Would this help the bottleneck at all?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No because the program needs to know
valid_blocks.any()
to decide which branch of the if-else statement to execute. So it gets computed.