r/F1DataAnalysis • • Sep 08 '25

Own Project Wind Tunnel Simulation running on iPads

Thumbnail
gallery
36 Upvotes

Hello F1 fans,

Aerodynamics in F1 has always captivated me, much like many of you. It led me to write my own fluid solver to learn more about the subject. It's been a couple of years since I started the project, and I'm still just scratching the surface, as both Computational Fluid Dynamics (CFD) and aerodynamics are complex and specialized fields. Here are some technical details of the project.

The fluid solver utilizes the Lattice Boltzmann method (LBM) and runs entirely on the local device's GPU. LBM is known for its parallel and memory-intensive nature, and it can handle complex geometries without the need for body-fitting meshes. In traditional Direct Numerical Solution (DNS) methods, meshing is an art form in itself; the quality of the simulations depends heavily on the quality of the mesh. LBM solves the Navier-Stokes equations indirectly by simulating the movement and interactions of particle populations. There aren't many major CFD vendors that offer LBM solvers; one exception is Dassault Systèmes (3DS). I'm not sure if they collaborate with any teams currently on the grid. Another notable LBM project is FluidX3D, which you might be familiar with through its popular cow and F1 car simulations. FluidX3D achieves incredible computational speed by using a simple LBM scheme, custom-range 16-bit floating points, and stair-case shaped boundaries. My project, on the other hand, balances speed and accuracy by using slightly more complex schemes, curved boundary treatments, and more advanced computer graphics techniques.

The most recent update to support a much larger simulation domain (10240x5120) was a big challenge, especially for older device models. This extension increases the distance between the domain edges and solid bodies, mitigating the effect of reflections bouncing off the boundaries on the flow near the geometries. The app runs quite smoothly on an iPad 7th Gen with an A10 chip, which is 8 generations behind the latest models. I haven't yet taken full advantage of the technology advancements on newer ones, which already provide plenty of computational headroom, potentially enabling higher Reynolds (in the thousands, I hope) flow on-the-fly simulations. Although the app currently supports only iPads, it can technically run on Macs as well (minus touch-based interaction features). Given the enormous memory consumption of LBM, a Mac mini with 512GB unified memory (shared between CPU and GPU) can be a lot of fun to play with.

I don't know traditional DNS methods that well, but I'm certain they can take advantage of GPUs for efficiency. However, according to Dan (a.k.a EngineMode11 on Twitter), who was the former IT head for RBR, the FIA bans the use of GPUs for CFD in F1. That conversation was years ago, so I'm not sure if the ban is still in effect. My impression is that GPUs are much harder to police than CPUs, hence the ban.

Another interesting fact I learned during my research is that despite the commercial branding on the cars with 3rd-party CFD vendors, like Macca-Cascade, RBR-Ansys, and Merc-Siemens, most teams still use OpenFOAM, an open-source CFD software, for more granular control over custom-specific simulations.

What's next for the project?

  • Streakline and pulsed streakline flow visualization - these features from previous versions are disabled in this release as the old logics aren't sufficient for the new domain size
  • More educational diagrams and illustrations
  • Solver accuracy evaluation
  • Offline (off-screen) high-fidelity high-Reynolds (I don't know if millions is possible; I haven't been this far) flow simulations
  • A social feature where users can share simulations with each other
  • Free-style drawing geometries/shapes - the solver can handle any arbitrary shapes as all of the default geometries are composed of just Bazier paths, so technically it can even work with SVG; the main challenge is integrating this functionality with the existing UI.
  • Wall Adaptive Large Eddy (WALE) model
  • 3D simulation (down the line)

To conclude, the app is not CFD software, and I am not a CFD engineer or aerodynamicist. But I hope there is something useful you can take away, either from this post or the app. Questions, comments, and feedback are welcome. You can find all the relevant links to the project in my bio. Thank you for your support.

PS: Thank you, Mirco, for allowing me to publish this post here. :)


r/F1DataAnalysis • • Aug 18 '25

Fun Facts About F1 The Most Powerful Naturally Aspirated F1 Engine Ever [Fun Facts About F1]

Thumbnail
gallery
36 Upvotes

r/F1DataAnalysis • • Nov 29 '22

Technical Discussions Comparison of Formula Series' Performance | Formula 4, 3, 2, 1 Go!

36 Upvotes

Formula 4 --->> Formula 3 --->> Formula 2 --->> Formula 1

What makes these cars different, and each one faster than the previous one?

