Why not support the FFTW 2 interface in FFTW 3?
FFTW 3 has semantics incompatible with earlier versions: its plans can only be used for a given stride, multiplicity, and other characteristics of the input and output arrays; these stronger semantics are necessary for performance reasons. Thus, it is impossible to efficiently emulate the older interface (whose plans can be used for any transform of the same size). We believe that it should be possible to upgrade most programs without any difficulty, however.
Related Questions
- How does SelfReliant support redundant network interfaces? What scheme is used and is there any requirement needed at the network interface/switch level to support this?
- If ESR positions are modelled around cost centres will this have to change in future to support the interface?
- Does the RVU Remote User Interface (RUI) support High Definition format resolutions?
