[SciPy-dev] Cleaning and fixing fft in scipy ?

Pearu Peterson pearu@cens.ioc...
Sat Apr 28 06:15:12 CDT 2007

On Sat, April 28, 2007 1:52 pm, David Cournapeau wrote:

> I think that I was not really clear in my former emails: I do not
> suggest a rewrite, but a 2 steps improvements:
>     - one which does not change anything to the code except its
> organization (one file for one fft API instead of the #ifdef)
>     - once the first step is done and considered acceptable by the scipy
> developers, I would like to improve fftw3, such as it is at least on par
> with fftw2: right now, for fftw3, the arrays are copied twice. I think
> fftw3 requires a more sophisticated caching scheme, because with fftw3
> you cannot use the same plan when the input/output are changed, at least
> with the basic API. For example, Octave is using such a scheme. Other
> implementations would be untouched.

I am ok with both steps. Let us know when the first step is complete
so that we can test that the interface is working for different backends.


More information about the Scipy-dev mailing list