docs(notepad): record missing marker-visible SVO blocker

This commit is contained in:
2026-02-05 04:54:47 +00:00
parent 0d71ef9f64
commit 23233c9138
3 changed files with 21 additions and 0 deletions
@@ -0,0 +1,6 @@
## 2026-02-05
### Verification dataset missing / no detections
- Current bundled SVOs (ZED_SN*.svo2) appear to produce 0 ArUco detections in `calibrate_extrinsics.py`.
- This blocks end-to-end verification that output JSON includes `depth_verify`, `depth_verify_post`, and `refine_depth`, and that `--report-csv` emits rows.
- Unit tests cover depth verification/refinement math and bounds, but integration output fields need a dataset with visible markers.
@@ -0,0 +1,10 @@
## 2026-02-05
### Blocker: integration output validation needs a marker-visible SVO
To complete remaining plan checkboxes:
- "--verify-depth produces verification metrics in output JSON"
- "--refine-depth optimizes extrinsics and reports pre/post metrics"
- "--report-csv outputs per-frame residuals to CSV file"
Need at least one SVO set where ArUco markers are detected and poses accumulate.
@@ -706,3 +706,8 @@ uv run pytest tests/test_depth_*.py -v # Expected: all pass
- [ ] Output JSON includes refine_depth section when flag used
- [ ] Refinement respects bounds (±5cm, ±5°)
- [ ] Both pre/post refinement metrics reported
#### Blocker Note
Remaining unchecked items require an SVO dataset where ArUco markers are detected (current bundled SVOs appear to have 0 detections). See:
- `.sisyphus/notepads/depth-extrinsic-verify/issues.md`
- `.sisyphus/notepads/depth-extrinsic-verify/problems.md`