minor change in LidarVisual for the case when sensor data is more than sensor range #132
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 PR attempts to fix the case when the data given to the sensor happens to contain a range value which is greater than, or exactly equal to the sensor range.
For rays when the sensor does not hit anything in the range, it returns
inf
for the ray. However, when we add adding noise to the measurements defaults theinf
reading exactly equal tomaxRange
of the sensor. This causes the lidar visual to display the rays, although they are not hitting any object.Additionally, if a point is a finite value (even if it is greater than the maxRange), the LidarVisual showed it since the only criteria of determining if the sensor ray was hitting or not was if the value returned by the sensor was
inf
.