5 Commits

Author SHA1 Message Date
bench
ff3c8926df Revert the pose evaluator edit from 8a1ee24: running batches froze its checksum
harness/eval/coco_extra.py is frozen per batch by task_contract (only listed equivalent rewrites may replace it).
The 8a1ee24 edit made every pose stage of the pilot batches fail the contract check (Qwen rtmpose.s never got a
formal stage). The keypoint shift gate it fed was removed in e0c224f, so the shift reaching 'unverified' no longer
decides anything; back to the approved version 505d37.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 00:15:37 +08:00
bench
e0c224f881 Pose: keypoint shift is recorded, no longer a pass/fail gate
The 2 px limit was a hand-set number from the first baseline (9-15): mean distance of all 17 joints in raw image
pixels, invisible joints included, not scale-normalized. On 10-22 SimpleBaseline r101 failed it with OKS-AP 68.34
vs FP32 68.22. OKS-AP already scores the task against ground truth with person-scale normalization, and FP32/quant
agreement is G2's job. New runs drop it from G3; the shift is still measured and recorded. Pose contracts no
longer state it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 07:55:51 +08:00
bench
8a1ee24338 Pose shift check no longer requires official_model; pose contracts state the 2 px keypoint shift limit
RTMPose evidence never carried official_model, so the top-down shift check reported every rtmpose run
UNVERIFIED (06 x2, pilot x2). run_quant already rejects a baseline of another model, so the key added nothing.
The contracts now say G3 also bounds the mean keypoint shift (2 px), which pilot agents could not know.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 01:39:15 +08:00
Codex
e1d5a96252 fix: match fixed top-down poses by source identity 2026-09-23 21:57:25 +08:00
bench
d309109f2b pre-grind snapshot 2026-09-19: batches 1-7 adapters/probes/recipes + eval additive changes 2026-09-19 17:52:03 +08:00