-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question to loop closing #101
Comments
The yellow path represents the LiDAR odometry path, and its frequency matches the LiDAR’s cycle. The green path is a collection of poses used in graph optimization, which are downsampled compared to the yellow path. Loop closure is achieved by dividing the map into submaps, performing matching between submaps to search for loops, and the green path represents a collection of representative poses of these submaps. Therefore, the lower resolution of the green path is by design. To increase the resolution, code modifications would be necessary. |
oh I understand. |
But how did you achived this result? |
The image is from an early test, and at that time, the test environment was small, so instead of looking for loops with a set of submaps, the implementation might have been set to look for loop closures directly between single scans. |
Hello,
First of all, thank you for creating this lidar-based SLAM. In particular, that it works for ROS2 Humble. :)
So far, it's working really well. I use it with a Velodyne VLP-16 for outdoor use.
I want to show the differences between with and without loop closure, as you did in an example. But I'm a beginner with loop closing. So I've already noticed that the normal path is without loop closure and the modified path is with loop closing.
However, on the picture you can see that it looks like the modified path has a lower "resolution" than the yellow path. Especially in the curve it looks really bad.
But I don't know why? What parameter can I change to fix the problem?
The text was updated successfully, but these errors were encountered: