Closed martinakos closed 1 year ago
You can increase the parameter init_requestFullResetNormalizedErrorThreshold
in t265_noise_tumvi.yaml
(or simply pass a different value as a commandline parameter, e.g. init_requestFullResetNormalizedErrorThreshold=1.0
A bit of background: when initializing, the CoarseIMUInitializer checks the error of the graph and if it is above a threshold it assumes that the visual system failed. The best setting for it might depend on you application however. You can first set it to a very large value and have a look at the commandline output lines starting with CoarseIMUInit normalized error:
and then set the threshold accordingly.
One more thing to note is that the dmvio_t265 executable will usually work a bit better than the ROS version with the Realsense, because the latter does not get the exposure times from the camera.
Setting init_requestFullResetNormalizedErrorThreshold=1.0 worked! Thanks. I have another question but maybe I'll open another issue as it's not related to this one.
I got dm-vio working with a realsense t265 camera. I've also got this dm-vio-ros wrapper to work well with a live t265 camera. However, when running from a rosbag I keep getting repeated resets and the /dmvio/system_status only oscillates between 0 and 1. Curiously, the same rosbag with useimu=0 tracks well.
The output I get looks like this:
It seems to start tracking for a few moments but it resets again. I suspected from the camchain but I've checked it a few times and I think it's correct.
Do you have any suggestions to get it to work with this rosbag and useimu=1?