You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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?
Hi, I have been using Okvis successfully for a while but recently I received
std::out_of_range
from the map lookup inEstimator::removeObservation
. It seems the index would always be out of bounds when you requestlandmarksMap_.at(landmarkId)
after verifying thatlandmarkId
is not inlandmarksMap_
. 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!The text was updated successfully, but these errors were encountered: