Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Promote expanded building detector profile
GeoIntel CI / docs-smoke (push) Canceled after 0s
Details
GeoIntel CI / contract-smoke (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-13 02:21:42 +02:00
parent d02b4e5219
commit 1c16313ae6
7 changed files with 71 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/AI_PIPELINES.md
+13 -11
View File
@@ -335,15 +335,17 @@ hard-negative gates, then run `sparse_building_context` as a separate review
matrix. The first expanded local model improved dense AOI F1, but Kasterlee-bos
false positives block default promotion.
The AOI1024 background-aware local model asset,
`geointel-building-yolov8s-aoi1024bg512r3e50-pt`, is exposed in Detection Lab
only through deliberate operator profiles. `balanced-review` applies threshold
`0.15` for the strongest positive-AOI F1 observed so far, but remains
candidate-only because pure-empty false-positive pressure failed at that
threshold. `conservative-review` applies threshold `0.35` and is marked as the
promoted candidate after the split-background report passed the strict
pure-empty gate. Sparse-context detections remain review-only evidence, not a
default-promotion blocker.
The expanded-AOI local model asset,
`geointel-building-yolov8s-aoi1024expandedminpx4vis035e50-pt`, is the current
recommended Detection Lab operator profile. Use tile size `512`, overlap `64`
and confidence threshold `0.15`. Persisted QA/QC across seven positive AOIs
measured mean precision `0.6471`, recall `0.4700` and F1 `0.5433`; the strict
three-sample pure-empty background gate produced zero detections. The previous
`geointel-building-yolov8s-aoi1024bg512r3e50-pt` model remains available as a
legacy conservative `0.35` review profile. Sparse-context detections remain
review-only evidence, not a default-promotion blocker. Persistent misses are
concentrated in small buildings, so every production-like run still requires
persisted QA/QC against suitable reference data.
To update a Tower/Unraid `.env` from a promoted report, use the guarded
activation helper. It validates the exact report candidate key, verifies that
@@ -353,8 +355,8 @@ when `--apply` is supplied:
```bash
python scripts/activate_promoted_yolo_candidate.py \
--promotion-report artifacts/detection-model-promotion/split-aware/aoi1024bg512r3e50-high-threshold-split-20260710T222934Z/detection_model_promotion_report.json \
--candidate-key 'geointel-building-yolov8s-aoi1024bg512r3e50-pt|512|64|0.35' \
--promotion-report artifacts/detection-model-promotion/split-aware/aoi1024expandedminpx4vis035e50-split/detection_model_promotion_report.json \
--candidate-key 'geointel-building-yolov8s-aoi1024expandedminpx4vis035e50-pt|512|64|0.15' \
--models-dir /mnt/user/appdata/geointel/models \
--env-file /mnt/user/appdata/geointel/.env \
--json