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

Vortex Indicator (+VI/−VI)

Install and import#

bash
npm install fintech-algorithms
ts
import { vortexIndicatorViVi } from "fintech-algorithms/technical-indicators/trend-systems/vortex-indicator-vi-vi";

Signature#

vortexIndicatorViVi(input)

Sums the upward and downward vortex movements over a rolling window and divides each by the summed true range, giving the paired plus_vi and minus_vi lines.

Parameters#

NameTypeNotes
inputTopicInputbars is the OHLCV series, validated for finite prices, strictly increasing timestamp, a single adjustment basis, non-negative volume, and a high and low that bracket the other prices. From parameters this topic reads only period (integer, minimum 2, default 14), the length of both the movement sums and the true-range sum.

Returns#

TopicResult

series and latest carry plus_vi and minus_vi, and nothing else. Both share one warm-up, and either is null on any bar whose true-range sum is zero.

Warm-up#

The first period bars (14 by default) positions are null. The vortex movements are undefined on the first bar, so the first complete window ends one bar later than a plain rolling sum would: with the default period, indices 0 to 13 are null and ready_at is 14.

Errors#

  • When parameters.period is present but is not an integer of at least 2 — throws Error
  • When bars is empty, or a bar has a non-finite price, a negative volume, a timestamp not greater than the previous one, or a high 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#

vortexIndicatorViVi(input)

Returns#

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

{
  "topic_id": "D07-F02-A10",
  "title": "Vortex Indicator (+VI/−VI)",
  "state": "calculated",
  "ready": true,
  "ready_at": 14,
  "series": {
    "plus_vi": [null, null, null, null, null, null],
    "minus_vi": [null, null, null, null, null, null]
  },
  "latest": {
    "plus_vi": 0.91078566552092,
    "minus_vi": 1.0406526774370142
  },
  "parameters": {},
  "diagnostics": {
    "causal": true,
    "input_count": 96
  }
}

Diagrams#

Vortex Indicator (+VI/−VI) — article hero
Vortex Indicator (+VI/−VI) — concept map
Vortex Indicator (+VI/−VI) — decision comparison
Vortex Indicator (+VI/−VI) — worked example

Calculation flow#

Vortex Indicator (+VI/−VI) calculation flow
flowchart LR
    A["ordered OHLC or close observations with explicit window, s"] --> B["Validate order, basis, and finite values"]
    B --> C["Apply the selected Vortex Indicator (+VI/−VI) 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"]
Vortex Indicator (+VI/−VI) 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 Trend Systems family#