Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: FFTW 3.3.5: Advanced Real-data DFTs Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: Chris@42:
Chris@42:

Chris@42: Next: , Previous: , Up: Advanced Interface   [Contents][Index]

Chris@42:
Chris@42:
Chris@42: Chris@42:

4.4.2 Advanced Real-data DFTs

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

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

Chris@42:

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

Chris@42:

If an nembed parameter is NULL, it is interpreted as what Chris@42: 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 Chris@42: the same as n, but with the last dimension cut roughly in half. Chris@42: For the real array, the size is assumed to be n if the transform Chris@42: is out-of-place, or n with the last dimension “padded” if the Chris@42: transform is in-place. Chris@42:

Chris@42:

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

Chris@42:

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

Chris@42:
Chris@42:
Chris@42:

Chris@42: Next: , Previous: , Up: Advanced Interface   [Contents][Index]

Chris@42:
Chris@42: Chris@42: Chris@42: Chris@42: Chris@42: