Settings

This page is the single reference for every input Axiom MA ships. It is organised by slot lifecycle rather than by the order TradingView happens to list the controls in: first what the slot does on and off, then where...

Written By Axiom Admin

Last updated 22 days ago

Settings

This page is the single reference for every input Axiom MA ships. It is organised by slot lifecycle rather than by the order TradingView happens to list the controls in: first what the slot does on and off, then where it reads from and when, then how it shapes itself, then how it presents, then how it contributes to the blend. Blended-group inputs and the one global control follow.

Before the catalogue, a banner that belongs at the very top of any MA reference on this tool.

Length: is not Trend Length:

Two inputs, two different jobs. They have similar names and sit next to each other in the inputs dialog. Confusing them is the single easiest misread on this tool, and it is the one most likely to change the colour of a line you are about to base a decision on.

  • Length: is the MA's smoothing window. It drives the moving-average calculation itself. A larger Length: smooths more and lags more; a smaller Length: smooths less and tracks the price series more tightly. This input does not, on its own, decide whether the slot reports up or down β€” it decides what the slot's line actually is.

  • Trend Length: is the rising-versus-falling comparison. It decides the slot's trend state by comparing the current MA value against the MA value from Trend Length: bars ago on the slot's own timeframe. Up when the current MA is greater than or equal to the past MA, down otherwise. The trend state drives the slot's line colour (up-state vs. half-opacity down-state) and the per-slot trend alerts. It does not change the MA itself at all.

One source-truth caveat: SWMA is fixed-length in the Lite library, so changing Length: does not change the smoothing window for that MA type. The length explanation below applies to the length-based types: SMA, EMA, RMA, WMA, and VWMA.

A worked example makes the split concrete. Imagine Slot 01 at SMA, Length: 20, Trend Length: 3, on a 5-minute timeframe.

  • Change Length: from 20 to 50. The MA is now a 50-bar smoothing of price on 5-minute bars. The line on the chart moves to a different trajectory β€” generally slower, generally further from price. The trend state may or may not flip as a side effect of the new line having a different value now versus three bars ago.

  • Instead, change Trend Length: from 3 to 20. The MA itself does not change β€” the 20-bar SMA is still the 20-bar SMA. What changes is the comparison window that decides the line's colour. The slot is now deciding up-versus-down by comparing the MA to its value twenty bars ago. The line's shape on the chart is identical; the colour rule is slower.

Two practical consequences to keep on hand:

  • Shortening Trend Length: makes the slot flicker more often. Its line can flip colour from one bar to the next, and per-slot trend alerts become noisier. Lengthening Trend Length: asks the slot to move more before it is willing to call a change. None of that has anything to do with how much the MA itself smooths the price series.

  • Changing Length: changes the MA itself. It will also indirectly change the trend state if the new MA crosses its own past value differently, but that is a downstream consequence, not the input's job.

Every per-slot entry below implicitly links back to this banner. Other pages in this pack refer you here rather than repeat it.


Per-slot inputs (three slots total: MA 01, MA 02, MA 03)

Each slot has the same set of inputs. The defaults below are the shipped Base defaults. Slots 01, 02, and 03 are configured identically except that their default timeframes are 5, 15, and 60 minutes respectively.

Enabling and hiding

Input

Type

Default

What it changes

When you might change it

Misuse warning

Enable MA NN

boolean

on

Turns the slot fully on or off. A disabled slot contributes nothing: no line, no trend colour, no blend contribution, no per-slot alert, no entry into the alignment alerts.

Drop to a two-slot read; isolate a single slot to inspect its behaviour; temporarily silence a slot whose current configuration you are not ready to trust.

Disabling a slot also drops it from the alignment alerts. If you expect "three-of-three" after disabling Slot 03, you will be surprised.

Hide MA NN Plot

boolean

off

Hides the slot's line on the chart. The slot is still computed, still in the blend (if its weight is non-zero), still in the per-slot trend alert, and still counted in the alignment alerts.

