Home › Methodology
BoxBoxF1Fantasy Prediction Methodology
A transparent explanation of how BoxBox turns public F1 data into driver, constructor and lineup projections — what changes during a race weekend, how uncertainty is represented, and how errors are corrected.
What the system predicts
The pipeline first estimates qualifying and race finishing order for each driver. A separate fantasy layer converts those outcomes into expected points from qualifying, race position, positions gained or lost, overtakes, fastest lap, Driver of the Day, DNFs, constructor teamwork and pit stops. The lineup tools then compare legal combinations under the user's budget and chip settings.
Expected points are estimates, not promises. The deterministic projection represents one central finishing-order scenario. The risk-adjusted mean comes from repeated simulations that include uncertainty and adverse outcomes, which is why it can be materially lower than the deterministic figure.
Data sources and feature layers
The model uses public motorsport and weather data collected through FastF1, Jolpica, OpenF1 and Open-Meteo, alongside manually maintained fantasy prices and rules. Public outputs and source timestamps are documented in the data catalog.
- Historical priors: recent driver and constructor form, reliability, teammate comparisons, circuit experience and track-similarity signals.
- Practice telemetry: lap, sector, long-run and tyre-degradation features when current-weekend free-practice data exists.
- Session and weather context: qualifying grid when available, rain risk, temperature and track characteristics.
- Fantasy context: current prices, official scoring rules, pit-stop expectations, overtakes and DNF exposure.
Prediction models
Gradient-boosted ranking models estimate relative qualifying and race order rather than treating every driver as an unrelated regression problem. The race forecast uses the appropriate qualifying input for the current phase: a predicted grid before qualifying or the actual grid afterward. Practice pace can refine the qualifying view once telemetry exists.
The public explanation intentionally describes model families, data availability and behavior without publishing proprietary feature weights, manual ratings or tuning constants. That keeps the process understandable without turning the page into a recipe for reproducing every internal adjustment.
Race-week forecast phases
- Pre-practice: historical priors, current-season form, reliability and circuit context; no current-weekend practice telemetry.
- Post-practice: current-weekend practice pace is included. This is the primary actionable forecast before the usual fantasy lock.
- Post-qualifying: the actual qualifying grid can be included, but the normal fantasy deadline has usually passed, so this phase is mainly retrospective.
Every current race and profile page labels its phase. Data feeds can refresh at different times; for example, a weather forecast may be newer than the model run. When that happens, the page says the newer feed has not yet been applied rather than implying otherwise.
Fantasy scoring layer
The scoring implementation follows the current fantasy rules documented in the scoring guide. Drivers can score through qualifying, the race, overtakes, position changes and bonuses, with penalties for DNFs or disqualification. Constructors combine both drivers plus qualifying teamwork and pit-stop points. Driver boost multipliers never increase constructor totals.
Monte Carlo uncertainty
The fantasy simulation runs 10,000 scenarios for each round. It perturbs model scores, re-ranks the field and samples events such as DNFs, overtakes, fastest lap, Driver of the Day and constructor pit outcomes. Published P5 and P95 values form the displayed 90% interval; they are downside and upside markers, not best- and worst-case guarantees.
DNF risk includes driver-level reliability and incident exposure, with limited team correlation for shared mechanical failures. Weather can widen position uncertainty and retirement risk. These mechanisms are deliberately probabilistic because a single race cannot be forecast as one fixed script.
Validation and leakage safeguards
Historical rolling features are shifted so a training row cannot use the result it is trying to predict. Race-week archives are phase-labelled, and completed-round guards prevent an already-run race from being silently overwritten by a later model. Model and data changes are assessed against walk-forward or completed-round evidence where available rather than judged only on in-sample fit.
The Accuracy page publishes error and confidence-interval coverage for completed rounds. The Changelog records meaningful changes to models, scoring, data and tools. Accuracy evidence grows through the season; a small number of races should not be treated as proof that any model is permanently superior.
Corrections and version accountability
Report a suspected data, rule or explanation error to boxboxf1fantasy@gmail.com with the affected URL. Reproducible problems are fixed at the source or generator, affected outputs are rebuilt, and material changes are recorded publicly. Historical forecasts are preserved for accountability instead of being rewritten after the result is known.
Known limitations
- Practice programmes, fuel loads and tyre plans are not fully observable.
- Weather forecasts change and may update after a model run.
- Upgrades, penalties, strategic calls, safety cars and incidents can invalidate the expected order.
- Fan-voted Driver of the Day and exact overtake counts are inherently difficult to predict.
- Fantasy prices and rules can change; the official game remains the final authority.
Using the outputs responsibly
Use expected points as one input, then inspect the confidence range, DNF probability, value, phase and budget effect. Compare complete teams in Team Compare or the Optimizer. The site is independent, informational and intended for entertainment.
Prediction methodology FAQ
Does BoxBox use current-weekend practice data?
Yes, after free-practice data is available and the post-practice pipeline runs. Pre-practice forecasts explicitly exclude current-weekend telemetry and rely on historical and current-season priors.
What does the 90% confidence interval mean?
The displayed P5-to-P95 range contains the middle 90% of simulated fantasy outcomes. It is a probabilistic downside/upside range, not a guarantee that the actual result must fall inside it.
How does BoxBox prevent result leakage?
Historical rolling features are shifted so each training row uses only information available before that result. Completed-round and archive safeguards also prevent later data from silently replacing historical forecasts.
Why are all model weights not published?
The site publishes model families, data layers, phase behavior, uncertainty, validation and limitations while keeping proprietary feature weights, manual ratings and tuning constants private.
How can I report a prediction-data error?
Email boxboxf1fantasy@gmail.com with the page and issue. Reproducible source or rule errors are corrected, affected pages are rebuilt and material changes are documented in the Changelog.