We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Remapping Names is apply to node name on ros1 example:
rosrun turtlesim turtlesim_node __name:=A __ns:=/pp rostopic list /pp/turtle1/cmd_vel /pp/turtle1/color_sensor /pp/turtle1/pose rosnode list /pp/A
Remapping Names isn't apply to node name on ros2 bouncy example 👍
ros2 run demo_nodes_cpp talker __ns:=/tt __node:=JJ ros2 run topic list /tt/chatter ros2 run topic list JJ
My question is why not the action is not same between ros1 and ROS2 bouncy。
The text was updated successfully, but these errors were encountered:
Hi @Guochd,
Are you asking why the output of ros2 node list is JJ instead of /tt/JJ? It looks like a bug that was fixed after bouncy was released.
ros2 node list
JJ
/tt/JJ
With this node in the background
ros2 run demo_nodes_cpp talker __ns:=/tt __node:=JJ
Using bouncy I see the following
$ ros2 node list JJ
Using a pre-release of crystal I see
$ ros2 node list /tt/JJ
If you would like to see it released in bouncy, I recommend opening a PR at https://github.com/ros2/ros2cli targeted at the branch bouncy with a fix.
bouncy
I will close this for now. It can be reopened if this does not answer your question.
Sorry, something went wrong.
No branches or pull requests
Remapping Names is apply to node name on ros1
example:
Remapping Names isn't apply to node name on ros2 bouncy
example 👍
My question is why not the action is not same between ros1 and ROS2 bouncy。
The text was updated successfully, but these errors were encountered: