Skip to main content
Track Robustness testing
38 / 51
Library

2011issue C0316-23

Session-split evaluation of regular and overnight systems

A session-split procedure treats regular hours and overnight hours as separate systems rather than one continuous bar. Editorial view: score entry, exit, and abstention rules on the session that produced the result.

  • A session-split procedure treats regular hours and overnight hours as separate systems rather than one continuous bar.
  • Overnight change is next-session open minus prior close. Regular-session change is close minus open.
  • Constituent names can prefer one session and lose in the other, so basket-level results do not validate a single holding-period rule.
  • Editorial view: treat each session as its own testable procedure so entry, exit, and abstention rules are scored on the session that produced the result.
Entries in this reading3 entries

Separate systems by session

A session-split procedure treats regular hours and overnight hours as separate systems rather than one continuous bar.

How session change is defined

Overnight change is defined as next-session open minus prior close. Regular-session change is close minus open.

Why basket results are not enough

Constituent names can prefer one session and lose in the other, so basket-level results do not validate a single holding-period rule.

QQQQ overnight-session cumulative change

A trader scoring overnight hours as their own book would have seen QQQQ add dollars from 2004 into 2010, give back about six dollars in the 2008–09 break, then make new highs—unlike the full-price crash. Points were read from the article’s overnight running-performance figure using its dollar scale, with the stated $6.01 overnight loss between 31 October 2007 and 9 March 2009 as the interior anchor.
A trader scoring overnight hours as their own book would have seen QQQQ add dollars from 2004 into 2010, give back about six dollars in the 2008–09 break, then make new highs—unlike the full-price crash. Points were read from the article’s overnight running-performance figure using its dollar scale, with the stated $6.01 overnight loss between 31 October 2007 and 9 March 2009 as the interior anchor.QQQQ · Overnight session · 2004-01-01T00:00:00.000Z to 2010-09-30T00:00:00.000Z

The raster is cropped and unlabeled; readings are nearest-dollar. The $0–$30 vertical scale and the $6.01 crisis giveback come from the article, not from pixel counting alone.

Test each session as its own procedure

Editorial view: System optimization, Walk-forward analysis, and Robustness testing should be applied to each session as its own procedure. That keeps the test aligned with the session that produced the result rather than with one continuous bar.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
38 of 51 in the Robustness testing track
201210-11 pp.Next on Robustness testingWalk-forward evaluation as operator rehearsalAn evaluation that shows only in-sample historical results is treated as incomplete unless it also includes a substantial walk-forward run on previously unused data.
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