Skip to main content
Track Robustness testing
51 / 51
Library

2018issue C1034-37

A critique of parameter fitting in system design

The archive treats exhaustive search of rule inputs as hindsight fitting, not a trusted procedure. The editorial reading is that system-optimization critiques the finished entry, exit, and abstention process only after walk-forward-analysis freezes the rules and robustness-testing checks a band of inputs.

  • Searching every combination of rule inputs is described as recovering the hindsight-best set, not a procedure that can be trusted on unseen data.
  • Optimization is treated as useful when inputs chosen on one data segment are then applied, unchanged, to a later unused segment.
  • Testing a band of inputs is presented as robustness-testing, which is distinct from keeping a single winning setting.
  • A bar-by-bar engine and an equity-curve constraint keep later signals tied to the live equity path, so risk control stays inside the same procedure.
Entries in this reading3 entries

Fitting recovers a hindsight-best set

The archive describes searching every combination of several rule inputs as recovering the hindsight-best set rather than establishing a procedure that can be trusted on unseen data.

Color-coded buy and sell cues that cannot be independently validated are contrasted with entry, exit, and abstention rules a trader can test on historical data as one procedure.

Freeze the rules, then test a band of inputs

Optimization is treated as useful when inputs chosen on one data segment are then applied, unchanged, to a later unused segment. Walk-forward-analysis is that step: select the inputs on one historical segment, then apply the frozen procedure to a later unused segment so the same signal process is judged after the fitting data ends.

Testing a band of input values to see whether behavior holds across that band is presented as a robustness check, distinct from keeping a single winning setting. Robustness-testing asks whether the same entry, exit, and abstention procedure still produces coherent signals across a range of inputs rather than only at one winning setting.

Let the equity path constrain later signals

A bar-by-bar engine that runs the same rules on each symbol as history advances is described as letting the live equity path affect later decisions, unlike per-symbol tests that are merged only after the fact.

Stop-losses and rules that inspect the equity curve while the test is still unfolding are listed as ways to keep risk control inside the same procedure rather than adding it afterward. An equity-curve constraint inspects the procedure's own open equity path while the test is still running and can change later entries, exits, or abstention.

Specify the rules yourself

Risk tolerance and preferred markets are described as personal enough that a self-specified rule set is preferred to adopting a generic packaged system.

A simple, familiar rule such as a moving-average crossover is recommended as a first idea to encode, test in the trader's market of interest, and refine from those results.

Reviewing how a rule set behaved in the past is justified by the claim that participant psychology is relatively stable, so similar events may draw similar reactions, while conceding that this does not always occur.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
51 of 51 in the Robustness testing track
1989Track finished · Next track: Support and resistanceA daily checklist that separates the screen from the entry24 readings
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