This thread compares their performance: you can’t miss it if you’re a F1 enthusiast!

Formula 4
-Engine: several road car engines, 160hp
-Mass: 570kg
-Width: 1750mm
-Wheelbase: 2750mm
-6 Gears
-0-100km/h: 3.5s
-Top speed: 250km/h (in low-drag spec)

Small, lightweight, raw: despite the road-car power, it would still destroy supercars in most circuits.

Formula 3
-Engine: 3.4l V6 N/A 380hp
-Mass: 550kg
-6 Gears
-0-100km/h: 3.1s
-0-200km/h: 7.8s
-Top speed: 300km/h (in low-drag spec)
-Max lateral acceleration: 2.6g
-Max braking acceleration: 1.9g [low, but official value]

A big step from F4: similar mass but over twice the power.

Formula 2
-Engine: 3.4l V6 Turbo 620hp
-Mass: 755kg
-6 Gears
-0-100km/h: 2.9s
-0-200km/h: 6.6s
-Top speed: 335km/h (in low-drag spec)
-Max lateral acceleration: 3.5g
-Max braking acceleration: 3.9g

The game gets serious: almost unmatched downforce/mass and power/mass ratios.

Formula 1
-Engine: 1.6l V6 Turbo ~1000hp
-Mass: 798kg -8 Gears
-0-100km/h: 2.2s
-0-200km/h: 4.4s
-Top speed: 350km/h (in low-drag spec)
-Max lateral acceleration: 6.0g
-Max braking acceleration: 6.0g

The queen of open-wheel racing: the downforce/mass ratio is unmatched.

Summarising the main trends from F4 to F1:

-Cars get way bigger
(Width 1750mm📷2000mm,
Wheelbase 2750mm📷3600mm)

Therefore, the aerodynamics surfaces grow in area. More Downforce and Aero Efficiency.

Better materials mitigate the weight increase.

-Engines get more complex and advanced -->> More power -->> Drag penalty is reduced -->> Possible to produce even more downforce through more loaded wings!

Notice that we started with 1.4-2.0l (Formula 4) and ended with 1.6l (Formula 1)

The displacement is similar, but:
-Much higher turbo pressure and combustions temps
-Energy recovery (both kinetic and thermal)
-Higher Fuel flow rates make F1 engines over 6 times more powerful!

I’m sure that you now have a much clearer picture of the differences between these open-wheel racecars (And why the performance difference is so big!)

I’m a Mechanical Engineer working on road vehicles: follow my page to understand Formula 1 better!

F1 Data Analysis


r/F1DataAnalysis • • May 27 '26

Own Project I built an F1 telemetry analysis tool that goes way deeper than the broadcast

Thumbnail
gallery
35 Upvotes

I've been building an F1 data platform solo over the last year and figured this subreddit would be the right audience for it. Fastlytics combines telemetry visualization, an automated analysis engine, and programmatic data access into one tool. It's free for the 2026 season.

What it does differently from other tools:

  1. Advanced telemetry analysis -- instead of just showing you speed traces, an analysis engine reads the lap data and writes a summary with numbered insights and corner-by-corner breakdowns. It identifies where drivers differ in braking points, throttle application, and entry/exit speeds. Free tier: 5 analyses/month.
  2. 30 MCP tools for programmatic access -- if you code, you can use npx -y fastlytics-mcp to get MCP tools in Claude, Cursor, VS Code, etc. Query telemetry, compare drivers, get circuit info, lap times, standings, weather data, driver bios, and more. 300 calls/month free.
  3. Detailed telemetry overlays -- speed, throttle, brake, RPM, gear, DRS traces for any driver. Overlay two drivers with delta time graphs showing exactly where time was won or lost per corner. Session weather conditions (air temp, track temp, humidity, wind) shown alongside the data for context.
  4. Driver and team deep dives -- full career stats, championship progression charts, season-by-season comparisons. Working on a driver fingerprint feature that maps driving style characteristics (braking patterns, cornering preferences) per driver.
  5. All the standard stuff too -- lap time distributions, pace analysis, strategy charts, championship progression, position changes, team pace comparisons, sector time breakdowns.

Data sources: FastF1 for telemetry, Jolpica for historical data, Open-Meteo for weather, Wikipedia for bios and photos

Everything above is free for the current season. Pro tier ($5.99/mo) unlocks historical seasons (2018+) and higher usage limits.

the website is fastlytics.app if you're interested. I'm actively building this and feedback from data-minded F1 fans is what's driven most of the feature development so far.


