Learning outcomes
- Choose one public system and one dataset sequence
- Understand what Docker should reproduce
- Write the estimated trajectory to the SOP algorithms folder
Start with one case
Do not begin with a full batch. First make one system run on one sequence and verify that the output file exists.
The SOP pose output is `# timestamp(s) tx ty tz qx qy qz qw`.
Estimated trajectories belong under `algorithms/<system>/<dataset>/<sequence>.txt`.
Record the run
A public row needs the system commit, Docker image or build command, dataset sequence, config file, and command log.
If the run is not reproducible from GitHub and Docker instructions, keep the public metric values as TBD.
Checklist
- Docker image or build instructions exist
- Dataset is mounted read-only
- Trajectory is written under algorithms/
- Command metadata is saved
Practice task
Write down the expected output path for OpenVINS on EuRoC MAV MH_01_easy.