Analysis
Market regime analysis and conditional performance
Live Mathematical Analysis
Real-time price analysis via Coinbase — computing 30+ math features
BTC / USD
Spot--
0
0 / 500
+0.0000%
Waiting for price data...
Connecting to Coinbase WebSocket + REST fallback
Chronos Range Prediction Accuracy
How close predicted high/low ranges land to observed ranges. Only evaluates rows with observed data (5 min+ old).
No observed ranges yet
Waiting for the first batch of predictions to age into the 5-minute observation window.
Predicted vs Actual Bands
Chronos predicted range (blue ribbon), current price (solid), and observed extremes (dashed)
Waiting for observed data
Ribbon fills in once predictions age into the 5-minute observation window.
Accuracy Scatter
Confidence vs range error — green dots are predictions where the high was hit
No scored predictions yet
Scatter fills in once the accuracy view backfills (5 min+ cadence).
Live BTC Price
Most recent ticks from market_pulse
No ticks landed yet
Chart fills in once the ticker service is streaming market_pulse.
Volatility Timeline
Realized volatility over the last ~300 ticks — thin line is 10s, thick line is 60s
No volatility data yet
Timeline fills in once the ticker service writes realized_vol fields.
Performance by Volatility
How the bot performs in different volatility environments
| Regime | Win Rate | Avg PnL | Trades | Health |
|---|---|---|---|---|
| Low Vol | 42.8% | +0.4 bps | 108 | |
| Med Vol | 39.5% | +-2.1 bps | 134 | |
| High Vol | 37.2% | +-4.3 bps | 70 |
Trend vs Range
Performance when BTC is trending vs consolidating
| Regime | Win Rate | Avg PnL | Trades | Health |
|---|---|---|---|---|
| Strong Trend | 43.1% | +1.2 bps | 82 | |
| Weak Trend | 39.8% | +-2.4 bps | 128 | |
| Ranging | 37.9% | +-3.1 bps | 102 |
BTC Correlation
Bot returns vs BTC price movement -- lower correlation = more independent alpha
Volume Regime Performance
How trade volume conditions affect bot profitability
Low volume weakness: Only +8.4 bps avg PnL during low-volume periods (72.1% WR). Consider reducing position size or filtering entries during low-volume hours.