Skip to content
StatePath
Tool Atlasinterpretor.bands

Tool

Bands Interpretor

interpretor.bands

InterpretorVolatility

Inputs

upperBuffer (time series)

The upper band level (out.upper from market.bands) as a price line. Becomes the upper edge used to compute %b and a ready-to-wire resistance/target level.

middleBuffer (time series)

The middle band (out.middle from market.bands), the moving-average basis. Used as the center for %b and as a mean-reversion reference level.

lowerBuffer (time series)

The lower band level (out.lower from market.bands) as a price line. Becomes the lower edge used to compute %b and a ready-to-wire support/stop level.

Outputs

Bundle (untagged)

A bundle exposing %b and bandwidth (BUFFER/SCALAR) plus the upper, middle, and lower levels as num.price SCALARs — tap one with from_port to feed a stop or target.

Bands Interpretor takes a raw Bands bundle and turns it into the values you actually trade with: %b (where price sits inside the band, 0 at the lower edge, 1 at the upper), bandwidth (how wide the band is), and clean upper/middle/lower price levels you can drop straight into a stop or target.

Bands Interpretor overview diagram

How it works

Wire the out.upper, out.middle, and out.lower sub-handles from a market.bands node into its matching inputs, and it destructures them into %b and bandwidth (BUFFER for gates, SCALAR for confidence) plus each band level as a num.price SCALAR. Project an output like the lower level via from_port='out.lower' to wire it into a CreateOrder slot.

Connects to

Reads from
Feeds into

Examples

  • Stop-loss source: project the lower band level straight into a CreateOrder SL slot for a long trade.
  • Filter gate: only enter when %b is below 0.1, meaning price is hugging the lower band.

Common mistakes

  • Wiring price itself instead of the market.bands sub-handles — it reads the three band levels, not a raw price series.
  • Forgetting to use from_port to select which band level you want when projecting an output into an order slot.

See also