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

WaveTrend Oscillator

Install and import#

bash
npm install fintech-algorithms
ts
import { wavetrendOscillator } from "fintech-algorithms/technical-indicators/momentum/wavetrend-oscillator";

Signature#

wavetrendOscillator(input)

Builds a CCI-style channel index from the typical price against its own 10-period EMA and mean deviation, then smooths it into a fast line and a slower trigger.

Parameters#

NameTypeNotes
inputTopicInputbars is a chronological array of OHLCV rows, each with a non-empty timestamp plus finite open, high, low, close and volume. This topic reads no keys from parameters: the typical price is (high + low + close) / 3 and the 10, 10, 21 and 4 lengths are fixed in the implementation. The shared momentum preamble still validates period (default 14), fast_period (default 5) and slow_period (default 34) before branching, so a bad value for any of them throws even though this topic reads none of them.

Returns#

TopicResult

series and latest carry two keys: wt1, the 21-period EMA of the channel index, and wt2, the 4-period simple average of wt1. The two keys have different warm-ups, wt2 trailing wt1 by three bars.

Warm-up#

The first 38 bars for `wt1`, 41 bars for `wt2` positions are null. The 10-period EMA of typical price seeds at index 9, its mean-deviation EMA at 18, and the 21-period EMA at 38, so ready_at is 38 on the canonical fixture; wt2 remains null until index 41. A mean deviation of exactly 0 also yields a null.

Errors#

  • When period is supplied but is not an integer >= 2, even though this topic ignores it — throws Error
  • When a bar's high is below its open, close, or low — 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#

wavetrendOscillator(input)

Returns#

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

{
  "topic_id": "D07-F03-A23",
  "title": "WaveTrend Oscillator",
  "state": "calculated",
  "ready": true,
  "ready_at": 38,
  "series": {
    "wt1": [null, null, null, null, null, null],
    "wt2": [null, null, null, null, null, null]
  },
  "latest": {
    "wt1": -25.94276818159519,
    "wt2": -13.858032304032271
  },
  "parameters": {},
  "diagnostics": {
    "causal": true,
    "input_count": 96
  }
}

Diagrams#

WaveTrend Oscillator — article hero
WaveTrend Oscillator — concept map
WaveTrend Oscillator — decision comparison
WaveTrend Oscillator — worked example

Calculation flow#

WaveTrend Oscillator calculation flow
flowchart LR
    A["an ordered price or OHLC series, declared lookbacks, smoot"] --> B["Validate order, basis, and finite values"]
    B --> C["Apply the selected WaveTrend 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"]
WaveTrend 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 Momentum family#