fintech-algorithms
Using a coding agent? Give it the skill: npx skills add IslamBaraka90/Fintech-Algorithms-Library What it does →

Volatility Stop

Install and import#

bash
npm install fintech-algorithms
ts
import { volatilityStop } from "fintech-algorithms/technical-indicators/range-and-volatility-indicators/volatility-stop";

Signature#

volatilityStop(input)

Volatility Stop: a trailing long stop set multiplier ATRs below the highest close of the last period bars, and a short stop the same distance above the lowest close.

Parameters#

NameTypeNotes
inputTopicInputbars is the required OHLCV array -- each bar carries timestamp, open, high, low, close, volume and an optional basis, strictly ordered by timestamp. From parameters this topic reads period (default 14, integer >= 2), used for both the rolling close extremes and the Wilder ATR, and multiplier (default 3, a finite number >= 0).

Returns#

TopicResult

series holds long_stop and short_stop, both in price units; latest carries the last of each. They share a warm-up of period - 1 leading nulls, so ready_at is 13 at the default period.

Warm-up#

The first `period - 1` bars (13 at the default period) positions are null. Both stops need the ATR seed and a full extremes window, and both complete at the same index. The stops do not ratchet or flip; each bar is recomputed from its own window.

Errors#

  • When parameters.period is not an integer >= 2 — throws Error
  • When parameters.multiplier is not a finite number, or is negative — throws Error
  • When a bar is missing open, high, low, close, or volume, or one of them is not a finite number — throws Error

Complexity: time O(n * period), space O(n).

Worked example#

executed Captured by running this function on the input its own test provides. Real output of real code — but not asserted against a published figure.

Input#

input
{
  "bars": [
    {
      "timestamp": "2024-01-02",
      "basis": "synthetic-unadjusted",
      "open": 100,
      "high": 101.45,
      "low": 98.695,
      "close": 100,
      "volume": 750000,
      "benchmark": 200
    },
    {
      "timestamp": "2024-01-03",
      "basis": "synthetic-unadjusted",
      "open": 101.49111452,
      "high": 103.38381693,
      "low": 100.05480022,
      "close": 101.78791214,
      "volume": 795117,
      "benchmark": 200.56326135
    },
    {
      "timestamp": "2024-01-04",
      "basis": "synthetic-unadjusted",
      "open": 102.45519048,
      "high": 104.6701838,
      "low": 100.91147007,
      "close": 102.9549389,
      "volume": 840234,
      "benchmark": 201.11020913
    }
  ],
  "parameters": {}
}

Call#

volatilityStop(input)

Returns#

object with 9 fields: topic_id, title, state, ready, ready_at, series, latest, parameters, …

{
  "topic_id": "D07-F06-A12",
  "title": "Volatility Stop",
  "state": "calculated",
  "ready": true,
  "ready_at": 13,
  "series": {
    "long_stop": [null, null, null, null, null, null],
    "short_stop": [null, null, null, null, null, null]
  },
  "latest": {
    "long_stop": 98.43630241500071,
    "short_stop": 109.72647177499931
  },
  "parameters": {},
  "diagnostics": {
    "causal": true,
    "input_count": 96
  }
}

Diagrams#

Volatility Stop — article hero
Volatility Stop — concept map
Volatility Stop — decision comparison
Volatility Stop — worked example

Calculation flow#

Volatility Stop calculation flow
flowchart LR
    A["ordered OHLC observations with session calendar, previous "] --> B["Validate order, basis, and finite values"]
    B --> C["Apply the selected Volatility Stop convention"]
    C --> D["Emit value, readiness, and diagnostics"]
    D --> E["Interpret descriptively; test outcomes separately"]
    B -->|invalid or insufficient| X["Withhold output with a reason"]
Volatility Stop readiness and evidence states
stateDiagram-v2
    [*] --> Waiting
    Waiting --> Ready: enough valid causal observations
    Waiting --> Rejected: malformed or unsupported input
    Ready --> Calculated: selected formula applied
    Calculated --> Interpreted: diagnostic and limitation retained
    Interpreted --> Ready: next observation arrives
    Rejected --> Waiting: corrected input and deterministic reset

How it works#

This page states the contract — how to call it correctly. The article explains the concept: why it works, and where it breaks.

Read the article →

References#

  • TA-Lib function groups — see linked primary or authoritative record
  • TA-Lib C/C++ API — see linked primary or authoritative record
  • TA-Lib maintained source — see linked primary or authoritative record
  • Evidence decision
  • Level 1 evidence map

The rest of the Range and Volatility Indicators family#