forked from numpy/numpy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request numpy#25711 from mhvk/pocketfft-cpp
ENH: support float and longdouble in FFT using C++ pocketfft version
- Loading branch information
Showing
11 changed files
with
492 additions
and
2,744 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,11 @@ | ||
``out`` for `numpy.fft` | ||
----------------------- | ||
The various FFT routines in `numpy.fft` have gained an ``out`` | ||
argument that can be used for in-place calculations. | ||
`numpy.fft` support for different precisions and in-place calculations | ||
---------------------------------------------------------------------- | ||
|
||
The various FFT routines in `numpy.fft` now do their calculations natively in | ||
float, double, or long double precision, depending on the input precision, | ||
instead of always calculating in double precision. Hence, the calculation will | ||
now be less precise for single and more precise for long double precision. | ||
The data type of the output array will now be adjusted accordingly. | ||
|
||
Furthermore, all FFT routines have gained an ``out`` argument that can be used | ||
for in-place calculations. |
This file contains 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
Oops, something went wrong.