Support Resistance Breakout: what inputs it uses
Support Resistance Breakout is a breakout-style trading idea built around two main reference levels: support and resistance. The “inputs” are the data you use to (1) define those levels and (2) decide when price has broken out of them.
Support and resistance are not unique mathematical objects. In practice, they are created from prior price information using a chosen method. Because that method can vary, the input set for this concept is best described as data definitions plus rule parameters rather than a single fixed formula.
Mechanism: definition of the reference levels and breakout rule
Input 1: price history used to mark support and resistance
The first material input is a historical price series (commonly open/high/low/close data) over a lookback period. From this series, support and resistance levels are typically estimated using one or more of the following data-to-level mappings:
- Swing points: levels derived from recent turning points.
- Range clustering: levels derived from zones where price repeatedly interacted.
- Moving-average or channel references: levels derived from calculated trend baselines.
A key parameter here is the lookback window (how far back you examine) because it changes the resulting levels. Another parameter is the granularity of the chart (for example, how the candle timeframe affects the frequency and appearance of interactions).
Input 2: the breakout condition (a decision rule)
The second material input is a breakout condition that turns continuous price action into a yes/no event. Common categories include:
- Touch vs. cross: whether entering the level region counts or whether price must move beyond it.
- Magnitude: how far beyond the level is required.
- Confirmation: whether the condition is evaluated at close, intrabar, or after a second check.
- Time constraint: whether the breakout must occur within a certain number of bars.
These breakout parameters matter because different definitions can label the same market behavior as a breakout or as a non-event.
Input 3: handling direction and context assumptions
Support Resistance Breakout also implicitly uses assumptions about direction:
- A “bullish” breakout typically references leaving resistance upward.
- A “bearish” breakout typically references leaving support downward.
Even when direction is clear, you still need inputs that specify which side you are watching and how you treat cases where price moves between levels (for example, whether you wait for the opposite boundary or ignore such movement).
Evidence or example inputs (with explicit assumptions)
To see the dependencies, consider a concrete input setup without assuming any live data:
Assume you have daily candlestick data with these chosen parameters:
- Lookback for levels: 30 trading days.
- Support/resistance method: select the highest and lowest swing levels that appear repeatedly in that window.
- Breakout rule: a breakout is confirmed only when the daily closing price is beyond the level by at least a fixed buffer (for example, a small percentage).
- Failure rule for false breaks: treat it as a failure if price later closes back inside the original level region.
Under this example, the inputs are: the 30-day price series, the swing-detection logic, the buffer size, the “close-based” confirmation choice, and the re-entry definition. If you change any of these inputs, you change which events are labeled as breakouts.
Because these are definitional choices, you can independently verify them by re-running the same definitions on historical data and checking whether your labeled breakout events match your expectations.
Limitations and failure modes to account for
1) Levels can be inconsistent
Support and resistance are not uniquely defined. Two analysts can mark different levels from the same price series due to different lookback windows, swing rules, or zone widths.
2) Breakouts often produce false breaks
A false break happens when price temporarily crosses a level and then returns. This failure mode is a core risk for breakout-style logic. Your failure handling depends on your inputs (especially confirmation and re-entry definitions).
3) Execution reality changes outcomes
Even with the same breakout labels, real outcomes depend on non-model inputs such as transaction costs and how orders are filled. If spreads, commissions, or slippage are significant relative to your breakout buffer, the practical results can differ from the label-based logic.