Updating the EurocMono params to give good VIO performance #255
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
On the current version of master, the default EurocMono params give very poor pose estimation. See this issue for full details.
Change Summary
Updating the EurocMono params to give "good" VIO pose estimation. These changes include:
feature_detector_typefield inparams/EurocMono/FrontendParams.yamlfrom GFTT to FASTlinearizationModefield inparams/EurocMono/BackendParams.yamlfrom Hessian to Implicit SchurTesting
This change was tested using the
stereoVIOeuroc.bashscript with the Euroc V1_01_easy dataset in a monocular configuration. With the updated params, the VIO performance produced less than +/-0.2m of error in axis.