Idea: A short record next to a long one
Venue K: days averaging . Venue L: days, also . One number for each?
- Each venue alone takes lucky days at face value
- One pooled number ignores real differences
- A hierarchical model sits between
Idea: Randomness in layers
Each venue has its own edge , drawn from a shared population.
- Between venues:
- Within a venue:
- The shared layer lets a thin record borrow
Formula: Partial pooling
The estimate slides from the venue’s own average toward μ by the shrinkage factor B.
Formula: The shrinkage factor
Noise of the venue’s average over noise plus real spread. A noisy average gives B near 1.
Example: Venue K after 3 days
Take , , . Venue K has and averages . Estimate its edge.
- Noise of the average:
Quick check: Venue L after 36 days
Same population. Venue L has and also averages . What is its estimate?
Show the answer
Answer:
, so .
Idea: Does it help?
Venue K’s raw average has squared error . The shrunk estimate has .
- A small pull toward buys a large cut in variance
Common mistake: Shrinkage as a discount
Estimates move toward , not toward zero, so bad records improve too.
Instead A venue at after days moves up to .
Idea: Where the top level comes from
With equal , the spread of the averages estimates .
- Spread , , :
- Negative? Set to zero and pool fully
- Few groups: put priors on and too
Idea: News travels through the top level
A good run from one signal raises the chance of a good regime, and so the estimate for another signal.
- Even for a signal that has never traded
- The data moved up to the top level and back down