Settings

This page is for the reader who is about to change an input and wants to know what that change costs and what it buys. Inputs are ranked by how much they change the read, not by their order in the settings panel. Tier A inputs change the pane's meaning. Tier B inputs change what the structure features report. Tier C inputs are cosmetic or power-user.

Every input row carries the default, the practical range, a one-sentence description of what it does, and where applicable a misuse line naming the most common wrong reading. The misuse lines are not padding. They are the sentences that would have saved a real reader a real hour of debugging had they been read first. If you are tempted to skim them as disclaimers, read them as the findings of a careful user who already got confused by the dial you are about to touch.

None of this is a ranked recommendation. "Push this dial in this direction, expect this cost" is the whole teaching posture, and it applies to every row. The only numbers called out as load-bearing are the defaults, and they are defaults because they are legible on first contact — not because they are optimal for your instrument, your timeframe, or your regime.

A few facts bind this entire page before any row matters:

• The script runs in a separate pane below price with a fixed 0..100 vertical axis. Hard clamps at every stage make sure no plotted series ever exits that range.

• Defaults were chosen to be legible at first contact on an intraday chart. They are not claims that the defaults are optimal.

• Several inputs interact. The dependency subsection at the end of this page names the pairs worth holding together in your head.

• The Pro MA library is doing real work on every slot and on every blend-derived feature. The Power User blocks only matter when you have selected an MA family whose behaviour is tunable beyond length alone. Most readers never need them.

Tier A — changes the read fundamentally

These inputs decide what the pane is saying. Touch any of them and the meaning of the blend changes.

Enable Stoch 0X

• Pine line: 198, 212, 226, 240, 254.

• Defaults: true, true, true, false, false.

• What it does: Runs the slot. A disabled slot does not run, does not plot, does not alert, and does not contribute to the blend.

• Misuse: Toggling slot 04 or 05 on while leaving its weight at the default 0. The slot now runs and fires per-slot alerts but contributes zero to the blend. If you want slot 04 in the blend, enable it and raise its weight above zero.

Blended Weight

• Pine line: 208, 222, 236, 250, 264.

• Defaults: 33.3, 33.3, 33.3, 0.0, 0.0.

• Range: non-negative numbers.

• What it does: Sets this slot's weight in the weighted-mean blend. The blend divides the weighted sum by the total active weight, so weights are relative, not absolute. Scaling every weight by the same factor produces the same blend.

• Misuse: Assuming weight zero means "slot off." Weight zero silences the slot's contribution to the blend, but the slot still runs, still draws its K line if Hide Plot is off, and still fires per-slot alerts. For a real kill switch, use Enable Stoch 0X = false.

TimeFrame

• Pine line: 201, 215, 229, 243, 257.

• Defaults: "5", "15", "60", "", "".

• Range: any valid TradingView timeframe string. Empty inherits the chart timeframe.

• What it does: Runs this slot at a higher timeframe than the chart, via request.security. Empty means "use chart TF."

• Misuse: Setting a slot's timeframe below the chart timeframe. The script throws a runtime error — "Stoch 0X timeframe cannot be lower than the chart timeframe." — and the indicator stops. Move the chart down to a timeframe the slot can legally read, raise the slot to the chart timeframe or higher, leave the slot empty to inherit chart TF, or disable the slot.

Optional Ticker

• Pine line: 209, 223, 237, 251, 265.

• Defaults: "" (chart symbol) on all five slots.

• What it does: Runs this slot on a different symbol. The slot reads its Source on that other symbol, not on the chart's symbol.

• Misuse: Pointing at an illiquid or session-mismatched symbol and treating the resulting slot read as equivalent to the others. The divergence module still compares chart-price pivots against blended K, so the blend is a mix of chart-context and cross-symbol context. Legitimate, but only if you know what you are doing with the mix. See the workflows page, Pattern B.

On Bar Close? (per slot)

• Pine line: 358, 370, 382, 394, 406.

• Default: true on all five slots.

• What it does: Controls whether the slot returns confirmed values (the previous bar's K/D, [1] shift) or live values (the currently forming bar's K/D). Combined with lookahead_on on the underlying request.security call, the true / [1] pattern is the documented safe way to pull HTF values without painting the future into historical bars.

• Misuse: Mixing true and false across enabled slots. The blend now averages a confirmed series and a live series together. Alignment counts compare posture states drawn from different temporal frames. The mtf-and-repainting page teaches the mixed-posture failure mode in depth; read it before you flip this on a single slot in isolation.

Plot Blend

• Pine line: 272.

• Default: true.

• What it does: Draws the blend K and blend D lines and the fill between them.

