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

docs: record Mol benchmark decision
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-14 12:40:11 +02:00
parent 9f61037794
commit 5db93a9530
7 changed files with 57 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/README.md
+5 -2
View File
@@ -267,12 +267,15 @@ the canonical footprint-IoU metrics.
The runner also writes `mol_operational_benchmark_report.json` and `.md`. The
default operational gates require four positive holdouts, one background
control, coverage provenance for every positive run, at least 95% reference
control, coverage provenance for every positive run, at least 90% reference
coverage in every zone, mean F1 at least `0.25`, per-zone F1 at least `0.10`
and zero detections in each pure-empty control. Override the numeric gates only
through the documented `MOL_MIN_MEAN_F1`, `MOL_MIN_ZONE_F1`,
`MOL_MIN_REFERENCE_COVERAGE` and `MOL_MAX_BACKGROUND_DETECTIONS` variables.
An `accepted` report records bounded operational evidence; it does not mutate
Source bbox queries retain complete edge features and can intentionally
over-cover the exact projected raster polygon, so the coverage gate detects a
gross source/raster mismatch rather than scoring the model. An `accepted`
report records bounded operational evidence; it does not mutate
the active model. A `review_required` report is still a successful benchmark
execution but explicitly blocks a promotion recommendation.