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

std::out_of_range in Estimator::removeObservation #88

Open
hdamron17 opened this issue Sep 16, 2020 · 1 comment
Open

std::out_of_range in Estimator::removeObservation #88

hdamron17 opened this issue Sep 16, 2020 · 1 comment

Comments

@hdamron17
Copy link

Hi, I have been using Okvis successfully for a while but recently I received std::out_of_range from the map lookup in Estimator::removeObservation. It seems the index would always be out of bounds when you request landmarksMap_.at(landmarkId) after verifying that landmarkId is not in landmarksMap_. This is just for logging, so I will remove the statement for now, but I wanted to see if there is a justification for doing this. Thanks!

@1ADZX
Copy link

1ADZX commented Jan 3, 2024

Hi, I have been using Okvis successfully for a while but recently I received std::out_of_range from the map lookup in Estimator::removeObservation. It seems the index would always be out of bounds when you request landmarksMap_.at(landmarkId) after verifying that landmarkId is not in landmarksMap_. This is just for logging, so I will remove the statement for now, but I wanted to see if there is a justification for doing this. Thanks!

I also encountered a similar problem to yours, how did you solve it?

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