Skip to content
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

Closed
mattiasmar opened this issue Dec 5, 2024 · 4 comments
Closed

rtabmap-export (Global Full vs Global iterative) #1398

mattiasmar opened this issue Dec 5, 2024 · 4 comments

Comments

@mattiasmar
Copy link

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?

@matlabbe
Copy link
Member

matlabbe commented Dec 7, 2024

Related to #1387

Yes, it is Global Full. I'll check if I can also add the iterative option in that PR: #1391

@mattiasmar
Copy link
Author

During localization which graph is used: "Global iterative" or "Global full"?

@matlabbe
Copy link
Member

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.

@mattiasmar
Copy link
Author

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants