# How To Decide Which Inputs Stay Enabled Slug: how-to-decide-which-inputs-stay-enabled. Canonical: https://tradingtune.com/blog/how-to-decide-which-inputs-stay-enabled ## Summary Shows how to keep the most relevant inputs active while leaving unclear controls fixed. ## Key facts - Keep an input enabled only if you have a stated hypothesis for why it should matter, and pin the unclear controls at a default. - Every extra input multiplies the search space and the risk of overfitting, so pinned controls keep the sweep readable. - Look for a plateau of neighboring values that behave alike, because a narrow spike is usually luck in one stretch of data. - Check each enabled input on a later unseen window before you trust it. ## Outline - Deciding Which Inputs Stay Enabled In A Parameter Sweep (#deciding-which-inputs-stay-enabled-in-a-parameter-sweep) - Setting Up The Sweep: Parameters, Ranges, And The Walk-Forward Split (#setting-up-the-sweep-parameters-ranges-and-the-walk-forward-split) - What Changes Across The Search Space As You Move Each Input (#what-changes-across-the-search-space-as-you-move-each-input) - Illustrative Data: Reading A Sweep Table (#illustrative-data-reading-a-sweep-table) - An Edge Case: When An Enabled Input Looked Right And Wasn’t (#an-edge-case-when-an-enabled-input-looked-right-and-wasnt) - Applied Next Step: A Working Rule For Search Space Management (#applied-next-step-a-working-rule-for-search-space-management) - Practitioner Conclusion: Keep The Search Space Honest (#practitioner-conclusion-keep-the-search-space-honest) - Sources (#sources) ## Code snippets - Anchor: #pine-snippet-1