-
Notifications
You must be signed in to change notification settings - Fork 405
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
Infinite loop when no IMU data between two frames #37
Comments
About to merge fix |
Ok, fix merged. Let us know if it works for you @ruffsl |
I've rebased off the latest push to the public repo, and no longer encounter this issue. Though the diff from the recent set of commits pushed to the public repo is rather large so I couldn't easily grok which exact changes may have fixed this. I'd might suggest making more regular steady syncs to the open repos, as large infrequent pushes of commits can dissuade external collaboration. |
Thank you @ruffsl, I totally agree! We should make smaller PRs and encourage regular syncs. |
Description:
As firsted pointed out in MIT-SPARK/Kimera-VIO-ROS2#5 (comment) , it seems the Kimera-VIO is liable to fall into an infinite loop when no IMU data between two frames is received. Such can occur when IMU messages are lost or dropped by the middleware QoS, or when the sample rates from the IMU and Stereo frames happened to alias such that two Stereo frames are timestamped between two consecutively received IMU samples.
Command:
See launch command and context from linked PR:
MIT-SPARK/Kimera-VIO-ROS2#5 (comment)
Console output:
The infinite looping is encountered most of the time, but something one can get lucky with the race condition and avoid it for a few seconds:
Additional files:
For reference, I'm using an updated realsense package for ROS2:
https://github.com/ruffsl/ros2_intel_realsense/tree/devel
(The repo's devel branch includes a Dockerfile for how to build)
And the Kimera-VIO-ROS2 branch for the current work in progress PR:
MIT-SPARK/Kimera-VIO-ROS2#5
.repo
files in respective fork/repoThe text was updated successfully, but these errors were encountered: