-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
use __node:= in NodeOptions #858
use __node:= in NodeOptions #858
Conversation
This way, if __node:= is passed to the node executable, it gets overridden on each subnode and these subnodes get unique names.
Where possible, you should use get_name() in place of the string that is passed to the central node's constructor. That way both nodes get renamed appropriately if a node name override is supplied. |
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.
I see one redundant comment line, and you need to pass the lint tools before merge.
I believe this is the test command to run to see the failures:
colcon test --packages-skip nav2_system_tests nav2_dynamic_params nav2_motion_primitives nav2_bt_navigator nav2_costmap_2d nav2_lifecycle_manager nav2_tasks nav2_robot
… use that as its prefix (thanks, Scott!)
…te_internal_node uncrustify
Codecov Report
@@ Coverage Diff @@
## master #858 +/- ##
==========================================
+ Coverage 20.44% 20.48% +0.04%
==========================================
Files 181 181
Lines 9305 9317 +12
Branches 2259 2268 +9
==========================================
+ Hits 1902 1909 +7
- Misses 6320 6323 +3
- Partials 1083 1085 +2
Continue to review full report at Codecov.
|
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.
Looks good, thanks for cleaning it up. It's passing CI now.
This way, if __node:= is passed to the node executable, it gets overridden on each subnode and these subnodes get unique names.
Fixes #842
This is a better approach than #851 since it respects other global options, like topic remapping.
To test, run the nav stack with node name overrides in your launch file.