-
Notifications
You must be signed in to change notification settings - Fork 541
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
How to get IMU-only trajectory? #67
Comments
OKVIS does not provide this, but for sure will be a terrible trajectory. I don't think you need to show that this is a bad idea. Just the noise and bias in the IMU are enough to give a completely wrong trajectory |
Thanks for your answer! What I want to do is that, if the feature tracking lost, I want to optimize IMU data only, not include reprojection error term. This means that the IMU error term also has to be changed. Or just use the IMU integration result between two image frames to replace the joint optimization result. This idea right or wrong? Dose it work? |
Just some anecdotal evidence: OKVIS seems to work fine if there is little-to-no visual information for a short period of time (at least if it has been well initialized). Check the results for sequences |
I want to get the IMU-only trajectory, and use it to compare with the ground-truth and Visual-Inertial output. How? Thank you !
The text was updated successfully, but these errors were encountered: