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
One of the invalid tf configuration is that frame_id fields of messsages published from stage_ros start with '/' when using multi-robot configuration. ( this is already reported in #68 )
This issue seems comes from mapName() function according to
@wjwwood can you please merge this asap? This is breaking the compatibility of many multi-robot packages that rely on stage in the latest ROS1 versions.
I am using stage_ros with move_base_multi_robot.launch in navigation_tutorials. The launch file does not work properly since tf configuration is invalid.
One of the invalid tf configuration is that frame_id fields of messsages published from stage_ros start with '/' when using multi-robot configuration. ( this is already reported in #68 )
This issue seems comes from mapName() function according to
stage_ros/src/stageros.cpp
Lines 478 to 481 in c3abc19
And seeing
stage_ros/src/stageros.cpp
Lines 172 to 227 in c3abc19
positionmodels
is lager than 1, frame_id is resolved as like/robot_0/base_laser_link
.This specification is valid for topicnames. But for frame_id, this is invalid.
The text was updated successfully, but these errors were encountered: