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 variablea
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 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