Revision history [back]

hector_mapping doesn't use odometry data. That's very nice if you have a real world system that provides no or very bad odometry. If you have perfect odometry in stage on the other hand and can't use it, this can be a disadvantage. In the video, the map breaks when the robot rotates very fast in place, so it appears the scanmatcher can't keep up there, as the change in shape from one scan to the next is too large. Generally, high update rate and high range LIDARs work best.