Record YOLO max detection live calibration
This commit is contained in:
@@ -13,6 +13,8 @@
|
||||
- Wired the setting through `.env.example`, Docker Compose, Unraid env examples and the Dockerman run script.
|
||||
- Documented why dense building AOIs should not inherit the Ultralytics default cap of 300 detections before persisted QA/QC.
|
||||
- Added regression coverage for adapter forwarding and Docker/Unraid runtime exposure.
|
||||
- Redeployed the Tower all-in-one runtime and verified live dense-AOI sweeps can exceed 300 persisted detection candidates: Westerlo reached 523/1000 detections and Turnhout reached 822/1000 at tested thresholds.
|
||||
- The current AOI512 YOLOv8s candidate remains rejected for default use because persisted QA/QC F1 remains too low despite the runtime cap fix.
|
||||
- No model was activated, no detections were faked, and no API route or migration changed.
|
||||
|
||||
## Sprint 147 AOI512 YOLOv8s scale-match candidate gate (2026-07-09)
|
||||
|
||||
Reference in New Issue
Block a user