docs: match the false-accept record to the evaluator's own columns
Some checks failed
tests / model-free (pull_request) Has been cancelled
Some checks failed
tests / model-free (pull_request) Has been cancelled
The record said '2 false accepts of 48 unknowns', which conflated two fields: the 2 are 0 unknown accepts plus 1 unenrolled in-catalog facing and 1 enrolled misidentification. Also restores the hybrid-verify line the lane vocabulary edit dropped, and reframes the l09 note: its hubness ratio is 1.76 full / 1.36 live against G7's limit of 2.0, so the gate passes and the 30% internal share heuristic is what raises the alarm.
This commit is contained in:
parent
47c4273eec
commit
2b7dd0c193
3 changed files with 12 additions and 4 deletions
|
|
@ -59,9 +59,12 @@ text lane the signatures that cover them.
|
|||
the enrollment protocol wants (§8 of the architecture decision). Its matcher
|
||||
scores dwarf the other references (85-129 inliers against 10-40), so it wins
|
||||
facings it should not; re-source it before trusting l09 precision. Measured on
|
||||
the corrected image6 labels at full resolution, that is the one hub alarm the
|
||||
local lane raises: 18 accepts, 12 correct, a 37.5% share against the 30% limit.
|
||||
At live resolution the alarm clears (29%).
|
||||
the corrected image6 labels, l09 is the largest single-SKU share of accepts at
|
||||
both resolutions: 18 of 48 accepts (37.5%) at full, 11 of 38 (28.9%) at live,
|
||||
against a true share of 13 of 61 facings (21.3%). That is a hubness ratio of
|
||||
1.76 and 1.36 against the completion gate's limit of 2.0, so G7 passes; the
|
||||
stricter internal 30% share heuristic is what raises the alarm at full
|
||||
resolution. Re-sourcing the reference is the fix, not a threshold change.
|
||||
|
||||
## Rejected
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue