No saved results · Entries · 2026-09-13
Enter at D+1 (idealised) or at real-time confirmation?
What this means
This compared entering one bar after Point D with entering when the zigzag confirms D in real time. The output only went to the screen and nothing was saved. The D+1 entry is also impossible in live trading, because D is not known to be the low until later. Nothing can be concluded; a fair test would need a confirmation-only entry in TradingView, compared against a delayed or limit entry that is also achievable in real time.
The explanation is our best reading; the data shows the result but not the cause directly.
By timeframe
| Timeframe | Verdict | n | Result |
|---|---|---|---|
| 15-minute | Not tested: no saved output; 'enter at D+1' uses hindsight (D is only known at confirmation), so it is not a tradeable rule to test | ||
| 1-hour | Not tested: no saved output; 'enter at D+1' uses hindsight (D is only known at confirmation), so it is not a tradeable rule to test | ||
| 4-hour | Not tested: no saved output; 'enter at D+1' uses hindsight (D is only known at confirmation), so it is not a tradeable rule to test | ||
| Daily | Not tested: no saved output; 'enter at D+1' uses hindsight (D is only known at confirmation), so it is not a tradeable rule to test | ||
- Hypothesis
- Entering right after D beats waiting for zigzag confirmation.
- Method
- Own Python sim, yfinance 1h; Model 1 confirmation entry at D + zigzag length, Model 2 entry at D+1.
- Result
- No saved output (console only).
- How much to trust it
- Low: D+1 entry is look-ahead by construction
- Did it change the live rule?
- No.
Scripts and data for this study will be linked here when the research code is published on GitHub.
Education and research only. Not financial advice. Backtests use today's index members (survivorship bias).