Separate function/class for FFT?
Opened this issue · 1 comments
MaxThevenet commented
Random late Friday thought: we could have a function for the FFT + metadata, if that's needed in multiple places.
rob-shalloo commented
Certainly I think separate functions for correctly scaling the axes of the FFT and clearly stating the convention used (in terms of pre-multipliers) would be very valuable to make the code more readable and would help prevent energy conservation issues when it comes to propagating the pulse.
What's your reasoning behind making it a class? Simply to store information like frequency axes etc in a convenient package? Could also be nice