-
Notifications
You must be signed in to change notification settings - Fork 787
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
with map::at
exception with gtsam 4.1.1
#823
Comments
std::out_of_range
with mapt::at
exception with gtsam 4.1.1std::out_of_range
with map::at
exception with gtsam 4.1.1
Hi, I meet the same error with gtsam 4.1.1. It occasionally occurs terminate called after throwing an instance of 'std::out_of_range' what(): map::at. I think it is a gtsam bug. So I mention it on borglab/gtsam#1092 (comment) |
Hi, @matlabbe
I randomly occur this issue. I can not confirm it, but I will update the devel branch. Maybe you could give it a try. |
Thx for looking at this issue, I'll keep this in mind next time I compile with gtsam 4.1.1. We will see if they try it on the code reproducing the problem in this issue borglab/gtsam#1092 (comment) |
Hi, I think I fixed the issue in GTSAM, could you pull the latest |
I will look out if this fixes it #799 |
I have confirmation from another person having the same bug that with latest gtsam nightly build binaries from PPA (gtsam-develop), the bug didn't appear again. |
With GTSAM version built from source (revision: 4.1.1) during loop closure optimization:
The bug doesn't appear with gtsam binary version (4.0.3-1) from PPA when processing the same dataset.
The text was updated successfully, but these errors were encountered: