[lab · T4] Measurement — track thread

[akash-coded]

L.A.B. track thread. One per track. Ask here rather than opening a new thread — the
answers accumulate where the next person will look.

Labs: L07, L08 · Lifecycle stage: Testing · the method

What this track is about

Two recalls that measure different stages, and the arithmetic that decides whether a delta is real. This is the track the rest of the repository is built on.

Where people get stuck

The single most valuable check here is L08's n_boot does not change the width. Raising resamples from 500 to 8,000 stabilises the printed digits and does not narrow the interval. n is how much uncertainty there is; n_boot is how carefully you measure it. Only one is under your control after the eval set is fixed.

How to ask here

Paste the check that failed and its message. The messages are written to be actionable — if
one is not, that is a bug in the lab and saying so is a useful contribution.

python scripts/lab.py run <id>            # public checks
python scripts/lab.py run <id> --hidden   # everything

Submitting

Fork, fill in starter.py, open a pull request. The
Labs workflow posts your results as a comment and
edits it in place on each push. It will not fail the build on red checks — the comment says
what failed.

What this track hands to the next one

Testing produces the artefact the following stage needs. If you finish L07, L08 and cannot say what
that artefact is for your own corpus, the track is not done — that is the point of the lifecycle
running underneath the pathway rather than beside it.