On thing that is often overlooked but should be emphasized is that the considered frequencies are fixed values while the phase shifts are continuous values. This creates tons of downstream problems
If your underlying signal is at frequency that is not a harmonic of the sampling length, then you get "ringing" and it's completely unclear how to deal with it (something something Bessel functions)
Actually using DFTs is a nightmare ..
- If I have several dominant frequencies (not multiples of the sampling rate) and I want to know them precisely, it's unclear how I can do that with an FFT
- If I know the frequency a priori and just want to know the phase shift.. also unclear
- If I have missing values.. how do i fill the gaps to distort the resulting spectrum as little as possible?
- If I have samples that are not equally spaced, how am I supposed to deal with that?
- If my measurements have errors, how do I propagate errors through the FFT to my results?
So outside of audio where you control the fixed sample rate and the frequencies are all much lower than the sample rate... it's really hard to use. I tried to use it for a research project and while the results looked cool.. I just wasn't able to backup my math in a convincing way (though it's been a few years so I should try again with ChatGPT's hand-holding)
I recommend people poke around this webpage to get a taste of what a complicated scary monster you're dealing with
FFT/DFT is not precise if you do not have the exact harmonic in you signal. If you are also (or only) interested in phases you might use a maximum likelihood estimator (which brings other problems though).
And as the previous answer said: compressed sensing (or compressive sensing) can help as well for some non-standard cases.
A while back I looked at matching pursuit. At first it seemed very complicated, but after staring at it a bit realized it's simple.
- Start with a list of basis functions and your signal.
- Go through the list and find the basis function that best correlates with the signal. This gives you a basis function and a coefficient.
- Subtract out the basis function (scaled by the coefficient) from your signal, and then repeat with this new residual signal.
The Fourier transform is similar using sine wave basis functions.
The key that makes this work in situations where the Nyquist theorem says we don't have a high enough sampling rate is ensuring our sampling (possibly random) is un-correlated with the basis functions and our basis functions are good approximations for the signal. That lowers the likelihood that our basis functions correlating well with our samples is by chance and raises likelihood it correlates well with the actual signal.
You can use single bin DFTs and not FFTs? Basically use precomputed twiddles for a specific frequency. FFT is only fast because it reuses operation across multiple frequencies, but if you need a specific frequency instead of the whole spectrum, then a single-bin DFT makese sense, right?
Somewhat related field, compressive sensing, attempts to answer some of those questions (particularly missing data, uneven sampling and errors) using a L1 minimisation technique.
That was actually fantastic. The professor is quite goofy, but he really goes over everything from first principles and goes through a real example - constructing a solution without any cheating :))
I was a bit bummed out there weren't a lot of Compressed Sensing libraries around, but it seems you just need a "convex optimization" routine (aka linear programming). And these seem to exist in every language
I'll try to play around with this!
Thank you so much
From the video tutorial is seems relatively straightforward. I guess the basis selection is a fundamental issue that will be problem-specific.
I will have to try it with some concrete examples. The first question I have is, will it still work if you have a lot of high frequency noise? In the cases I'm thinking either there is measurement noise or just other jitter. So while the lower frequencies are sparse but I guess the higher frequencies not so much. I can't bandpass the data b/c it's got lots of holes or it's irregularly spaced.
This was my first exposure to the Fourier transfer. I also highly recommend this book. It was recommended to me by the head of the math department at university.
I would just suggest the author to replace the sentence “99% of the time, it refers to motion in one dimension” with “most of the time” since this is a mathematical article and there’s no need to use specific numbers when they don’t reflect actual data.
If you're dealing with computer graphics, audio, or data analysis, I highly recommend learning Fourier transforms, because they explain a whole lot of things that are otherwise mysterious.
If anyone wants to learn about the 2D DFT, the best explanation I've ever read was the relevant chapter in Digital Image Processing by Nick Efford.
If anyone wants to see my favorite application of the 2D DFT, I made a video of how the DFT is used to remove rainbows in manga on Kaleido 3 color eink on Kobo Colour:
In the video you show a 2D mask to blur diagonal lines. How is that mask applied to the DFT? Is the mask also converted to a DFT and the two signals get combined?
I've actually found the opposite, it's easier to conceptually understand the continuous FT, then analyze the DTFT, DFT, and Fourier Series as special cases of applying a {periodic summation, discrete sampling} operator before the FT.
I have not read the whole article. But, what is shown at the beginning is not the Fourier Transform, it is the Discrete Fourier Transform (DFT).
Though the DFT can be implemented efficiently using the Fast Fourier Transform (FFT) algorithm, the DFT is far from being the best estimator for frequencies contained in a signal. Other estimators (like Maximum Likelihood [ML], [Root-]MUSIC, or ESPRIT) are in general far more accurate - at the cost of higher computational effort.
The FFT is still easy to use, and it you want a higher frequency resolution (not higher max frequency), you can zero pad your signal and get higher frequency resolution.
Zero-padding gives you a smoother curve, i.e., more points to look at. But it does not add new peaks. So, if you have two very close frequencies that produce a single peak in the DFT (w/o zero-padding), you would not get two peaks after zero-padding. In the field, were I work, resolution is understood as the minimum distance between two frequencies such that you are able to detect them individually (and not as a single frequency).
Zero-padding helps you to find the true position (frequency) of a peak in the DFT-spectrum. So, your frequency estimates can get better.
However, the peaks of a DFT are the summits of hills that are usually much wider than compared to other techniques (like Capon or MUSIC) whose spectra tend to have much narrower hills. Zero-padding does not increase the sharpness of these hills (does not make them narrower).
Likewise the DFT tends to be more noisy in the frequency domain compared to other techniques which could lead to false detections (e.g. with a CFAR variant).
Statistical algorithms always make more concrete assumptions of the signal. DFT / Fourier transforms are great as they are a direct mathematical operation, that maps neatly to (basic) equations. There's a lot you can do, and easily grok, with FTs. Once you get statistical, a lot of things are harder :)
If you want pure performance, and understand the underlying statistical processes, then sure I totally agree with you.
I'd never thought about it in this way before but the idea of writing a number as a decimal (or other) string of numerals, bears some resemblance to a Fourier transform.
Think of the components of a written number: ones, tens, hundreds etc which have a repeating pattern. Digits are inherently periodic. Not too far from periodic basis functions.
Both involve breaking something down into periodic components, and reversing the process by adding up the components.
The Fourier transform predates functional analysis by a century. I don't see the point in downplaying its significance just because 'duh it's simply a unitary linear operator on L2'.
The Fourier Transform isn't even Fourier's deepest insight. Unless we're now ranking scientific discoveries based on whether or not they get a post every weekend on HN.
The FFT is nifty but that's FINO. The Google boys also had a few O(N^2) to O(N log N) moments. Those seemed to move the needle a bit as well.
But even if we restrict to "things that made Nano Banana Pro possible" Shannon and Turing leapfrog Fourier.
It's really getting in the way of all the daily AI opinion pieces I come here to read.
More seriously, there are tens of thousands of people who come to HN. If Fourier stuff gets upvoted, it's because people find it informative. I happen to know the theory, but I wouldn't gatekeep.
My favorite application of the Fourier transform is converting convolution into pointwise multiplication. This is used to speed up multiple sequence alignment in bioinformatics.
It is more about the duality between the amplitude and frequency spaces and conversion between them. A bit similar to Hadamard gate for transforming a quantum state from computational basis to diagonal basis.
This is great! I would love to see this method extended to the full Pasterski–Strominger–Zhiboedov (PSZ) triangle, where Fourier transforms are the binding relationships tying together soft theorems and memory effects. Such an extended guide would be a powerful interaction encompassing also vacuum transitions and Ward's identities. A "smoothie" combining the theory of relativity, quantum field theory and quantum gravity might make those subjects more accessible.
I've decided math isn't my thing. The first part of the article I couldn't stop thinking "how the hell would you construct a banana filter?" And the entire smoothie metaphor seemed to describe nothing at all.
Then there was something about circles and why do some people call them some other silly thing?
So far, so utterly meaningless, as far as I could tell. just seemed like meaningless babble to make even a kindergartner feel comfortable with the article, but it didn't seem to have communicated much of anything, really.
Then there were circles. Some of them were moving, one of them had a sinus wave next to it and some balls were tracing both in sync, indicating which part of the sinus wave equalled which part of the circle I guess?
I understood none of it.
I asked chat gpt to explain to me, i think it has read this article cause it used the smoothie analogy as well. I still don't understand what that analogy is meant to mean.
Then finally I found this:
If someone plays a piano chord, you hear one sound.
But that sound is actually made of multiple notes (multiple frequencies).
The Fourier Transform is the tool that figures out:
which notes (frequencies) are present, and how loud each one is
The piano analogy is incomplete. First, of all, a piano constructs sounds by combining multiple string sounds in a unique manner. But the idea behind transforms (Fourier being a particular case) is that you can take a function (“sound”) that isn’t necessarily produced by combining components and you can still decompose it into a sum of components. This decomposition is not unique in the general case as there are many different transforms yielding different results. However, from the mathematical (and i believe, quantum mechanical) standpoint, there is full equivalence between the original function and its transforms.
The other important point is that Fourier doesn’t really give you frequency and loudness. It gives you complex numbers that can be used to estimate the loudness of different frequencies. But the complex nature of the transform is somewhat more complex than that (accidental pun).
A fun fact. The Heisenberg uncertainty principle can be viewed as the direct consequence of the nature of the Fourier transform. In other words, it is not an unexplained natural wonder but rather a mathematical inevitability. I only wish we could say the same about the rest of quantum theory!
All analogies are incomplete. It's kinda inherent in the definition of the word.
But it is a lovely, real-world and commonly understood example of how harmonics can work, and thus a nice baby-step into the idea of spectral analysis.
Yes, I could understand almost all of this actually! Thanks for explaining Fourier so well!
I really don't have any mathematics in my background, so you lost me towards the very end when the actual math came in, but I can't fault your Fourier explanation for not also explaining imaginary numbers: even I can see they're out of scope for this post!
Imaginary numbers are strange, basically i * i = -1. So it's a square root of negative one. It's imaginary because well, you need some imagination to come to terms with this. But they are useful to show things on a 2d plane, one axis is the real numbers -1 to 1, and the other -i to i. And then multiplying by number i will rotate in circles: i × i = -1, -1 × i = -i, -i × i = 1, 1 × i = i. And then there is this wonderful property that e ^ iπ = -1, which somehow combines the euler constant, number pi and the imaginary number, and it somehow works. And then also the related formula e^ix=cosx+i sinx, and so to rotate by x you just multiply with e^ix, where x = 2π × frequency. It somehow all fits in neatly, even though none of it is essential for the mechanism described. At least that's my uneducated understanding (my math background is also not that great, that's why I tried to explain this to myself with a more intuition based approach).
Hmm.. Imaginary numbers are indeed a bit confusing.
I'm trying to imagine a 2d surface where the X-axis coordinates are all the real numbers, and the y axis are all the imaginary numbers. That makes them orthogonal, and that seemed to add up with your explanation, up until ixi=-1.
The only way I can get that to add up is if I instead imagine a arbitrary coordinate system, where x and y are not necessarily perpendicular, and i describes the angle between x and y.
I've only just finished my first cup of coffee for the day, so I haven't quite decided yet if that makes any sense whatsoever, but it's the only way I can intuit about it that includes a circular motion like the one you describe..
In this case you could almost describe i as the square root of 180°, which... Yeah it's kinda weird...
I think so, it's called the complex plane. A complex number has a real and an imaginary component a+bi, so like a vector. The amount of each gives you the coordinates on the plane (a or b can be zero as well on the axes).
I had a chat with gpt to try and clear out some details. It seems that one is supposed to think of real and imaginary as a vector. The rotation part comes in when the imaginary numbers is used as an exponent to the real, in which case you're no longer saying "3 left, two right" but "4 units from origin, at an angle of (imaginary number)"
of course, the math here doesn't work out as using degrees or any other unit of rotation a normal person is used to, but instead, some other unit of rotation I haven't quite wrapped my head around yet (what the hell does atan2(b,a) mean? Is atan(a,b) deprecated or what? ) I didn't know namespace collisions were a thing mathematicians worried about, they should just release maths 2.0 and be rid of the legacy atan at this point!
I think it's because the normal atan receives one argument, eg atan(y/x) and then sometimes you can't divide by zero, and it can’t distinguish quadrants (because we loose info on the sign of Y-coordinate and the X-coordinate). atan2 takes 2 params and knows the signs so it can understand the quadrants and also handle divide by zero. I now realize that the name atan2 probably refers to 2 parameters.
On thing that is often overlooked but should be emphasized is that the considered frequencies are fixed values while the phase shifts are continuous values. This creates tons of downstream problems
If your underlying signal is at frequency that is not a harmonic of the sampling length, then you get "ringing" and it's completely unclear how to deal with it (something something Bessel functions)
Actually using DFTs is a nightmare ..
- If I have several dominant frequencies (not multiples of the sampling rate) and I want to know them precisely, it's unclear how I can do that with an FFT
- If I know the frequency a priori and just want to know the phase shift.. also unclear
- If I have missing values.. how do i fill the gaps to distort the resulting spectrum as little as possible?
- If I have samples that are not equally spaced, how am I supposed to deal with that?
- If my measurements have errors, how do I propagate errors through the FFT to my results?
So outside of audio where you control the fixed sample rate and the frequencies are all much lower than the sample rate... it's really hard to use. I tried to use it for a research project and while the results looked cool.. I just wasn't able to backup my math in a convincing way (though it's been a few years so I should try again with ChatGPT's hand-holding)
I recommend people poke around this webpage to get a taste of what a complicated scary monster you're dealing with
https://ccrma.stanford.edu/~jos/sasp/sasp.html
FFT/DFT is not precise if you do not have the exact harmonic in you signal. If you are also (or only) interested in phases you might use a maximum likelihood estimator (which brings other problems though).
And as the previous answer said: compressed sensing (or compressive sensing) can help as well for some non-standard cases.
Do you have any good reference for compressed sensing?
The high level description on wikipedia seems very compelling.. And would you say it'd be a huge task to really grok it?
A while back I looked at matching pursuit. At first it seemed very complicated, but after staring at it a bit realized it's simple.
- Start with a list of basis functions and your signal.
- Go through the list and find the basis function that best correlates with the signal. This gives you a basis function and a coefficient.
- Subtract out the basis function (scaled by the coefficient) from your signal, and then repeat with this new residual signal.
The Fourier transform is similar using sine wave basis functions.
The key that makes this work in situations where the Nyquist theorem says we don't have a high enough sampling rate is ensuring our sampling (possibly random) is un-correlated with the basis functions and our basis functions are good approximations for the signal. That lowers the likelihood that our basis functions correlating well with our samples is by chance and raises likelihood it correlates well with the actual signal.
Article by Terrence Tao: https://terrytao.wordpress.com/2007/04/13/compressed-sensing...
Paper by Stan Osher et al: https://arxiv.org/abs/1104.0262
You can use single bin DFTs and not FFTs? Basically use precomputed twiddles for a specific frequency. FFT is only fast because it reuses operation across multiple frequencies, but if you need a specific frequency instead of the whole spectrum, then a single-bin DFT makese sense, right?
https://github.com/dsego/strobe-tuner/blob/main/core/dft.odi...
Somewhat related field, compressive sensing, attempts to answer some of those questions (particularly missing data, uneven sampling and errors) using a L1 minimisation technique.
Can you recommend where to learn more about it? It looks like what I should be looking at.. hopefully not a rabbit hole :))
Here is a good lecture on this subject:
https://www.youtube.com/watch?v=rt5mMEmZHfs
That was actually fantastic. The professor is quite goofy, but he really goes over everything from first principles and goes through a real example - constructing a solution without any cheating :))
I was a bit bummed out there weren't a lot of Compressed Sensing libraries around, but it seems you just need a "convex optimization" routine (aka linear programming). And these seem to exist in every language
I'll try to play around with this! Thank you so much
It's a fascinating topic and i'm still trying to get my head around some of the concepts.
Have fun on your discovery journey.
Are there any gotchas you've come across?
From the video tutorial is seems relatively straightforward. I guess the basis selection is a fundamental issue that will be problem-specific.
I will have to try it with some concrete examples. The first question I have is, will it still work if you have a lot of high frequency noise? In the cases I'm thinking either there is measurement noise or just other jitter. So while the lower frequencies are sparse but I guess the higher frequencies not so much. I can't bandpass the data b/c it's got lots of holes or it's irregularly spaced.
Maybe it'll still work though!
The absolute best teaching of the Fourier transform I've ever encountered is the extremely bizarre book "Who is Fourier?"
https://www.amazon.com/Who-Fourier-Mathematical-Transnationa...
This was my first exposure to the Fourier transfer. I also highly recommend this book. It was recommended to me by the head of the math department at university.
If you're only interested in the gist of the concept and how it can be applied to compression, without the mathematical rigor, here is my go to: https://bertolami.com/index.php?engine=blog&content=posts&de...
Brilliant!
I would just suggest the author to replace the sentence “99% of the time, it refers to motion in one dimension” with “most of the time” since this is a mathematical article and there’s no need to use specific numbers when they don’t reflect actual data.
It's quite interesting that our ears implement a better-than-Fourier-like algorithm internally: https://arxiv.org/pdf/1208.4611
Article on how this might work (nonlinearity)
https://jontalle.web.engr.illinois.edu/Public/AllenSpeechPro...
Note the two electric circuit models figs 3.2 & 3.8
If you're dealing with computer graphics, audio, or data analysis, I highly recommend learning Fourier transforms, because they explain a whole lot of things that are otherwise mysterious.
If anyone wants to learn about the 2D DFT, the best explanation I've ever read was the relevant chapter in Digital Image Processing by Nick Efford.
If anyone wants to see my favorite application of the 2D DFT, I made a video of how the DFT is used to remove rainbows in manga on Kaleido 3 color eink on Kobo Colour:
https://youtu.be/Dw2HTJCGMhw?si=J6dUYOj2IRX1nPRF
In the video you show a 2D mask to blur diagonal lines. How is that mask applied to the DFT? Is the mask also converted to a DFT and the two signals get combined?
Just remove anything under the mask basically, similar to a low pass filter.
My only quibble is that the article is about the discrete Fourier transform.
It’s usually easier to explain the dft. and easier to do a periodic function than a totally arbitrary sequence.
I've actually found the opposite, it's easier to conceptually understand the continuous FT, then analyze the DTFT, DFT, and Fourier Series as special cases of applying a {periodic summation, discrete sampling} operator before the FT.
I have not read the whole article. But, what is shown at the beginning is not the Fourier Transform, it is the Discrete Fourier Transform (DFT).
Though the DFT can be implemented efficiently using the Fast Fourier Transform (FFT) algorithm, the DFT is far from being the best estimator for frequencies contained in a signal. Other estimators (like Maximum Likelihood [ML], [Root-]MUSIC, or ESPRIT) are in general far more accurate - at the cost of higher computational effort.
Can you provide more details please?
The FFT is still easy to use, and it you want a higher frequency resolution (not higher max frequency), you can zero pad your signal and get higher frequency resolution.
Zero-padding gives you a smoother curve, i.e., more points to look at. But it does not add new peaks. So, if you have two very close frequencies that produce a single peak in the DFT (w/o zero-padding), you would not get two peaks after zero-padding. In the field, were I work, resolution is understood as the minimum distance between two frequencies such that you are able to detect them individually (and not as a single frequency).
Zero-padding helps you to find the true position (frequency) of a peak in the DFT-spectrum. So, your frequency estimates can get better. However, the peaks of a DFT are the summits of hills that are usually much wider than compared to other techniques (like Capon or MUSIC) whose spectra tend to have much narrower hills. Zero-padding does not increase the sharpness of these hills (does not make them narrower). Likewise the DFT tends to be more noisy in the frequency domain compared to other techniques which could lead to false detections (e.g. with a CFAR variant).
Thanks for clarifying :)!
Not a particularly fair comparison, the DFT is a non-statistical operation.
Why do you think, that it is not fair?
You can even use these algorithms with a single snapshot (spatial smoothing).
Statistical algorithms always make more concrete assumptions of the signal. DFT / Fourier transforms are great as they are a direct mathematical operation, that maps neatly to (basic) equations. There's a lot you can do, and easily grok, with FTs. Once you get statistical, a lot of things are harder :)
If you want pure performance, and understand the underlying statistical processes, then sure I totally agree with you.
I'd never thought about it in this way before but the idea of writing a number as a decimal (or other) string of numerals, bears some resemblance to a Fourier transform.
Think of the components of a written number: ones, tens, hundreds etc which have a repeating pattern. Digits are inherently periodic. Not too far from periodic basis functions.
Both involve breaking something down into periodic components, and reversing the process by adding up the components.
Clever, but only really appropriate for the most significant digit.
The one's digit gives info about parity (odd/even), but nothing else.
This is the best content on this topic - a 2023 video by Reducible: https://www.youtube.com/watch?v=yYEMxqreA10
>The Fourier Transform is one of deepest insights ever made.
No, it is not. In fact it is quite a superficial example of a much deeper theory, behind functions, their approximations and their representations.
The Fourier transform predates functional analysis by a century. I don't see the point in downplaying its significance just because 'duh it's simply a unitary linear operator on L2'.
But is it the deepest insights ever made?
The Fourier Transform isn't even Fourier's deepest insight. Unless we're now ranking scientific discoveries based on whether or not they get a post every weekend on HN.
The FFT is nifty but that's FINO. The Google boys also had a few O(N^2) to O(N log N) moments. Those seemed to move the needle a bit as well.
But even if we restrict to "things that made Nano Banana Pro possible" Shannon and Turing leapfrog Fourier.
>Unless we're now ranking scientific discoveries based on whether or not they get a post every weekend on HN.
Glad I'm not the only one who noticed there is a weekly (or more) post on what Fourier transform is.
It's really getting in the way of all the daily AI opinion pieces I come here to read.
More seriously, there are tens of thousands of people who come to HN. If Fourier stuff gets upvoted, it's because people find it informative. I happen to know the theory, but I wouldn't gatekeep.
My favorite application of the Fourier transform is converting convolution into pointwise multiplication. This is used to speed up multiple sequence alignment in bioinformatics.
What is the bioinformatic application? Could you point me towards some programs that use this?
I was thinking about mafft in particular. You should know though that there are many different MSA tools out there.
It is more about the duality between the amplitude and frequency spaces and conversion between them. A bit similar to Hadamard gate for transforming a quantum state from computational basis to diagonal basis.
This is great! I would love to see this method extended to the full Pasterski–Strominger–Zhiboedov (PSZ) triangle, where Fourier transforms are the binding relationships tying together soft theorems and memory effects. Such an extended guide would be a powerful interaction encompassing also vacuum transitions and Ward's identities. A "smoothie" combining the theory of relativity, quantum field theory and quantum gravity might make those subjects more accessible.
Past comments: https://news.ycombinator.com/item?id=38652794
I've decided math isn't my thing. The first part of the article I couldn't stop thinking "how the hell would you construct a banana filter?" And the entire smoothie metaphor seemed to describe nothing at all.
Then there was something about circles and why do some people call them some other silly thing?
So far, so utterly meaningless, as far as I could tell. just seemed like meaningless babble to make even a kindergartner feel comfortable with the article, but it didn't seem to have communicated much of anything, really.
Then there were circles. Some of them were moving, one of them had a sinus wave next to it and some balls were tracing both in sync, indicating which part of the sinus wave equalled which part of the circle I guess?
I understood none of it.
I asked chat gpt to explain to me, i think it has read this article cause it used the smoothie analogy as well. I still don't understand what that analogy is meant to mean.
Then finally I found this: If someone plays a piano chord, you hear one sound. But that sound is actually made of multiple notes (multiple frequencies).
The Fourier Transform is the tool that figures out:
which notes (frequencies) are present, and how loud each one is
That, finally, makes sense.
The piano analogy is incomplete. First, of all, a piano constructs sounds by combining multiple string sounds in a unique manner. But the idea behind transforms (Fourier being a particular case) is that you can take a function (“sound”) that isn’t necessarily produced by combining components and you can still decompose it into a sum of components. This decomposition is not unique in the general case as there are many different transforms yielding different results. However, from the mathematical (and i believe, quantum mechanical) standpoint, there is full equivalence between the original function and its transforms.
The other important point is that Fourier doesn’t really give you frequency and loudness. It gives you complex numbers that can be used to estimate the loudness of different frequencies. But the complex nature of the transform is somewhat more complex than that (accidental pun).
A fun fact. The Heisenberg uncertainty principle can be viewed as the direct consequence of the nature of the Fourier transform. In other words, it is not an unexplained natural wonder but rather a mathematical inevitability. I only wish we could say the same about the rest of quantum theory!
All analogies are incomplete. It's kinda inherent in the definition of the word.
But it is a lovely, real-world and commonly understood example of how harmonics can work, and thus a nice baby-step into the idea of spectral analysis.
I wonder if my approach would help with your understanding?
https://dsego.github.io/demystifying-fourier/
Yes, I could understand almost all of this actually! Thanks for explaining Fourier so well!
I really don't have any mathematics in my background, so you lost me towards the very end when the actual math came in, but I can't fault your Fourier explanation for not also explaining imaginary numbers: even I can see they're out of scope for this post!
Imaginary numbers are strange, basically i * i = -1. So it's a square root of negative one. It's imaginary because well, you need some imagination to come to terms with this. But they are useful to show things on a 2d plane, one axis is the real numbers -1 to 1, and the other -i to i. And then multiplying by number i will rotate in circles: i × i = -1, -1 × i = -i, -i × i = 1, 1 × i = i. And then there is this wonderful property that e ^ iπ = -1, which somehow combines the euler constant, number pi and the imaginary number, and it somehow works. And then also the related formula e^ix=cosx+i sinx, and so to rotate by x you just multiply with e^ix, where x = 2π × frequency. It somehow all fits in neatly, even though none of it is essential for the mechanism described. At least that's my uneducated understanding (my math background is also not that great, that's why I tried to explain this to myself with a more intuition based approach).
Hmm.. Imaginary numbers are indeed a bit confusing.
I'm trying to imagine a 2d surface where the X-axis coordinates are all the real numbers, and the y axis are all the imaginary numbers. That makes them orthogonal, and that seemed to add up with your explanation, up until ixi=-1.
The only way I can get that to add up is if I instead imagine a arbitrary coordinate system, where x and y are not necessarily perpendicular, and i describes the angle between x and y.
I've only just finished my first cup of coffee for the day, so I haven't quite decided yet if that makes any sense whatsoever, but it's the only way I can intuit about it that includes a circular motion like the one you describe..
In this case you could almost describe i as the square root of 180°, which... Yeah it's kinda weird...
Am I still on the right track?
I think so, it's called the complex plane. A complex number has a real and an imaginary component a+bi, so like a vector. The amount of each gives you the coordinates on the plane (a or b can be zero as well on the axes).
I had a chat with gpt to try and clear out some details. It seems that one is supposed to think of real and imaginary as a vector. The rotation part comes in when the imaginary numbers is used as an exponent to the real, in which case you're no longer saying "3 left, two right" but "4 units from origin, at an angle of (imaginary number)"
of course, the math here doesn't work out as using degrees or any other unit of rotation a normal person is used to, but instead, some other unit of rotation I haven't quite wrapped my head around yet (what the hell does atan2(b,a) mean? Is atan(a,b) deprecated or what? ) I didn't know namespace collisions were a thing mathematicians worried about, they should just release maths 2.0 and be rid of the legacy atan at this point!
I think it's because the normal atan receives one argument, eg atan(y/x) and then sometimes you can't divide by zero, and it can’t distinguish quadrants (because we loose info on the sign of Y-coordinate and the X-coordinate). atan2 takes 2 params and knows the signs so it can understand the quadrants and also handle divide by zero. I now realize that the name atan2 probably refers to 2 parameters.
*lose, not loose
Will I ever be able to learn the Fourier transform?
Yes! Step 1 is forgetting about the name so it doesn't feel as daunting.
Disclaimer: I've not actually done step 1, but I have more faith in you than in myself.