Data and processing flow
- Daily OHLCV history is collected for the maintained ticker universe.
- Indicator cache files are built from local history: moving averages, RSI, Stoch RSI, Williams %R, relative strength, liquidity, market regime, and other technical fields.
- The report generator merges current indicators with static company metadata and broker availability lists.
- Assets are displayed when they match at least one report candidate condition or selected strategy preset.
Core indicators
| Indicator | Purpose |
|---|---|
| 200D moving average | Longer-term trend filter and major risk boundary. |
| Monthly EMA10 | Medium-term trend and exit context. |
| Stoch RSI | Momentum cycle and pullback timing across weekly and monthly periods. |
| Williams %R | Additional momentum and overbought/oversold context. |
| RS vs SPY | Relative strength comparison against a broad U.S. equity benchmark. |
| Liquidity fields | Filters out assets with weak volume or unreliable trading history. |
| Ichimoku fields | Daily, weekly, and monthly cloud context for trend-confirmed strategy research. |
Why filters are combined
No single indicator is treated as sufficient. TrendRadar combines trend, momentum, liquidity, and historical strategy behavior because many standalone technical signals produce too many weak candidates.
The report labels are designed to make the reason for inclusion visible. A strategy badge links a current candidate to a documented historical rule set.
Known limitations
- Historical data can contain gaps, symbol changes, delistings, survivorship effects, or vendor corrections.
- Backtests use historical rules and cannot account for future liquidity, news, spreads, taxes, or execution quality.
- Some strategy ideas require intraday data; TrendRadar's primary research layer is daily/weekly/monthly unless explicitly stated.
- Published reports are research snapshots and may become stale as markets move.