Level Scope › Ours, measured
Reach threshold
Price has travelled a stated number of ATR from where the session opened. A plain, checkable event — and the one place we attach a forward probability that was measured against held-out data rather than quoted from a forum.
What it looks like on a chart
A horizontal line at the session open, drawn forward from the bar that reached the threshold.
| Timeframe | Bars of history it reads | Settings | Events, last 30 days |
|---|---|---|---|
| H1 | 240 | distance from the session open in ATR(14) H1; steps 2.0, 3.0, 4.0, 5.0 | 591 |
Not on M15, M30, H4, D1. It quotes a table built on H1. Running it elsewhere would attach an H1 measurement to another timeframe's bar — not a null claim, a false one.
What we measured
The probability comes from our own reach table, built on everything before a split date and checked against everything after it. But read it with the two limits we found when we audited our own copy: at the 24-hour horizon this detector uses, the table is not conditioned on the hour of day — the hour dimension stops at eight hours — and it has no instrument dimension at all, so all 17 instruments are pooled. Across all 1,717 events in a 90-day log, a subscriber saw exactly two numbers.
What it does not claim
And the side term is the dangerous part: the probability of a further ATR up and a further ATR down are both quoted, at the same bar, simultaneously, and they are close to each other. Reading only the one that matches your position turns a symmetric statement into a signal it never was.
Where the definition comes from
ours — reach/table.json, the shipped reach table