dask: cf.size#554
Merged
Merged
Conversation
sadielbartholomew
approved these changes
Jan 30, 2023
Member
sadielbartholomew
left a comment
There was a problem hiding this comment.
Thanks David for the useful context giving the motivations for this. I agree that:
creating our own little function was the path of least resistance :)
is the sensible way to handle this.
Perfect, please merge once one typo has been fixed.
|
|
||
|
|
||
| def size(a): | ||
| """Return the number of elements. |
Member
There was a problem hiding this comment.
+1 for documenting this by hand and not going with the blanket "This docstring was copied from numpy.size. Some inconsistencies with the cf version may exist." 😃
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replace
np.size(...)with the newcf.size(...), which is a basically a copy of the numpy function.The reason for doing this is that when dask arrays are passed to
np.sizethis happens:This is related to how Dask interacts with the numpy
__array_function__interface: https://github.com/dask/dask/blob/2022.12.1/dask/array/core.py#L1707-L1728. I haven't really looked at what is going on here, but what look I had led me to think that creating our own little function was the path of least resistance :). If this were to be something which could be "fixed" via Dask functionality, then great! But until such a time we are covered.Took the liberty of deleting some ancient redundant code from
field.pyat the same time.