| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The parameter name seem to have a typo in both those case and reference
axis (and not axes), this is likely due to copy-past as some other
functions in this modules use axes (when several indices are required),
but other also use `axis` and have the correct spelling.
From review it also seem like previous phrasing is unclear so update
all similar entries to reflect the new phrasing.
|
|\
| |
| | |
DOC: added examples section for rfft2 and irfft2 docstring
|
| |
| |
| |
| |
| | |
Update rfft2 example to conform to fft2 example and switch the irfft2
example to illustrate round-tripping.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
ENH: Add placeholder stubs for all sub-modules
|
| | | |
|
| |/ |
|
|/
|
|
| |
Some more Python 2 cleanup
|
|
|
|
|
|
| |
Adds sentence to the top of routines.fft.html explaining that scipy.fft
is a more comprehensive collection, per mailing list discussion
(http://numpy-discussion.10968.n7.nabble.com/Add-Chebyshev-cosine-transforms-implemented-via-FFTs-td48373.html#a48382)
|
|
|
|
| |
* DOC: Clarify input to irfft/irfft2/irfftn
* DOC: Update see also link with rfft
|
|\
| |
| | |
BUG: Remove non-threadsafe sigint handling from fft calculation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The fft calculation is the only point in our code where this function
is used. Allowing Ctrl+C, in FFT specifically used have more reasons,
since before pocketfft, some array-sizes could lead to very large
run-times.
Pocketfft fixed that issue, and now FFT is not really any slower,
faster, or memory hungry than any other NumPy operation so it feels
it does not need this handling. Rather, if we can find a better
solution, it should also be added to more functions.
The reason for removal is that it is not only unsafe while the
FFT is running (in theory). Multiple, threaded FFT run can easily
leave the signal handler in a bad state, causing crashes if Ctrl+C
(sigint) is given at any point after the call.
It would be possible to patch that over, by only resetting the
signal handler if we actually changed it (or even more complex
tricks), or possibly only using this technique when on the main
thread.
But, all of these solutions seem to complicate things, when the
main reason for why allowing sigint seems useful is gone with
pocketfft.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The kwarg option norm=inverse leads to scaling of the transforms
inverse (opposite) to that of the default option norm=None; i.e. the
forward transform is normalized with 1/n whereas the backward one
with 1. The fft routines and their tests have been modified to
reflect the changes; all tests have been passed successfully.
Closes #16126
* modified _unitary, fft & ifft and their tests; tests passed
* modified rfft & irfft and their tests; tests passed
* modified hfft & ihfft and all tests; all modifications are now done
* correction in ihfft; all 79 fft tests passed successfully
* undo unnecessary docstrings changes made in my previous commits
* use norm=forward kwarg value name
* Update numpy/fft/__init__.py
Co-authored-by: Leo Fang <leofang@bnl.gov>
* add code review suggestions
Co-authored-by: Leo Fang <leofang@bnl.gov>
* add default norm=None alias norm=backward
* streamline private normalization functions
* modify hermitian FFTs
* add review suggestions
Co-authored-by: Leo Fang <leofang@bnl.gov>
* add review suggestions v2 (dict as module const)
* make review suggestions v3
* Apply suggestions from code review
Co-authored-by: Leo Fang <leofang@bnl.gov>
|
| |
|
|
|
| |
Add missing closing brackets, script to generate the list in the PR gh-16051.
|
|
|
| |
AIX needs to be told to use large file support at all times. Fixes parts of gh-15801.
|
|
|
|
|
|
|
|
| |
There was an identical statement in both possible branches of
a conditional.
Moved statement out of conditional to eliminate one
repititious LOC
|
|
|
|
|
|
|
| |
* Cleanup unused imports (F401) of mostly standard Python modules,
or some internal but unlikely referenced modules
* Where internal imports are potentially used, mark with noqa
* Avoid redefinition of imports (F811)
|
| |
|
| |
|
|
|
|
|
|
|
| |
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.
Dropping the object is more idiomatic Python.
|
|\
| |
| | |
MAINT: Remove unnecessary 'from __future__ import ...' statements
|
| |
| |
| |
| |
| | |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
|/
|
|
|
| |
Dropping the support for python 2, the difference in module setup do not have to be accounted
for anymore. This removes the macros and ifdef's related to module setup code and python 2
support.
|
|
|
|
|
|
|
| |
* DOC: Note FFT type promotion
The NumPy FFT implementation will promote `float32` types to `float64` types. This may not be desired for some applications, but the SciPy implementation supports more data types.
Closes #14892
|
|
|
|
|
|
|
|
|
| |
Closes gh-14552
The Pocketfft author (mreineck) agreed on gh-14552 that Pocketfft can
simply fall under the NumPy license, no separate license file needed.
[ci skip]
|
| |
|
|
|
|
| |
These aren't public, and should have been added with underscores.
|
|
|
|
|
|
|
|
| |
* introduce inv_fct to avoid divisions by zero
* add comment describing the purpose of inv_fct
* inv_fct -> inv_norm
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Relaxed test_fft_with_order for float32.
Infinity norm round-off error of FFT is shown in
G.U. Ramos, "Roundoff Error Analyss of the Fast Fourier Transform,"
Mathematics of Computation, vol. 25, no. 116, Oct. 1971, p. 757
to be bounded by sqrt(N)*K*eps.
|
| |
|
|
|
|
|
| |
Test for ND transforms with axes for invariance of
permutation of axes.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
tweak and add test
better fix
fix
cleanup, additional test
fix test
|
|
|
|
|
|
| |
* as requested by review in gh-12634,
the vast majority of docstring matplotlib
imports can be simplified to a single line
|
|
|
|
|
|
|
| |
* there is no longer any usage of "agg"
backend switching in our docstrings because
this backend is already activated in
the refguide_check machinery
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* ported the refguide_check module from SciPy for usage
in NumPy docstring execution/ verification; added the
refguide_check run to Azure Mac OS CI
* adjusted NumPy docstrings such that refguide_check passes
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes GH-12271
Tests verify that everything in ``dir(numpy)`` either has ``__module__`` set to
``'numpy'``, or appears in an explicit whitelist of undocumented functions and
exported bulitins. These should eventually be documented or removed.
I also identified a handful of functions for which I had accidentally not setup
dispatch for with ``__array_function__`` before, because they were listed under
"ndarray methods" in ``_add_newdocs.py``. I guess that should be a lesson in
trusting code comments :).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ENH: __array_function__ support for np.fft and np.linalg
xref GH12028
* CLN: remove unnecessary dispatcher functions from np.linalg
* CLN: remove more unneeded dispatchers
* CLN: remove repeated dispatchers from np.linalg
|
| |
|
|
|
|
|
|
|
|
| |
unnecessary import dependencies
pytesttester is used by every single subpackage, so making it depend on np.testing just creates cyclic dependencies that can lead to circular imports
Relates to #11457
|