#ifndef USE_FFTW // FFTW now uses out of place transforms. memcpy( WorkData, &ChirpedData[CurrentSub], int(fftlen * sizeof(sah_complex)) ); #endif
LOL, Here's one in seti_analyze that disappears if going to FFTW, Code: [Select] #ifndef USE_FFTW // FFTW now uses out of place transforms. memcpy( WorkData, &ChirpedData[CurrentSub], int(fftlen * sizeof(sah_complex)) ); #endifI see a few of those.Another thought. Has anyone attempted to use that FFTW codelet generator given that only a small portion of fftw is used? I have played with OCAML before, didn't seem hard.[but it was long enough ago to have forgotten everything ]Jason
... #ifndef USE_FFTW // FFTW now uses out of place transforms. // Commenting out the mempy() // memcpy( WorkData, &ChirpedData[CurrentSub], int(fftlen * sizeof(sah_complex)) ); #endif ... // Now fix the source for out of place IPP call properly #if defined( USE_IPP ) ippsFFTInv_CToC_32fc( // ( Ipp32fc * ) WorkData, // changing from this source ( Ipp32fc * ) &ChirpedData[CurrentSub], // to direct source for out of place ( Ipp32fc * ) WorkData, // leave as same destination FftSpec[FftNum], FftBuf );
... The reversibility of a complete FFT is only needed during baseline smoothing. Joe
...What do you think about this in benchmark.cpp ?regards heinz
the yellow line was there....
yes very different linenumbers, I give the analyzeFuncs.cpp a new structure......I will have a look at benchmark again.... make a trigger for the case we use a zero fill.heinz