Raise configured YOLO max detections
This commit is contained in:
@@ -7,6 +7,14 @@
|
||||
|
||||
# Changelog
|
||||
|
||||
## Sprint 148 YOLO max-detection cap hardening (2026-07-09)
|
||||
|
||||
- Added `YOLO_MAX_DETECTIONS` with default `1000` and forward it to Ultralytics as `max_det`.
|
||||
- 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.
|
||||
- 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)
|
||||
|
||||
- Built and audited an AOI-scale YOLO dataset at `512px` tile size to test whether the previous `160px` training scale was the main quality blocker.
|
||||
|
||||
Reference in New Issue
Block a user