-
Notifications
You must be signed in to change notification settings - Fork 791
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
rtabmap-export (Global Full vs Global iterative) #1398
Comments
During localization which graph is used: "Global iterative" or "Global full"? |
Full. Both are iterative. There should not be a huge difference, but with "iterative", we do each iteration outside the optimization library to get intermediate results (that is the default one in rtabmap-databaseViewer, to give a slider to see state of the graph after each iteration). The "full" approach lets the optimizer doing all the iterations internally. I don't have a full comparison between these two approaches, but rtabmap will use "full" when mapping/localizing. |
Thanks. |
Hello,
I've noticed that the tool "rtabmap-export --poses" generates poses corresponding to what is referred to as "Global Full" in the rtabmap-databaseViewer.
Can one instead have rtabmap-export generate poses corresponding to "Global iterative"? How?
The text was updated successfully, but these errors were encountered: