-
Notifications
You must be signed in to change notification settings - Fork 166
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
Ros2 node info does not show info for nodes of the same name #279
Comments
I think that the idea is to enforce node name uniqueness, but it has not been applied yet (see here). |
I think that that's a great idea down the road, and it would obviate this issue. But it's also way too easy to have nodes not be unique right now and it's extremely confusing when the tools make this harder to introspect. My naive expectation is that the cli tools should throw up a warning and print info on all the nodes with that same name. Is that duplicate node in |
The problem is that that change would require changes in the cli, |
Ouch! So RCL doesn’t even have a globally unique identifier for nodes? |
No. I think originally it was assumed that the node names were unique, but this isn't enforced (possibly an oversight?). IMO we should first decide if node names should be unique (ros2/design#187), if not, then we should implement GUIDs for nodes and use it throughout the stack. |
#include <alsa/asoundlib.h> #define PCM_DEVICE "default" // Function declarations int main(int argc, char *argv[])
} int initialize_ros2(int argc, char *argv[], rcl_context_t *context, rcl_node_t *node, rcl_publisher_t *publisher)
} int capture_and_publish_audio(rcl_context_t *context, rcl_publisher_t *publisher)
} void cleanup_ros2(rcl_context_t *context, rcl_node_t *node, rcl_publisher_t *publisher)
} |
That question has nothing to do with this issue. Please open a question over on https://robotics.stackexchange.com/questions/tagged/ros, which is our central Question and Answer site. You'll get a better answer there, and it will be searchable for the future. Make sure to include a lot of information on what platform you are using, which ROS distribution you are using, and the exact steps you took. |
It is possible to launch multiple nodes of the same name. When this happens, those multiple nodes show up in
ros2 node list
but it is impossible to get info on these nodes withros2 node info
.In the below example, I have launched a single
amcl
process which spins up 3 nodes. But since the three nodes were assigned the same name, I can't introspect to see what topics those nodes are listening/publishing on.The text was updated successfully, but these errors were encountered: