feat(autoware.repos): change vls driver to nebula driver #3699
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.
Description
This PR should be tested in conjunction with autowarefoundation/sample_sensor_kit_launch#64
This PR changes the LiDAR driver used from
velodyne_vls
to Nebula.Nebula is actively maintained, supports more different LiDARs, and has been tested to have feature parity with
velodyne_vls
for Velodyne VLP16 and Velodyne VLS128.Tests performed
This has been tested with the Autoware
sample_sensor_kit_launch
on branchfeat/nebula
and the sample Autoware map and rosbag data found here:https://autowarefoundation.github.io/autoware-documentation/main/tutorials/ad-hoc-simulation/rosbag-replay-simulation/
Localization, pointcloud preprocessing, and perception were all found to work with the same performance as with the previous
velodyne_vls
driver.Effects on system behavior
System behavior should be the same as when using the previous
velodyne_vls
LiDAR driver, with some performance benefits (and more to come as Nebula is developed and optimized).Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.