From 4e08b5a55528674a13eb81642c8d87aa9cfcc712 Mon Sep 17 00:00:00 2001 From: Mihai Dusmanu Date: Sun, 26 Feb 2023 08:43:21 +0100 Subject: [PATCH] Mention directions of transformations in readme. --- CAPTURE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CAPTURE.md b/CAPTURE.md index e343e22..c3b4c73 100644 --- a/CAPTURE.md +++ b/CAPTURE.md @@ -75,7 +75,7 @@ A Python interface that mirrors this file structure is available in `scantools.c ### 1. Session data -- `sensors.txt`, `rigs.txt`, `trajectories.txt` follow [the Kapture format](https://github.com/naver/kapture/blob/main/kapture_format.adoc#2--sensors). +- `sensors.txt`, `rigs.txt`, `trajectories.txt` follow [the Kapture format](https://github.com/naver/kapture/blob/main/kapture_format.adoc#2--sensors). However, the pose convention is reverted: `rigs.txt` contains camera-to-rig transformations and `trajectories.txt` contains sensor-to-world transformations. - `images.txt`, `pointclouds.txt`, `depths.txt`, `wifi.txt`, and `bt.txt` follow the specifications of their corresponding `records_*.txt` in Kapture. ### 2. Processed files