Avoid generating entire heatmaps #8

Open
opened 2024-12-29 19:13:13 +02:00 by cfalas · 1 comment
Owner

Both papers using the AoA-ToF heatmaps generate the heatmap for the entire space, which is quite computationally expensive (each pixel of the heatmap requiring a series of 4 matrix multiplications, with dimensions proportional to both the number of subcarriers and the number of antennas.

Instead of doing this for all pixels of the heatmap, we can dynamically increase/decrease the resolution near peaks (which is where all useful information is)

Both papers using the AoA-ToF heatmaps generate the heatmap for the entire space, which is quite computationally expensive (each pixel of the heatmap requiring a series of 4 matrix multiplications, with dimensions proportional to both the number of subcarriers and the number of antennas. Instead of doing this for all pixels of the heatmap, we can dynamically increase/decrease the resolution near peaks (which is where all useful information is)
Author
Owner

A simpler thing to try first: Store the steering vectors for each pixel (although I expect that the time needed to generate the steering vectors is negligible in compariston to the matrix multiplication)

A simpler thing to try first: Store the steering vectors for each pixel (although I expect that the time needed to generate the steering vectors is negligible in compariston to the matrix multiplication)
Sign in to join this conversation.
No Label
idea
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cfalas/dissertation#8
No description provided.