Skip to main content
Track Robustness testing
18 / 51
Library

1996issue C101-4

Parameter grids can fit random walks

A finished in-sample scorecard can report the system-optimization hunt rather than the next trade. A random-price-path has no structure to recover, so robustness-testing starts only after the chosen rules are frozen.

  • System-optimization that keeps the single best in-sample set shows a close fit to one preselected window, not that the rules captured lasting price dynamics.
  • A random-price-path has no repeatable history to recover, so an attractive fitted scorecard cannot establish that the same rules have later value.
  • Walk-forward-analysis on a holdout-window is a basic robustness-testing step, and it starts only after the chosen rules are frozen.
  • Anecdotal-selection of a few flattering episodes is a narrower form of curve-fitting, because it withholds the other signals the same rules would have issued.
Entries in this reading3 entries

What the in-sample scorecard reports

Cheap historical data and desktop search tools made it routine to vary every rule input across a large grid and then keep the single in-sample set that looked best. That workflow is system-optimization: varying every rule input across a historical window and keeping the single set that maximizes a chosen in-sample score.

That search only shows a close fit to one preselected window. It does not show that the rules captured lasting price dynamics.

A polished ledger on a random-price-path

The demonstration used a relative-strength threshold rule whose inputs were length, a buy zone, and a sell zone. The search enumerated those inputs and skipped cases where the buy zone exceeded the sell zone. It retained one combination as the set that maximized the chosen in-sample scores on the fitted sample.

The tested path was an artificial random-price-path, a manufactured series with no recoverable market structure. Each next print was the prior print adjusted by a random percentage held inside a bound, continued across a long run of prints, with only a later date slice shown in the test.

A random series has no repeatable history to recover, so an attractive fitted scorecard on that series cannot establish that the same rules have later value. The result is curve-fitting: forcing a rule set to match one fixed window so closely that the ledger describes the fit rather than a repeatable process.

Freeze the hunt before scoring unseen prints

A basic robustness-testing step is walk-forward-analysis: freezing those chosen rules and scoring the same entry, exit, and abstention logic on a reserved window that never entered the search. That reserved slice is a holdout-window: price data withheld from the parameter hunt so the locked rules can be checked once on unseen prints.

Robustness-testing checks whether a fitted procedure still behaves when the path, the window, or the assumed participant behavior is no longer the one that was tuned. A clean holdout still does not guarantee later behavior, because future dynamics can differ and the reserved window may, by chance, resemble the fitted window.

Hypothetical in-sample ledgers do not authorize an assumption of later profit. Continued ability has to be examined on unseen data, and even a pass only improves probability.

Flattering episodes are the same error

Picking a few flattering chart episodes is a narrower form of the same fitting error, because it withholds the remaining signals the identical rules would have issued. That selection is anecdotal-selection: showing only a few flattering signals while hiding the rest of the trades the same rules would have issued.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
18 of 51 in the Robustness testing track
19961-7 pp.Next on Robustness testingWalk-forward analysis belongs in the design of a mechanical trading systemA mechanical procedure must specify entries, profitable exits, and loss-cutting exits together so discretionary overrides cannot rewrite the test.
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