KB / signal
Relative strength vs SPY (252d)
Last verified
Auto-generated. This article is rebuilt from
app/signals/config/signal_definitions.jsonbyscripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.
Relative strength vs SPY (252d)
What it is
Relative strength vs SPY (252d) — registry key screener_rs_spy.
Per-ticker relative strength ratio vs SPY: (ticker_return_252d) / (spy_return_252d), where both are computed as close / close_252d_ago. Ratio > 1 means outperformance. Stored in screener_features_daily. Feeds archetype scorers (D5 RS divergence in selloff).
Source
Source module: screener
Data source: computed
Derived metric — produced inside the platform (app/sources/screener.py or equivalent) rather than fetched as a raw upstream value. See the How it's computed section below for the formula.
How it’s computed
(close / close_252d) / (spy_close / spy_close_252d). NULL when fewer than 252 aligned rows.
Where it surfaces
- API field:
screener.features.rs_spyonGET /api/v1/signals/latest
Health-score / alignment role
Data carrier — no implication, no health-score contribution.
Persisted for downstream consumers (sparklines, base-rate matcher, calibration substrate) but does not classify into BULLISH / NEUTRAL / BEARISH and does not contribute to the 0-100 health score.
Release cadence
- Publishes:
daily