Move the cursor · steer the lap
family

YAW· Drift Brain

A drift coach that reads the car's slip angle, so practice compounds instead of blurring.

Open the live siteyaw-e3r.pages.dev ↗
In progress
What it is

A drift is an angle held on purpose. This measures the angle, then coaches it.

Two things that grew into one. YAW estimates a drift car's slip angle — the angle between where it points and where it travels — from the sensors already in a phone. Drift Brain is the coaching system that reads it back.

Drift practice is hard to improve at because it is hard to see. A run feels good or bad, and the feeling is the only record. Measure the angle, corner by corner, and the reps start to compound: which corner is inconsistent, which one is already solved, what to work on next time.

It runs on the phone, installs to the home screen and works with no signal at the track. A Raspberry Pi is an optional upgrade, not a requirement — a fused motion sensor, a 10 Hz GNSS receiver, and a tap into the car's own ECU over CAN.

Drift Brain is a library of technique, track knowledge, series intel, budget and event history, structured so an AI reads it as context and the advice is about this car and these tracks rather than about drifting in general. The telemetry feeds it; the coaching reads it back.

The direction now is laps that can be compared between drivers, not just logged for one — a Strava for racing laps. Drift comes first, but the base is built for any racing car: lap times, sectors and where a lap was lost are worth as much to a grip car on a circuit, and the drift numbers ride on top. That was decided on purpose, against the app's own rules rather than around them: a run is a file that stays on the driver's phone and is sent to another driver to compare against, and backup is six optional words, not an account.

What it reads

Four channels, and what each one is for.

Slip angle

The core number. How far sideways the car is actually travelling, held against where it is pointed.

The line

Where the car went, drawn on satellite imagery of the real asphalt, timed through a start/finish and three sectors, and sharp enough to split a lap into corners.

Grip

Lateral and longitudinal g as a traction circle — how much of the tyre was being used, and where it ran out.

The engine

RPM, throttle, boost, gear, temps, pressures, lambda and wheel speed, read off the ECU's own CAN stream rather than inferred.

The phone gives the first three on its own. The Pi makes all four trustworthy.
How a run is judged

Graded the way a judge would, against the driver's own best.

A machine can't fake an FD judge on absolute style, so it doesn't try. The driver stars one run as the benchmark; every other run is resampled onto that run's distance grid, so two runs at different speeds compare point for point, and each is scored in the four categories judges use.

LineHow far the car strayed from the benchmark's line.

AngleHow well the slip angle tracked the benchmark through every on-angle zone.

StyleSmoothness and commitment, minus visible saves.

SpeedSpeed carried, station by station.

For lap time it goes corner by corner. Every lap is laid over the best one and split into a zone per corner, and each zone is read for speed in, the braking point, the slowest point and speed out. That gives an ideal lap — the best pass through every corner, strung together — and for each corner the time still on the table and the likely reason. A spin or a stop is named as one, not passed off as pace to find.

Then the coach: it names the weakest category as the place with the most leverage, prescribes one drill tied to a real technique note in the library, and gives one focus for the next attempt. Across sessions it ranks the leaks, keeps a list of what's working, and a session report exports straight back into the library's run log — so the coach remembers. A logbook keeps every session: what was best, personal bests as of the day they happened, what moved since the last visit to that track, and the one note the coach would leave.

Phone, then Pi

Everything works on the phone. The Pi turns estimates into measurements.

ChannelPhone aloneWith the Pi
headinggyro fused with GPS course; drifts over a runBNO085 absolute fused heading — the drift goes away
line1 Hz GPS10 Hz u-blox GNSS — ten times the resolution
engine—the Link ECU over CAN: RPM, throttle, boost, gear, temps, lambda, wheel speed
wheelspin—wheel speed against GPS speed
tandembuilt, waitingtwo identical units on one GPS clock
About $227 of parts for the v1 unit. The phone connects to the Pi over its own Wi-Fi at the track. The Pi is on hold for now: everything YAW has done at a real track, it has done with the phone alone.
Beyond one phone

The same runs at an event, between drivers, and in the sim.

At an event

A big screen for the paddock: every car live on the satellite map, boards a driver can read from across the tent, and a tap on any driver to follow them in 3D. Drivers join with a QR code, a phone at the track is offered a listed event, and the results sheet leads with most improved.

Between drivers

