-
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
[launch_ros] node_name overrides for a multi-node rclpy process #7
Comments
FYI @IanTheEngineer |
is there a workaround/fix for this? remapping the |
@masynthetic If you can't use components, a possible workaround is to launch your process as a plain process using Alternatively, contributions are most welcome. A multi-node aware action proposal would be great. |
This is what brought me here. Since even a single-node executable is an executable which owns a node and not the node itself, it feels like Also is it weird that some |
Feature description
A means of setting
node_name
overrides for a multi-node rclpy process such as that given in ros2/launch#204.Implementation considerations
This also brings into question the naming of the class
launch_ros.actions.Node
since it currently can launch a multi-node process. Perhaps that should fail on trying to launch a multi-node process and for that, use alaunch_ros.actions.MultiNode
action.Note: This is a different problem to the composable node launch. Here the nodes are brought into the same process via ... the process, not the launcher. I suspect the same situation would arise linking two c++ classes with nodes and instantiating them in the same application.
The text was updated successfully, but these errors were encountered: