You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 92c9dcf
Browse filesBrowse the repository at this point in the historyBrowse files
feat(xtest): compare benchmark candidates with each other
Stage 4 of the DSPX-4372-t1 plan. With more than one candidate, every pair of
candidates is compared directly. These comparisons never gate.
- perf/stats.py: FASTER/SLOWER/TIED verdicts in their own BH family. Each
tail is tested at alpha/2, since neither candidate is privileged; TIED
requires the interval inside the +/-threshold band. The rule is
antisymmetric, so listing order does not change a conclusion.
- perf/runner.py: candidate pairs follow the reference pairs; the control
yields every copy-to-copy pair so its floor covers the widest spacing.
- perf/conclusions.py (new): pairwise conclusions per cell and metric, and
winner eligibility, decided once. A winner must be FASTER than every
other candidate, and a tripped A/A control suppresses it however narrow
the interval. Ties and unresolved competitors say so.
- report JSON 'conclusions', a candidate-comparison section in the
markdown, and the same conclusion lines on the terminal.
Fixes the three defects review found in #621: the control-registration
order (kept from stage 3), a winner named from the top two point estimates,
and a tripped control that did not suppress the winner.
Signed-off-by: Dave Mihalcik <dmihalcik@virtru.com>
0 commit comments