Skip to main content
Track Robustness testing
52 / 57
Library

2019issue C1234-39

Noise-matched rules still need trend filters and robustness tests

TradersWeek editorial: treat a trading system as unfinished until noise class, a longer trend filter, and neighboring calculation periods are tested as one procedure for entry, exit, and abstention.

  • Short-horizon movement is treated as news-driven price noise, so directional persistence is a longer-horizon property and a long-horizon trend rule is adapted by lengthening the calculation period rather than adding complexity.
  • A 10-day efficiency ratio assigns trendier series to trend following and noisier series, including some index markets and sometimes gold, to short-horizon fade rules.
  • A longer trend filter screens short-term pattern rules, and technical divergence is taken as a brief stall in the existing trend rather than as a reversal forecast.
  • Robustness testing keeps a daily divergence only when it appears across many nearby momentum windows, and treats trend following as an allocation across several calculation periods rather than one chosen lookback.
Entries in this reading3 entries

Three choices tested as one procedure

The archive describes a historical workflow in which a trading system is not finished when a single rule is written. Short-horizon price movement is characterized as news-driven and erratic price noise, so directional persistence is treated as a longer-horizon property.

TradersWeek editorial: the design is unfinished until three choices are tested as one procedure. Those choices are which noise class the market belongs to, whether a longer trend filter allows or blocks the short-horizon rule, and whether the same signal survives neighboring calculation periods.

Assign the rule family with an efficiency ratio

A 10-day efficiency ratio, net change divided by the sum of absolute daily changes, is used to assign trendier series to trend rules and noisier series to short-horizon fade rules. That ratio is net displacement over the sum of absolute one-period moves, used to rank a series as trendier or noisier.

Strategy family is then matched to measured noise. Noisier index markets, and sometimes gold, are assigned fade rules, the short-horizon mean reversion used where prices reverse often. Quieter interest-rate markets are assigned breakout-and-hold trend following, a directional rule that stays with a measured price trend over the system holding period.

Lengthen the calculation period instead of adding complexity

As markets become more active or more volatile, the stated adaptation for a long-horizon trend rule is to lengthen the calculation period rather than add rule complexity.

An opening-range breakout is adapted to noisier sessions by scaling the first entry near a 0.1 fraction of 10-day volatility and the profit objective near a 0.7 fraction of the same measure.

Let a longer trend filter accept or block the short rule

A trend filter is a longer-horizon directional overlay that accepts, blocks, or times a shorter-horizon entry. Short-term pattern rules, including a three-day cycle, are described as more usable when that overlay screens trades and when the chosen market reverses frequently.

Price-versus-momentum divergence is framed as technical divergence: a short-lived split between price direction and a momentum oscillator inside an existing trend. The archive workflow treats that split as a brief stall inside a larger price trend, to be taken in the trend’s direction for a few days rather than as a reversal forecast.

Keep the signal only if nearby windows still agree

Robustness testing checks that entry, exit, and abstention stay consistent across nearby lookbacks, markets, or noise classes. A daily divergence setup is treated as robust only if it appears in at least half of 11 momentum windows from 5 to 15 days, and is closed when it remains in only two windows.

For trend following, robustness is described as allocating across several calculation periods instead of choosing one, because many long-horizon windows can look acceptable after the fact.

A test of standing aside before scheduled reports and re-entering afterward is described as usually forfeiting a move that continued the existing trend.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
52 of 57 in the Robustness testing track
201947-52 pp.Next on Robustness testingThree gates for evaluating a trading systemEvaluate a trading system as one procedure that jointly specifies entry, exit, and abstention, not as a collection of isolated signals.
All readings on this track · 57 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
  52. 2019Noise-matched rules still need trend filters and robustness tests
  53. 2019Three gates for evaluating a trading system
  54. 2020Data construction as a mechanical system input
  55. 2020Hidden optimization in ported relative-strength systems
  56. 2020When mechanical historical tests decay after optimization
  57. 2025Add a second procedure before you retune the first
All 67 readings tagged Robustness testing
Also on Robustness testing5 readings