Schematic — not model output. Plate imagery is NPEC's; this draws the three stages the pipeline runs.
01 / 08 · Team capstone, five people
Two gates decide what reaches production.
github.com/filipp-lotsmanov/root-inoculation-mlops0.8371 F1, 0.7199 IoU on 20,512 held-out test patches — orchestrated by six Airflow DAGs, with an 85% coverage floor gating every build.
How it works
Researchers correct predictions in the UI. A daily DAG merges the corrections into training data while keeping the test set frozen, retrains, and puts the candidate through two independent gates.
- Scope
- Airflow orchestration and the Azure ML job layer, the feedback flywheel, the champion–challenger promotion gate, and most of the cv-pipeline package — inference, training loop, validation, weights handling and CLI. One inference path serves all three delivery forms, so the CLI, the HTTP API and the Azure ML scoring script cannot drift apart.
- Limitation
- The university-provisioned Azure and on-premise environments are decommissioned; the local Compose stack is the reproducible path.
- 01Correctionsresearchers flag predictions in the UI
- 02Retrainmerged in, test set frozen
- 03F1 gateclears the threshold on held-out
- 04Registrythe candidate is versioned
- 05Champion gatemust beat what is already serving
- 06Trafficonly now does it serve
Registered, never promotedclears 03, loses 05
The same thresholds the backend monitors on. 0.50 is the model’s decision midpoint; confidence held under 0.60 for an hour raises a drift alert. The interface shows researchers the same confidence the alert is computed from.