summaryrefslogtreecommitdiff
path: root/numpy/fft
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Fix for #4655: Make fftpack._raw_fft threadsafeAlex Stewart2014-05-021-3/+3
|
* DOC: fixed small whitespace error in rfft notesArun Persaud2014-02-081-1/+1
|
* 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: Unlink non-variable 'm', use monospace insteadendolith2013-08-301-3/+3
|
* DOC: Remove parentheses around axisendolith2013-08-291-18/+18
|
* DOC: change "Hermite" to "Hermitian", "though" to "although"endolith2013-08-292-6/+6
|
* DOC: add note clarifying why ifftshift is neededendolith2013-08-231-1/+2
|
* DOC: Add examples, copy some text from rfft functions to clarify inputs and ↵endolith2013-08-221-12/+49
| | | | outputs
* DOC: hfft/ihfft description conflicts with itselfendolith2013-08-211-6/+6
| | | Says Hermite spectrum when it means signal
* STY: Giant comma spacing fixup.Charles Harris2013-08-184-17/+17
| | | | | | | 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-182-12/+12
| | | | 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-067-7/+7
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* Merge pull request #3178 from charris/2to3-apply-import-fixernjsmith2013-04-026-10/+10
|\ | | | | 2to3 apply import fixer
| * 2to3: Use absolute imports.Charles Harris2013-03-286-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Allow threads for FFT calculationsMartin Teichmann2013-04-011-0/+12
|/ | | | | This patch adds lines to release the Global Interpreter Lock while calculating an FFT with fftpack.
* 2to3: Replace xrange by range and use list(range(...)) where neededCharles Harris2013-03-272-4/+4
| | | | | | | | | | | | | | | 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
* DOC: Fix typo in fft docs (the indexing variable is 'm', not 'n').Maximilian Albert2013-03-061-1/+1
|
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-016-2/+13
| | | | | | | | 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.
* DEP: Remove scons related files and code.Charles Harris2013-01-133-25/+0
| | | | | | | | | This removes files and code supporting scons builds. After this change numpy will only support builds using distutils or bento. The removal of scons has been discussed on the list several times and a decision has been made that scons support is no longer needed. This was originally discussed for numpy 1.7 and because the distutils and bento methods are still available we are skipping the usual deprecation period.
* 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-262-13/+16
|
View Lorry Controller Status