cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: FFTW 3.3.5: Advanced Real-to-real Transforms cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127:
cannam@127:

cannam@127: Previous: , Up: Advanced Interface   [Contents][Index]

cannam@127:
cannam@127:
cannam@127: cannam@127:

4.4.3 Advanced Real-to-real Transforms

cannam@127: cannam@127:
cannam@127: 
fftw_plan fftw_plan_many_r2r(int rank, const int *n, int howmany,
cannam@127:                              double *in, const int *inembed,
cannam@127:                              int istride, int idist,
cannam@127:                              double *out, const int *onembed,
cannam@127:                              int ostride, int odist,
cannam@127:                              const fftw_r2r_kind *kind, unsigned flags);
cannam@127:
cannam@127: cannam@127: cannam@127:

Like fftw_plan_many_dft, this functions adds howmany, cannam@127: nembed, stride, and dist parameters to the cannam@127: fftw_plan_r2r function, but otherwise behave the same as the cannam@127: basic interface. The interpretation of those additional parameters are cannam@127: the same as for fftw_plan_many_dft. (Of course, the cannam@127: stride and dist parameters are now in units of cannam@127: double, not fftw_complex.) cannam@127:

cannam@127:

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

cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: