Concept map: Leakage
Prerequisites (two levels) and direct dependents of Leakage. Show everything
- 2prerequisites shown
- 2direct dependents
- 5lessons use it
Insights 9
- Use causal masking when the prediction must not see later tokens or events
- Judge custom-trained embeddings by downstream lift, not by nearest-neighbour anecdotes
- Exclude text written after the outcome, such as resolution notes and closing remarks
- Compute entity history features as of the prediction timestamp with point-in-time joins
- Remove features that are recorded because of the outcome, not before it
- Do not treat leave-one-out target encoding as a leakage fix; it still exposes each row's own label
- Include the outcome when imputing for an inferential model and leave it out of a deployed imputer
- Build training rows with as-of joins so each feature uses only values known at the cutoff
Projects 19
- Booking-flow A/B test: should the one-page passenger form ship?
- Late deliveries and review scores in a marketplace: how much damage, and on which lanes?
- From session data to an experiment backlog: which conversion drivers deserve a test?
- Passenger no-show probabilities for overbooking and reconfirmation decisions
- Predicting one-year diabetes progression with an honest error estimate: nested CV on 442 patients
- Probability of default for a card portfolio: calibrated, monotone, explainable and audited
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