comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Correction: 2D FFt
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Correction: 2D FFt [message #7290 is a reply to message #7281] Tue, 22 October 1996 00:00 Go to previous messageGo to previous message
peter is currently offline  peter
Messages: 80
Registered: February 1994
Member
Walid Atia (atia@wam.umd.edu) wrote:
: Hi,

: I just realized that FFT(data,-1) takes the FFT of an array of up to 7
: dimensions. What confused me was that when I plotted, say, the FFT of a
: gaussian, I got values only near the sides. However, the FFT of a
: gaussian is a gaussian, so I thought that the FFT routine must not be
: working correctly for my array. Just in case anyone out there is
: interested, the problem lies in the way IDL stores the FFT data. The
: edges are taken as 0 frequency, rather than the more intuitively obvious
: center to be zero. A simple shift in the FFT'd image solves the
: problem, and yields the expected results. The code which illustrates
: this is:

<snip>

: Does anyone know of a more direct (and elegant) way of performing this
: transform? And why does IDL store the 2D transform this way--doesn't
: the usual 2D transform treat the center of the array as zero frequency,
: so as to get a symmetrical function given a symmetrical image?

The customary way to perform FFTs always places DC in element 0, not in
the middle. IDL follows this convention. You'll confuse more than a
few people if you adopt any other rule, so please don't!

Peter
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Finding the index of the median
Next Topic: A Nice (undocumented?) feature for PS plotting

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:40:38 PDT 2025

Total time taken to generate the page: 0.00768 seconds