Which inputs does Support Resistance Reversal use?

Direct answer

Support Resistance Reversal uses inputs that let you identify (1) support and resistance levels, (2) a reversal condition that marks when price “reacts,” and (3) the rules that map those levels and the reaction into a testable description. It does not require live quotes, but it does require clear, repeatable choices about how you define levels and what counts as a reversal.

Mechanism or definition

Support and resistance are price areas where market participants previously showed buying interest (support) or selling interest (resistance). In Support Resistance Reversal, the core idea is to watch for price behavior that suggests a reaction against one of these levels. To make this concept operational, you typically treat the following as inputs:

1. Price history used to draw levels

• You select a timeframe (for example, minutes, hours, days) and a lookback window for where you will locate support and resistance.
• You choose how to convert messy candles into level candidates (for example, swing highs/lows, repeated closes around an area, or touch-and-reject behavior).

2. Level representation

• A “level” can be a single price or a price zone (a range). The width of that zone is a parameter that changes what later price action will be considered a “test” of the level.

3. Reversal event condition (the trigger) You need a defined condition for what counts as a reversal. Examples of inputs you must specify (without assuming one is always correct):

• Where the reaction happens relative to the level (touch, penetration, close back above/below).
• How many consecutive bars you require for confirmation.
• Whether you require a visible swing away from the level (a change in direction), or just a single bar response.

4. Mapping from observation to evaluation If your goal is to verify the idea, you need rules for outcomes you will measure, such as:

• The time horizon after the trigger.
• The threshold used to decide whether the price “moved away” enough to count as meaningful.

These inputs are “stable mechanics” of the concept: they define what data you use and what event you claim to observe. The specific values you pick are variable choices.

Evidence or example (how inputs become testable)

Consider a simple, self-checkable setup with explicit assumptions:

• Assumption A (levels): Use the last 60 trading sessions and mark the top 2 recurring swing-high areas as resistance and bottom 2 as support.
• Assumption B (zone): Represent each level as a zone with a fixed width (for example, a percentage band around the identified level), so that minor wicks still qualify as “touches.”
• Assumption C (trigger): Define a reversal trigger as: price touches the level zone and then closes back on the other side within N bars.
• Assumption D (evaluation): After the trigger, measure whether price reaches a pre-set distance away from the level within the next M bars.

Even without real-time data, this shows the key dependency: Support Resistance Reversal is only meaningful when you specify (i) how you drew the levels, (ii) how you define the reversal, and (iii) how you measure results.

Limitations and risks

Material limitations and failure modes come from ambiguity and market variability:

• Level misidentification: Different traders (or different algorithms) can draw different support/resistance areas from the same chart, changing the “inputs” and therefore the outcome.
• Timeframe sensitivity: A level that appears important on one timeframe may be noise on another.
• Range-bound conditions: In sideways markets, price may repeatedly touch zones without a sustained “reversal,” making the trigger definition crucial.
• Costs and execution effects: If you later convert the concept into real execution, spreads, commissions, slippage, and delays can alter realized results versus chart-based evaluation.
• Non-stationary behavior: Historical reactions to levels do not guarantee similar reactions in the future, because market conditions change.

A practical risk is confirmation bias: picking level rules and trigger rules after seeing the chart so the behavior “fits” the idea. Independent verification requires committing to rules before evaluating.

Verification or next question

To verify independently, focus on checking whether your chosen inputs are repeatable:

1. Redefine levels using a different lookback window and confirm whether triggers still occur similarly. 2) Change the zone width and confirm how often reversal conditions still meet your trigger.