Fix MinRange, MaxRange in LiDAR prefabs #361
Merged
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.
Jira ticket: RJD-1300
Change
MinRange
,MaxRange
in LiDAR prefabs according to this spreadsheet.Changes include:
HesaiPandarXT32
:MaxRange
: 120 → 80OusterOS1-64:
MinRange
: 0.8 → 0.5,MaxRange
: 120 → 90VelodyneVLS128
:MaxRange
: 300 → 220HesaiPandar128E4X (OT128)
:MinRange
: ** → 0.3→