-
Notifications
You must be signed in to change notification settings - Fork 237
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
Ability to configure domain ID in rclpy #484
Comments
related to ros2/rclcpp#910 |
Closing, as I think it has been clarified in ros2/rclcpp#910 (comment). |
this is for the same ability with ros2/rclcpp#910 for rclpy. i believe that this is needed for rclpy also not only for rclcpp. |
Sorry, I didn't understand that. |
my bad, that confuses you.
will do it right now. |
@ivanpauno sir I would like to contribute to this. |
For the same reason than here ros2/rclcpp#910 (comment), it's better to wait now. The other set of PRs will be done soon, after that, this will be unblocked. |
this one too, you can leave it to us. |
After checking current implementation of rclpy, it only supports use default rcl_opitions. rclpy/rclpy/src/rclpy/_rclpy.c Lines 523 to 528 in 8f601c6
If want to support configuring domain ID, I have to expose InitOption to rclpy. |
i think we do need to expose InitOption to rclpy, i think that's the idea. |
Thank you. |
Friendly ping. |
Prefer adding an extra keyword argument to the functions with a default: Line 62 in 7116fb4
Line 36 in 7116fb4
Both should have a new In |
Thanks for your suggestion. |
Please review codes. |
CC: @ivanpauno i am closing this since #596 is merged. |
Feature request
Feature description
ability to set the Domain ID on a per-node basis.
the same ability with ros2/rclcpp#910
Implementation considerations
The text was updated successfully, but these errors were encountered: