Closed rancheng closed 2 years ago
Thanks for providing all the relevant info in your issue!
Can you try to compile DM-VIO in the mode RelWithDebInfo
info instead of Debug
?
A bit of background on this: In debug mode I added lots of asserts for certain properties (e.g. PoseTransformation inverse should be correct, analytic Jacobians should be equal to numeric ones, etc.). However the epsilon thresholds are sometimes a bit tight and while they are satisfied on the EuRoC dataset, on datasets with different motions they might fail. Hence, Debug mode is currently only supported on the EuRoC dataset and on other datasets you should use RelWithDebInfo.
Lastly: You might find the new version of the code interesting. While the Realsense-Live-version currently only supports T265 officially, I think it should also work well on your camera with some adjustments.
haha, you are correct, adding the RelWithDebInfo
flag didn't prompt error anymore, at the same time me and my colleague wrote the D455
and D435i
version in our folk, we will clean the code and create a pull request as soon.
Thanks again for your quick reply!
As there is no problem in this case, I will close this issue for now.
@rancheng are you using the depth information from the D455 to give accurate world scale? Or just running monocular?
Thanks
Thanks for realeseing this awesome project, I tested with my own sensor,
Realsense D455
, I calibrated withbasalt
and prepared the full dataset here:https://drive.google.com/file/d/15B9qwuYwPDqlkmGxKPgyjYxCOanzWDRN/view?usp=sharing
it can initialize sucessfully and the track looks good though:
The parameter I use to run this dataset is as following:
The full error log is as shown below: