Rider handbook
Turn a Diablo Super Biker GPX export, or a RaceBox CSV export, into a map, synchronized telemetry, lap or mountain-run comparisons, and a local history of your progress.
Drop your lap-timer file into the page and the session opens on Summary: what happened, where it happened, and what to try next. That one screen is enough to walk away with something for your next stint.
Everything after it is optional depth. Analyze is one session in detail, Compare puts two laps side by side, Coaching collects what the recording actually supports, and Progress keeps your history on this device.
If you read only one section of this guide, read Quick start. The rest is here for when you want it — and for what each number means, see the KPI reference.
.gpx file or a RaceBox .csv export anywhere in the window, use the Load session button in the always-visible top bar beside the Trackday Analyst chicane mark to browse or pick a bundled sample, or choose a sample card from the welcome screen. Personal files are processed in this browser and never uploaded. (RaceBox's other export formats — VBO, KML, its own GPX — are not supported; always use the CSV.)
Before you load anything, the top bar offers only Summary and Progress — the workspaces that can actually show you something. Analyze, Compare and Coaching appear as soon as a file parses.
With a session open, the Load session panel also offers Close session. It closes the file and returns you to the welcome screen, clearing the session, its selected lap or run, comparison choices, cursor and playback state. Your saved Progress records, stored notes, preferences, theme and backups are kept — closing is not deleting, so it asks no confirmation.
Opening a workspace from a button inside the page — Compare laps on Summary, for instance — takes you to the top of that workspace, with its heading, headline figure and map in view. Choosing a workspace you have already visited from the top bar returns you to the spot you left it at. These positions last only for the open session and are never written to your device. If your system asks for reduced motion, the app jumps straight there instead of animating.
The whole entry journey is keyboard-reachable. Time and distance sliders are ordinary range controls (arrows, Page Up/Down, Home, End) and announce the coordinate, lap and sector rather than a bare number. Gains and losses are stated in words and signs, so nothing essential depends on telling red from green. The canvas charts each carry a text readout beside them with the current position and values, and the N-lap overlay has its own keyboard distance control.
Circuit sessions with at least two complete laps include one Coaching section. Its leading recommendation is open, while supporting advice, consistency figures, and source evidence are available on demand.
In Analysis mode, Coaching profiles show ranked demonstrated sector opportunities, their KPI values and best-lap reference, consistency figures, and data-confidence context. Unavailable analysis is stated explicitly; the profiles do not claim unrecorded rider inputs.
Summary and Coaching now locate the same lead corner on a compact map. Summary keeps only the first-level explanation; Understand this finding opens the fuller Coaching evidence, while Inspect telemetry opens Analyze on the reference lap with Corners active and the cursor already inside that corner.
When a session localizes repeatable time loss to one corner, that finding opens into what measurably differs there against your own best lap: where speed starts falling on the approach, how fast you are at the slowest point, your speed entering and leaving, how long the corner is spent with no speed change the recording can resolve, and how far your path sits from the path your best lap took. Each line carries its magnitude, a ± uncertainty, and the source channel it came from.
It does not say you braked too hard, used the wrong gear, or should have opened the throttle earlier — your device records none of those. It does not compare you to an ideal line; there is no such thing here, and every path comparison is against a lap you rode yourself. When several differences show up at one corner it lists them side by side and says outright that the recording cannot rank one of them as the cause.
A difference that cannot be told apart from measurement noise keeps its number and loses its sentence; those sit behind What could not be shown with the reason each was withheld. On a typical session most of the five are quiet, and the ones that speak are the ones the data supports. They need a recording at 20 Hz or better; below that — which includes every standard ~1 Hz Diablo export — all five are unavailable, and Coaching names each one with the frequency it would have needed rather than leaving a blank.
On recognized circuits, white transverse lines mark S2 and S3, and the finish line carries a permanent S1 label — all three sector labels (blue boxes) show in every view, whether or not a lap is selected. Numbered corner-apex markers (violet circles, shown when you turn on Corners) are a deliberately different colour and shape from the sector labels, so turns and timing gates are never confused. At desktop widths, Focus map gives the map the wide column and remembers the choice across Analyze and Compare.
At desktop widths (1200px or wider), Analyze starts with a full-width map plate. Below it, the sticky left rail keeps lap/run selection and compact cursor details visible while the sheet workbench uses the normal page flow. There is only one page scrollbar.
Choose Telemetry, Laps & sectors (or Runs & sectors for road sessions), Corners, Notes, or Telemetry controls from the workbench strip. Corners is absent for road sessions; only one detail group is shown at a time and the strip wraps safely on phone-width screens. Coaching is not one of these tabs — it is its own workspace in the top bar.
Click a lap to restrict the map, cursor, and charts to it. The table stays in the main Analyze flow on desktop, so it never forces a second map-column scrollbar. Best lap and best sector values are highlighted; the unfinished in-lap stays visibly separate. Pannónia-Ring can derive lap boundaries from its reviewed start/finish when Diablo left every lap marker empty; no sectors are invented.
The map appears before the lap/run selector. With a complete lap selected, a Corners button shows or hides the numbered corner-apex markers (off by default). Use Color by → Lean (φ) for blue left lean, silver upright running, and orange right lean; other channels retain their own ranges. The map automatically re-frames when containers resize.
Analyze stays clear of outage banners. Sampling thresholds, genuine outages, classifications, and gap details live in Session data. When acceleration is derived from lean and GPS, the compact ! opens and focuses its full limitations explanation there. The Session-data tab triangle still summarizes device or position limitations.
With a complete circuit lap selected, open the collapsed Corners section to see the same entry, minimum, exit, lean, and roll-rate readings used in Compare. Choosing a row moves the shared map cursor to that apex. On RaceBox CSV sessions, the small gyro label beside Max roll means that value is measured by the gyroscope and Kalman-fused; sessions without that label keep the existing lean-derived calculation.
Reads the current cursor. Derived longitudinal/lateral G say (derived) and carry D; vertical aZ remains a labelled recorded channel. Use raw accelerometer switches the inspector, strips, controls and G-G diagram together.
A collapsed-by-default section in the main Analyze flow. Click Add note, then click a spot on the map to drop a short text note there. Notes appear as pins; click one (on the map or in the list) to edit or delete it. Saved on your device only, and they resurface when you reload or load a different export of the same circuit.
Under the telemetry strips, the secondary panels are grouped into collapsible sections to keep the view clean. Toggle states are preserved during view navigation:
+difference together. The best lap is green and labelled Fastest; the hatched in-lap is excluded from the scale. Selection is shared with the table.! opens the single full limitations explanation in Session data → Telemetry quality.Select two complete laps to compare side-by-side using the balanced Lap A and Lap B card pickers. Click Change on either card to open an inline lap list showing each lap's duration, maximum lean angle, and consistency chart. When you switch from the Analyze tab, your active Analyze lap is pre-selected as Lap A. When no Analyze lap is active and no selection is persisted, the app pre-selects your best lap as Lap A and second-best lap as Lap B (or the two longest same-direction runs in road mode). Cross-session loading is folded cleanly inside the Lap B card. Your selection is remembered across reloads for the same session.
Debrief presents the best lap/run, ideal gap, consistency, and prioritized evidence coaching cards. The first is the focus; each keeps its supporting values expandable and offers an honest next-session experiment.
At desktop widths (1200px or wider), the Compare view is split into two panes: the left pane is sticky and displays the track map (auto-fitting layout size), ghost replay controls, the live A/B comparison readout panel (ComparePanel showing current speed, lean, and delta time readouts), and the circuit match notice banner. The right pane houses the card pickers (with Session B controls inside the Lap B card), comparison summary card, coaching summary panel, and the Compare detail tabs (Telemetry, G-G diagram, Corners). Below 1200px, it stacks into a single column, map first. Switching tabs preserves the pair and replay position. Road comparisons show Telemetry and G-G.
See both recorded paths; a Corners button toggles numbered corner apexes (off by default, using official turn names like T1, T2 when matching a recognized circuit layout, or sequential numbers as fallback). The side panel follows the ghost position with speed, lean, and cumulative Δt.
Enabled by default to make B green where it gains and red where it loses (the dashed B identity remains underneath). Toggle off via checkbox if desired (remembered in preferences).
Play, pause, reset, scrub, or choose 1×/2×/4×. Both colour-coded markers advance using recorded positions without floating labels obscuring the map.
Choose lap/run distance or elapsed time. Graph movement, slider/playback, map ghosts, and readouts share one nearest-recorded-sample position. Cumulative Δt appears only in distance mode.
The Corners tab starts with the selectable corner list. Selecting a row, a largest-local-change card, or Previous/Next updates the synchronized speed, lean, and cumulative Δt detail below; the map ghosts follow the same position.
Located in the Corners & coaching detail tab, this panel provides: (1) Neutral-motion cards that estimate the duration and share of qualifying leaned-over cornering time with near-zero derived longitudinal acceleration, plus comparison deltas; this is not a brake- or throttle-position measurement and has no universal better/worse verdict; and (2) a Corner Apex Diagnostics table displaying minimum speed, apex lean, and flick rate side-by-side. Click a corner apex row to snap the map cursor directly to that apex coordinate.
Review total time, each sector, maximum speed, and the overall signed B − A result side by side.
Both laps' longitudinal/lateral scatters share one circle — lap A as filled dots, lap B as open circles — with stats shown side by side. Reuses the same auto-detected fallback source (lean-derived lateral G vs GPS-derived longitudinal G) when the accelerometer is untrustworthy, ensuring a meaningful G-G overlay on circuit sessions.
Up to three neutral cards show where lap B gained or lost the most cumulative time and open that corner directly, without inferring a cause.
For circuit sessions with at least two complete laps, you can select "⭐ Ideal lap (best sectors)" as Lap B. This puts the workspace in a dedicated ideal-lap comparison mode:
If a file has no complete circuit laps but contains a useful elevation profile, Trackday Analyst switches to road mode. It derives alternating uphill and downhill runs without changing the original elevation samples.
The Analyze workspace provides two local downloads via a compact toolbar row at the bottom of the Analyze right pane. Nothing is uploaded while either file is created.
Downloads a clean schematic track outline with the selected lap or run highlighted and the current cursor marked. Satellite imagery is not included because the Esri tiles cannot safely be read back into a client-side canvas.
Downloads derived lap number, complete/incomplete status, lap time, best-lap marker, sector splits and best-sector markers, and maximum speed. Missing values stay empty; road sessions have no lap CSV.
Progress opens with the locally stored personal best, improvement across the selected venue's history, and laps ridden. Records and the trend remain derived from browser-stored summaries; grouping stays label-based.
Every loaded session contributes a small derived summary—date, best complete lap, lap count, and circuit label—to browser storage. Raw telemetry is never stored in the history.
Everything Trackday Analyst remembers—progress history, map notes, session notebook, preferences, and settings—is stored only in this browser. Clearing your browser's data erases it, and it never syncs between devices or browsers on its own.
The Local data panel (visible here even before you've loaded any session) lets you:
This is also how to move your data to a new device or browser: export from the old one, import into the new one.
Session data is the compact technical appendix: header chips summarize quality, and the channel provenance table distinguishes source, derived, low-quality, and absent channels without guessing missing coverage.
The expanded Session notebook stores motorcycle, tyres, front/rear pressure text, and a note for the current recording. Save is explicit; Clear removes only that recording's entry. Bike and tyre names remain as recent suggestions for later sessions, while the compact header summary omits empty fields and the long note.
Session data separates facts about the GPX from the analytical views, making data quality visible rather than silently repairing it.
! from Analyze or Compare opens and focuses Derived acceleration limitations here.Your device does not measure cornering load usefully, so where you see Lateral G (modelled) the app has worked it out rather than watched it happen. That is what "modelled" means, and it is why the word is on the label.
The calculation starts from your lean angle: a leaned-over motorcycle balances cornering force against gravity, so the angle tells you the load. It also allows for the fact that a real tyre has width — as the bike rolls, the contact patch moves toward the inside of the corner, shortening the lever the load acts on. A textbook calculation that assumes a knife-edge tyre reads about 10–25 % high.
The one thing it cannot see is you. The model works out where the bike is leaned, not where your body is. Hang off and you move the combined centre of mass inward, so the bike leans less for the same corner speed — and the figure reads low. No lean-based calculation can correct for this.
The Lateral G check, in Session data, shows whether the model is holding up on your session. The app separately measures cornering load from the path your GPS recorded and reports the ratio between the two. A value near 1.00 means the two agree. Consistently below 1.00 is the body-position effect above. The check needs enough fast corners to mean anything — it uses only samples above 0.3 g and needs at least a hundred of them, so a short or slow session will say it has not got enough to tell you.
Scan the whole session first, then select one lap or run and increase timeline zoom around an interesting braking or corner sequence.
A faster lap can lose in one corner and recover elsewhere. Use the Δt trace together with speed, lean, and the map.
A gap, missing value, or implausible channel remains missing or visible. Check Session data before drawing a strong conclusion from a strange graph.
Laps and sectors follow Diablo labels; ideal laps, distance alignment, runs, corners, braking points, deltas, and the coaching summary are calculations made by Trackday Analyst. Notes are the exception — your own typed text, stored as-is.