Concept map: Drift and monitoring
Prerequisites (two levels) and direct dependents of Drift and monitoring. Show everything
- 4prerequisites shown
- 1direct dependents
- 4lessons use it
Insights 48
- Treat a negative test R² as a signal of shift or broken features, not as a rounding curiosity
- Adjust predicted probabilities when the class prior shifts but the class-conditional patterns do not
- Separate prevalence changes from model decay before retraining on a production precision drop
- Avoid building reports or monitors on the meaning of individual principal components
- Track alert volume at a fixed score threshold, because score drift moves it silently
- Guard tree-model inputs against values outside the training range, because predictions go flat instead of failing
- Keep a fixed reference window beside a rolling one so slow drift cannot hide
- Set drift alerts on an effect size with a minimum sample, since p-values fire on trivial shifts at scale
Projects 12
- 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
- Structured extraction from disruption notices: JSON-schema validation, safe repair and injected-instruction detection
- Tool-calling agent vs deterministic workflow for rebooking proposals after a cancellation
- Golden-set regression suite that gates prompt changes for a claims-intake triage assistant
- Cost and latency routing study: small model, large model, router and cascade on checkable answers
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