cannam@95: cannam@95: cannam@95: Advanced Real-data DFTs - FFTW 3.3.3 cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95: cannam@95:
cannam@95: cannam@95: cannam@95:

cannam@95: Next: , cannam@95: Previous: Advanced Complex DFTs, cannam@95: Up: Advanced Interface cannam@95:


cannam@95:
cannam@95: cannam@95:

4.4.2 Advanced Real-data DFTs

cannam@95: cannam@95:
     fftw_plan fftw_plan_many_dft_r2c(int rank, const int *n, int howmany,
cannam@95:                                       double *in, const int *inembed,
cannam@95:                                       int istride, int idist,
cannam@95:                                       fftw_complex *out, const int *onembed,
cannam@95:                                       int ostride, int odist,
cannam@95:                                       unsigned flags);
cannam@95:      fftw_plan fftw_plan_many_dft_c2r(int rank, const int *n, int howmany,
cannam@95:                                       fftw_complex *in, const int *inembed,
cannam@95:                                       int istride, int idist,
cannam@95:                                       double *out, const int *onembed,
cannam@95:                                       int ostride, int odist,
cannam@95:                                       unsigned flags);
cannam@95: 
cannam@95:

cannam@95: Like fftw_plan_many_dft, these two functions add howmany, cannam@95: nembed, stride, and dist parameters to the cannam@95: fftw_plan_dft_r2c and fftw_plan_dft_c2r functions, but cannam@95: otherwise behave the same as the basic interface. cannam@95: cannam@95:

The interpretation of howmany, stride, and dist are cannam@95: the same as for fftw_plan_many_dft, above. Note that the cannam@95: stride and dist for the real array are in units of cannam@95: double, and for the complex array are in units of cannam@95: fftw_complex. cannam@95: cannam@95:

If an nembed parameter is NULL, it is interpreted as what cannam@95: it would be in the basic interface, as described in Real-data DFT Array Format. That is, for the complex array the size is assumed to be cannam@95: the same as n, but with the last dimension cut roughly in half. cannam@95: For the real array, the size is assumed to be n if the transform cannam@95: is out-of-place, or n with the last dimension “padded” if the cannam@95: transform is in-place. cannam@95: cannam@95:

If an nembed parameter is non-NULL, it is interpreted as cannam@95: the physical size of the corresponding array, in row-major order, just cannam@95: as for fftw_plan_many_dft. In this case, each dimension of cannam@95: nembed should be >= what it would be in the basic cannam@95: interface (e.g. the halved or padded n). cannam@95: cannam@95:

Arrays n, inembed, and onembed are not used after cannam@95: this function returns. You can safely free or reuse them. cannam@95: cannam@95: cannam@95: cannam@95: