2017issue C0918-21
Optimization without overfitting in trend-system evaluation
Overfitting occurs when parameters are tuned so tightly to historical patterns that the same rules fail on later, different data. Evaluation is stronger when ranges are chosen in advance, more history is used, and robustness is judged by how widely tests remain profitable rather than by a single peak.
- Overfitting occurs when parameters are tuned so tightly to historical patterns that the same rules fail on later, different data.
- Choose parameter ranges in advance from the expected holding style. Scanning every possible value and then keeping only the profitable ones is a first step toward overfitting.
- Prefer more history so evaluation includes bull and bear regimes, price shocks, and a larger trade count, and retest the same range on three successive windows.
- Treat a result as robust when a large share of tests remain profitable, and treat a new rule as generalized only when the average of all tests improves and most individual tests improve.
Overfitting in system optimization
Overfitting occurs when parameters are tuned so tightly to historical patterns that the same rules fail on later, different data.
Scanning every possible value and then keeping only the profitable ones is described as a first step toward overfitting.
Use more history, not less
Using more history is preferred because it adds bull and bear regimes, price shocks, and a larger trade count for evaluation.
Commit the range before the scan
Parameter ranges should be chosen in advance from the expected holding style, such as 40 to 120 days for macrotrend work and 5 to 40 days for short-term work.
Trend rules used for the tests
A one-parameter trend test can use the slope of a moving average to stay long when the line is rising and short when it is declining, avoiding many false signals from price-versus-line crossings.
A Moving-average crossover is long when the faster average is above the slower one and short when the faster average is below.
Retest the same range on later windows
Testing the same range over three successive windows, each about half as long as the previous, is used to check whether the edge still appears in later history.
A robust result is defined as a large share of tests remaining profitable, not as a single peak profit, with a trend example of as much as 70% successful tests.
When a new rule is treated as generalized
A new rule is treated as generalized only if the average of all tests improves and most individual tests improve. Improvement confined to one pocket while others worsen is treated as overfitting.
A volatility filter on new entries
A volatility filter that blocks new entries when annualized price volatility exceeds 50% and waits until it falls back below that level is presented as typically cutting return a little while cutting risk much more.
Copper crossover average profit by slow moving-average length

Each point is the published row average across fast averages of 5, 10, 15, 20, 25, 30 and 35 days. Tests use copper back-adjusted futures, long when the fast average is above the slow average and short when it is below, with futures size set to $25,000 divided by the 20-day ATR times the big-point value.
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