Learn / Data Acquisition & Analysis / Analysis software essentials: plots, overlays, XY, histograms, filtering, run notes
L1 · Foundation

Analysis software essentials: plots, overlays, XY, histograms, filtering, run notes

Most analysis is comparison. Know when to plot against time or distance, how to read XY plots and histograms, how filtering changes what you see, and how to keep run notes so data stays tied to a setup.

Analysis software essentials: plots, overlays, XY, histograms, filtering, run notes: L1 Foundation explanation

Pick the display for the question. A logger produces long lists of numbers; the software turns them into pictures.

  • Distance plots answer where: braking point, apex location, where time is lost. Use them for overlays, because a given track location stays at the same distance from lap to lap.
  • Time plots answer how long and how fast it changes: shift duration, brake build-up rate, damper response. Overlays against time drift apart as soon as lap times differ.
  • Track maps show where things happen; colour the map by a channel (gear, braking, damper direction) for quick orientation.
  • XY (scatter) plots show how two channels relate: lateral vs longitudinal g (the g-g "traction circle"), oil pressure vs lateral g, RPM vs speed (gear chart), front vs rear roll angle.
  • Histograms show distribution: RPM, throttle position, speed, damper velocity.
  • Run charts plot one statistic per lap across a run, a day or a season: average understeer angle, fuel per lap, full-throttle %.

Overlays are the core tool. Segers puts it bluntly: around 95 % of analysis is comparison, and software that can't overlay laps against distance isn't worth having. Always start with the speed trace because every setup or driving change aims to change speed. Then use the time-difference channel to find where the gain or loss happens, and only then look at why.

Keep notes with the data. Every file must link to a setup, fuel load, tyre set, track temperature and driver comment. Put the file name on the setup sheet and use the software's session-constant feature (static ride heights, motion ratios, spring rates, track widths) so math channels update when the setup changes. A file you can't link to a setup is noise.

Key formulas

Moving-average filter window
tfilter=nfst_{\text{filter}} = \frac{n}{f_s}
n
number of samples averaged
fsf_s
sampling rate (Hz)
tfiltert_{\text{filter}}
effective filter time (s)

Trackside takeaways

  • Overlay against distance, not time; start with speed, find the loss with delta time, then find the cause.

  • Time plots for durations and rates; distance plots for locations.

  • Filter as little as possible, show raw underneath, and use raw channels inside math channels.

  • Run charts of per-lap statistics reveal trends single-lap overlays hide.

  • Every data file must be linked to a setup, tyre set, fuel load and conditions – set this up before the event.

On your car

Pro-Am line-ups make driver-vs-driver overlays a daily job; build a dedicated template with brake pressure, throttle, steer and ABS/TC activity.

Check yourself

Question 1 / 4L1 · Foundation

Why should two laps be overlaid against distance rather than time?

Further reading
  • Segers – Analysis Techniques for Racecar Data Acquisition — Ch. 2 Data Analysis Software Requirements (§2.2–2.8)
  • Segers – Analysis Techniques for Racecar Data Acquisition — §2.6 Filtering
  • Segers – Analysis Techniques for Racecar Data Acquisition — §3.1 Check the Car’s Vital Signs · oil pressure vs lateral g scatter