Tool
S/R Level (state / anchor)
interpretor.sr_level
Inputs
The S/R info bundle from market.sr_levels — the detected support and resistance levels with their touch counts, strength and lifecycle state.
Outputs
An interpreted S/R bundle: the gated level plus level_price, broken_level_price and confidence SCALARs ready to wire into ORDER_EXIT.
The state/anchor node for support/resistance — it answers 'is there a strong level here right now?'. It reads the info bundle from market.sr_levels and keeps only the levels that pass your gate on touch count, strength, or lifecycle. It then projects the level price, any broken-level price, and a confidence value as ready-to-wire values for your order.
How it works
Wire the sr_levels 'info' handle in and pick a mode; the node gates the level and exposes level_price, broken_level_price, and confidence as SCALARs that drop straight into ORDER_EXIT. Use this for the level state and use interpretor.sr_event for the breakout/bounce/retest trigger.
Modes
Mode options
Keep only levels touched between min_touches and max_touches times — more touches means a better-tested level.
When to use: When you want levels validated by repeated tests, not one-off reactions.
Keep only levels whose strength score reaches strength_threshold — the higher the score, the more significant the level.
When to use: The default gate when you want to trade only meaningful, high-quality levels.
Keep only levels that have reached the maturity floor set by require_lifecycle.
When to use: When you want to admit levels purely by how confirmed they are, ignoring touch and strength.
Pick the single level closest to current price.
When to use: When you only care about the level price is about to interact with right now.
Require lifecycle options
Admit levels at any maturity, including unconfirmed ones that may still repaint.
When to use: Only when you want every candidate level and accept repaint risk.
Admit only levels that are fully formed.
When to use: A first guard against half-formed levels while still acting early.
Admit only confirmed, tradeable levels — a confirmed breakout or a retested level — the safe default.
When to use: The recommended floor; admits only levels solid enough to trade.
Admit only levels that have been retested and held — the strictest maturity.
When to use: When you want maximum confirmation and accept fewer levels.
Configuration
Which level gate to apply: touch_count_filter (by number of touches), strength_filter (by strength score), lifecycle_filter (by maturity), or nearest_level (the closest level).
The minimum number of touches a level must have to match, used in touch_count_filter mode.
The maximum number of touches a level may have to match (-1 means no upper limit), used in touch_count_filter mode.
The minimum strength score a level must reach to match, used in strength_filter mode.
Admits only levels at or past this maturity: any, completed, tradeable (the default, confirmed breakout or retested), or retested; this is the guard against repaint-prone levels.
Off fires on the active-level bar; on fires on later bars using the carried-forward snapshot.
Connects to
Examples
- Use strength_filter mode as a filter so trades are only allowed near a level above your strength threshold.
- Wire the projected level_price into ORDER_EXIT to set a take-profit at a strong resistance level.
Common mistakes
- Expecting this node to fire on a breakout — it reports a level's state, not an event; use interpretor.sr_event for triggers.
- Setting require_lifecycle to 'any', which lets in unconfirmed levels that may still repaint.