Auto-generated. This article is rebuilt from app/signals/config/signal_definitions.json by scripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.

Relative strength vs sector ETF (252d)

What it is

Relative strength vs sector ETF (252d) — registry key screener_rs_sector.

Per-ticker relative strength ratio vs the ticker’s GICS sector ETF (XLK/XLV/XLF/etc., from screener_config.json sector_etf_map) over a 252-day window. Identifies names outperforming their sector basket — key input for A2 (sympathy selloff reversion). Stored in screener_features_daily. NULL when sector is unknown or ETF has insufficient history.

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) / (sector_etf_close / sector_etf_close_252d). Sector ETF from screener_config.json:sector_etf_map. NULL when sector is unknown, ETF data missing, or fewer than 252 aligned rows.

Where it surfaces

• API field: screener.features.rs_sector on GET /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