Closed zinuok closed 2 years ago
the odometry is reasonable for the first few seconds, so it is not about extrinsic parameter error. In my opinion, this seems to be a problem caused by VIO not detecting enough features due to motion blur, not enough initialization, etc...
Hello @zinuok, were you able to run VINS-Mono on the dataset with acceptable results?
@rakshith95 Unfortunately, no.. :( I had several tries to make it work, but I confirmed that feature detection was not good due to motion blur, in VINS-Mono. Maybe it is possible to run other VIO (e.g., XIVO..? ), but I haven't tried it.
As you know, the RGB camera in D435i has rolling-shutter that easily causes blur.
If you find another VIO that works, please let me know.
Hi, I'm trying to run VINS-Mono (other than XIVO you used) on your dataset (using ROS bag files). I converted extrinsic parameters like the below values and the result camera marker direction in Rviz seems reasonable. (forward direction; meaning, at least, no significant error in rotation parameters) However, as you can see in the below picture, the VIO diverges every time, even if I've changed some other parameters or slowed down the play speed.
I've tested 'cabinat0, classroom' Does anyone succeed to run VINS-Mono (or other publicly-available VIO) on this dataset? Are there any wrong values in my extrinsic parameters?