Raise configured YOLO max detections
This commit is contained in:
@@ -109,8 +109,16 @@ Environment variables:
|
||||
- `YOLO_DEVICE`
|
||||
- `YOLO_IMAGE_SIZE`
|
||||
- `YOLO_MAX_TILES`
|
||||
- `YOLO_MAX_DETECTIONS`
|
||||
- `YOLO_BATCH_SIZE`
|
||||
|
||||
`YOLO_MAX_DETECTIONS` is forwarded to Ultralytics as `max_det` for each
|
||||
prediction call. GeoIntel defaults it to `1000` because building-rich AOIs can
|
||||
contain far more than the Ultralytics default of 300 candidate boxes; keeping
|
||||
the upstream default would cap recall before QA/QC begins. Operators may lower
|
||||
the value for small rasters or raise it for dense urban tiles after reviewing
|
||||
runtime and false-positive behavior.
|
||||
|
||||
### Local model asset catalog
|
||||
|
||||
GeoIntel can list local runtime model files mounted into the backend model
|
||||
|
||||
Reference in New Issue
Block a user