• Misuse: Turning off without realising the pane is now left with only hidden slots and structure overlays. The screen looks broken because the hero line is gone.

Divergence block: Show Div, Pivot Len, Plot On Pivot?

• Pine line: 290, 291, 292.

• Defaults: true, 20, false.

• What they do:

• Show Div turns the divergence module on or off. When off, no triangles draw and the two divergence alerts cannot fire.

• Pivot Len is the symmetric left and right lookback for ta.pivotlow and ta.pivothigh. A pivot is only confirmed n bars to the right of the actual pivot.

• Plot On Pivot? back-shifts the triangle's drawing to the original pivot bar. It does not back-shift the alert timing. The alert still fires at the confirmation bar.

• Misuse:

• Lowering Pivot Len to 3 or 5 to "see more divergences." The resulting triangle spam is not more signal; it is looser pivots. Default 20 is already short enough that confirmation takes work on a slow chart.

• Treating a Plot On Pivot? marker as evidence you could have acted on at that earlier bar. The triangle was not visible at that bar when the bar was printing; the drawing is shifted after the fact. This is an honest visual of where the geometry sits, not an honest visual of when you could have known.

Tier B — changes the structure read

These inputs change how the structure features behave on top of the blend. Touch them and the four structure features shift — sometimes all of them, because they share the same input series.

Overbought Level and Oversold Level

• Pine line: 268, 269.

• Defaults: 80, 20.

• Range: any float in the 0..100 range, user-positioned.

• What they do: Position the dashed overbought and oversold guide lines. In the current source, these values only move the guide lines. They do not drive alerts, plot colors, or any hidden overbought/oversold logic.

• Misuse: Moving to 70/30 to match RSI convention and expecting the tool's behavior to change beyond the guide placement. The default 80/20 is the classical stochastic convention. The indicator does not break at 70/30, but the code treats those levels as reference lines, not decision rules.

Show Keltner + KC Length + KC Mult

• Pine line: 295, 296, 297.

• Defaults: false, 20, 2.0.

• Range: bool, positive int, non-negative float.

• What they do: Turn on the Keltner envelope drawn around the blend's MA basis. KC Length is the range-EMA window; KC Mult scales the envelope's half-width. See the Keltner basis inputs below for the MA basis itself.

• Misuse: Reading a Keltner touch on the oscillator as "price is overbought." The envelope wraps the blended K — it measures the blend's stretch against its own recent range, not price's overbought/oversold condition. Use the 80/20 guides for oscillator-level overbought/oversold reference zones, not the Keltner bands.

Keltner basis and styling: Basis Type, Basis Len, Show Basis, Show Fill, Line Width

• Pine line: 298, 299, 300, 301, 302.

• Defaults: EMA, 20, false, true, 2.

• What they do: Pick the MA family and length for the envelope's basis. Toggle the middle basis line. Toggle the translucent fill. Control line thickness. The fill opacity is fixed in the source.

• Note: Basis Len and KC Length are independent. Basis Len drives the midline MA. KC Length drives the range EMA. Matching them is a stylistic choice, not a required one.

Show BBWP + BBWP Length + BBWP Lookback + BBWP Threshold

• Pine line: 305, 306, 307, 308, 309.

• Defaults: true, 20, 252, 50.

• Range: bool, positive int, positive int, 0..100.

• What they do:

• Show BBWP enables the histogram columns at the bottom of the pane.

• BBWP Length sets both the Bollinger basis length and the standard-deviation window — the script intentionally couples them so the BBWP is a matched-length Bollinger width. Changing the length changes both pieces.

• BBWP Lookback is the number of prior widths the current width is ranked against. The current column height is the percentile rank of the current width inside that lookback.

• BBWP Threshold picks the percentile where columns switch from blue below the threshold to aqua at or above the threshold.

• Misuse: Reading BBWP as price volatility. These columns measure the blended K oscillator's Bollinger width percentile, not price's. A low BBWP column can print on a choppy, range-bound session because the blend itself has been compressed by its own history. The correlation between oscillator-BBWP and price volatility is real in some regimes and broken in others; do not substitute one for the other.

Show DC + DC Len + DC Basis Type + DC Basis Len

• Pine line: 312, 313, 314, 315.

• Defaults: true, 20, SMA, 1.

• What they do:

• Show DC turns the Donchian steplines on or off.

• DC Len is the lookback for the highest and lowest of the blended K.

• DC Basis Type and DC Basis Len control the optional MA on the Donchian midpoint. Basis length 1 is a passthrough — the midpoint is the raw midpoint unless you raise the length above 1.

