Model Overview
CryptoView Pro offers three distinct models, each optimized for specific use cases:| Model | Best For | Time Horizon | Key Strengths |
|---|---|---|---|
| XGBoost | Short-term predictions | 1-72 hours | Fast, accurate for momentum |
| Prophet | Long-term forecasts | 1 week - 1 year | Trend detection, seasonality |
| Hybrid | All-purpose | Any timeframe | Combines both models |
XGBoost Model
When to Use XGBoost
Use XGBoost for:- Intraday trading (6-24 hours)
- Swing trading (1-3 days)
- High-frequency decisions requiring fast predictions
- Volatile markets where momentum matters
Technical Details
XGBoost uses gradient boosting with extensive feature engineering:Feature Engineering (app.py:50-128)
XGBoost creates 50+ features including: Returns:Strengths
- Fast training and prediction (< 5 seconds)
- Captures short-term momentum and patterns
- Feature importance analysis available
- Handles non-linear relationships well
- Robust to outliers
Limitations
- Degrades beyond 72 hours - predictions become less reliable
- Requires 500+ data points for good performance
- No built-in trend detection - relies on recent patterns
- Sensitive to distribution shift - needs frequent retraining
Optimal Configuration by Use Case
Day Trading (6-24 hours)
Swing Trading (24-72 hours)
Prophet Model
When to Use Prophet
Use Prophet for:- Position trading (1-4 weeks)
- Long-term forecasting (1-6 months)
- Trend analysis and market direction
- Seasonal pattern detection
Technical Details
Prophet decomposes time series into trend + seasonality + holidays:Key Parameters Explained
changepoint_prior_scale (0.001 - 0.5)
Controls how flexible the trend is:seasonality_prior_scale (1 - 20)
Controls seasonal component strength:Strengths
- Excellent for long-term trends (weeks to months)
- Automatic seasonality detection (daily, weekly patterns)
- Handles missing data gracefully
- Interpretable components (trend, seasonality)
- Wide confidence intervals reflect uncertainty
Limitations
- Poor for < 1 week - overkill for short-term
- Requires 100+ data points minimum
- Slower training (10-30 seconds)
- Less accurate for high-frequency patterns
- No feature engineering - only uses price and time
Optimal Configuration by Use Case
Medium-term (1-4 weeks)
Long-term (1-6 months)
Hybrid Model
When to Use Hybrid
Use Hybrid for:- Unknown time horizons - it adapts automatically
- Production systems - best general-purpose choice
- Model comparison - trains both models
- Risk management - combines predictions
How It Works
The Hybrid model intelligently weights XGBoost and Prophet based on prediction horizon:| Horizon | XGBoost Weight | Prophet Weight | Primary Model |
|---|---|---|---|
| 24h | 85% | 15% | XGBoost |
| 48h | 71% | 29% | XGBoost |
| 72h | 57% | 43% | Hybrid |
| 1 week | 0% | 100% | Prophet |
| 2+ weeks | 0% | 100% | Prophet |
Usage Example
Strengths
- Versatile - works for any time horizon
- Robust - blends model strengths
- Automatic selection - chooses best model
- Model comparison - easy to compare approaches
- Production-ready - handles edge cases
Limitations
- Slower training - trains both models
- Higher resource usage - 2x memory
- Complexity - harder to debug
Decision Framework
Quick Selection Guide
Detailed Decision Tree
Performance Comparison
Benchmark Results
Based on BTC/USDT 1-hour data (2000 points):24-Hour Predictions
| Model | MAE ($) | MAPE (%) | Direction Acc (%) | Speed (s) |
|---|---|---|---|---|
| XGBoost | 187 | 0.45 | 61.2 | 4.3 |
| Prophet | 312 | 0.73 | 54.8 | 18.7 |
| Hybrid | 215 | 0.51 | 58.9 | 23.0 |
7-Day Predictions
| Model | MAE ($) | MAPE (%) | Direction Acc (%) | Speed (s) |
|---|---|---|---|---|
| XGBoost | 892 | 2.14 | 48.3 | 4.8 |
| Prophet | 534 | 1.26 | 56.7 | 19.2 |
| Hybrid | 612 | 1.45 | 54.2 | 24.0 |
30-Day Predictions
| Model | MAE ($) | MAPE (%) | Direction Acc (%) | Speed (s) |
|---|---|---|---|---|
| XGBoost | N/A | N/A | N/A | N/A |
| Prophet | 1247 | 2.87 | 52.1 | 21.5 |
| Hybrid | 1389 | 3.12 | 51.8 | 26.3 |
Accuracy by Market Conditions
Advanced Selection Strategies
Ensemble Approach
For maximum robustness, use multiple models and average:Dynamic Model Switching
Switch models based on recent performance:Best Practices
- Start with Hybrid - Itβs the safest default choice
- Backtest before deployment - Always validate on historical data
- Monitor performance - Track prediction accuracy over time
- Retrain regularly - Models degrade as markets change
- Use confidence intervals - Never trust point predictions alone
- Combine with technical analysis - ML + indicators = better decisions
Next Steps
- Learn how to make predictions
- Understand result analysis
- Optimize with performance tuning