Volatility Ratio
Install and import#
npm install fintech-algorithmsimport { volatilityRatio } from "fintech-algorithms/technical-indicators/range-and-volatility-indicators/volatility-ratio";Signature#
volatilityRatio(input)Volatility Ratio: the standard deviation of close-to-close simple returns over a short window divided by the same measure over a long window.
Parameters#
| Name | Type | Notes |
|---|---|---|
input | TopicInput | bars 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 short_period (default 5, integer >= 2) and long_period (default 20, integer, and strictly greater than short_period). The family also validates period (default 14, integer >= 2) before this branch runs, even though the ratio does not use it. |
Returns#
TopicResult
series holds a single key, value, the short-over-long deviation ratio; latest.value is its last reading. The warm-up is long_period leading nulls, so ready_at is 20 at the defaults.
Warm-up#
The first `long_period` bars (20 at the defaults) positions are null. Returns are undefined on the first bar, so the long-window deviation only completes at index long_period rather than long_period - 1. value is also null on any bar where the long-window deviation is zero.
Errors#
- When
parameters.short_periodis not an integer >= 2 — throws Error - When
parameters.long_periodis not an integer greater thanshort_period— throws Error - When
parameters.periodis not an integer >= 2 — throws Error
Complexity: time O(n * long_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#
{
"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#
volatilityRatio(input)Returns#
object with 9 fields: topic_id, title, state, ready, ready_at, series, latest, parameters, …
{
"topic_id": "D07-F06-A05",
"title": "Volatility Ratio",
"state": "calculated",
"ready": true,
"ready_at": 20,
"series": {
"value": [null, null, null, null, null, null]
},
"latest": {
"value": 0.593478196387429
},
"parameters": {},
"diagnostics": {
"causal": true,
"input_count": 96
}
}Diagrams#
Calculation flow#
Volatility 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 Volatility 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"]
Volatility 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.
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