Fix runtime GIS uploads for operator QA
This commit is contained in:
+5
-1
@@ -464,4 +464,8 @@ This file now starts with the current implementation status. Older preparation/b
|
||||
- [x] Prepare the new samples on Tower and build a fresh hard-negative tile dataset.
|
||||
- [x] Rebuild Tower all-in-one image so the newly copied operator scripts are available inside `/app/scripts` without `docker cp`.
|
||||
- [x] Fix YOLO preflight CLI so it respects Tower `.env` runtime configuration.
|
||||
- [ ] Train a new candidate from `yolo-building-tile-uniquehardneg160` and run the positive/background promotion gates before activating it.
|
||||
- [x] Train a new inactive AOI1024 YOLOv8s candidate with visible-label filtering.
|
||||
- [x] Fix the all-in-one/compose Nginx upload limit after live 1024px GeoTIFF uploads hit `413 Request Entity Too Large`.
|
||||
- [ ] Rerun persisted QA/QC matrix for `geointel-building-yolov8s-aoi1024visible025e50-pt` after redeploying the upload-limit fix.
|
||||
- [ ] Add GRB paging or smaller dense AOI sampling before trusting 1000-feature-capped dense reference exports as full ground truth.
|
||||
- [ ] Keep every local YOLO candidate inactive until positive-AOI and hard-negative promotion reports recommend default activation.
|
||||
|
||||
Reference in New Issue
Block a user