Quick Start

This page is about the shortest correct first run for Axiom Stoch Osc Pro.

The first goal is not to build your final ten-slot stack in one session. The first goal is to get a small, legal baseline running cleanly enough that you can tell what the tool is helping with, what it is not settling for you, and what still needs verification before the pane earns more trust.

A clean first run matters here because this indicator gets harder to trust once setup errors, timing questions, and blend interpretation all start blurring together.

First decision: which path fits your chart?

Start here before you read the pane.

Why this matters:

• every enabled slot must stay at or above the chart timeframe
• the shipped defaults are usable, but they are not chart-neutral
• if you skip this check, the rest of the setup gets harder than it needs to
• if the first load starts with an avoidable runtime error, it becomes too easy to blame the tool for confusion that actually started in the chart-timeframe match

Before you choose a path, keep three things in mind:

• slots 4 through 10 are optional expansion space, not unfinished setup
• same-symbol confirmed mode is the calmest first baseline
• if the script is illegal on the current chart, fix that before you interpret anything

What a correct first run should look like

Before you worry about alerts, alternate tickers, or advanced MA families, a healthy first run is simpler than it sounds:

• the script loads without a timeframe runtime error
• you can name which slots are active
• you know whether those active slots are confirmed or still forming
• you know which active slots are shaping the blend
• the pane still feels explainable in plain English

If you do not have those five things yet, stay on this page a little longer.

Path A: use the shipped baseline as intended

Use this path when your chart timeframe is `1m` or `5m`.

1. Add Axiom Stoch Osc Pro to the chart.
2. Confirm that you can see a lower pane with three visible slot K lines and a blended K/D pair.
3. Open the settings panel and confirm the first three slots are still enabled with `TimeFrame:` values of `5`, `15`, and `60`.
4. Confirm these baseline settings are still in place on the active slots:
   • `Source:` = `close`
   • `K Length:` = `14`
   • `K Smoothing:` = `3`
   • `K Type:` = `SMA`
   • `D Length:` = `3`
   • `D Type:` = `SMA`
5. Confirm `On Bar Close?` is still on for those active slots.
6. Leave `Optional Ticker:` blank, `Enable Master Smoothing` off, and slots 4 through 10 disabled for the first pass.
7. Temporarily set one active slot's `Blended Weight:` to `0` and confirm the blended pair changes while that slot itself can still stay visible.
8. Return the weight to its prior value before moving on.

What you should be able to say before leaving this path:

• "This is a same-symbol three-slot baseline."
• "My active slots are still in confirmed mode."
• "The blend is reacting to weighted slots, not acting like a separate engine."
• "If this stack stopped making sense, I would simplify it before I expanded it."

Path B: adapt the baseline before you trust it

Use this path when your chart timeframe is above `5m`, or when you already know the shipped `5 / 15 / 60` ladder is not the right first baseline.

1. Add the indicator.
2. Open settings immediately.
3. For each enabled slot, compare `TimeFrame:` to the chart timeframe.
4. Raise the slot timeframe, clear it so it inherits the chart timeframe, or disable the slot if it conflicts.
5. Keep `On Bar Close?` on for every active slot during the first pass.
6. Leave `Optional Ticker:` blank and `Enable Master Smoothing` off.
7. Confirm the pane now loads with only the layers you intended to keep.

What you should be able to say before leaving this path:

• "Every enabled slot is legal on this chart."
• "I know which slots I kept on purpose."
• "I am learning the stack I built, not fighting the stack I inherited."
• "I did not let the runtime fix turn into random customization."

Three quick sanity checks

Run these before you create alerts or expand the stack. Each one teaches a rule that matters later.

If any of those checks surprise you, slow down there. That is exactly the kind of misunderstanding this indicator can hide behind a clean-looking pane.

Do not compensate for surprise by adding more slots, changing MA families, or turning on master smoothing. Fix the surprise while the stack is still small.

A sensible first configuration

If you are learning the indicator, keep the first session small:

• use no more than 3 active slots
• keep those slots on the same symbol
• leave all active slots on confirmed mode
• use one MA family across the first stack
• keep master smoothing off
• add alerts only after you can explain what each active slot is contributing

This is not minimalism for its own sake. It is how you keep the pane readable enough to verify under pressure.

If something goes wrong immediately

Start with these questions in order:

1. Is any enabled slot timeframe lower than the chart timeframe?
2. Did I hide a slot and then forget it was still active?
3. Did I set every weighted contributor to `0` and remove the blend by accident?
4. Did I turn `On Bar Close?` off and then read the slot as if nothing changed?

If you need the symptom-by-symptom version, go to Troubleshooting.

Finish line for this page

You are ready to move on when you can answer these without guessing:

• Which active slot has the lowest timeframe on your chart right now?
• Which active slots are confirmed, and which are still forming?
• Which active slots are shaping the blend right now?
• What would make this baseline less trustworthy on the next change you make?

If you cannot answer those yet, stay here. A slower first pass is cheaper than building habits around a stack you only half understand.

Once that version makes sense, move to MTF and Repainting, then Settings, then Visuals and Logic.

Visual placeholder: Side-by-side screenshots showing a valid `1m` or `5m` chart using the shipped `5 / 15 / 60` baseline and a higher-timeframe chart where at least one active slot had to be raised, inherited, or disabled before the pane became usable.