costmap updating issue
Hello, I use nav2d package for SLAM on a real robot. All of a sudden costmap building has an issue while updating.. I have uploaded a .gif because it's difficult to describe it:
It's like the costmap is correct in a small square around the robot, and beyond that square the costmap goes bad.
The weird thing is that I didn't have that issue before some days, and I cannot find which of the things that I changed broke the costmap! I guess it's a parameter but I cannot detect it.
Asked by MariaKrgr on 2016-05-30 08:27:48 UTC
Answers
This might still be due to odometry drift. The global map stays intact because it uses scan-matching to correct the robot's pose, but the local costmap depends alone on the odometry. The local map is corrected where it is updated by new measurements, but keeps distorted everywhere else. Up to this point I would say this is at least expected behavior in the presence of odometry drift. Have you tried moving the robot further away from this start area to see if this issue persists?
What actually worries me is how your local and global maps seem to be badly aligned. There are obstacles in the global map, that are not in your local map, which should not be the case. Are there lots of dynamic obstacles (people) around your robot?
Asked by Sebastian Kasperski on 2016-05-31 07:46:55 UTC
Comments
it does a similar thing even in the simulation, where I take odometry from V-REP simulator..
Asked by MariaKrgr on 2016-06-02 04:58:42 UTC
Comments
The basic map in /map topic is correct, so I guess it's not an odometry issue, but a parameter in costmap.yaml maybe or in another .yaml file...
Asked by MariaKrgr on 2016-05-30 08:34:13 UTC