-
Notifications
You must be signed in to change notification settings - Fork 11
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
Index out of bounds #8
Comments
The graph.g2o comes from |
Hello @glhwork ! I also encountered problem 2 and problem 3 you mentioned. For problem 3, since the length of list I is 5, how did you modify the code to change the way list I is assigned to matrix A? |
@Crystal-Biru Sorry, this problem still remains unsolved for me. I'm now working on other projects and will get back to this after a few months. |
Hello! As @bairuofei explained, the .g2o file comes from the SLAM algorithm ( Then, the .g2o (which contains information about the pose-graph) is parsed to recover the poses and uncertainties associated using this wrapper. To debug error number 2, the first step is to look at the .g2o file, as the error says it cannot recover the Fisher information matrix (see here). Lines of type "EDGE_SE2" in this file should have the following items:
This is written by g2o (see here and here). The covariance is encoded by the upper triangular part. Please, paste the .g2o content to further debug this problem. @glhwork, error number 3 is related to the workaround you made to bypass error number 2 -- you shrinked the Information matrix upper triangular part from 6 to 5 elements. |
@JulioPlaced I understand! You're right, problem-3 is caused by my modifications of the code. |
Thank you for sharing your algorithm!
Now I am trying to run the code in simulation and there are some problems I met,
I'm blocked by these problems for a while. I'm not sure whether the data generated (graph.g2o) is correct according to my steps. Or perhaps, I made a wrong modification of the code?
Many thanks if any suggestions!!
The text was updated successfully, but these errors were encountered: