feat(classify): any-aspect mono page is binary-scan, receipt is the tall specialisation (MK-8) #29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/classify-binary-aspect-MK-8"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
MK-8: fix the binary-scan / receipt boundary from MK-6 validation. Class membership is visual structure, not business purpose - a hotel receipt scanned full-page is a binary scan.
Changes
score(): drop(1.0 - aspect_long)from binary-scan, so a mono bimodal page scores on bimodality + low-sat regardless of aspect. Square/letter full-page scans now land in binary-scan instead of receipt orunknown.aspect_long * edges_text * low_sat * (1 - halftone)); when both score high the taller image wins via argmax (Receipt sorts after BinaryScan, so ties resolve to it).classify.toml:receipt_aspect_min2.0 -> 2.2, with a comment documenting the inversion.letter_aspect_mono_scan_is_binary_not_receipt(~1.3 aspect, the HamptonInn/Enterprise shape).receiptdescription states the aspect threshold.Acceptance status
tests/fixtures/classify/binary-scan/- blocked on the user fixture set.Blocked / needs input
Same pattern as MK-7: the real-image acceptance items need the user-provided validation set (HamptonInn, Enterprise, USPS, RegionsBank PNGs). Drop them into the repo and I will measure their features, confirm the boundary, and add the checked-in fixture test as a follow-up commit on this branch. The
receipt_aspect_minvalue (issue open question: 2.2-2.8) may also shift once the real receipt corpus is measured.The open question on widening
sat_mean_mono_max(0.06 -> ~0.12) for scanner colour casts is deferred - it needs the real scans to confirm, and is the same fix flagged on the MK-7 sibling.🤖 Generated with Claude Code