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

Non- determinstic behaviour in cartographer detected #1967

Open
Cosinus2412 opened this issue Feb 25, 2025 · 1 comment
Open

Non- determinstic behaviour in cartographer detected #1967

Cosinus2412 opened this issue Feb 25, 2025 · 1 comment

Comments

@Cosinus2412
Copy link

Hello,

I am currently working on an extension to optimize parameters to achieve better map results relative to its ground truth.
Using my robot I recorded a bag file of a larger environment and used the cartographer on this recording. While I was experimenting with this recording, I generated multiple maps without changing any of the parameters or the bag file. Also I reduced the number of background threads to 1 as well as the ceres threads.
For several maps I aligned them with their ground truth and already visually it was clear to see that those maps differ from each other. I read through the paper and also the issues here and couldn't find any problems related to that.
I have also read through the documentation for the scan matching of ceres and have found out that also other people complained that non deterministic behavior can occur. Is this non-determinism related to ceres?
I was wondering now if there is a way to avoid this non deterministic behavior?

Thank you in advance for the response.

@bufeng-12
Copy link

bufeng-12 commented Feb 25, 2025 via email

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