ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Why are obstacles added at the edges of the global costmap when GlobalPlanner is used?

asked 2019-09-27 06:12:02 -0500

pavel92 gravatar image

updated 2019-09-27 07:10:43 -0500

I recently run into the following problem. It looks like while using global_planner/GlobalPlanner as global planner whenever I give a goal, obstacles in form of lines are formed at the edges of the global costmap. Since I am using rolling_window: true, the line-shape obstacles are created when the costmaps move together with the robot.

This is a weird issue since the planner shouldn't be creating obstacles at all at any point. I could not reproduce this problem using different global planner (like carrot, navfn) and is not connected to the local planner as well (tried out eband, pose_follower and base_local_planner). I also tried disabling all costmap related plugins except the obstacles_layer but the lines are still created when the global_planner is used.

My initial guess is that there is something wrong with the costmap update when the costmap moves for one resolution step but I cannot understand how is this connected with the global_planner? Maybe it somehow messes with the costmap update so whenever the costmap moves the new values are updated with lethal cost or it is connected with my costmap configuration files (which I doubt since it works fine with other planners). I also tried tinkering with the global costmap update/publish frequency and resolution but the obstacles still appear. Changing the update/publish frequency though clears the obstacles but does not stop the creation of new ones.

Has anyone run into this problem? You can see the obstacles on the image and the bellow: image description

Also tried it with jackal_navigation and the same problem still occurs.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2019-09-27 15:19:44 -0500

David Lu gravatar image

global_planner does not do bounds checking. Instead it outlines the entire map with lethal obstacles so that it will never hit the edge case. It was not intended for use with rolling_window

edit flag offensive delete link more


Thanks for the information. I found that an existing issue regarding this already exists. As suggested by you I will make a PR with a parameter that enables outlineMap.

pavel92 gravatar image pavel92  ( 2019-10-01 02:19:40 -0500 )edit

Question Tools



Asked: 2019-09-27 06:12:02 -0500

Seen: 271 times

Last updated: Sep 27 '19