-
Notifications
You must be signed in to change notification settings - Fork 39
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
Static Azimuth-Elevation heatmap #32
Comments
My comment from the other issue I will check you parser with my device to get the data for the static heatmaps. |
I can verify that using the configuration from the demo visualizer with the Range-Azimuth heatmap enabled, triggers the Azimuth-Elevation mode in Python (I get the TLV type with a value of 8). However, in the demo visualizer the plot looks like the Azimuth-Range heatmap with some weird behavior, so the same parsing might not work. |
The size of the data is 24576 = (Range FFT size) x (Number of all virtual antennas) x (4Bytes), so the range fft size is 512 (number of virtual antennas is 12). |
Yeah nice.
That is not 100% correct. In the documentation I sent, you can see the difference of Azimuth Static Heatmap (TLV Type 4) and Azimuth/Elevation Static Heatmap (TLV Type 8) in the Lenght. So the TLV Type 4 just uses the azimuth antennas (I think this is the same as you had it with your other sensor) and the TLV Type 8 uses all virtual antennas (= 12).
So as you said before, that you get the TLV type with a value of 8, it seems that your sensor/demo uses AoA 2D DPU for AoA processing. In the demo visualizer the elevation heatmap is not shown, as it is mentioned in the quote above. What do you think? |
Yes, I reread it again and I realized about it. I see, makes sense, I guess you process the data the same way as the range azimuth heatmap, but at the end instead of getting a horizontal heat map, you reshape it to get a 512x4x3 cube. |
So you mean your heatmap demowith some adjustments could work? |
Do you mean, to get the elevation heatmap you have to reshape it to 512x4x3? Because in the documentation it is described as a 2D FFT array:
|
My implementation had issues so I would not recommend it, it needs some fixes (I would say that looking at how pymmw does it will help you with that. And for the azimuth/elevation, I would say the difference should be around the line 284 (ignore the left right flip in this case), where you will have to reshape Q to separate the virtual antennas horizontally and vertically (check the antenna order). But I might be wrong since I am not sure how the num angle bins would work in this case. I guess it will need some trial an error, and if the demo visualizer is also processing it, if you open it in gui composer you can check at the source code to see how they do it. Or maybe ask in the TI forum. |
This is from the source code of the demo visualizer (JavaScript), it seems to be more complex than I expected:
|
What do you mean with gui composer? Do I need to download the offline version of the demo visualizer? |
Oh wow that is a lot of code for that data process. I asked a similar question a few days ago -> Question in TI Forum So it seems, that there is no well-documented example how to parse the data for the heatmap. |
Hi I am working with IWR1642. The code is running but couldn't retrieve the data from the board. The configuration is sent and the sensor start command could be visualized but no data is retrieved. can you please help in this regard? Also 2d scatter plot opens but nothing displayed on it. |
There seems to be a hidden mode for Azimuth-Elevation heatmap that can be enabled: #6 (comment)
It is probably a special mode for the AOP and ODS devices that when the static azimuth is selected, instead of the Range-Azimuth heatmap that was provided in previous boards, it outputs the Azimuth-Elevation heatmap (the guimonitor command is the same).
First, test in the demo visualizer with the Range-Azimuth heatmap selected. If that provides the Range-Elevation heatmap, it can probably be extracted using the same logic as the Range-Azimuth heatmap.
The text was updated successfully, but these errors were encountered: