The high-stakes world of the GR Cup Series demands split-second decisions. We realized that while race engineers have access to mountains of data—lap times, weather conditions, and tire telemetry—they often lack a unified tool to synthesize this information in real-time.
We were inspired to bridge the gap between raw data and actionable strategy. We wanted to build a "digital race engineer" that doesn't just show you what happened, but helps you decide what to do next. The goal was to democratize elite-level race strategy, making professional-grade analytics accessible to every team on the grid.
What it does The GR Cup Real-Time Analytics Dashboard is a comprehensive command center for race strategy. It features:
Real-Time Simulation: A playback engine that visualizes race positions and gaps as they happen. Strategy Calculator: An intelligent system that recommends optimal pit windows based on tire degradation and traffic. Weather Analysis: A correlation engine that links track temperature and wind conditions to lap time performance. Driver Insights: Detailed telemetry breakdown to identify where time is being gained or lost in specific sectors (S1, S2, S3). How we built it We built the application using a robust Python stack designed for speed and interactivity:
Streamlit: For creating a responsive, high-performance web interface that race engineers can use on any device. Pandas & NumPy: To handle the heavy lifting of processing thousands of lap time records and telemetry data points instantly. Plotly: For rendering interactive, zoomable charts that allow users to drill down into specific laps or sectors. Modular Architecture: We structured the codebase into distinct engines (race_simulator.py, strategy_calculator.py, weather_analyzer.py) to ensure the system is scalable and maintainable. Challenges we ran into Data Harmonization: One of the biggest hurdles was normalizing data from different sources (European vs. US CSV formats, varying column names) to create a unified data pipeline. Simulation Logic: Building a faithful "replay" system that accurately tracks race order, gaps, and lapped cars required complex state management logic. Modeling Tire Wear: creating a realistic tire degradation model without direct sensor data was difficult. We had to infer wear patterns from lap time decay and historical averages to create meaningful alerts. What we learned Building this dashboard taught us that context is king. Data alone isn't enough; it needs to be presented at the right time and in the right format. We learned a tremendous amount about race engineering—undercuts, tire fall-off curves, and the massive impact of track temperature on grip levels. Technically, we honed our skills in building stateful web applications with Streamlit and optimizing Python for real-time data processing.
🚀 What's next for GR Cup Analytics We plan to take this from a reactive tool to a predictive one. Our roadmap includes:
Machine Learning Integration: Training models on historical season data to predict lap times and tire life more accurately. Live Telemetry: Connecting directly to car sensors for true live-streaming analysis. Cloud Deployment: Hosting the dashboard for remote access by distributed race teams.
Log in or sign up for Devpost to join the conversation.