cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: FFTW 3.3.8: Advanced Real-to-real Transforms cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: cannam@167:
cannam@167:

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

cannam@167:
cannam@167:
cannam@167: cannam@167:

4.4.3 Advanced Real-to-real Transforms

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

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

cannam@167:

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

cannam@167: cannam@167: cannam@167: cannam@167: cannam@167: