New collision mesh results in additional occupied space in the costmap

[kyouma9s]

Hi PAL team,

After applying the following change, the laser sensor will produce extra noises (two blue squares) under the robot base.

6f2f482#diff-ad08db4e382cb0e728defe237a9f3c1e5182555d33df65e413a7b74289504ce6R60

These noises will cause additional occupied space in the costmap.

Once I rollback this change, the noise will disappear, like the following image.

I don’t know if this is a bug or a new feature for TIAGO. 😅

[kyouma9s]

@v-lopez

[v-lopez]

Hi @kyouma9s I apologise for not seeing this earlier, thanks for the ping.

I'm trying to reproduce this locallly but can't. Can you share how are you launching the simulation?
Also could you enable collision view in gazebo window, and send me a screenshot of where the laser intersects with the base?

For me it doesn't

[kyouma9s]

Hi @v-lopez

This problem can be reproduced in Rviz.

1. Follow this tutorial http://wiki.ros.org/Robots/TIAGo/Tutorials/Navigation/Localization

2. Start the navigation demo by

roslaunch tiago_2dnav_gazebo tiago_navigation.launch public_sim:=true

3. Try to use the nav tool of Rviz to make robot reach somewhere, you will see occupied costmap behind the robot.