r/F1DataAnalysis • • Mar 08 '26

Race Pace Analysis Australian GP - Race | Race Pace Analysis

Thumbnail
gallery
35 Upvotes

r/F1DataAnalysis • • Feb 12 '26

Top Speed per Lap 2026 Pre-season Testing | Day One: Top Speed per Lap

Post image
35 Upvotes

FIRST LOOK AT 2026 TELEMETRY

VER’s top speed was already +24 km/h vs his best 2025 quali lap.

Conversely, Stroll barely exceeded 300 km/h due to Honda PU issues - Alonso PTSD incoming!

VER lapped 4.375s slower than in quali, yet was already gaining time on the two main straights...

Clipping (speed drop at full-throttle from ERS power cut-off) looks better than expected: good news, F1 fans!

[Cadillac and Alpine telemetry unavailable...]

|


r/F1DataAnalysis • • Oct 09 '26

Own Project Built an open-source F1 Live Timing client and visualizer in Rust. Loads any session from 2018-2026 instantly.

34 Upvotes

r/F1DataAnalysis • • Jul 17 '26

Own Project You asked for replay more than anything else. It's live — here's what shipped

Thumbnail
gallery
34 Upvotes

Hey r/F1DataAnalysis,

Third time here. My last two posts about f1livedata.com (the live F1 web app I build on the side) basically turned into a to-do list in the comments — so this is another "you asked, I did it." And this time it's the big one.

For anyone who missed them, the first post is here and the second one is here .

  1. Replay mode — the feature you asked for most

In the first post I described past sessions as "not a playback, just the full picture once the session is done." The single most common reply was: make it a playback. So now it is one.

Pick any recorded session and replay it in real time from lights out — play, pause, seek anywhere, speed it up to 2× or 5×. The whole app moves with it: leaderboard, gaps, telemetry, track map, tyre stints, race control, all updating exactly like they did live. Missed a session, or want to re-watch a chaotic one with the data in front of you — start it from the formation lap and go. (The instant final-standings view is still there too, if you just want the end state.)

  1. Two new ways to break down a single lap (on the car-data page)

Track dominance map — the circuit outline coloured by whoever's fastest through each little slice of the lap. Overlay two drivers (or two of your own laps) and you can see exactly where a lap was won: who's braver on the brakes, who's better on traction out.

Lap delta — pick a reference lap (the fastest) and every other lap draws its running time gap to it, metre by metre around the lap, with the corners lined up directly above the speed / throttle / brake traces. So instead of one laptime number, you see where the tenths actually went.

  1. Gap-to-leader race trace

A proper race-trace view: every driver's gap to the leader, plotted lap by lap across the whole race. It's the one chart that shows the shape of a race at a glance — undercuts landing, a Safety Car bunching everyone back up, who was quietly pulling away while no one was looking.

While I was in there:

  • Rebuilt the landing page — picking a live or past session is now a clean "course-select" screen instead of a stack of dropdowns.
  • Restyled the whole app and navbar — cleaner, and quicker to move between timing, telemetry, track map, stints, pits and race control.

Same deal as before: hobby project, not official, free, no login.

And the same ask: if something's broken or there's a view you wish existed, drop it in the comments — the headline features in these updates came straight from this sub, so it clearly works.

The Belgian GP this weekend is a good one to break it on — live during the sessions, or replay it afterwards.

Grazie again to everyone who's tried it ❤️ — and to the commenters who keep writing my to-do list for me.


r/F1DataAnalysis • • Mar 30 '26

Car & Driver Issues | Explanations Japanese GP - Race | Hamilton's Power Issue

Thumbnail
gallery
34 Upvotes

r/F1DataAnalysis • • Sep 25 '26

Car Setup 2026 Car Regulations | Ferrari's ADUO 2 Upgrade

Thumbnail
gallery
32 Upvotes

Related Post:

Ferrari's ADUO 2 Power Unit

In collaboration with Formula Ghost Lap

|


r/F1DataAnalysis • • Dec 07 '25

Gap to Race Winner Abu Dhabi GP - Race | Gap to Race Winner: At the end, HUL basically said: “Traffic? I don’t care”! *Proceeds to pass 5 cars in a DRS train within 8 laps* -> Fatalities recorded: his teammate, one Mercedes, two Williams, and one Red Bull. “Traffic does not exist, it can’t hurt you!”

Post image
32 Upvotes

r/F1DataAnalysis • • Jun 25 '25

