Record promoted detector runtime verification
This commit is contained in:
@@ -7061,3 +7061,13 @@ Open:
|
||||
## Remaining limitation
|
||||
|
||||
- Persistent small-building misses remain the weakest quality bucket. Continue with targeted evidence review and data coverage before considering another training run; do not infer production accuracy from aggregate F1 alone.
|
||||
|
||||
## Tower deployment verification
|
||||
|
||||
- Pushed commit `1c16313` and rebuilt the all-in-one runtime at `http://192.168.10.150:1202`.
|
||||
- The opt-in AI image installed `torch 2.13.0+cpu` and `torchvision 0.28.0+cpu` from the official CPU wheel index; runtime CUDA availability is `false`. Ultralytics reports version `8.4.93`.
|
||||
- The live model catalog exposes 23 local files and marks only `geointel-building-yolov8s-aoi1024expandedminpx4vis035e50-pt` active with the expected SHA256.
|
||||
- Explicit `--check-model-load` preflight passed against an existing nine-tile manifest: dependencies, model load, manifest structure, tile paths and tile limit were all valid; no inference or download ran.
|
||||
- Embedded PostGIS live migration smoke passed with PostGIS `3.6`, required tables/indexes, database collation and the single Alembic head `202606120900`.
|
||||
- Browser validation confirmed that the recommended profile selects the exact active asset and threshold `0.15`, while live preflight displays CPU dependency/model readiness and the expected missing-manifest guard before dataset handoff.
|
||||
- Browser console warnings/errors: `0`.
|
||||
|
||||
Reference in New Issue
Block a user