summaryrefslogtreecommitdiff
path: root/numpy/fft/helper.py
Commit message (Collapse)AuthorAgeFilesLines
* MAINT: Remove users of `numpy.compat.integer_types`Eric Wieser2020-08-311-2/+1
| | | | Some more Python 2 cleanup
* MAINT: Remove unnecessary 'from __future__ import ...' statementsJon Dufresne2020-01-031-2/+0
| | | | | As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior.
* replace fftpack with pocketfftMartin Reinecke2018-12-251-101/+0
|
* TST, DOC: enable refguide_checkTyler Reddy2018-12-141-3/+3
| | | | | | | | * 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
* ENH: set correct __module__ for objects in numpy's public APIStephan Hoyer2018-11-131-2/+3
| | | | | | | | | | | | | 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 :).
* MAINT: set preferred __module__ for numpy functionsStephan Hoyer2018-10-231-2/+2
|
* ENH: __array_function__ support for np.fft and np.linalg (#12117)Stephan Hoyer2018-10-121-0/+7
| | | | | | | | | | | | * 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
* Use dummy_threading on platforms that don't support threading (#10773)Michael Droettboom2018-03-201-1/+4
|
* ENH: Implement fft.fftshift/ifftshift with np.roll for improved performance ↵Gaspar Karm2018-01-161-26/+17
| | | | | | (#10073) See the PR for benchmarking information
* MAINT: replace len(x.shape) with x.ndimEric Wieser2017-02-241-2/+2
|
* Dropping dict like behavior and relying on explicit methods.Lion Krischer2016-06-081-27/+63
|
* BUG: Fix race condition with new FFT cacheLion Krischer2016-06-071-1/+2
| | | | | | 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-061-0/+62
| | | | | | | | 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.
* BUG: check axes and window length input for all integer typesChristoph Gohlke2013-09-071-5/+7
| | | On Python 2.7, the long type was excluded.
* DOC: change "Hermite" to "Hermitian", "though" to "although"endolith2013-08-291-1/+1
|
* DOC: add note clarifying why ifftshift is neededendolith2013-08-231-1/+2
|
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-6/+6
| | | | | | | Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long and will need to be broken at some point. OTOH, some lines were already too long and need to be broken at some point. Now seems as good a time as any to do this with open PRs at a minimum.
* STY: Giant whitespace cleanup.Charles Harris2013-08-181-6/+6
| | | | Now is as good a time as any with open PR's at a low.
* 2to3: Apply types fixer.Charles Harris2013-04-141-6/+7
| | | | | | | | | | | | | | | | | | | | Python 3 removes the builtin types from the types module. The types fixer replaces such references with the builtin types where possible and also takes care of some special cases: types.TypeNone <- type(None) types.NotImplementedType <- type(NotImplemented) types.EllipsisType <- type(Ellipsis) The only two tricky substitutions are types.StringType <- bytes types.LongType <- int These are fixed up to support both Python 3 and Python 2 code by importing the long and bytes types from numpy.compat. Closes #3240.
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Use absolute imports.Charles Harris2013-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3: Replace xrange by range and use list(range(...)) where neededCharles Harris2013-03-271-2/+2
| | | | | | | | | | | | | | | In python3 range is an iterator and `xrange` has been removed. This has two consequence for code: 1) Where a list is needed `list(range(...))` must be used. 2) `xrange` must be replaced by `range` Both of these changes also work in python2 and this patch makes both. There are three places fixed that do not need it, but I left them in so that the result would be `xrange` clean. Closes #3092
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+3
| | | | | | | | This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates.
* DOC: remove "the" from description, single backticks are for variables onlyendolith2012-11-261-2/+2
|
* DOC: Reword "Hermite symmetry", clarify units of sample spacingendolith2012-11-261-11/+15
|
* DOC: Fix length mistake in docstring (rfft length is n//2+1, not n)endolith2012-11-251-1/+1
|
* MAINT: Don't use assert to check variable typeendolith2012-11-181-2/+4
|
* DOC: Clarify size of odd-length FFTs, default `d` for fftfreq, and some PEP8 ↵endolith2012-10-131-9/+10
| | | | style fixes
* ENH: Add rfftfreq() for numpy's rfft(), which behaves differently from ↵endolith2012-10-131-1/+49
| | | | scipy's rfft()/rfftfreq().
* BUG: Make fftshift and ifftshift accept integer arguments for the axesCharles Harris2010-05-101-0/+5
| | | | | value. The functions now match their documentation. Fixes ticket #1182, patch from rgommers.
* 3K: fft: fix integer division in (i)fftshiftPauli Virtanen2010-02-201-2/+2
|
* Docstring update: fftPauli Virtanen2009-10-021-16/+57
|
* Import documentation from doc wiki (part 2, work-in-progress docstrings, but ↵Pauli Virtanen2008-10-281-11/+54
| | | | they are still an improvement)
* Try to speed up fftfreq a bit.Travis Oliphant2008-02-281-3/+10
|
* clean up unused imports and bad whitespaceTim Leslie2007-01-091-1/+1
|
* Optimize fftfreq.Stefan van der Walt2006-09-051-2/+2
|
* Many name-changes in oldnumeric. This may break some numpy code that was ↵Travis Oliphant2006-08-041-0/+66
using the oldnumeric interface.
View Lorry Controller Status