You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the launch file in gz.launch.py does not include a namespace argument. Additionally, in the model spawn, the namespace is not utilized as part of the naming convention for the spawned robot, unlike the ros2 classic and ros1 . Furthermore, the joint states and other topics are hardcoded to "bcr_bot,"
Steps to Reproduce
Execute the current version of gz.launch.py without the namespace argument.
Observe the robot spawn behavior and the naming convention used.
Monitor the topics and verify that they are hardcoded to "bcr_bot".
Expected Behavior
After implementing the proposed changes:
The gz.launch.py launch file should include a namespace argument.
The robot spawned using the model spawn should incorporate the namespace argument in its name.
Joint states and other topics should be properly mapped to the provided namespace.
The text was updated successfully, but these errors were encountered:
Issue with Namespace Argument in ROS2 + Ignition
Description
Currently, the launch file in
gz.launch.py
does not include a namespace argument. Additionally, in the model spawn, the namespace is not utilized as part of the naming convention for the spawned robot, unlike the ros2 classic and ros1 . Furthermore, the joint states and other topics are hardcoded to "bcr_bot,"Steps to Reproduce
gz.launch.py
without the namespace argument.Expected Behavior
After implementing the proposed changes:
gz.launch.py
launch file should include anamespace
argument.namespace
argument in its name.namespace
.The text was updated successfully, but these errors were encountered: