# Why Range Versioning Matters Slug: why-range-versioning-matters. Canonical: https://tradingtune.com/blog/why-range-versioning-matters ## Summary Explains how changes to boundaries, steps, and included inputs should be tracked across runs. ## Key facts - A change to a boundary, a step, or an included input creates a new experiment, so each run needs a record of exactly what it tested. - The step size matters as much as the endpoints, because a coarser step can hide the region where a parameter stops generalizing. - A tighter, smoother result can come from quietly narrowing the range or dropping an input rather than from a setting that generalizes better. - A version tag is only useful when it is written before the run starts, not after the result looks interesting. ## Outline - Why Tracking Parameter Range Changes Keeps a Sweep Honest (#why-tracking-parameter-range-changes-keeps-a-sweep-honest) - Defining the Swept Parameters and the Walk-Forward Split (#defining-the-swept-parameters-and-the-walk-forward-split) - How Sweep Behavior Shifts When a Range Boundary Moves (#how-sweep-behavior-shifts-when-a-range-boundary-moves) - A Versioned Range Log for the Smart Momentum Grid (#a-versioned-range-log-for-the-smart-momentum-grid) - When an Unversioned Range Change Creates an Overfit Illusion (#when-an-unversioned-range-change-creates-an-overfit-illusion) - Applying Range Versioning to Your Own Sweep (#applying-range-versioning-to-your-own-sweep) - Range Versioning as a Habit, Not a One-Time Task (#range-versioning-as-a-habit-not-a-one-time-task) - Sources (#sources) ## Code snippets - Anchor: #pine-snippet-1