A run is a file. Send one to another driver and they lay it beside their own at the same track, corner by corner — nothing to sign up for.

In the sim

YAW Sim, a Windows app, puts a real run into Assetto Corsa as a ghost to chase, brings sim sessions back, and cuts every session into clips with the gauge on. Where a track has both, the sim lap is laid over the real one, corner by corner.

The car itself

One photo of the car becomes the car in the 3D replay — its shape, paint and wheels — driving the run over satellite imagery.

Free for drivers, for good: recording, their own runs, getting them out, their place on a board, and YAW Sim.
Drift Brain — the library

A crew chief that remembers everything.

10

Tracks

Layouts, judged zones, surface, initiation plans and setup, one folder each.

19

Technique notes

Initiation, recovery, style and transitions — the drills the coach prescribes.

6

Series

Intel on the championships worth entering, and how their judges score.

1

Run log

Event history and qualifying scores, fed by the app's session reports.

About a hundred files in all, with a season budget and an event-cost calculator. Opened in Claude, the whole library is the context.
Where it stands

The app is live and has been to the track. The phone does it alone; the hardware waits.

APP
COACH
EVENTS
TRACK
SIM
KIT
APP = phone app shipped · COACH = grading and coaching built · EVENTS = the big screen, judging and the bracket · TRACK = used at real track days and a first competition · SIM = YAW Sim and Track Builder out · OPEN = an event of drivers new to it · KIT = hardware in the car · the dashed tick is next
184
versions shipped
4
days at real tracks
29
runs at its first competition
4
judged categories
~100
files in the library

Built and running: the live heads-up display with slip arc and friction circle, hands-free recording with voice callouts, lap timing with sectors, a theoretical best and a live lap clock, a corner-by-corner lap coach, a logbook of every session, a course editor for marking corners on satellite, per-corner breakdowns, lap-against-lap comparison synced by distance, session trends, the grading and coaching above, engine and grip views, live spectating, and a tandem mode that reads two cars against each other — gap, proximity, line match, reaction lag. Since then: backup by six words (built, switched on once its storage is), any two laps compared across sessions and drivers, a 3D replay driven by the car itself from one photo, the event big screen with live 3D and events that find a phone at the track, and YAW Sim.

Since October it has been to the track: a first day at Thunderhill, its first competition at the Bullring, and two weekends at Sonoma. Around that it grew judges scoring on a tablet, a bracket, battle replays in 3D and the day's reel; the phone as a lap timer, its GPS and motion sensors joined into one live read and checked against a dedicated timer; Track Builder, which turns a real road or lot into an Assetto Corsa track from a phone; an organiser page for setting up an event screen alone; and YAW Sim as a public download.

What is left is people. Every day so far has been a driver or two who already knew it. The test that matters is an event of drivers who have never seen YAW, and whether they come back to the next one. The Pi is on hold; the hardware that comes after it is drawn, not built.

The road ahead

One unit proven in the car, then two cars, then the steering wheel.

Open threads

Whether a driver from one event comes back to the next · what the hardware after the Pi should be · which sensor earns the slot after that · a live coaching cue in the heads-up display once richer data is flowing.

Lineage — YAW Sim, its half on the sim PC (it began as DriftClip), whose clip overlay shares this data schema · VBOX and Racelogic, the pro telemetry it measures itself against · the FD judging criteria, which the grade follows.
Shipped
  1. A phone running YAW is now a lap timer, its GPS and motion sensors joined into one live read 25 times a second see it ↗
  2. An event organiser can now set up YAW's big screen for their event on their own see it ↗
  3. Track Builder turns a real road or car park into an Assetto Corsa track, from a phone see it ↗
  4. YAW went to its first drift competition and read every one of the 29 runs it was there for
  5. YAW Sim, YAW's Windows app for Assetto Corsa, can now be downloaded from YAW's sim page see it ↗
  6. DriftClip became YAW Sim, part of YAW: a page in the app says what it does on a sim PC, and the Windows download comes next see it ↗
  7. At a YAW event, tap any driver on the big screen and watch them drift in 3D, drawn live from their own phone a moment and a half behind see it ↗
  8. The event screen's demo opens in 3D: tap any driver and follow their real lap from a chase camera, with the overhead map kept in a corner see it ↗
Everything done, across all the projects →
It is liveyaw-e3r.pages.dev