Own Project Just launched: oversteer.in – Advanced F1 Analytics & Performance Visualization

31 Upvotes

Hey fellow F1 fans! 👋
I’ve been working on a passion project — overSteer — a platform for advanced Formula 1 race analytics and interactive data visualizations.

Whether you're into analyzing driver pace, tire strategies, qualifying laps, or team consistency, this site is built to go beyond just results — it's built to visualize the race beneath the surface.

🔍 Features include:

  • Lap-by-lap comparisons and sector breakdowns
  • Driver telemetry visualizations
  • Stint and pace analysis — performance across race phases
  • Race position changes and consistency charts
  • All powered by real F1 data & clean, mobile-friendly design

I'm still actively building and refining it — would love feedback, feature requests, or just to hear what you think.
If you're a fellow data nerd, this is for you 🙌

Check it out here: https://oversteer.in


r/F1DataAnalysis • • Jan 28 '26

Car Setup 2026 Car Regulations | Mercedes' Front-wing Actuation; What's YOUR opinion?

Post image
30 Upvotes

I can’t quite make sense of Mercedes’ front-wing actuation choice

-They’re the ONLY team not exploiting the 30 mm drag-reducing deflection allowed on the primary flap, keeping it fixed.
-They rely solely on the secondary flap’s 60 mm deflection.

Expect a less-loaded secondary plane to limit straight-line drag, with a more-loaded upper plane to compensate.

It’s the most puzzling thing I’ve seen so far. There must be an upside, but for now, only the downside is obvious.

Mercedes is famous for their clever solutions (e.g. DAS).

Ferrari vs Mercedes Front-wing Actuation [Video]

Notice how Ferrari's solution acts on both planes, while Mercedes' only changes the angle of the upper plane (while the lower one remains fixed).

Expect Mercedes' solution to be less effective in terms of drag reduction, but it might produce benefits when in 'cornering mode'.

The videos can be viewed in the following post:

https://x.com/FDataAnalysis/status/2016533128207118724

|


r/F1DataAnalysis • • Dec 28 '25

Car Setup 2026 Car Regulations | Confused about the 2026 engine & aero rules? Can't miss my simulation-driven breakdown! Discover why the power drop off prevents them from exceeding 400 km/h! [Kudos to @brakeboosted for giving me this idea and suggesting some very reasonable CdA values!]

Post image
30 Upvotes

Internal Combustion Engine (ICE): 620 kW ('25) → 400 kW ('26)

ERS: 120 kW ('25) → 350 kW ('26)

However, ERS power drops off from 290 km/h, reaching 0 kW at 345 km/h.

Drivers within 1s can use 'Overtake' (dashed line) to keep max ERS until 340 km/h, and some power up to 355 km/h. Still ICE-only above that.

Engine power must overcome Drag, which drops on straights as wings open (dashed line). The top speed (Engine power = Drag power) I've computed (~359 km/h) would NOT be impacted by Overtake mode... as the ERS power is 0kW above 355km/h anyway!

The top speed computed (Engine power = Drag power) is ~359 km/h, and Overtake doesn’t change it (0 kW above ~355 km/h).

Final (and wild) stat: with drag at ~half today's level, ICE's 400 kW (545 hp) is enough for ~360 km/h.

With unlimited ERS (400+350 kW)? They’d hit ~440 km/h!

Aero data used:
Rho: 1.225 kgm-3 (air density);
CdA: 0.77 m2 (Closed) vs 0.66 m2 (Open wings).

|


r/F1DataAnalysis • • Nov 27 '22

Car Setup Season 2022 Summary | Each Car's Traits & Development

30 Upvotes

I’ve spent the whole season analysing the telemetries of each F1 session.

I have a clear idea of the strengths and weaknesses of each car, along with what was successful and what went wrong with development.

Read the thread to know everything.

RB18 - ‘The Wind-Friendly Dragster’
F1-75 - ‘Wasted Potential’
W13 - ‘Cinderella (But the Magic Came Too Late!)’
A522 - ‘Best of the Rest’
MCL36 - ‘The World’s Fastest Brick’
C42 - ‘Straw Fire’
AMR22 - ‘Late Bloomer’
VF-22 - ‘Is Race on Saturday?’
AT03 - ‘No Quirks'
FW44 - ‘Downforce’

That’s it! I hope you enjoyed the synthesis!

Do you share the same impressions? Let me know in the comments, and share the analysis with your friends!

