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

Question About Loop Closure in /vins_estimator/camera_pose Results #461

Open
setareh-soltanieh opened this issue Nov 21, 2024 · 0 comments

Comments

@setareh-soltanieh
Copy link

Hi,

I have been working on this algorithm as part of my Master's thesis and have tested it using the EuRoC dataset with the provided configurations from this repository. I ran each test case 10 times, recorded the final poses from the /vins_estimator/camera_pose topic, and computed the average Absolute Trajectory Error (ATE) for each test case.

However, I noticed that my results are closer to the VINS results provided in the paper without loop closure, even though I ensured that loop_closure: 1 was set in the configuration file.

In RViz, I can see loop closure happening (e.g., matched frames and camera pose jumps), which suggests that loop closures are being detected. Despite this, the results from /vins_estimator/camera_pose do not seem to reflect the improvements expected from loop closure.

Can someone clarify why the poses from the /vins_estimator/camera_pose topic appear to lack the effects of loop closure, or if there is another topic I should be using to evaluate the loop-closed trajectory?

Thank you for your help!

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

1 participant