-
Notifications
You must be signed in to change notification settings - Fork 19
Set parameters directly in lidar mapping node #1
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
base: humble
Are you sure you want to change the base?
Conversation
Make use of ROS2 NodeOptions to allow undeclared parameters. Guard against parameters already set by parameters file.
Signed-off-by: Tanner, Gilbert <gilbertta@edu.aau.at>
Signed-off-by: Tanner, Gilbert <gilbertta@edu.aau.at>
fix: Change Velodyne message time handling
fix: Complilation errors on ROS versions older than Iron
|
Hi! @sujit-168 is there a reason this hasn't been merged yet? @james-ward were you still working on this? |
You can find the answer at the following link. |
Thanks for replying. I checked out the PR's comments, and (correct me if I'm wrong) it seems that this PR used integralrobotics' rpg_vikit fork, instead of Robotic-Developer-Road's rgp_vikit fork which only open-sourced last Dec (here). Does this mean someone just has to make sure this PR uses Robotic-Developer-Road's version of rpg_vikit? |
@vic-bart |
No description provided.