Skip to main content
Track Robustness testing
8 / 51
Library

1990issue C061-2

Why popular indicator optimization fails robustness

A limited public catalog of popular indicators is presented as already thoroughly examined, so historically attractive rule combinations are easy for other traders to locate as well. Wider use of the same theoretically correct entries and exits is said to make those fills harder to obtain.

  • A limited public catalog of popular indicators is already thoroughly examined, so further remixes of those same inputs are unlikely to be undiscovered.
  • Historically attractive rule combinations are easy to locate and therefore likely to be found by other traders, which makes theoretically correct fills harder to obtain.
  • A general spreadsheet can encode nonstandard hypotheses, but a change of spreadsheet generation slowed or blocked the same workbooks, so the testing tool belongs inside robustness testing.
  • Obscure, costly research is presented as more likely to remain useful in the short run than cheap, widely shared approaches; the least obvious procedures are argued to retain value longer.
Entries in this reading3 entries

A shared catalog is already searched

A limited public catalog of popular indicators is presented as already thoroughly examined, so further remixes of those same inputs are unlikely to be undiscovered. Historically attractive rule combinations are described as easy to locate, and therefore likely to be found by other traders as well.

A mechanical trading system is a complete, testable procedure that states when to enter, exit, or stand aside from given rule inputs, market state, and execution constraints. System optimization searches combinations of rules and indicators for historically attractive results. When that search space is public, the search is treated as easy, and therefore fragile.

Fills become contested

As more traders compete for the same theoretically correct entries and exits, those fills are said to become harder to obtain. Fill competition is the process by which wider use of the same signal makes the intended entry and exit prices harder to obtain.

A widely shared system that is attractive at the time is described as self-eroding: more users follow, competition for fills increases, and late adopters are left with little remaining opportunity. Robustness testing asks whether a fitted recipe still holds after imitation and contested fills, not only whether it fit the original sample.

Nonstandard hypotheses need a general workbook

A general spreadsheet is presented as the environment that can encode nonstandard hypotheses, such as whether a timestamp is a singularity or how closing volume relates to opening prices, through formulas and summary calculations. Those questions sit outside a limited public catalog of popular indicators.

The testing tool is part of the procedure

On a then-typical desktop, a 600-row calculation was reported as more than 10 seconds in one spreadsheet generation versus under 7 seconds in the prior generation, about 50 percent slower. A dependency-and-correlation workbook with about 15 columns and three normalizing recalculations finished in about five minutes on the older generation. The newer generation was stopped after more than 10 minutes, and the largest models would not load.

Robustness testing, as used here, also checks whether the same procedure can still be run after a change in the computing environment used to test it.

Uncomfortable procedures last longer

Obscure, costly research is presented as more likely to remain useful in the short run than cheap, widely shared approaches, because serious investigation is described as expensive. Choosing a trading system is compared to trading itself: the least comfortable or least obvious procedures are argued to retain value longer than convenient, inexpensive ones.

Editorial reading

Editorial interpretation: robustness is a crowding problem, not a curve-fit score. If a mechanical trading system is optimized over the same public indicator catalog everyone else can search, a clean historical signal is evidence that the recipe is discoverable, not that entries and exits will remain executable. Hypothesis novelty, research cost, and even the speed of the testing tool are part of the procedure being validated. This reading is editorial and is not attributed to the archive.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
8 of 51 in the Robustness testing track
19911-12 pp.Next on Robustness testingRetesting weighted indicator balances across horizonsEach bullish or bearish call is checked against later market direction over a fixed horizon, then hits and misses become a period hit-rate.
All readings on this track · 51 readings
  1. 1986Degrees of freedom in trading system optimization
  2. 1988Walk-forward and neighborhood tests after optimization
  3. 1988Undisclosed rules block system robustness tests
  4. 1988Testing re-optimization calendars against random parameter controls
  5. 1989Binary search limits on multi-peak average grids
  6. 1989Parameter neighborhoods that survive a shift
  7. 1990Use profit mapping to keep a cycle and stop plateau
  8. 1990Why popular indicator optimization fails robustness
  9. 1991Retesting weighted indicator balances across horizons
  10. 1992Constructing forecast models with regression, walk-forward, and robustness
  11. 1992Diagnose regimes before you lock parameters
  12. 1992When stops change system timing
  13. 1993Walk-forward halt rules for forecast models
  14. 1994Walk-forward evaluation of genetic index rules
  15. 1995Input pruning as walk-forward system evaluation
  16. 1995Critiquing neural nets as incomplete trading systems
  17. 1996Rebuild the equity-path ratio before it ranks a designed system
  18. 1996Parameter grids can fit random walks
  19. 1996Walk-forward analysis belongs in the design of a mechanical trading system
  20. 1997When a holdout fails, discard the rule set
  21. 1997Test rewarded rule breaks before replacing the system
  22. 1997Walk-forward rules keep system research from rewriting live trades
  23. 1999Keep a channel-breakout to two lookbacks and test neighbor stability
  24. 1999Constant investment size in stock system evaluation
  25. 2000Forcing optimization maps mechanical system failure boundaries
  26. 2000Robust parameter selection with surface charts
  27. 2001A two-gate classroom test for a two-window momentum trend filter
  28. 2002How a two-sided continuation factor becomes a testable trend rule
  29. 2002Evaluating two-window trend intensity as a reversal rule
  30. 2003Discounting speculative bubbles in system robustness tests
  31. 2003Walk-forward evaluation of locked stochastic oscillator rules
  32. 2003Critiquing mechanical system design after extreme price regimes
  33. 2004Evaluating a two-window trend trigger
  34. 2005Grade backtested signals with holdouts and optimization plateaus
  35. 2006Reserved-sample evaluation of trading system design
  36. 2006Walk-forward critique of hindsight crossover systems
  37. 2008Condition-matched walk-forward evaluation for mechanical systems
  38. 2011Session-split evaluation of regular and overnight systems
  39. 2012Walk-forward evaluation as operator rehearsal
  40. 2013Two-window evaluation of mechanical trading systems
  41. 2013Walk-forward filter selection for repeated-median velocity
  42. 2014Walk-forward evaluation for fading-memory velocity systems
  43. 2015Test oscillator events before tuning rules
  44. 2016Walk-forward evaluation of a five-parameter parabolic stop-and-reversal
  45. 2016Walk-forward optimization without curve fitting
  46. 2017Optimization without overfitting in trend-system evaluation
  47. 2017Parameter stability is a better guide than a larger crossover grid
  48. 2018Point-in-time universes for system evaluation
  49. 2018Walk-forward robustness evaluation for optimized systems
  50. 2018Critiquing breakout systems through robustness tests
  51. 2018A critique of parameter fitting in system design
All 58 readings tagged Robustness testing
Also on Robustness testing5 readings