Weighted Close
Install and import#
npm install fintech-algorithmsimport { weightedClose } from "fintech-algorithms/technical-indicators/price-transforms/weighted-close";Signature#
weightedClose(input)Averages high, low and a double-weighted close so the settlement price dominates the bar.
Parameters#
| Name | Type | Notes |
|---|---|---|
input | TopicInput | bars needs timestamp, high, low and close. This topic reads no keys from parameters, though parameters must still be an object when supplied. |
Returns#
TopicResult
series holds a single value, (high + low + 2 * close) / 4 for every bar, and latest its last element. Every bar produces a value, so there is no warm-up.
Warm-up#
The first none positions are not applicable. ready_at is 0. The close carries half the weight, the extremes a quarter each.
Errors#
- When a bar's
high,loworcloseis not a finite number — throws Error - When a
highis below the bar'sopen,loworclose— throws Error - When bars do not share one adjustment
basis— 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#
{
"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#
weightedClose(input)Returns#
object with 9 fields: topic_id, title, state, ready, ready_at, series, latest, parameters, …
{
"topic_id": "D07-F08-A03",
"title": "Weighted Close",
"state": "calculated",
"ready": true,
"ready_at": 0,
"series": {
"value": [
100.03625,
101.75361035750001,
102.8728829175,
103.14077006,
102.77185682000001,
102.27277061000001
]
},
"latest": {
"value": 100.1199943175
},
"parameters": {},
"diagnostics": {
"causal": true,
"input_count": 96
}
}Diagrams#
Calculation flow#
Weighted Close calculation flow
flowchart LR
A["finite, basis-consistent OHLC observations and any require"] --> B["Validate order, basis, and finite values"]
B --> C["Apply the selected Weighted Close 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"]
Weighted Close 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