CHALLENGER: numpy_fft with a different rfft #13
Closed
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.
Tested numpy_fft but with a different rfft in which some computations are combined. See the changed files. For convenience, sharing it here as well:
Note that I wanted to set
niterto a large number, and therefore I decided to only check performance for a shorter range of p. So, that's why I setpminandpmaxto 6 and 15, respectively. I also did not considernjitas it slows down the total running time.