Loading…

Do candlestick patterns such as the hammer predict returns against matched controls?

Candlestick Pattern Scanner (M-016). Short answer: the hub rates it NOT RELIABLE.

Data as of .

The verdict

NOT RELIABLE as a trading signal — the detector's own rigorous, correctly-clustered audit found 0 of 15 tests survive correction and 2 patterns invert — but the audit methodology itself is a model of how to do this kind of test properly.

Development summary: A rigorous 2026-07-15 audit vs a matched control (prior-move gate, trend x 200-SMA side x regime x region) found NONE of 13 patterns beat it: edges span -1.9pp to +1.3pp, 0 of 15 tests survive correction, 2 patterns invert.

What the review allows

  • As a descriptive 'what shape printed' read, exactly as the tab's own copy directs.
  • The date-clustered, matched-control audit methodology as a template for auditing other pattern-style detectors on this dashboard.

What the review rules out

  • Trade any of the 13 patterns on the edge10 numbers shown — 0 of 15 tests survive correction.
  • Read Hammer or Three White Soldiers as bullish confirmation — both measure inverted.
  • Use naive (non-date-clustered) significance on this kind of overlapping-window pattern data — it would falsely pass 6 of 13 patterns here.

What it predicts

ItemDetail
Question it answersWhich of 13 classic 1-3 bar candlestick patterns completed in the last 3 sessions, and does a matched-control audit support treating any of them as an edge?
MethodCandlestick pattern + EB pooling
How it worksQuantitative ATR(14)-unit pattern definitions with a prior-move gate -> forward 10/20-session outcome -> hierarchical empirical-Bayes pooling (pattern x 200-SMA side, own->region->global)
Inputs13 candle patterns (1–3 bars), ATR(14) body & shadow sizes, Prior-move gate, 200-SMA side, Own→region→global EB pooling
OutputPer-symbol pattern flag (completed within 3 sessions) with edge10 (measured drift in the pattern's own claimed direction)
Horizon10/20 sessions from the pattern's completion bar
Coverage~1,700-name panel (S&P 500 + Nifty + curated watchlists); symbols need >=300 bars
MarketsUS, India
Model typeModel · Rule
StageContext-only
Versionv1, first recorded 15 Jul 2026

Validation evidence

Headline results from the model's development record, as the hub publishes them.
MeasureResultCompared withNote
Tests surviving BH correction015 tested2026-07-15 audit, CIs clustered by date
Edge range vs matched control-1.9pp to +1.3pp0pp (no edge)every pattern's edge10
Autocorrelation inflation~1.7x wider standard errorsnaive (non-clustered) SEshammer's 25,485 events act like ~6,200 independent ones; naive tests would have 'passed' 6 patterns
Hammer, Three White Soldiersinvertedclaimed bullish directionslightly underperform matched post-decline/post-rally bars
The hub's standard metrics for this model class (only those the record measured).
MetricSample / windowCompared withValueRange (CI)
Cells surviving2026-07-15 audit · BH, date-clustered15 tested0n/a

What the validation review found

Is the design sound? Strong: quantitative ATR-unit definitions, a prior-move gate measured strictly before the pattern, a matched control, and date-clustered CIs to correct for overlapping-window autocorrelation — better methodology than most of this dashboard's pattern-style engines.

Backtest. 13 patterns x multiple outcome cuts = 15 tests, all against a matched control, correctly clustered by date; 0 survive. The naive-vs-clustered comparison (6 would falsely pass) is itself a useful, well-evidenced methodological finding.

Limitations

Questions

Is the Candlestick Pattern Scanner validated?
Its validation review dated 3 Sep 2026 rated it NOT RELIABLE as a trading signal — the detector's own rigorous, correctly-clustered audit found 0 of 15 tests survive correction and 2 patterns invert — but the audit methodology itself is a model of how to do this kind of test properly.
What does the Candlestick Pattern Scanner predict?
It answers: Which of 13 classic 1-3 bar candlestick patterns completed in the last 3 sessions, and does a matched-control audit support treating any of them as an edge? Output: Per-symbol pattern flag (completed within 3 sessions) with edge10 (measured drift in the pattern's own claimed direction). Horizon: 10/20 sessions from the pattern's completion bar. Coverage: ~1,700-name panel (S&P 500 + Nifty + curated watchlists); symbols need >=300 bars.
How was the Candlestick Pattern Scanner tested?
Tests surviving BH correction (2026-07-15 audit): 0 of 15; Edge range vs matched control: -1.9pp to +1.3pp; Hammer / Three White Soldiers: measured INVERTED vs claimed direction.

Source: the Model Hub's public model register, as of 6 Nov 2026. The M-016 page in the live Model Hub carries the full development and validation record, monitoring and open decisions. All 30 models and their verdicts.

Terms used on this page