I am a beginner,
I rosplay bag the park dataset bag file, and recorded it using:
rosbag record -O park_evaluation_results.bag
/lio_sam/mapping/trajectory
/lio_sam/mapping/path
/clock
/tf
/tf_static
/lio_sam/mapping/odometry
/odometry/gps
/lio_sam/mapping/map_global
To visualize the trajectory map using evo, I used the odometry topic as my estimated SLAM path first and it looked nothing like the research paper trajectory map. Then I tried using Trajectory and later path topic as my estimated SLAM, again same issue.
Command:
evo_ape bag park_evaluation_results5.bag /odometry/gps /lio_sam/mapping/odometry
-v -a -r trans_part --plot --plot_mode xy
and
evo_traj bag park_evaluation_results.bag /lio_sam/mapping/odometry --ref /odometry/gps -v -a -s --plot --plot_mode xy
For the park dataset the trajectory path screenshot I have attached
I dont understand the issue since i did the same thing for campus_large dataset and it worked fine. But it's trajectory path is a bit tilted to the left too.
The end-to-end translation error is also a few centimeters bigger.

Note i have not taken gpsz(gps altitude) into account and have changed the params.yaml for both the datasets correctly.
I am a beginner,
I rosplay bag the park dataset bag file, and recorded it using:
rosbag record -O park_evaluation_results.bag
/lio_sam/mapping/trajectory
/lio_sam/mapping/path
/clock
/tf
/tf_static
/lio_sam/mapping/odometry
/odometry/gps
/lio_sam/mapping/map_global
To visualize the trajectory map using evo, I used the odometry topic as my estimated SLAM path first and it looked nothing like the research paper trajectory map. Then I tried using Trajectory and later path topic as my estimated SLAM, again same issue.
Command:
evo_ape bag park_evaluation_results5.bag /odometry/gps /lio_sam/mapping/odometry
-v -a -r trans_part --plot --plot_mode xy
and
evo_traj bag park_evaluation_results.bag /lio_sam/mapping/odometry --ref /odometry/gps -v -a -s --plot --plot_mode xy
For the park dataset the trajectory path screenshot I have attached
I dont understand the issue since i did the same thing for campus_large dataset and it worked fine. But it's trajectory path is a bit tilted to the left too.

The end-to-end translation error is also a few centimeters bigger.
Note i have not taken gpsz(gps altitude) into account and have changed the params.yaml for both the datasets correctly.