Estimating Alpha Half-Life
Half-life turns a decay curve into a single, tradeable number — the time it takes a signal's predictive power to fall to half its starting value — and it drives rebalance frequency and holding-period choices directly.
Prerequisites: Measuring a Signal's Decay Curve
A decay curve is a picture; a half-life is a number you can put in a spec document. It answers one question precisely: how long until this signal has lost half of what it started with? That single number drives rebalance frequency, position sizing, and how nervous to be about lag in the pipeline.
Turning a curve into a half-life
Most decay curves are roughly exponential — IC falls off at a constant proportional rate rather than a constant absolute one. If is the information coefficient days after the signal fires, an exponential fit looks like
where is the decay rate. The half-life is the time at which , which solves to
In words: fit how fast the log of the IC falls in a straight line against time, read off the slope as , and divide 0.693 by it. You don't need calculus to use this in practice — a spreadsheet regression of against gives you directly as the negative of the slope.
Half-life is not the maximum useful holding period — it's the point where you've given up half your edge. Most desks rebalance at somewhere between a quarter and a full half-life, trading off the cost of turning over faster against the decay you accept by waiting.
A worked example
A momentum signal starts at . Measured IC at day 10 is 0.028. Taking logs: . Since , that gives , so per day. Half-life is then days.
That number is directly actionable: a rebalance every 4–5 days uses roughly a quarter of the half-life, keeping most of the signal's power while still refreshing before too much decays away. A weekly rebalance (7 days) is defensible too, and would cost less in turnover for a modest give-up in freshness. A monthly rebalance, at over a full half-life, would mean trading on a signal that has already lost more than half its original information by the time it's acted on again.
Don't fit a half-life from a single pair of points if you can avoid it — noise in one horizon's IC estimate can swing wildly. Use a regression across many horizons (day 1, 5, 10, 20, 40…) so the estimate averages out sampling noise rather than being driven by one lucky or unlucky measurement.
Related concepts
Practice in interviews
Further reading
- Grinold & Kahn, Active Portfolio Management (ch. 14, information horizon)