Production-oriented MLOps platform for real-time Motorsports telemetry analysis with automated model training, Pit Wall Monitoring Dashboard ,drift detection, and production deployment on AWS infrastructure.
Source: FM7 Rio de Janeiro Race Telemetry
This dataset contains race telemetry data recorded from the game Forza Motorsport 7 during a full race session on the Rio de Janeiro circuit. It captures per-car, time-series telemetry describing vehicle motion, control inputs, and race progress throughout the event.
The data includes information related to:
- Car state (position, velocity, orientation)
- Driver inputs (throttle, brake)
- Race context (lap number, lap time, race position)
- Track and session metadata
Each row represents a telemetry snapshot at a specific moment in time, making the dataset suitable for lap analysis, performance comparison, visualization, and machine-learning experiments related to motorsport analytics.
This dataset is sourced from in-game telemetry and reflects realistic racing behavior within the constraints of the simulation environment.
Real-time Components:
- ML predictions (lap time, gear, behavior)
- Live telemetry charts
- Vehicle attitude display
- Track position overlay
Monitoring Metrics:
- Inference latency & throughput
- Feature drift detection (PSI)
- System resource utilization
- Model performance tracking
- Target:
current_lap_time - Features: Speed, RPM, power, torque, boost, tire temperature etc.
- Hyperparameters: 600 estimators, 0.03 learning rate, depth 4
- Target:
gear - Features: Speed, RPM, throttle position, track position etc.
- Hyperparameters: 20 estimators, depth 4, min samples 100
- Clusters: 2 (Conservative vs Aggressive)
- Analysis: Wheel slip, steering variance, tire stress patterns etc.
- Key Differentiators: Slip ratios, RPM variability, steering corrections
python main.pyExecution Flow:
- Data Ingestion: MongoDB Atlas β CSV extraction
- Data Validation: Schema compliance & quality checks
- Feature Engineering: Temporal & vehicle dynamics feature enginerring
- Model Training: Multi-model training (regression/classification/clustering)
- Model Evaluation: Performance metrics & DagsHub tracking
- PostgreSQL data fetching
- Real-time model loading from DagsHub
- Multi-model prediction execution
- Drift detection & alerting
- Prometheus metrics collection
- Monitored Features: Speed, RPM, boost, torque, tire temperature
- Threshold: PSI > 0.2 triggers drift alert
- Bins: 10 percentile-based buckets
api_requests_total: Request counterinference_latency_seconds: Response time histogramfeature_psi: Drift metrics by feature
docker-compose up -d# Automated via GitHub Actions
git push origin mainInfrastructure:
- Container Registry: AWS ECR
- Compute: EC2 with self-hosted runner
- Orchestration: Docker Compose
- Monitoring: Prometheus + Grafana + Node Exporter
- Pit Wall:
http://localhost:8501 - API Docs:
http://localhost:8000/docs - Grafana:
http://localhost:3000 - Prometheus:
http://localhost:9090
Race-Telemetry/
βββ src/ # ML Pipeline Components
β βββ components/ # Data processing modules
β βββ models/ # Algorithm implementations
β βββ pipeline/ # Training & inference workflows
β βββ utils/ # Shared utilities
βββ backend/ # FastAPI Production API
βββ notebooks/ # EDA & Research
βββ config/ # Configuration files
βββ monitoring/ # Observability stack
βββ artifacts/ # Model artifacts & datasets
βββ .github/workflows/ # CI/CD automation
βββ app.py # Streamlit dashboard
βββ main.py # Training orchestrator
βββ docker-compose.yml # Local development
βββ docker-compose.prod.yml # Production deployment
- Inference Latency: P95 < 100ms
- Throughput: 1000+ RPS sustained
- Model Accuracy: Lap time RMSE < 0.5s, Gear accuracy > 95%
- Drift Detection: Real-time PSI monitoring
- Scalability: Horizontal scaling ready
Live demo - click here
- Training and inference are decoupled to prevent production outages caused by failed retraining runs.
- Models are loaded dynamically at inference time to support versioned rollouts and rollback.
- Artifacts are externalized to avoid container immutability violations.
- CI/CD uses a self-hosted runner to enable Docker-in-Docker and direct EC2 deployment.



