You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have successfully deployed Kimera-Multi and run the provided examples. Now I want to run the campus_tunnels_1207_compressed dataset with 2 additional robots, but during execution, I encounter ROSbag stuttering/lagging and failure to run simultaneously. What might be causing these issues? I hope you can help me understand the root causes when you have time.
Due to the incomplete ROSbag execution, the Kimera-VIO trajectory only partially appears, as shown below:
As shown in the figure, the ROSbags for the two newly added robots (apis and sobek) only ran for ~30 seconds. Previously, when running 6 robots, others completed fully without this issue. After adding these 2 robots, all robots now stutter and terminate early (see visualization).
Additionally, the output logs and related files for the newly added robots are completely empty (no data recorded).
The text was updated successfully, but these errors were encountered:
I have successfully deployed Kimera-Multi and run the provided examples. Now I want to run the campus_tunnels_1207_compressed dataset with 2 additional robots, but during execution, I encounter ROSbag stuttering/lagging and failure to run simultaneously. What might be causing these issues? I hope you can help me understand the root causes when you have time.
Due to the incomplete ROSbag execution, the Kimera-VIO trajectory only partially appears, as shown below:
As shown in the figure, the ROSbags for the two newly added robots (apis and sobek) only ran for ~30 seconds. Previously, when running 6 robots, others completed fully without this issue. After adding these 2 robots, all robots now stutter and terminate early (see visualization).
Additionally, the output logs and related files for the newly added robots are completely empty (no data recorded).
The text was updated successfully, but these errors were encountered: