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