Open eleboss opened 1 month ago
I checked several git issues, https://github.com/microsoft/lamar-benchmark/issues/44 https://github.com/microsoft/lamar-benchmark/issues/10 https://github.com/microsoft/lamar-benchmark/issues/49
my best guess so far is : The IOS and HL traj.txt are both local poses generated by devices. They are not GT. Navvis's traj.txt is a globally GT (with PGO and BA optimized??). And it seems this is not directly connected with IOS and HL. So, I can use navvis's pointcloud, mesh, and traj.txt for visualization and other rendering process.
I think you're right. To get see aligned poses you would need to use one of their validation datasets eg. benchmark/CAB/sessions/query_val_phone/proc/alignment_trajectories/txt
.
Hi,
Thanks for the amazing benchmark.
I am confused with the trajectory.txt file in Lamar benchmark. In the data web server, there are two folders.
**1. benchmark,
Inside the /raw there are multiple types of trajectories.txt like: ./raw/CAB/sessions/hl_2022-06-30-23-54-19-330/trajectories.txt:
./lamar/raw/CAB/sessions/ios_2021-06-03_12.16.58/trajectories.txt:
./lamar/raw/CAB/sessions/navvis_2022-06-21_09.28.22/trajectories.txt:
Is the IOS one a relative pose in the submap? Is HL a global GT obtained using superpoint+superglue? Is navvis a globally aligned with PGO and BA optimized as mentioned in the ECCV paper?
I need to use the GT pose for some rendering tasks, so the accuracy is my major concern. It would be great if you could clarify some details.
Except that, I saw ./lamar/benchmark/CAB/sessions/query_val_hololens/proc/alignment_trajectories.txt. Is this traj an accurate gt pose, optimized with PGO and BA mentioned in the ECCV paper?
Thanks again.
Yours Shijie HKU