NearFieldCorrection: fix unit scale of lambda #38
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the unit scale of LAMBDA_77GHz_MILLIMETER which is currently meters instead of millimeters.
All other calculation already assume millimeters, i.e. the range
OpenRadar/mmwave/dsp/compensation.py
Line 201 in 65bcd62
or the geometry point offsets for point D of 8.7mm:
OpenRadar/mmwave/dsp/compensation.py
Line 190 in 65bcd62
Hence, lambda should be scaled to millimeters as well to avoid adding variables with different unit scales.