Closed YoungHaulk closed 1 year ago
I don't know yet why it's shown like this, might be a display issue of matplotlib with the large values of the UNIX timestamps? But as a workaround you could add --plot_relative_time
to the command. Then the axis is showing values starting at zero, relative to the start time of your reference gt.txt
.
I don't know yet why it's shown like this, might be a display issue of matplotlib with the large values of the UNIX timestamps? But as a workaround you could add
--plot_relative_time
to the command. Then the axis is showing values starting at zero, relative to the start time of your referencegt.txt
.
Thank you very much for your quick answer! After adding --plot_relative_time, the problem was solved!
Also, I have another problem. Description: The yaw, pitch and roll in the resulting graph seem to have an overall offset from the groundtruth(please see attached image). May I ask this kind of problem, is it because of the accuracy of my algorithm, or did I not set the relevant parameters when using evo_traj?
The command used is:
evo_traj tum vins_result_loop.txt gt.tum --ref gt.tum -pva --plot_relative_time
The two files above are still used(gt.txt vins_result_loop.txt)
Description: Thanks a lot for such a great tool! The image drawn by evo_traj has a negative time stamp, what is going on?
Command:
Console output:
Additional files: Please attach all the files needed to reproduce the error.![tmp](https://user-images.githubusercontent.com/84961677/236396548-26a8df7d-b342-42dc-8bb8-9906f9128603.png)
Please give also the following information:
evo pkg --version
:evo pkg --pyversion
:evo_config show --brief --no_color
:remove this line and paste your config HERE