The slot is useful in the blend or in alerts but visually crowds the chart; building an alerts-only workflow; reducing clutter without losing information.

Hidden is not excluded. If you mean "out of the blend," set Blended Weight: to zero. If you mean "out of everything," toggle Enable MA NN off.

The difference between Enable MA NN off, Hide MA NN Plot on, and Blended Weight = 0 is the single most productive distinction to hold in your head when configuring this tool. Visuals & Logic reinforces it on-chart; Workflows shows you the routine each state is actually good for; Alerts shows how each state interacts with the ten alert conditions.

Alignment qualifier: hidden slots still count only after their MA value is non-na. The source checks Enable MA NN and not na(slotNNValue) before adding a slot to the active alignment count.

Where and when the slot reads

Input

Type

Default

What it changes

When you might change it

Misuse warning

Source:

price series

close

The price series the slot reads from, evaluated inside the slot's chosen timeframe context.

Reach for hl2, hlc3, ohlc4, or another plot when a mid-bar or typical-price reference matches the reasoning behind your read.

Pointing the source at another indicator's plot breaks the "standard MA on this timeframe" mental model and makes the slot's behaviour depend on the other tool's output β€” any bug or change there silently propagates here.

TimeFrame:

timeframe string

01 = "5", 02 = "15", 03 = "60"

The higher timeframe the slot runs on. The slot's MA, its trend state, and its trend alert are all computed inside this timeframe's context and then drawn on the chart.

Build a custom HTF ladder; switch a slot from a short HTF to a structural HTF to carry bias; align a slot with the cadence you actually trade on.

Must be greater than or equal to the chart timeframe. A slot whose TimeFrame: is strictly below the chart's raises a runtime error naming the offending slot and blanks the chart. See Troubleshooting for the recovery procedure and MTF & Repainting for why the guard has to exist.

Two notes worth keeping on hand:

  • Each slot is its own higher-timeframe context. Slot 02 on 15 minutes is not reading Slot 01's 5-minute value and smoothing it further. It is evaluating its own SMA-of-close (or whatever you chose) on the 15-minute bars. The three slots are independent. They coincide only when you deliberately configure them to.

  • The source is evaluated inside the slot's timeframe. Setting Source: to close on a 60-minute slot means "the 60-minute bar's close," not the chart bar's close. This matters for hl2, hlc3, and ohlc4 β€” they are computed from the slot's HTF bar, not from the chart's live tick stream.

How the slot shapes itself

Input

Type

Default

What it changes

When you might change it

Misuse warning

Length:

int

20

The MA's smoothing window. See the banner above.

Tighten smoothing on a faster timeframe; slow smoothing on a structural timeframe.

Very short lengths track noise; very long lengths lag heavily. Neither is "better" on its own β€” each answers a different question. Do not treat a longer length as a safety feature.

Type:

enum from maLib.MaType

SMA

The moving-average style the slot uses. Routed through the Axiom MA Lite library, so the list of available types is whatever the Lite library exposes.

Use EMA for a more responsive smoothing, or another style the Lite library offers when the shape of its kernel matches your intended read.

The Base trim uses the Lite library's palette. Readers who expect ALMA, KAMA, FRAMA, Jurik, Laguerre, VAMA, or other power-user MA types will not find them here β€” those live in the Pro library the CTX trim imports. See the trim note at the bottom of this page. Type mechanics are taught in the MA Lite library manual, not re-taught here.

Trend Length:

int

3

The bars-back comparison that decides whether the slot's MA is rising or falling. See the banner above.

Ask the slot to move more before it calls a change (longer Trend Length:); or respond faster at the cost of noisier flips (shorter).

Very small values (1 or 2) will flicker on slow timeframes. Setting Trend Length: to 0 disables the trend read entirely β€” the slot's computed trend becomes false, and the slot's line renders in its down-state colour at half opacity regardless of price action. Zero is not "no trend filter"; zero is "do not compute a trend."

Lite-library type note: Base exposes SMA, EMA, RMA, WMA, VWMA, and SWMA. SWMA is available, but it does not use the Length: value; the local Lite library routes it to Pine's fixed-length ta.swma().

How the slot presents

Input

Type

Default

What it changes

When you might change it

Misuse warning

Line Width:

int

2

The thickness of the slot's line on the chart.

When two or more slots overlap at similar price and a thicker line helps you tell them apart, or when you want a slot visually de-emphasised.

Cosmetic only. No effect on computation, on alerts, or on the blend. Changing Line Width: does not make the slot "more accurate" β€” accuracy is a function of TimeFrame:, Source:, Type:, Length:, Trend Length:, and the global repaint posture.

How the slot contributes to the blend

Input

Type

Default

What it changes

When you might change it

Misuse warning

Blended Weight:

float

33.3

How strongly this slot steers the blended MA's value, and how strongly its trend state contributes to the blended trend vote.

Give a timeframe more say in the composite; reduce a timeframe's voice without disabling it; set a slot to "visible but silent" in the blend by using weight 0.

Weights are free. There is no forced ranking, no built-in rule against lopsided distributions. A heavy weight on a timeframe you do not actually trade on will tilt the blend toward a cadence that is not your read.

The blended-weight field sits at the centre of a lot of reader confusion, so three more clarifications you may as well read now:

  • The weights are proportional, not absolute. The blend sums weight Γ— value across contributing slots and divides by the sum of contributing weights. (20, 20, 60) and (1, 1, 3) produce the same blended value. The ratios matter; the totals do not.

  • A slot with weight 0 is skipped entirely by the blend accumulator and contributes nothing to the trend vote. Its line stays on the chart (unless you hide the plot) and its per-slot alerts continue to fire on closed chart bars. "Weight zero" means "visible and vocal on its own, silent in the composite."

  • There is no "normalise to 100" step and no enforcement that the weights sum to 100. The shipped 33.3 / 33.3 / 33.3 default sums to 99.9, which is fine β€” the divisor in the blend is whatever the enabled weights sum to.

A small reality check: if you find yourself tempted to set (33, 33, 34) to "make the total come out clean," the instinct is harmless and the math is going to produce the same blended line either way. The tool does not reward round numbers; it rewards proportions you can defend.

One sharper edge: the input does not enforce positive-only weights. Use zero-or-positive weights unless you are deliberately testing an edge case. If every enabled slot is weight 0, or unusual negative weights leave no usable positive total weight, the current source can leave the enabled blend at its default 0/down state. That is a configuration problem, not a market read.


Blended MA inputs

Collected in the MA Blended group. Three controls.

Input

Type

Default

What it does

Misuse warning

Enable Blended MA

boolean

on

Turns the blended line and its two trend alerts on or off.

Disabling the blend does not change any per-slot behaviour. The three slot lines, their trend colours, and their per-slot alerts keep running.

Hide Blended MA Plot

boolean

off

Hides the blended line. The blend math, the blended trend vote, and the blended alerts all continue.

Useful in alerts-only workflows or for a dashboard arrangement where the blend is only referenced through alerts. Do not interpret a hidden blend as "the blend is off."

Line Width:

int

3

The thickness of the blended line. Shipped one notch thicker than the default slot lines so the composite is visually distinct from its components on a shared chart.

Cosmetic only. Thickness is not a claim of importance.

What the Base blended group does not include, on purpose:

  • No Up Color: / Down Color: inputs. The blended colours are fixed in code β€” lime for an up-voted blend, red for a down-voted blend. There is no intermediate state and no configurable variant. If you need recolouring from the inputs dialog, that is a CTX feature. See the trim note below.

  • No explicit "averaging rule" selector. The rule is weight-normalised averaging with a majority-vote trend resolution that breaks ties to uptrend. The rule is named and disclosed. It is not selectable. Visuals & Logic and For the Geeks both describe what the rule actually does on a real chart.


PU Settings β€” the one global control

This group holds the single most consequential input on the tool.

Input

Type

Default

What it does

Misuse warning

On Bar Close?

boolean

on

A single global switch applied to every enabled slot. ON gates every slot to the last confirmed higher-timeframe bar β€” the slot does not move on the live HTF bar. OFF lets every slot read the live HTF bar and drift until that bar closes.

One switch, three slots. You cannot use this input to keep Slot 01 confirmed while Slot 03 runs live β€” that is a CTX-trim feature. Flipping this input is not a free speed-up. ON is slower and stable; OFF is faster and repaint-exposed on the live HTF bar. The cost of each posture is real.

Because this input deserves real context, it has its own page. Read MTF & Repainting before you flip it in production. That page teaches what repainting is in this specific context, the global scope of the switch, the runtime-error guard that sits adjacent to it, and a verification walkthrough you can run on your own chart in under a minute.


Defaults as defaults

The shipped three-slot configuration β€” Slot 01 at 5 minutes, Slot 02 at 15 minutes, Slot 03 at 60 minutes, each with SMA, length 20, Trend Length 3, equal 33.3 weights, slot line widths 2, blended line width 3 β€” exists because it loads cleanly on a 1-minute chart of a regular-session liquid instrument and demonstrates what the tool does in plain terms.

That is what the defaults are. It is worth naming what they are not:

  • The defaults are not a recommendation. SMA-20 on 5 / 15 / 60 is a legible first example, not a validated setup for any instrument, any session, any timeframe, or any trading style.

  • The defaults are not optimised. Nothing was back-tested to produce them. They were chosen for the first ten minutes a new reader will spend with the tool.

  • The defaults are not ranked. The three slots are equally weighted because "this is the tool's entry chart," not because equal weights are a neutral posture. Equal weights is itself a statement β€” one that says each of these three cadences gets an equal voice in the majority vote. Sometimes that is the read you want. Sometimes it is not. Workflows names the statement and the alternative explicitly.

If the tool is going to do real work for you, you will choose your own timeframes, lengths, trend-lengths, and weights. The shipped defaults are the chart you load before you make those choices, not a starting line someone else has already crossed on your behalf.


Version note β€” what Base deliberately does not ship

Across Axiom indicator families, the version progression is Base β†’ CTX β†’ STR when the full set exists. Base is the focused/free surface. CTX expands Base into a broader context tool. STR sits after CTX and spends extra processing on structure around the blended output, which is why STR carries fewer slots than CTX where both exist. Base holds back several features on purpose. Listing them here, in one place, saves you the search.

  • Per-slot On Bar Close?. Base ships a single global switch. The CTX trim carries one per slot β€” ten of them.

  • Cross-ticker input. Every Base slot reads the chart's own ticker. The CTX trim lets each slot read a different symbol.

  • User-configurable colour inputs. Base slot colours (teal / blue / purple) and blend colours (lime / red) are fixed in code. The CTX trim exposes Up Color: and Down Color: inputs per slot and on the blend.

  • The Pro MA palette. Base imports the Lite library's MA types; CTX imports the Pro library's wider palette (ALMA, KAMA, FRAMA, Jurik, Laguerre, VAMA, and the rest).

  • Ten slots. Base ships three.

None of those absences is an oversight. Each is a version decision. The series exists so a reader can match the tool's surface to the surface their work actually needs. If three slots, one switch, the Lite palette, and fixed colours fit your work, Base is the right version and CTX would cost you attention for features you would not use. If your work genuinely needs one of the missing context features, Axiom MA CTX is the context-expansion version of this pack. If your work needs structure around the blended output, that is STR territory where an STR version exists.


Cross-references

  • The MA type mechanics shipped by Type: are documented in the Axiom MA Lite library manual and are not re-taught here.

  • The global repaint switch has its own end-to-end walkthrough at MTF & Repainting. Read that before flipping On Bar Close? in production.

  • The difference between hiding a plot, disabling a slot, and setting weight to zero is worked through again at Visuals & Logic and is the spine of several cases in Troubleshooting.