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

Tips for performance? #2

Open
y22ma opened this issue Jan 25, 2015 · 2 comments
Open

Tips for performance? #2

y22ma opened this issue Jan 25, 2015 · 2 comments

Comments

@y22ma
Copy link

y22ma commented Jan 25, 2015

It would be much appreciated if a section on how to get the best performance from this package can be added.

Currently, both stereo_vo and mono_vo either crashes because there are not sufficient correspondences, or its pose estimates are diverging wildly if I lower the rejection thresholds.

@hengli
Copy link
Owner

hengli commented Jan 26, 2015

The rejection thresholds are already low enough. It is important to have a accurate calibration for the monocular/stereo camera in use. Perhaps you can describe your situation more specifically so that I can have a better idea of why too few correspondences are being detected.

@y22ma
Copy link
Author

y22ma commented Jan 26, 2015

After calibration using the stereo_calibration_node, I got stereo_vo working fairly consistently. The reprojection error is around 0.45 for both cameras.

With this calibration, however, mono_vo is not really capturing the camera translation. When I move the camera in pure sideway translation, the pose estimates output indicates a rotation without much translation at all. Just wondering what would likely cause that?

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