Other Parts Discussed in Thread: IWR6843
Sebastien
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
To be even more specific, NUM_ANGLE_BIN is equal to 64 earlier in the code.
We create therefore 1D arrays of real and imaginary numbers of 64 bytes because of that zeros.(NUM_ANGLE_BIN).valueof()
although I don't know what valueof does, but I know zeros returns an array.
and there are 2 loops where we go through real and imaginary numbers array.
One that goes up to qrows, which at max is 8.
And the second one that goes up to NUM_ANGLE_BINS which is 64.
How does fft.transform(real,img) magically fill up the remaining 64-8 spaces remaining ?
Hi,
I believe it is just allocating the max possible amount of space for the angle bins, and is just 0-padding whatever is unused. As i'm sure you know, the number of angle bins depends on your chirp configuration, and the NUM_ANGLE_BIN is a static value which does not take the chirp configuration into account. In regards to the algorithm executed here, the majority of the code here is used to convert the RA heatmap from bins to having actual units associated with them.
Best Regards,
Alec
Hi,
thanks for your reply about it, now the code makes a little bit more sense.
But now here comes another question about the process of converting the data coming in into an azimuth heatmap.
Why is there so much flipping around ?
More specifically here :
Hi,
Similarly, I believe it is just adjusting the shapes and layouts of the arrays in order to organize the value in such a way that is most readable in a graph. If you have more questions on this, you can probably add some debug prints to the visualizer code to see exactly what the values are at various points in the code and use that to follow along with what exactly is going on.
Best Regards,
Alec