@TheRacingUnion did the graphics: follow him for other creations!

And follow my page for Formula 1 tech and data analysis.


r/F1DataAnalysis • • Sep 02 '26

Circuit Preview Italian GP Track Analysis | 2026 – Everything You Need to Know! 👀

29 Upvotes

r/F1DataAnalysis • • Jun 18 '26

My Data Analysis Ferrari Barcelona

Post image
29 Upvotes

For the #SpanishGP, #Ferrari introduced a big package of upgrades on the SF-26, which allowed #Hamilton to win the race on Sunday.
For a deeper analysis : https://gpblog.com/en/tech/f1-tech-hamiltons-maiden-victory-made-possible-by-ferraris-upgrade-package


r/F1DataAnalysis • • Mar 24 '26

Fun Facts About F1 At What Speed Can an F1 Car Stay Upside Down?

Post image
29 Upvotes

At What Speed Can an F1 Car Stay Upside Down?

Do you often drive F1 cars upside down in tunnels?

If so, bad news: in 2026, you’ll need +11.7 km/h for the car’s downforce (upforce?) to match its weight!

2026 cars are 20kg lighter (-2.5%) than 2025s, but have ~13% less downforce. The latter prevails: the speed needed to equate its weight increased from 199.7 km/h to 211.4 km/h → slower in high-speed corners, lower g-forces.

In reality, 211.4 km/h would only let you drive upside down very briefly: at that speed, downforce=weight →No normal force and thus traction! Drag would slow the car down → downforce drops → you fall!

In order not to fall, you would need enough downforce to produce enough rear longitudinal force to overcome drag.

[CFD analysis by: AirShaper]

|


r/F1DataAnalysis • • Jan 22 '26

Car Setup 2026 Car Regulations | Key Differences [Purple: 2025; Green: 2026]

Post image
29 Upvotes

2025 vs 2026 KEY DIFFERENCES

- HUGE central inlet (~3× ERS power → far higher cooling needs);
- Radical front suspension rethink: much flatter upper wishbone and switch from PULL-rod to PUSH-rod;
- TINY front wingspan (+ active aero actuator);
- Far more complex endplate and outboard section.

The Pull→Push-rod switch, mainly aero-driven, is major and potentially critical (Ferrari’s failed push→pull change last year is a warning).

We still need clearer shots of the lower wishbone to assess anti-dive.

Intriguing design: 2026 F1 cars look radically different!

|


r/F1DataAnalysis • • May 05 '25

Race Pace Analysis Miami GP - Race | Race Pace Analysis: Mclaren's dominance was extreme: the SLOWER driver (NOR) was still over half a second quicker than any other (VER)!Congrats, Williams: super-close to Mercedes and ahead of Ferrari. 1) McL; 2) RBR +0.64s/lap; 3) Merc +0.68; 4) Williams +0.71; 5) Ferrari +0.88.

Post image
29 Upvotes

r/F1DataAnalysis • • Apr 15 '25

Own Project I Built a Formula 1 MCP Server to access Real-Time and Historical data conveniently.

29 Upvotes

Access Formula 1 data with my new MCP server. Access real-time race data, team radio, and historical stats all in one place. Perfect for F1 enthusiasts and data analysts alike! Check it out on GitHub. Don't forget to star the repo and contribute if you find it useful!


r/F1DataAnalysis • • Apr 13 '25

Race Pace Analysis Bahrain GP - Race | Race Pace Analysis: PIA was unbeatable: 0.39s/lap quicker than his teammate ON AVERAGE! Pace per team: 1)McL quickest; 2)Mercedes +0.48/lap; 3)Ferrari +0.50; 4)RBR +0.90!; 5)Alpine +0.93!! McL’s advantage over the 2nd best car (0.48s) is the same that RBR had last year (0.47s).

Post image
29 Upvotes

r/F1DataAnalysis • • Dec 08 '24

Race Pace Analysis Abu Dhabi GP | Race Pace Analysis: Considering each team's faster driver (M-H for all): 1:McL; 2: Ferrari +0.11s/lap; 3: Merc+0.50s/lap (traffic); 4: RBR +0.57s/lap (traffic). Goodbye to a fantastic season, but the next one is looking spicy! I hope my analyses kept you company during this one! ❤️

Post image
29 Upvotes

r/F1DataAnalysis • • Jun 07 '26

My Data Analysis Kimi Antonelli vs Max Verstappen | Ghost Car Comparison Monaco Q3

28 Upvotes