Two fields added in SensorViewConfiguration for Radar and Lidar. #390
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
PhRosenberger
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reference to a related issue in the repository
Solves #389.
Description
This PR is an extension of OSI with two fields added in
SensorViewConfigurationfor Radar and Lidar to properly configure a ray tracer. One ismax_range_per_rayin m that terminates a ray if nothing is hit, the other ismax_range_per_pixelin m that is applied to the sum of the lengths of all rays on one path that terminates the ray propagation in case of multi-path-propagation.Mention a member
@pmai, Please check this extension.
Check the checklist