2008issue C011-3
Condition-matched walk-forward evaluation for mechanical systems
A conventional historical average does not record whether the dates were advancing, declining, or sideways. Condition-matched walk-forward analysis names the market trend and market condition first, then freezes the mechanical rules and judges the path in that state.
- A conventional historical average does not record whether the dates were advancing, declining, or sideways, so it cannot be mapped to the market trend a trader faces now.
- Mechanical stock systems are described as five primary designs, each built for one pairing of market trend and market condition rather than for every state at once.
- Walk-forward analysis keeps a rule freeze on entry, exit, and stand-aside rules and applies them only in a condition-matched sample.
- Robustness testing either runs the system only in its matching environment or rotates among several systems as trend and condition change.
The average hides the path
A conventional historical test that optimizes or replays a strategy on prior data, then reports an average, does not record whether those dates were advancing, declining, or sideways. That average cannot be mapped to the market trend a trader faces now.
Averaging a multi-year sample into one profit-to-loss figure can hide a continuous losing stretch lasting as long as 20 weeks. That path can exhaust a short-horizon trader's capital and willingness to continue before conditions turn favorable.
Mechanical systems are built for one pairing
A mechanical trading system is a fixed set of entry, exit, and stand-aside rules treated as one testable procedure rather than as discretionary chart reading.
Mechanical stock systems are described as falling into five primary designs. Each design is intended for a pairing of one of three market trends with one of six market conditions, such as velocity, moderate trend, or platform, rather than for every market state at once.
Market trend is the directional regime used to decide whether a system is in scope: advancing, declining, or sideways. Market condition is the texture of that trend, used to decide when the system should be active.
No single mechanical procedure is treated as valid in every market state. A complete evaluation states why the system was built, which environment it was designed for, and when it should remain idle.
Name the state, then walk the rules forward
Walk-forward analysis applies unchanged entry, exit, and abstention rules to unfolding or current-condition data so the system's path can be judged in the environment it will actually trade.
Condition-aware evaluation uses a market-realistic simulator rather than a contest-style game. It first names the present market trend and market condition and how long that state is likely to last, then applies the system only if that environment matches its design.
If historical data are still used, the sample should be limited to past intervals that share the system's intended trend and condition. That condition-matched sample replaces an undifferentiated multi-year span.
Rule freeze and retest windows
A rule freeze is a test window in which the mechanical rules are not edited, so recorded fills reflect the original procedure.
The walk-forward protocol sizes the simulated book at four times actual trading capital so more candidates can be exercised. It keeps the rules unchanged for two to four weeks of documented trades, and it retests any subsequent rule edits for at least two more weeks.
Robustness testing checks whether those frozen rules remain usable after the intended trend and condition are specified, losing streaks stay visible, and any later rule change is retested forward.
Robust practice is either to run a system only in its matching environment or to keep several systems and rotate among them as trend and condition change. A new or revised rule set should be retested under that same matched environment.
All readings on this track · 51 readings
- 1986Degrees of freedom in trading system optimization
- 1988Walk-forward and neighborhood tests after optimization
- 1988Undisclosed rules block system robustness tests
- 1988Testing re-optimization calendars against random parameter controls
- 1989Binary search limits on multi-peak average grids
- 1989Parameter neighborhoods that survive a shift
- 1990Use profit mapping to keep a cycle and stop plateau
- 1990Why popular indicator optimization fails robustness
- 1991Retesting weighted indicator balances across horizons
- 1992Constructing forecast models with regression, walk-forward, and robustness
- 1992Diagnose regimes before you lock parameters
- 1992When stops change system timing
- 1993Walk-forward halt rules for forecast models
- 1994Walk-forward evaluation of genetic index rules
- 1995Input pruning as walk-forward system evaluation
- 1995Critiquing neural nets as incomplete trading systems
- 1996Rebuild the equity-path ratio before it ranks a designed system
- 1996Parameter grids can fit random walks
- 1996Walk-forward analysis belongs in the design of a mechanical trading system
- 1997When a holdout fails, discard the rule set
- 1997Test rewarded rule breaks before replacing the system
- 1997Walk-forward rules keep system research from rewriting live trades
- 1999Keep a channel-breakout to two lookbacks and test neighbor stability
- 1999Constant investment size in stock system evaluation
- 2000Forcing optimization maps mechanical system failure boundaries
- 2000Robust parameter selection with surface charts
- 2001A two-gate classroom test for a two-window momentum trend filter
- 2002How a two-sided continuation factor becomes a testable trend rule
- 2002Evaluating two-window trend intensity as a reversal rule
- 2003Discounting speculative bubbles in system robustness tests
- 2003Walk-forward evaluation of locked stochastic oscillator rules
- 2003Critiquing mechanical system design after extreme price regimes
- 2004Evaluating a two-window trend trigger
- 2005Grade backtested signals with holdouts and optimization plateaus
- 2006Reserved-sample evaluation of trading system design
- 2006Walk-forward critique of hindsight crossover systems
- 2008Condition-matched walk-forward evaluation for mechanical systems
- 2011Session-split evaluation of regular and overnight systems
- 2012Walk-forward evaluation as operator rehearsal
- 2013Two-window evaluation of mechanical trading systems
- 2013Walk-forward filter selection for repeated-median velocity
- 2014Walk-forward evaluation for fading-memory velocity systems
- 2015Test oscillator events before tuning rules
- 2016Walk-forward evaluation of a five-parameter parabolic stop-and-reversal
- 2016Walk-forward optimization without curve fitting
- 2017Optimization without overfitting in trend-system evaluation
- 2017Parameter stability is a better guide than a larger crossover grid
- 2018Point-in-time universes for system evaluation
- 2018Walk-forward robustness evaluation for optimized systems
- 2018Critiquing breakout systems through robustness tests
- 2018A critique of parameter fitting in system design