TradingView Elliott wave count indicator: compare the same price series first
Check chart type, session and loaded history before attributing a disagreement to a wave algorithm.
Published: (UTC+3)
Русский · English · Deutsch · Español · Français · Italiano · 繁體中文 · 日本語 · 한국어
Two Elliott wave outputs can disagree because they received different price observations. When comparing a TradingView indicator with a separate analysis workflow, begin with data parity: whether the two inputs actually describe the same instrument, intervals and prices.
Match the identity of the chart
Record the full symbol with its exchange or provider, interval and chart type. A transformed chart is not interchangeable with ordinary candles merely because the displayed symbol is similar. Also record applicable session and adjustment settings rather than assuming that identical ticker text means identical data.
Compare source rows
Choose several completed price bars around the proposed turning points. Match timestamps and OHLC values, not just the visual outline. In an invented comparison, one series has a high of 120 and the other 119 at the same nominal time. The observations are already different before any wave label is calculated.
Check the actual history window
TradingView states that chart-data export uses loaded chart data. Verify the first and final exported observations and compare them with the separate workflow. If one tool starts later, write down the difference rather than treating the two analysis windows as equivalent.
Only then compare interpretations
Once the input differences are understood, compare the model assumptions and outputs. Student Wyckoff Pro has a supported own-CSV workflow; that is distinct from running a TradingView indicator. An input comparison does not demonstrate that the two programs share an algorithm or should produce identical wave interpretations.
The two sources disagree on a turning-point high. Is the wave algorithm already proven faulty?
No. First resolve or document the source difference. Different inputs prevent a clean comparison of the algorithms.