Continue rejected v37 through frozen loop
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s

This commit is contained in:
Jens
2026-07-29 16:23:28 +02:00
parent f18a23c060
commit b393d9f65d
5 changed files with 30 additions and 2 deletions
+13
View File
@@ -11804,6 +11804,19 @@ Deployment evidence:
malformed JSON and filesystem errors produce an explicit fail-closed
supervisor state before any subprocess is started. The updated supervisor
was activated live with one remaining v37 GPU process.
- V37 early-stopped normally at epoch 23; epoch 5 remained the immutable best
checkpoint. The supervisor observed `results.png` and executed its one-shot
completion handoff.
- Fixed a completed-checkpoint entry defect exposed by that live handoff: the
iteration directory is now created before copying/hash-binding an existing
model. The repaired calibration ran without opening test/background.
- V37 improved calibration aggregate F1 to `0.568` and Flanders F1 to `0.307`,
but failed Flanders F1/precision/recall and Wallonia precision. It was
rejected and produced checksummed failure-driven sampling for iteration 2.
- Made training patience an explicit orchestrator input. A pre-epoch iteration
2 process exposing the old hardcoded value `35` was terminated before any
result row existed; iteration 2 restarted from the identical checkpoint and
sampling with the frozen `patience=18` contract on CUDA.
- Added those aerial augmentation parameters to the orchestrator CLI and
training command, preventing later failure-driven checkpoints from silently
reverting to generic orientation assumptions.