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

Gap Volatility

Install and import#

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

Signature#

gapVolatility(input)

Gap Volatility: measures each bar's opening gap -- this open less the prior close -- and the rolling standard deviation of those gaps.

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 only period (default 14, integer >= 2), the standard-deviation window.

Returns#

TopicResult

series holds gap, the raw open-minus-prior-close difference, and value, the population standard deviation of gap over period bars. latest carries the last of each. The two warm-ups differ: gap is null only on the first bar, which makes ready_at 1, while value first appears at index period (14 at the default).

Warm-up#

The first 1 bar for `gap`, `period` bars for `value` (14 at the default period) positions are null. gap is undefined on the first bar because there is no prior close, so the deviation window needs one extra bar and lands at index period rather than period - 1.

Errors#

  • When parameters.period is not an integer >= 2 — throws Error
  • When a bar is missing open, high, low, close, or volume, or one of them is not a finite number — throws Error
  • When bars are not strictly ordered by timestamp, or a bar's high is below its open, low, or close — 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#

gapVolatility(input)

Returns#

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

{
  "topic_id": "D07-F06-A08",
  "title": "Gap Volatility",
  "state": "calculated",
  "ready": true,
  "ready_at": 1,
  "series": {
    "gap": [
      null,
      1.4911145199999964,
      0.6672783399999958,
      -0.26733595999999693,
      -0.8183669500000121,
      -0.720687060000003
    ],
    "value": [null, null, null, null, null, null]
  },
  "latest": {
    "gap": -1.106646689999991,
    "value": 1.1343149298154644
  },
  "parameters": {},
  "diagnostics": {
    "causal": true,
    "input_count": 96
  }
}

Diagrams#

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

Calculation flow#

Gap Volatility calculation flow
flowchart LR
    A["ordered OHLC observations with session calendar, previous "] --> B["Validate order, basis, and finite values"]
    B --> C["Apply the selected Gap Volatility 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"]
Gap Volatility 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#