• Misuse: Reading the steplines as chart-price highs or lows. They are the highest and lowest the blended K has reached. Donchian here is entirely an oscillator-space construction.

Master smoothing: Enable Smoothing, Smooth Type, Smooth Len

• Pine line: 277, 278, 279.

• Defaults: false, EMA, 3.

• What they do: Apply a single smoothing pass to both blend K and blend D after the weighted mean. The resulting series is the one every structure feature reads from, so enabling master smoothing changes BBWP, Keltner, Donchian, and divergence too.

• Misuse: Enabling "to fix" choppy blend-based alerts. Smoothing adds lag to every downstream consumer. Divergence confirmations arrive later. The calmer plot is often worse information, not better. Per-slot alerts are unaffected because they evaluate the slot's K vs D, not the smoothed blend.

Tier C — slot-level knobs, styling, and Power User blocks

These inputs do not change what the pane means; they change the slot's shape or the visible styling. Included for completeness so a reader hunting a specific input finds it without grepping the script.

Per-slot stochastic pipeline

Slots 01 through 05 each expose the same stochastic-pipeline inputs. Defaults are identical across slots, so a single table below covers all five. Pine line citations are for slot 01; the corresponding inputs for slots 02–05 live at offsets of 14 lines per slot starting from line 198.

Blend styling

Structure feature styling (Keltner, BBWP, Donchian)

Each feature's styling — line width, basis toggle, fill toggle, and column threshold colours — is available in its own input group and maps 1:1 to visible changes. Fill opacity itself is fixed in the source. These are the least likely controls to cause misreads. Read the feature description on the visuals-and-logic page once, then tune styling to taste.

Power User blocks

Pine lines 321–352 (feature-level) and 358–475 (slot-level _PU groups). These blocks expose MA-family-specific parameters for families whose behaviour is not fully captured by length alone: ALMA offset and sigma and floor, KAMA fast and slow, FRAMA fast and slow, Jurik phase and power, Laguerre alpha, VAMA volatility length. A few principles govern when to touch them:

• These blocks only affect the compute when the paired MA family is selected. Setting K Type to SMA and then tweaking ALMA offset does nothing; you have to pick ALMA first.

• If you cannot finish the sentence "I am changing this block because I expect X to happen, and I will verify X by looking at Y," close the Power User block and come back later. Tuning without a test builds confusion, not edge.

• Cross-reference the Axiom MA Library Pro manual pack for the individual family internals. That pack teaches what each family is for and how each Power User parameter changes its shape. This settings page does not re-teach the families.

Dependency pairs worth holding in your head

These pairs interact in ways that regularly trip up readers. The pattern is always the same: two inputs share a surface or a label that implies they do similar things, and then they behave differently when you change one without the other. Note each pair once and you will recognize the symptom the next time it happens instead of spending an afternoon on it.

Hide Plot vs Enable Stoch 0X. Hide Plot affects visibility. Enable affects whether the slot runs. The default config uses Hide Plot = true on three enabled slots so the pane stays clean without sacrificing the blend.

Blended Weight = 0 vs Enable Stoch 0X = false. Weight zero silences the blend contribution; the slot still runs, still plots if shown, and still alerts. Enable false turns the slot off entirely. The visual effect on the blend line can look identical — only one of the two is a kill switch.

BBWP Length drives two things. The same input length is used for the Bollinger basis and for the standard-deviation window. That is a deliberate design choice, called out in the code at the construction site, to keep the BBWP as a matched-length Bollinger width. Changing Length changes both pieces at once.

DC Basis Len = 1 is a passthrough. The default Donchian setup does not smooth the midpoint. Raise DC Basis Len above 1 and you are smoothing the midpoint only; the upper and lower steplines are still the raw highest and lowest of the blended K.

KC Basis Len vs KC Length. Two independent lengths. Basis Len drives the midline MA. KC Length drives the range EMA. Matching them is common but not required, and the two control very different behaviours.

Master smoothing touches every structure feature. When you enable master smoothing, you are changing the input series that divergence, Keltner, BBWP, and Donchian all read from. Their output shifts together. This is one of the clearest places the "four structure features share an input" fact becomes visible.

Source vs the stochastic range. ta.stoch(src, high, low, n) always uses bar high and bar low for the range denominator. Source only changes where inside that range the current bar's value is placed. If you change Source and the K line barely moves, that is not a bug — it is the range denominator refusing to change.

Where to go next: Visuals and logic to see what each knob actually changes about the pane's story, MTF and repainting before you change any slot's On Bar Close?, Workflows for three configurations a working trader can actually run, For the geeks if you want the pipeline math behind these inputs.