Repository navigation
docs: say how to regenerate the front-end measurements, and that they reproduce (T1-10) - #133
Merged
Merged
Conversation
… reproduce (T1-10) Add a "Reproducing these rows" section to docs/real_front_end.md with the commands and the result of one like-for-like check. Add tests that pin the section, the three file names, the one-off label and the CLI flags. Update the generated test count. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Telschow
force-pushed
the
docs/t1-10-front-end-provenance
branch
from
October 19, 2026 16:31
85671c8 to
5f26dc2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Adds a section "Reproducing these rows" to
docs/real_front_end.md. It names the three files, gives the command that regenerates each, and states what was checked, labelled "measured once on one machine, not checked by CI". It says nothing about any earlier mismatch. Two tests pin it. The generated test count is updated.Evidence: every front-end row reproduces on main
Main at a79b935. Each window was run with the wide study's own call,
measure(seq, (1, 4), window=(start, start + 30)). The original window used the original call,measure(seq)with all five gaps, with only its 600 frames on disk. Outputs went to the scratchpad. The raw data was read through symlinks and nothing was written into it.The frame-set hypothesis is refuted (MEASUREMENT).
measure()filters frames to the window before tracking, and the two MH_01 runs gave identical rows.Step 2: the two replays
docs/data/vo_wide.csvnavkit euroc vo --root <euroc> --from-csv docs/data/vo_errors.csv --wide-replay --wide-csv <scratch>docs/data/vo_clone_check.csvnavkit euroc vo --root <euroc> --from-csv docs/data/vo_errors.csv --clone --clone-csv <scratch>The committed CSVs were not touched.
What the page does not claim
The
--sequence ... --csvand--widecommands were not run end to end. The front-end rows were checked by calling the measurement function they call, window by window. The page says so.Audit finding F20 was a mistake
F20 and the premise of #106 came from one mismatch seen in T1-1b, raised without a like-for-like run. The like-for-like runs above do not show a mismatch. The earlier mismatch is unexplained. I did not look for the cause beyond refuting the frame-set hypothesis.
Tests
tests/test_vo_page.py, two new tests, written first and shown failing without the section:vo_errors.csv,vo_clone_check.csvandvo_wide.csv, and carries the exact label;--flagin the section'snavkit euroc vocommands is an option of the parser, and--wide-replayand--cloneare among them. This needs no data.Gates: ruff, format, mypy,
check_doc_tables.py,metrics.py --check(run--write: the count went from 1586 to 1588 in four files),check_links.py, the three page and error test files, and the full suite (1557 passed, 29 skipped, 2 xfailed).Left alone
No ADR notes. No change to
src/, the CSVs, the 4x preset, the README ordocs/status.md.Closes #106
🤖 Generated with Claude Code