0032 — Indicator-aware warmup
Status: Accepted
Date: 2026-11-05
Amends: ADR-0009 (the meaning of warmup and its “cumulative-indicator seam” consequence; paging and tail polling stay as decided there)
Amended by: ADR-0056 (the need applies to png, summary and both, without a warmup argument)
Context and Problem Statement
Section titled “Context and Problem Statement”ADR-0009 pages history with end_time plus warmup and accepts that
recursive indicators “can step slightly at a seam”. The web app sends
warmup: 300 with every load, page, tail poll and push subscription.
QA found the step is not slight. On 1m BTCUSDT the ema_stack EMA 200
jumped by about $250 at $80k (0.3%) at every history seam. The deterministic
sample data shows 1.9%. Pine’s ta.ema is seeded with the SMA of its first
200 bars, so with 300 bars of warmup the first returned bar is only 100
recursions past the seed. The seed still weighs (1 − 2/201)^100 ≈ 37%. The
newer side of a seam, which is the left edge of the response loaded before,
is the one that is off. Keeping already-loaded values when a page is merged
therefore does not help. A tail poll computed over 302 bars has the same
error against the history it is merged into.
An SMA-seeded EMA of length N needs N bars for the seed and about
ln(1000) / −ln(1 − α) more until the seed weighs under 0.1%. For EMA 200
that is 200 + 691 = 891 bars. Wilder’s RMA (α = 1/N) needs about 7.9 N:
RSI, ATR, ADX, MACD and Supertrend converge within 300 at their default
lengths, but not an RSI 50 (393 bars), and kalman_volume needs 399 even at
its defaults.
Decision Drivers
Section titled “Decision Drivers”- Values at a seam or on a live tail should match one long request, as on TradingView.
- Charts whose indicators converge within 300 bars should not pay for longer fetches on every poll and push.
- Indicator math, and what it needs, stays in the Rust engine (ADR-0003).
Considered Options
Section titled “Considered Options”- A larger fixed client warmup (1000). Fixes EMA 200 everywhere, but every tail poll, push window and page then costs 1000 more bars, also for an RSI-only chart. Two Binance requests per poll.
- Keep already-loaded values when merging a page. Does not help: the badly warmed side of the seam is the newer response’s left edge. Fixing it would need pages overlapping it by about 700 bars, and tails would still be off.
- The client picks a warmup per indicator. The web app would need each indicator’s lookback and smoothing, duplicating engine knowledge.
- The server raises
warmupto what the indicators declare. Each indicator reports the bars it needs to converge; the server uses at least that.
Decision Outcome
Section titled “Decision Outcome”Chosen: option 4.
Indicator::warmup_bars()returns the bars of history an indicator needs before its values converge (an SMA-seeded EMA’s seed weighs under 0.1%). The default is 0.pine::ma_warmupgives it per moving-average type: the seed window pluspine::decay_bars(α)for EMA (DEMA and TEMA two and three times that) and RMA/SMMA, the lookback for window kinds (HMA n + ⌊√n⌋ − 1). Chained smoothings add up. Declared, from their parameters:ema_stack(891),ma,ma_ribbon,envelopes,keltner,atr,rsi,adx(two RMAs),supertrend,macd,stoch_rsi,trix,ppo(EMA type),elder_force_index,tsi,smi_ergodic,volume_oscillator,connors_rsiandkalman_volume(HMA, 200-bar stdev, the Kalman smoothing, the signal SMA).generate_chart(format=series)andsubscribe_chartraise a non-zerowarmupto the largestwarmup_bars()of the requested indicators, still capped at 1000.warmup: 0(or none) stays 0, so a caller asking for the bare window still gets it.- The payload is unchanged: warmup bars are trimmed as before.
has_morestays true while trimmed bars remain. ADR-0009 setshas_morefrom the upstream fetch (the fullbars + warmupcame back, or Yahoo’s window was not cut). When history runs out, the warmup bars that did come back are still older bars the client has not seen, and with up to 891 of them (all the history of a young symbol on 1d, or the first two years of a Yahoo 6h series cut at Yahoo’s 730-day 1h limit) they must stay reachable. Sohas_moreis also true when more bars were fetched than returned; the next page returns them and ends the history.- The push cadence (ADR-0021: half the rate for a warmup above 300) follows
the client’s
warmup, not the raised one, so the server’s own raise does not slow pushes down. A group still recomputes over the raised window. - The web app keeps sending
warmup: 300and does not change its merge.
Consequences
Section titled “Consequences”Positive. EMA 200 joins pages and tails within 0.01% of one long
request (measured on the sample data: the extra step at a seam went from
1.9% to 0.005%). The test ema_stack_pages_join_without_a_step holds it
under 0.05%. Charts without long EMAs fetch exactly what they did before.
Negative.
- A chart with
ema_stackfetches up to 891 +barsbars per request. On Binance a tail poll (893 bars) is still one request; a full load or a history page (1391) is two instead of one. Its push group recomputes 893 bars per push instead of 302. - On Yahoo the request window grows with the bar count: a 1h tail poll asks for about 220 calendar days (one request, roughly 1100 hourly bars of a stock) instead of 10, every 15 s; a 4h one is cut at Yahoo’s 730-day limit. The responses are larger, the request count is unchanged.
- The 1000 cap still limits user-configured long smoothings: an EMA converges to 0.1% only up to length 224, an RMA (RSI, ATR) up to 126. Longer ones step less than before but still visibly.
- Only the built-ins listed above declare a need. The community composites
(
cipher_b,wavetrend,rsi_mfi_stoch) and user scripts (ADR-0025) report 0 and get the client’s warmup. - Running sums (OBV, CVD, A/D line) and VWAP sessions are unaffected: they still differ by a constant or reset at anchors, as ADR-0009 says.
More Information
Section titled “More Information”- ADR-0009 — Live tail polling and history paging
- ADR-0018 — Pine semantics for indicators: SMA-seeded
ta.ema/ta.rma - ADR-0021 — Real-time chart push