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

Range Efficiency Ratio

Install and import#

bash
npm install fintech-algorithms
ts
import { rangeEfficiencyRatio } from "fintech-algorithms/technical-indicators/range-and-volatility-indicators/range-efficiency-ratio";

Signature#

rangeEfficiencyRatio(input)

Range Efficiency Ratio: the absolute net close-to-close move across period bars divided by the sum of the high-low ranges over the same span.

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), which sets both the close lookback and the range-summing window.

Returns#

TopicResult

series holds a single key, value, a 0-1 efficiency reading; latest.value is its last value. The warm-up is period leading nulls, so ready_at is 14 at the default period.

Warm-up#

The first `period` bars (14 at the default period) positions are null. The numerator compares the close against the close period bars earlier, so it needs one more bar than the range window does. value is also null on any bar where the summed range is zero.

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#

rangeEfficiencyRatio(input)

Returns#

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

{
  "topic_id": "D07-F06-A09",
  "title": "Range Efficiency Ratio",
  "state": "calculated",
  "ready": true,
  "ready_at": 14,
  "series": {
    "value": [null, null, null, null, null, null]
  },
  "latest": {
    "value": 0.07606679254426744
  },
  "parameters": {},
  "diagnostics": {
    "causal": true,
    "input_count": 96
  }
}

Diagrams#

Range Efficiency Ratio — article hero
Range Efficiency Ratio — concept map
Range Efficiency Ratio — decision comparison
Range Efficiency Ratio — worked example

Calculation flow#

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