-
Notifications
You must be signed in to change notification settings - Fork 174
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
R-VIO initialization #7
Comments
Just realized this is basically the same question as Issue #1 |
Thanks @chutsu for testing the code. The initialization that I implemented is very simple, if you refer to the corresponding part of code. So, here I would like to clarify that current R-VIO codebase is for validation of the idea proposed in our paper and provides basic navigation functionality. If you want a full-function solution (e.g., with a better initialization), then I would encourage you to implement your own one. |
Thats fair enough. Thanks for sharing your code! :) |
Was wondering if R-VIO needs the IMU to be stationary for a minimum time for initialization?
What I'm seeing after testing a couple MAV EuRoC bags is that the bags that start with the drone stationary at the beginning seems to initialize well. However, the
MH_01_easy.bag
dataset, for example, starts with the drone being moved up and down first (presumably to initialize a VO), and that seems to cause R-VIO to diverge significantly at the start. Could this be because the sliding window hasn't been filled yet and the up and down motion cause the intialization to fail? If so this might be worth mentioning in the README?Tested:
^ screenshot of R-VIO running on
MH_01_easy.bag
The text was updated successfully, but these errors were encountered: