Elliott wave analysis software: audit a result before trusting it
Build a compact evidence record that connects an input chart, a proposed wave interpretation and the checks you actually completed.
Published: (UTC+3)
Русский · English · Deutsch · Español · Français · Italiano · 繁體中文 · 日本語 · 한국어
An analysis result becomes reviewable when another session can reconstruct what was examined. Save the input conditions and the reasons for accepting or rejecting the interpretation. A label such as wave 3 is a conclusion to inspect, not its own supporting evidence.
Create an input record
Use a plain record with instrument, data source, timeframe, first and last timestamps, file name and calculation date. Record the selected analysis range separately from the full file coverage. These fields prevent two different datasets from being treated as the same experiment.
For example, two files can have the same instrument name while one contains an extra month of history. If their outputs differ, first check that difference before attributing the change to the counting method.
Connect each wave hypothesis to evidence
For each candidate, record the proposed pattern and the coordinates of its main turning points. Distinguish price relationships that you checked from internal subdivisions that still need examination.
A candidate can pass one boundary check while lacking enough internal detail to establish the complete pattern. Mark that specific gap. Do not turn a partial check into an overall verified status.
Test repeatability without changing the question
Keep the original file intact. Repeat the review with the same input and selected range. If you change a setting, change one item at a time and record it so that you know which comparison you are making.
If a difference remains unexplained, retain both records and classify the cause as unknown. The aim is an honest audit trail, not a forced declaration that one image must be correct.
Write a limited conclusion
A useful conclusion says which data and candidate were reviewed, which checks passed and which questions remain. Keep any trading decision separate: the software review does not determine personal position size or an order.
Use the first-calculation guide for the working sequence and the alternatives guide for comparing interpretations. This article describes a manual review record; it does not wave hypothesis an automatic audit report is built into the software.
Two screenshots have different wave labels. What should you compare first?
Compare their source data, timestamps, selected range and settings. Without matching inputs, the screenshots do not isolate a disagreement in interpretation.