Closed joshuaoreilly closed 4 months ago
--t_max_diff 10000000000000000000000000
Hmm... :smile:
The timestamps in the trajectories are completely different. Either fix the files or use --t_offset
in evo if you know the exact time offset.
When you do what you did with --t_max_diff
, all poses in the second trajectory are matched only to the first pose of the other trajectory because that's then the "best fitting" timestamp. Alignment against only one pose doesn't work and causes the rank issue in the Umeyama algorithm.
--t_max_diff 10000000000000000000000000
Hmm... 😄
The timestamps in the trajectories are completely different. Either fix the files or use
--t_offset
in evo if you know the exact time offset.When you do what you did with
--t_max_diff
, all poses in the second trajectory are matched only to the first pose of the other trajectory because that's then the "best fitting" timestamp. Alignment against only one pose doesn't work and causes the rank issue in the Umeyama algorithm.
Ah, okay, I think I'm trying to achieve the opposite of what evo does, then; we have two trajectories that should be following the same trajectory (both cameras were mounted on the same robot and recorded simultaneously), but whose timestamps have an unknown offset we're trying to find. I don't suppose you know any tools that would be suitable for this purpose?
Yes, time synchronization is not part of this package. It depends too much on the specific recording and SLAM setup that is used.
You might find tools for specific systems, or papers describing how time sync was done (for example, the TUM RGBD benchmark paper by Sturm et al. describes how they synced the camera to their mocap system.)
Perfect, thank you so much!
When running the following command on two trajectories:
I get the following error:
This also occurs without
--correct_scale
. I'm not well versed in the theory behind how Umeyama alignment works; I know that at the very least, I don't have the case of static motion, but I'm otherwise at a loss as to the cause.trajectories_spot_tum.txt trajectories_zed_tum.txt
evo version: v1.26.0 Python version: 3.10.12 OS: Ubuntu 22.03 Changed source code: No Output of
evo_config show --brief --no_color
: