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

costmap mapping the map without noise

asked 2014-03-19 17:46:01 -0500

physicsex gravatar image

updated 2014-03-24 15:18:12 -0500

hello everyone,I am new in ROS and I'am studing with explore package. I run the code without problems. But When I use the rviz to see the explored map,I find that after the costmap got laser scan's data, as soon as the obstacle is detected, it has a probability to be a Free Space while if the truth is Obstacle, that made the wall(in the rviz ) it detected has some sawtooth shape. So I want to ask that how can the map mapping the stage's map exactly and I want it mapping without noise,which parameters should I change?

Thank you every much !

edit retag flag offensive close merge delete


You will have to be a bit more specific than that. What exactly are you doing? Which package are you using? What commands are you executing? What is happening? What would you like to happen?

demmeln gravatar image demmeln  ( 2014-03-23 15:39:57 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2014-03-24 21:26:45 -0500

updated 2014-03-24 21:45:05 -0500

Not sure if I understand you correctly, but the sawtooth shape/pixelization of the costmap happens because space is represented by grid cells with a fixed cell size (typically 5cm). What you could try is reducing the cell size, but that will have various side-effects. The point of the cost map isn´t so much good looks but rather well working obstacle avoidance of the robot. You could try writing your own improved visualization if you absolutely require nicer visualization.

edit flag offensive delete link more


Thank you very much for the explaining, but what I mean is not for the reason of the pixelization problem, I upload a picture for this problem you can see on the walls there are some white blocks which I want to erase .

physicsex gravatar image physicsex  ( 2014-03-25 21:24:24 -0500 )edit

Those are artifacts due to noise in both sensor data and state (i.e. pose) estimation as well as discretization of the environment. There are basically two things you could look at: * Postprocess map data using various computer vision approaches * Change the actual map generation process to try to get rid of these artifacts. Both will be pretty involved if you want to achieve really good results, so I´d recommend leaving things as they are :)

Stefan Kohlbrecher gravatar image Stefan Kohlbrecher  ( 2014-03-27 03:03:35 -0500 )edit

so the map generation process comes from the code of the costmap? does costmap used gmapping or other estimation methold of the robot?Then the sensor data come from the Stage and it don't have any noise. Thank you very much!

physicsex gravatar image physicsex  ( 2014-04-05 02:56:01 -0500 )edit

Question Tools

1 follower


Asked: 2014-03-19 17:46:01 -0500

Seen: 449 times

Last updated: Mar 24 '14