Skip to main content
Track Robustness testing
31 / 51
Search the archiveLibrary
Library

2003issue C061-4

Walk-forward evaluation of locked stochastic oscillator rules

The archive frames stochastic oscillator rules as a quantitative baseline inside a complete trading-system procedure. Walk-forward analysis and robustness testing keep entry, exit, and abstention testable on later windows.

  • The stochastic oscillator is treated as a quantitative baseline whose forecast comes from ordered price, volume, or breadth observations over a defined lookback.
  • Walk-forward analysis and robustness testing keep entry, exit, and abstention as one procedure, judged over the system's holding period.
  • A recommended reliability check is to identify a strategy on one historical window and test that same locked strategy on a later out-of-sample window.
  • Archive notes repeat the same evaluation design from listed futures to an equity-index futures contract and treat parameter-sensitivity, stops, windows, and tradable choice as stages of test design.
Entries in this reading3 entries
Current trackRobustness testing58 readingsWalk-forward analysis95 readingsStochastic oscillator170 readings

A complete procedure rather than an isolated reading

Archive system-evaluation guidance is framed around designing or testing a trading system as a complete procedure rather than as an isolated indicator reading.

The supplied taxonomy treats the stochastic oscillator as a quantitative model whose output is a forecast from ordered price, volume, or breadth observations over a defined sampling interval and lookback.

Here that oscillator is the explicit quantitative baseline: a bounded oscillator built from ordered price observations over a defined lookback, whose forecast-like readings are compared with later out-of-sample results.

Walk the locked rules onto later windows

Walk-forward analysis is specified as a trading-system procedure whose output is a signal and whose horizon is the system's holding period.

It is a sequential evaluation procedure that re-estimates or re-applies a locked rule set on successive out-of-sample windows so entry, exit, and abstention remain one testable system.

The holding period is the system-defined interval from entry through exit or abstention, and it is the horizon against which robustness and walk-forward results are judged.

A recommended reliability check is to identify a strategy on one historical window and then test that same locked strategy on a later window.

That later segment is out-of-sample: a time window reserved after a rule or parameter is chosen, used to judge whether the procedure still behaves as specified.

Manugistics daily closes on the locked FVE sample

Manugistics Group (NASDAQ: MANU) slides from the mid-sixties into the mid-thirties through November 2000, then snaps partway back. These closes are read from the revised MANU1.xls worksheet Katsanos attached to the June 2003 letters — the same window on which the 22-day finite-volume rules were locked and rolled forward.
Manugistics Group (NASDAQ: MANU) slides from the mid-sixties into the mid-thirties through November 2000, then snaps partway back. These closes are read from the revised MANU1.xls worksheet Katsanos attached to the June 2003 letters — the same window on which the 22-day finite-volume rules were locked and rolled forward.NASDAQ:MANU · Daily · 2000-11-02T00:00:00.000Z to 2000-12-12T00:00:00.000Z

FVE is defined only after a locked 22-session lookback and a 0.3 percent-of-close volume gate. The June 2003 revision drops an extra illustration row so the sum is 22 sessions, not 23.

Robustness as the same testable process

Robustness testing is specified as the same class of procedure: rule inputs, market state, and execution constraints are exercised together so entry, exit, and abstention remain one testable process.

The check is whether those same inputs still produce a coherent signal when parameters, windows, or related markets change.

Parameter-sensitivity asks how much a system's signals change when a coefficient or lookback is moved inside a stated range rather than left at a single fitted value.

How the archive evolves a timing model

Related archive notes point readers to prior work that applied stochastics and other oscillators to listed futures and then repeated the same evaluation design on an equity-index futures contract.

The same notes flag out-of-sample testing, parameter-sensitivity testing, and the addition of nonprice timing inputs as explicit stages in how a timing model is evolved.

Further evaluation notes describe improving a system's test design by varying stops, trading windows, and the choice of tradables across different time periods.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
31 of 51 in the Robustness testing track
20031-3 pp.Next on Robustness testingCritiquing mechanical system design after extreme price regimesAn arithmetic price scale can make a 12.5 percent drop near a former high look larger than a 50 percent drop near the new low, while a logarithmic price scale can read a long post-collapse path as a continued downtrend.
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
By fieldSystem design117 readingsBy year2003104 readings
All 58 readings tagged Robustness testing
Also on Robustness testing5 readings
1986Degrees of freedom in trading system optimization1988Testing re-optimization calendars against random parameter controls1988Walk-forward and neighborhood tests after optimization1992Constructing forecast models with regression, walk-forward, and robustness1992Diagnose regimes before you lock parameters