Freeze aerial warmup across training 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:27:30 +02:00
parent b393d9f65d
commit 18387448de
5 changed files with 46 additions and 0 deletions
+10
View File
@@ -11817,6 +11817,16 @@ Deployment evidence:
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.
- The first iteration-2 result row then exposed further generic-default drift:
bias LR reached `0.066775` because the direct v37 run's warmup bias `0.01`
and aerial HSV settings were not represented in the orchestrator. Both exact
processes were stopped after one row, and the invalid run was retained as
`iteration-002-invalid-warmup` with a reason marker.
- Added explicit warmup epochs, warmup bias LR and HSV hue/saturation/value to
the orchestrator and versioned completion command. Iteration 2 restarted
cleanly from the same candidate and checksummed sampling with
`warmup_epochs=1`, `warmup_bias_lr=0.01`, HSV `0.01/0.2/0.15`, patience 18
and the existing aerial rotation/flip contract.
- Added those aerial augmentation parameters to the orchestrator CLI and
training command, preventing later failure-driven checkpoints from silently
reverting to generic orientation assumptions.