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

Klinger Volume Oscillator

Install and import#

bash
npm install fintech-algorithms
ts
import { klingerVolumeOscillator } from "fintech-algorithms/technical-indicators/volume-indicators/klinger-volume-oscillator";

Signature#

klingerVolumeOscillator(input)

Signs each bar's volume force by the direction of the high-low-close sum and weights it by where the close sits in the bar range, then returns the fast EMA of that force minus the slow EMA.

Parameters#

NameTypeNotes
inputTopicInputbars needs timestamp, high, low, close and volume. Inside the branch fast_period defaults to 34 and slow_period to 55 (minimum fast_period + 1). The family validates the same two keys first against defaults of 3 and 10, so supplying fast_period of 10 or more without also supplying slow_period throws on that earlier check.

Returns#

TopicResult

series holds a single value, the fast EMA of the volume force minus the slow EMA, and latest its last element. The warm-up is set by the slow EMA seed.

Warm-up#

The first `slow_period` - 1 bars (54 with the default 55) positions are null. ready_at is 54 on default parameters, so short inputs return state: waiting with a null value.

Errors#

  • When fast_period is 10 or more and slow_period is not supplied — throws Error
  • When slow_period is not an integer greater than fast_period — throws Error
  • When a bar carries a negative volume — throws Error

Complexity: time O(n), 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#

klingerVolumeOscillator(input)

Returns#

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

{
  "topic_id": "D07-F05-A13",
  "title": "Klinger Volume Oscillator",
  "state": "calculated",
  "ready": true,
  "ready_at": 54,
  "series": {
    "value": [null, null, null, null, null, null]
  },
  "latest": {
    "value": -13741.12194581165
  },
  "parameters": {},
  "diagnostics": {
    "causal": true,
    "input_count": 96
  }
}

Diagrams#

Klinger Volume Oscillator — article hero
Klinger Volume Oscillator — concept map
Klinger Volume Oscillator — decision comparison
Klinger Volume Oscillator — worked example

Calculation flow#

Klinger Volume Oscillator calculation flow
flowchart LR
    A["basis-consistent OHLCV observations with venue/session cov"] --> B["Validate order, basis, and finite values"]
    B --> C["Apply the selected Klinger Volume Oscillator 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"]
Klinger Volume Oscillator 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 Volume Indicators family#