-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance setting up a 2d fft, reverse and forward? #52
Comments
True that ffts lacks documentation, but 2d and higher ranks use common practice; rows are transformed using 1d transform followed by transpose and transform of cols using 1d transform followed by final transpose. The real data is stored as a row-major array of size n0 × n1 and the complex data is stored as a row-major array of size n0 × (n1/2 + 1). Row-major order is the standard C array storage order. You may find this helpful. But clearly we need to add proper examples and tests how-to use ffts for various problems. |
linkotec, Thank you very much for answering. I'm a rookie, so I'm unaware of know common practice. What you said is indeed helpful but I am now puzzled about the size of input and output buffers bc in issue #46 in January of this year. (#46) you said to csolorio:
and earlier in that same issue you wrote:
I am using input data that is 2d and have done it in row major order, and so I am using ffts_init_2d_real(). My width and height are 512 (a power of 2). But it seems there are several ways to calculate size of buffers including:
It's clear that some are just different ways of doing the same thing. However, sometimes 2 * is used, sometimes not. 2 * is used in #1, #4 and #7. I don't know when to use 2 * and when not to use it. |
Hey, trying hard to use this great fft library. Is there a short example of how to use ffts_init_2d_real() with ffts_execute? Only example is a 1d. And what I can glean from a couple of bug reports on use of ffts_init_2d_real() leaves me confused. Or should I use Stack Overflow?
The text was updated successfully, but these errors were encountered: