-
Notifications
You must be signed in to change notification settings - Fork 116
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
Visual Odometry in fuse? #371
Comments
It appears that this PR #352 addresses adding somethings that might be needed for performing matching inside the package |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is fuse appropriate for doing visual odometry inside the framework? i.e. having fuse optimize the matched keypoints directly? Or is it expected that you will be doing the matching externally and just sending the transformation + covariance to fuse in order to fuse it?
If so, are there examples of such use cases?
The text was updated successfully, but these errors were encountered: