Concept map: Experiment tracking and model registry
Prerequisites (two levels) and direct dependents of Experiment tracking and model registry. Show everything
- 2prerequisites shown
- 0direct dependents
- 1lessons use it
Taught and used in
Insights 9
- Write a run manifest that lets a stranger repeat the experiment
- Freeze and version bin edges so models and monitors compare like with like
- Run RAG ablations one component at a time with per-stage metrics
- Tier regression gates by cost and cache model outputs keyed by their full input
- Keep rollback one alias change away and test it before you need it
- Define reproducibility as recoverable inputs plus tolerances, not identical bits
- Record why a model version was promoted, not only that it was
- Make lineage queryable from dataset to models so a bad table has a known blast radius
Projects 5
- Passenger no-show probabilities for overbooking and reconfirmation decisions
- Card-fraud alerts under a fixed review budget: ranking on day 1, tested on day 2
- Data validation, drift monitoring and a retrain decision for a booking forecast with delayed labels
- Weekly batch forecasting platform for tens of thousands of item-store series
- Real-time call-prioritisation scoring: serving contract, training-serving skew and safe rollout
List view151 concepts
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 11
Day 12
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Day 19
Day 21
Day 22
Day 23
Day 24
Day 25
Day 26
Day 27
Day 28
Day 29
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
Day 49
Day 51
Day 52
Day 53
Day 54
Day 55
Day 58
Day 59
Day 60