summaryrefslogtreecommitdiff
path: root/numpy/fft
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #10775 from mdboom/return-errors-from-initEric Wieser2018-04-191-3/+6
|\ | | | | BUG: Return NULL from PyInit_* when exception is raised
| * Return NULL from PyInit_* when exception is raisedMichael Droettboom2018-03-301-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | I don't think this is documented anywhere, but I'm pretty sure module init functions should return NULL in order to communicate that an exception occurred during initialization (as is the standard Python/C API convention). It's clear from the CPython code [here](https://github.com/python/cpython/blob/master/Python/importdl.c#L162) that if you don't return NULL, the exception is swallowed and replaced with the message "initialization of %s raised unreported exception". Admittedly, this is only useful for people porting Numpy to new platforms where it is helpful to know where module initialization is failing, but it can't hurt.
* | MAINT: Remove all uses of run_module_suite.Charles Harris2018-04-062-11/+2
| | | | | | | | | | That function is nose specific and has not worked since `__init__` files were added to the tests directories.
* | TST: Update modules `test` to PytestTester.Charles Harris2018-04-041-2/+3
| | | | | | | | | | | | | | | | Numpy can now be tested using the standard `python -c"import numpy; numpy.test()"` construct.
* | MAINT: Remove "bench" from testing modules `__init__`s.Charles Harris2018-03-311-1/+0
| | | | | | | | | | The "bench" testing with the old bench files is no longer supported. These days we use `runtests.py` and `asv`.
* | Use dummy_threading on platforms that don't support threading (#10773)Michael Droettboom2018-03-201-1/+4
|/
* Merge pull request #10618 from eric-wieser/avoid-nontuple-indicesMarten van Kerkwijk2018-03-151-2/+2
|\ | | | | MAINT: Stop using non-tuple indices internally
| * MAINT: Stop using non-tuple indices internallyEric Wieser2018-02-161-2/+2
| | | | | | | | | | | | By not using this type of indexing, it becomes easier for subclasses to override indexing in a way that works correctly with numpy functions. These locations were found by deprecating the behavior in question, which is deliberately not part of this commit
* | BUG: Improving the accuracy of the FFT implementationNils Becker2018-02-201-46/+81
|/ | | | | | Previously, the numerical constants in the FFT code were not provided at full double precision which led to a loss of accuracy in the FFT operation. Additionally this commit improves the accuracy of the twiddle factor calculation by reducing the argument of exp(2j*pi*m/n) to the first octant before calling the library function. On average the commit lowers the remaining numerical error in the FFT by a factor of ten.
* ENH: Implement fft.fftshift/ifftshift with np.roll for improved performance ↵Gaspar Karm2018-01-162-34/+119
| | | | | | (#10073) See the PR for benchmarking information
* TST, MAINT: Add `__init__.py` files to tests directories.Charles Harris2017-08-061-0/+0
| | | | | | | | This allows pytest to run with duplicate test file names. Note that `python <path-to-test-file>` no longer works with this change, nor will a simple `pytest numpy`, because numpy is imported from the numpy repository. However, `python runtests.py` and `>>> numpy.test()` are still available.
* TST: Remove unittest dependencies in numpy/fft/tests.Charles Harris2017-07-242-22/+26
|
* MAINT: Rearrange files in numpy/testing module.Charles Harris2017-07-041-1/+1
| | | | | | | | | | | | | | | | | The aim here is to separate out the nose dependent files prior to adding pytest support. This could be done by adding new files to the general numpy/testing directory, but I felt that it was to have the relevant files separated out as it makes it easier to completely remove nose dependencies when needed. Many places were accessing submodules in numpy/testing directly, and in some cases incorrectly. That presented a backwards compatibility problem. The solution adapted here is to have "dummy" files whose contents will depend on whether of not pytest is active. That way the module looks the same as before from the outside. In the case of numpy itself, direct accesses have been fixed. Having proper `__all__` lists in the submodules helped in that.
* MAINT: Include the function name in all argument error messagesEric Wieser2017-03-281-6/+6
| | | | | | | Performed using the following regex, replacing with $0:$1. Some manual cleanup was then required. ^[a-z]+_(\w+)(?:(?!\}).*\n)+.*PyArg_ParseTuple(AndKeywords)?\(args[^"]+"[^:"]+(?=")
* MAINT: replace len(x.shape) with x.ndimEric Wieser2017-02-241-2/+2
|
* MAINT: Remove shebang from test modulesSami Salonen2017-01-151-1/+0
|
* BUG: correct norm='ortho' scaling for rfft when n != NoneGregory R. Lee2017-01-042-4/+28
| | | | closes #8444
* DOC: Correct documentation of hfft/ihfft.Charles Harris2016-11-041-28/+33
| | | | | | | | | Corrections to #7492. Correct the examples in the notes specifying the output length for the hfft. Also clean up the documentation a bit. [ci skip]
* Dropping dict like behavior and relying on explicit methods.Lion Krischer2016-06-083-100/+122
|
* BUG: Fix race condition with new FFT cacheLion Krischer2016-06-072-6/+14
| | | | | | There is now a lock around cache accesses ensuring thread safety. The size of a cache entry is now also calculated by summing over all arrays in the list.
* ENH: Changing FFT cache to a bounded LRU cacheLion Krischer2016-06-063-2/+152
| | | | | | | | Replaces the simple dictionary caches for the twiddle factors of numpy.fft to bounded LRU (least recently used) caches. The caches can thus no longer grow without bounds. See #7686.
* DOC: fix a number of reST formatting issues in docstrings.Ralf Gommers2016-02-131-8/+22
|
* BUG:Should fix astype cast bug in numpy.fft moduleTushar Gautam2016-01-191-1/+1
| | | | Closes #6693
* [TST] Refactor new raise_warnings logic for subpackage test suitesNathaniel J. Smith2015-12-301-3/+3
|
* DOC: Clarify documentation for np.fft.ifft.Charles Harris2015-12-181-8/+12
| | | | | The relationship between frequency and position in the input array is clarified.
* Fix #6798Phaiax2015-12-181-2/+4
|
* MAINT: Remove bento related files.Charles Harris2015-08-292-13/+0
| | | | | Numpy will no longer support the bento build system, so remove the associated files.
* Fix #2128 once again.Antony Lee2015-08-061-1/+1
| | | | Not sure why the error was still in the docs.
* ENH: Add a norm keyword and tests for fft transformsJoseph Martinot-Lagarde2015-06-213-43/+214
|
* MAINT: fft: np.asarray(...) -> array(...)alex2015-06-021-9/+8
|
* MAINT: in fft, make copying more explicitalex2015-05-291-7/+14
|
* MAINT: remove unnecessary helper functionalex2015-05-291-13/+9
|
* MAINT: explicit fft copyalex2015-05-221-14/+12
|
* MAINT: fftpack.c needs #define NPY_NO_DEPRECATED_API NPY_API_VERSION.Charles Harris2015-02-141-6/+3
| | | | This is because of the inclusion of numpy/ndarraytypes.h in b3121e8.
* BLD: fix include order of headers, otherwise AIX build fails. See gh-5474.Ralf Gommers2015-01-281-1/+1
|
* Merge pull request #5492 from grahamc/gotofail-malloc-ret-null-fftJulian Taylor2015-01-251-1/+4
|\ | | | | | | PyErr_NoMemory when PyArray_Zeros fails to initialize
| * BUG: PyErr_NoMemory when PyArray_Zeros fails to initializeGraham Christensen2015-01-251-1/+4
| |
* | BUG: Rename fft C functions to avoid name conflictRyan Nelson2014-12-043-34/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Resolves issue #565. The public fft functions defined in fftpack.c have name conflicts on certain systems, so the prefix "npy_" was added to these functions. Added NPY_VISIBILITY_HIDDEN to the public functions in both fftpack.h and fftpack.c. This required rearranging the includes at the beginning of fftpack_litemodule.c so that this macro was properly defined. In addition, Python.h and numpy/ndarraytypes.h were included in the fftpack.h. One function, rfftb1, was flagged as `static` as it was not exported in the header. Build and tests pass using both Python 2.7.8 and Python 3.4.2.
* | Merge pull request #5282 from larsmans/c-fixesJulian Taylor2014-11-171-20/+12
|\ \ | | | | | | MAINT: fft: cleanup in fftpack module
| * | MAINT: fft: cleanup in fftpack moduleLars Buitinck2014-11-161-20/+12
| | | | | | | | | | | | | | | | | | | | | * put string constants in const arrays * use static functions were possible * removed a stale comment * more consistent whitespace
* | | Merge pull request #5035 from juliantaylor/fft-testseberg2014-09-031-1/+1
|\ \ \ | |/ / |/| | TST: join fft threads before getting values
| * | TST: join fft threads before getting valuesJulian Taylor2014-09-031-1/+1
| |/ | | | | | | avoids timeouts on slow machines
* | STY: minor PEP8 fixups for numpy/fft.Charles Harris2014-07-313-4/+3
|/
* Merge pull request #4692 from juliantaylor/fft-interruptCharles Harris2014-05-291-12/+12
|\ | | | | BUG: fix crash when sending interrupt signal to fft functions
| * BUG: fix crash when sending interrupt signal to fft functionsJulian Taylor2014-05-091-12/+12
| | | | | | | | | | | | | | | | | | | | the SIGINT handling code must be in the GIL released section so the longjmp does not skip the retaking. This implies that the signal handlers must use thread local storage to avoid a crash when sending interrupt to threaded fft functions. Distribution of SIGINT to each threads must be handled by the application as only the master thread receives it Closes gh-4634
* | Docs: fix numpy.fft.fft2 exampleFrederik Rietdijk2014-05-241-5/+10
| | | | | | | | | | | | Fixes issue #4736 The example showed a call to np.fft.fft instead of np.fft.fft2.
* | TST: reduce memory usage of fft testJulian Taylor2014-05-161-3/+5
|/ | | | | tests should not use more than 500 MB of memory, this one uses more than a GB. Also it didn't join its threads.
* Make TestFFTThreadSafe tests Py3-compatibleAlex Stewart2014-05-061-7/+16
|
* Added regression tests for #4655Alex Stewart2014-05-061-1/+38
|
* Add comments to clarify cache handling in _raw_fftAlex Stewart2014-05-061-0/+8
|
View Lorry Controller Status