-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add a way to set remapping rules for all nodes in the same scope #163
Conversation
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
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
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
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 !
Last commit only improved doc blocks, merging! (edit) and the Rpr checker was happy |
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
… (#203) Signed-off-by: Ivan Santiago Paunovic <[email protected]> Co-authored-by: Ivan Santiago Paunovic <[email protected]>
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/tf-tree-in-a-multi-robot-setup-in-ros2/41426/8 |
Fixes #45.
The other half of #158.
I'm unsure of how precedence should work.
When importing a launch file, it might become handy to override the remapping rule that was specified in the node.
Should that be the default?
For parameters, I took the opposite approach ... maybe we should revisit that after this PR.
Related discussion: ros2/design#289.