-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(sample_sensor_kit_launch): pass container to velodyne nodes #48
feat(sample_sensor_kit_launch): pass container to velodyne nodes #48
Conversation
Signed-off-by: Kaan Colak <kcolak@leodrive.ai>
1264c41
to
b1273fa
Compare
Hello @mitsudome-r Mitsudome-san, Relevant PR was merged today: autowarefoundation/autoware.universe#2114 Could you review this PR? without these changes, localization will work own container. |
@mitsudome-r ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I made a small suggestion, but I will leave it to you whether you want to make the change.
Signed-off-by: Kaan Colak <kcolak@leodrive.ai>
Thanks, Mitsudome-san. I applied your suggestion. |
@kaancolak @YamatoAndo Are there any other issues before merging this PR? (Sorry if I couldn't catch up related discussions) |
Signed-off-by: Kaan Colak kcolak@leodrive.ai
Description
Working with an individual container for each lidar increases network traffic and CPU utilization. Make it possible to pass
pointcloud_container
to Velodyne nodes.When working with logging_simulator.launch.xml, it decreased network utilization around ~30-40 MB/s .
When setting
launch_driver:=true
onlogging_simulator.launch.xml
orautoware.launch.xml
it looks working without problem, but needs to test with real device. I will test it to make sure multiple velodyne drivers working in the same container with different namespaces without any problems.Relevant issues and PR :
autowarefoundation/autoware.universe#1228
autowarefoundation/autoware.universe#2114
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.