2012issue C048-11
Dated wave and ratio cases need a later-sample test
A reader who had already fitted a weekly-close stock model asked whether adding more names from 2000 forward under the same rules would count as unseen data. The archive reply split that question into a development-sample replay and a later-sample run of unchanged rules, which is the discipline a dated elliott-wave or fibonacci-retracement case needs.
- A development-sample test reruns a system on the historical set used to build it. A later-sample test runs those unchanged rules on data they had not previously seen in the same market and time frame.
- An elliott-wave count and a fibonacci-retracement grid become dated case files only when a case-checkpoint is attached before unused bars print.
- A manufactured-technical-picture can look decisive when a large participant forces the pattern, so locating event patterns is not a complete allocation answer.
- A long-cycle-wave still needs a nearer case-checkpoint that says whether a correction is routine or a thesis break.
The later-sample question
A reader who had already fitted a weekly-close stock model asked whether adding more names from 2000 forward and applying the same rules would count as a test on unseen data.
The editorial reply treated a development-sample test as rerunning a system on the same historical set used to build it. It treated a later-sample test as running those unchanged rules on data they had not previously seen in the same market and time frame.
A gold analog that matched only in point distance
One gold-market letter said a 2011 advance matched a late-1970s peak only in point distance and differed in the other market characteristics the writer cited. That letter also argued that dominant bullion-market institutions could generate almost any desired technical picture.
A reply on gold chart work said reading charts and locating event patterns is not a complete answer for every allocation decision. The same reply described the presented gold technical discipline as aiming to capture a large share of a large move rather than nearly the whole path of every major swing.
A long-cycle-wave still needs a case-checkpoint
A reader returned to a late-2008 long-cycle-wave discussion that had suggested share accumulation around 2010. The reader asked whether a major 2012 pullback should be avoided or whether a fully invested stance through 2016 was the intended path.
The wave-piece author replied that a correction was expected, was not described as severe, that the projected advance ran through 2016, and that a presidential cycle was said to line up with that long wave.
Editorial reading: file the count, then wait
This section is editorial, not archive attribution. TradersWeek treats an elliott-wave as a labeled swing sequence taken from price structure so a later bar can confirm or break the count. It treats a fibonacci-retracement as a ratio grid drawn on a completed swing to mark pullback zones that later price can hold or reject. Neither is a finished forecast in this reading.
Editorial view: a case-checkpoint is a calendar date attached to that wave or ratio call so a later reader can see what would have counted as a miss. Lock the structure and the invalidation before unused bars print. Then let a later-sample of the same market and time frame decide whether the case still stands.
Editorial view: the gold letter's claim that dominant institutions could generate almost any desired technical picture is the manufactured-technical-picture risk. Chart reading and event patterns, in the archive reply, were not a complete answer for every allocation decision, and the stated aim was a large share of a large move rather than nearly the whole path of every major swing. The 2012 pullback question is the nearer case-checkpoint on the long-cycle-wave: whether a correction is routine or a thesis break.
Editorial note: the archive does not report whether those later stretches confirmed or broke the cases. It records how the questions were framed.
All readings on this track · 26 readings
- 1984Three-gate confirmation for wave, ratio, and cycle turns
- 1988Triaging Elliott wave counts with weekly stochastic divergences
- 1989Dominant-cycle phase flips as regime tests
- 1989Audit signals against elasticity regimes
- 1990When wave counts fail the exclusion test
- 1991Evaluating hourly DJIA growth-rate and velocity attractors
- 1996If a terminal fifth is rewritten, fail the first count
- 1998Mapping industrial-average swings with Fibonacci growth and retracements
- 1999Define the stop before the wave or the divergence
- 2001Form-first Elliott wave construction with phi
- 2006Wave count, channel floor, and Fibonacci bands after a correction
- 2007Impulse and correction as a recursive fractal recipe
- 2008Gold-silver ratio as a shoreline wave
- 2008A daily chart trend filter with Elliott wave abstention
- 2010Revising Elliott wave counts with RSI and stochastic guides
- 2010Constructing corrective-wave hypotheses with Fibonacci retracements
- 2011Pre-commit the wave-and-ratio stop before entry
- 2012Dated wave and ratio cases need a later-sample test
- 2013Keep a 1-2-3 count only while zigzag, Fibonacci depth, and divergence still agree
- 2014Elliott-wave target versus the option bid-ask
- 2014A three-layer classroom on one daily futures chart
- 2015Elliott wave classifies the swing; trend following holds the trade
- 2016Constructing wave labels and retracement zones from chart structure
- 2017Sector ETF pairs in quiet regimes
- 2017A policy-shift case that tested a delayed long-cycle wave count
- 2018One role each for wave, Fibonacci, and stochastic