Remove unneeded copying.#12
Merged
danielballan merged 3 commits intoFeb 7, 2020
Merged
Conversation
When algorithm operates by modifying the input array in place, it is good manners to make a copy first so that the function does not mutate user input. I am guessing that that was the motivation for the use of `copy()` here. However, as far as I can tell, this algorithm does not modify `signal` (or its alias `a`) in place. It reassigns the variable `a` in a loop, but does not actually modify the input array object. Therefore, we can remove this copying and increase the speed. Also, note that the call to `np.array` explicitly cast the input to a literal numpy array. By removing that from the code, we accept dask arrays and cupy arrays and allow them to flow through the algorithm via the NEP-18 numpy dispatch mechanism.
|
Sorry I was digging out old GitHub notifications from my inbox and just saw this. It'd be great to have some sort of NEP guarantee. If this works, #10 is likely no longer needed, and users could just do this? import cupy as cp
import autocorr
data = # a cupy array
g1, tau = autocorr.multitau(data) |
Draft
Member
Author
|
@leofang That's my hope! It doesn't quite work as is with sparse arrays, but it's close, and I think we can get there. See #14 for my work in progress on that. Likely it would be the same situation for cupy. It does work as is with dask, though, which is cool. I am going to self-merge this; @aryabhatt gave me the go-ahead on a call. |
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.
When algorithm operates by modifying the input array in place, it is
good manners to make a copy first so that the function does not mutate
user input. I am guessing that that was the motivation for the use of
copy()here.However, as far as I can tell, this algorithm does not modify
signal(or its alias
a) in place. It reassigns the variableain a loop,but does not actually modify the input array object.
Therefore, we can remove this copying and increase the speed. Also, note
that the call to
np.arrayexplicitly cast the input to a literal numpyarray. By removing that from the code, we accept dask arrays and cupy
arrays and sparse arrays and allow them to flow through the algorithm via the NEP-18 numpy
dispatch mechanism. (See this section of the numpy documentation,
written by me as it happens, for details.)
attn @leofang @aryabhatt