follow tf2 name convention

[ompugao]

A leading slash of frame_id should be stripped.
see http://wiki.ros.org/tf2/Migration.

[wjwwood]

Sorry, I accidentally closed this when changing the branch layout of the repository. I've reopened it and updated the target base to be lunar-devel which is the new default branch. You can edit again to point at indigo-devel, which is what is used to release for ROS Indigo and Kinetic, if you like.

[ompugao]

please merge this pr into lunar-devel if you like.

[croesmann]

this issue is now very crucial to me.
In melodic, the navigation stack migrated to tf2.
Running now stage_ros with multiple robots and the navigation stack for at least one of them
spams the following error

[ERROR] [1533643336.506100416, 271.300000000]: TF Exception that should never happen for sensor frame: , cloud frame: /robot_0/base_laser_link, Invalid argument "/robot_0/base_laser_link" passed to lookupTransform argument source_frame in tf2 frame_ids cannot start with a '/' like:

which is indeed correct, since stage_ros defines the frame id as "/robot_0/base_laser_link" and not "robot_0/base_laser_link".

Is there any chance to get this into melodic @wjwwood? I would like to push a melodic release of the teb_local_planner_tutorials but all the multiple robot configurations fail due to the issue mentioned above.

thanks a lot!

[wjwwood]

Sorry, I don't have time to maintain this repository beyond doing releases, but I believe @rtv is helping review and merge things as he has time.

[amattag]

Has this problem been fixed in ros-melodic-stage?
I am having this problem with ros melodic. The /robot_0/base_laser_link frame name must be changed to robot_0/base_laser_link frame. Otherwise a simulation with multiple robots/objects will not work.
Had to switch back to ros-kinetic.

[croesmann]

The fix is still crucial for multi robot simulations in stage, would be great if we could get this in.

[AndyHuska]

+1 for merging this pull request, it's ready to go!