Student Wyckoff LBC: keep the selected and calculated ranges aligned
Record range boundaries in timestamps and preserve the context needed to compare two calculation sessions.
Published: (UTC+3)
Русский · English · Deutsch · Español · Français · Italiano · 繁體中文 · 日本語 · 한국어
A range setting matters because it changes what part of the data is being investigated. Use the current LBC and range guide for the product workflow, then keep a session record that explains the actual boundaries used. Do not infer those boundaries solely from a cropped screenshot.
Record file coverage and selected coverage
Write the first and last timestamps of the available data. In a separate field, write the range you selected for the task. Record the relevant range-control state as shown in your version, without inventing a universal numeric setting.
If the calculated or displayed result uses a distinguishable range, record that range too. Verify it from the actual working result and documentation rather than assuming every boundary is identical.
Keep coordinates tied to the same price bars
When comparing a saved result with a new session, use timestamps and the same data source to identify the price bars. A price bar index or a screen position can change when earlier history is added or the view is moved.
Keep timeframe and timestamp convention with the coordinates. The same printed clock time on two differently interpreted datasets does not necessarily identify the same observation.
Compare one range change
In an invented exercise, keep the right boundary fixed and change only the selected left boundary. Save the original state before calculating the revised one. Compare which higher-degree wave context and turning points change.
Treat the second result as a different range experiment. A changed output is not, on its own, proof of a software defect or proof that the revised wave interpretation is structurally correct.
Finish with an explainable record
Keep the source file reference, available coverage, selected coverage, relevant control state and result together. If a boundary cannot be verified, mark it unknown rather than filling it from memory.
The linked range and first-calculation guides supply the product context. This article is a manual recording exercise and does not wave hypothesis an undocumented implementation rule for LBC.
Earlier history was added and a price bar index changed. What should anchor the comparison?
Use the preserved source context, timeframe and timestamps to identify the same price bars. Do not rely only on the old index or screen position.