-
Notifications
You must be signed in to change notification settings - Fork 654
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
Error using Monocular Visual Odometry and other questions #342
Comments
I get the following errors about cam1 calibration: You should run the following since those datasets are monocular camera only (one camera).
For a monocular camera, it is unable to run unless there is movement, thus to initialize the platform needs to be stationary and then moving. We detect this based on both IMU threshold and disparity (see the config file comments). The colors are the depth of features, you can inspect the code here: open_vins/ov_msckf/src/ros/ROS2Visualizer.cpp Lines 928 to 943 in 58afb2d
The system is built around using an IMU sensor at its core. Thus support for IMU-free isn't something we will ever support. I recommend checking out the ORB-SLAM family if you want monocular visual odometry (VO). We support static matching, checkout the tum_vi config file, but to support dynamic initialization you would need to either call a network to get that segmentation, or change the ROS subscriptions to subscribe to a topic which has that masking. The key place to change would be here: open_vins/ov_msckf/src/ros/ROS2Visualizer.cpp Lines 536 to 545 in 58afb2d
You can imaging either having the mask as another sync'ed input here, or just directly calling a network and getting a mask. Hope this helps, good luck! |
HI. @Aishkrish18 I recommend opening a new issue if you were unable to solve it. I recommend inspecting the published topics and enabling higher verbosity to see if the system is properly getting data. Likely, the published topics are not correct with your sensor launch file. |
Error using Monocular Visual Odometry:
When I attempt to run Monocular config files (eg. using either of the commands below), I immediately get the [ERROR] [run_subscribe_msckf-1]: process has died. How can I fix this in order to run monocular Visual Odometry?
Other (unrelated) Questions:
[init]: disparity is 0.283,0.302 (10.00 thresh)
[run_subscribe_msckf-1] [init]: failed static init: no accel jerk detected
The text was updated successfully, but these errors were encountered: