Skip to content

Clarification in docs #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nushakrishnan merged 3 commits into from
Oct 14, 2025
Merged

Clarification in docs #13

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1888d0c
clarify
nushakrishnan Oct 14, 2025
a377a80
clarify
nushakrishnan Oct 14, 2025
7225109
readme
nushakrishnan Oct 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ python -m evaluate_wrt_control_points --estimate demo/estimate/sequence_1_19.txt
--output_path demo_outputs/eval_cp
```

*This command evaluates the provided estimate w.r.t. control points and stores the results in `demo/eval_cp`. The `--corresponding_sensor` flag indicates which sensor the poses are expressed in (e.g., `imu` or `cam0`).*
*This command evaluates the provided estimate w.r.t. control points and stores the results in `demo/eval_cp`. The `--corresponding_sensor` flag indicates which sensor the poses are expressed in (e.g., `imu` or `cam0`). Note that the evaluation by default assumes that the estimated trajectory (from the estimate file) includes transformations from the world to the IMU frame.*

To learn more about the control points and sparse evaluation, refer to Section 4.1 and 4.2 of our paper.

Expand Down