Compare the same piece of track
Generated from
content/lms/data-interpretation-ii-advanced/01-beyond-the-basics/01-distance-not-time.md; edit the source file, not this page.
Source path: content/lms/data-interpretation-ii-advanced/01-beyond-the-basics/01-distance-not-time.md
Course: Read the data your hands can't feel
Module: Move past speed traces and guesswork
Estimated duration: 55 minutes
The core skill in this lesson is simple: when you compare laps, put distance on the horizontal axis unless you have a very specific reason not to. You are trying to compare what the car and driver did at the same piece of racetrack. Time alignment does not do that. If one lap reaches the braking zone earlier than another, then the two laps are already in different places at the same elapsed second. From that point onward, a time-based overlay can make two unrelated events look related, or make a real difference look like noise.
Distance alignment turns the overlay back into a driving question. At this distance down the lap, what was the speed? What was the brake pressure? Was the throttle open? Was the lateral load building, peaking, or falling? Did the time compare channel start to move here? Those questions are meaningful because they are anchored to the same part of the track.
This matters because most useful driver data analysis is comparative. You are rarely learning much from one isolated squiggly line. You learn by comparing this lap to that lap, this driver to that driver, this run to the previous run, or this setup to the earlier setup. The bonded material is blunt on this point: overlaying laps is one of the most powerful tools in the software, and comparison is the bulk of real analysis work. For you as an intermediate driver, that changes the job. You are not opening data to admire the shape of a trace. You are opening data to ask where the lap changed, what driver input changed with it, and whether that change is something you should repeat.
The distance overlay is the foundation of that question. It is the difference between comparing two braking zones and comparing one braking zone to the exit of a previous corner. A time plot can be useful for some forms of review, but it is a poor default for lap overlays because different lap times mean different locations at the same clock reading. The more the laps differ, and the longer the circuit, the more the traces pull away from each other. By the end of a lap, the time-axis overlay can be visually tidy while being analytically wrong.
Think of the track as the reference object. The brake marker, the apex area, the throttle pickup zone, the straight, and the next braking area do not move just because one lap is faster. Your data display should respect that. When the x-axis is covered distance, the cursor is asking what happened here. When the x-axis is elapsed time, the cursor is asking what happened then. For driving improvement, here is usually the better first question.
The mechanism: why time alignment lies
Suppose you overlay two laps by elapsed time. Lap A gets off a corner better and is faster down the following straight. Lap B is slower. At ten seconds after the lap start, Lap A may already be closer to the next braking zone while Lap B is still earlier on the straight. If you compare brake pressure, throttle, speed, or lateral g at that same elapsed second, you are no longer comparing the same task. You are comparing two different positions on the racetrack.
That is why the bonded data-acquisition text says the same-time events probably happen at different locations and the traces tend to diverge over the length of the lap. The problem is not just cosmetic. It damages causation. You might see a speed difference and conclude that one driver braked earlier, when in reality the faster lap simply reached the corner sooner. You might see a throttle trace open earlier in time and think the driver was more aggressive, when in distance terms the throttle pickup happened at the same place. You might chase a steering or lateral-g difference that is only an alignment error.
Distance alignment removes that specific failure mode. At 1,200 yards into the lap, both traces are being compared at 1,200 yards into the lap. At the entry to a corner, both traces are at the entry to that corner. If the speed is different there, that is a real difference at that location. If brake pressure begins earlier in distance, that is an earlier brake application on the track. If throttle opens later in distance, that is a later throttle application on the track. The overlay becomes a map of driver behavior rather than a stopwatch artifact.
This is also why speed is usually the first channel you inspect. Speed is the outcome channel. The intention of a setup change or a driver change is to influence vehicle speed somewhere. The speed trace does not explain everything by itself, but it shows where the result changed. A higher speed at a given distance usually means the car is covering the lap more quickly, and an increase in speed tends to reduce lap time. Once speed shows you where the lap changed, the input and state channels help explain why.
The right sequence is therefore location first, result second, cause third. Location comes from distance alignment and the track map or cursor. Result usually starts with speed and the time compare channel. Cause comes from the supporting channels: throttle position, brake pressure, lateral g, steering angle if you have it, and any other channel you actually trust. The sibling lesson on trustworthy channels belongs here because a distance overlay only aligns the question. It does not magically make a bad channel good.
Set up the display before you analyze
Do not start the analysis by dragging traces around randomly. Set up a repeatable display template. The corpus lists the software features that matter for this work: multilap overlays, time-difference plots, zooming, cursor functions, distance and time location, track mapping, statistical data by lap or section, session notes, unit switching, mathematical channels, filtering, and export. You do not need every advanced feature to learn, but you do need the basic comparison tools ready before the session. If you are still building the display template when someone asks for a speed, throttle, and RPM view, you are spending paddock time on setup instead of learning.
For this lesson, make one standard distance-overlay page. Put distance on the x-axis. Put speed on top. Under it, put the cumulative time compare or time lost channel if your software has one. Then add the driver-input channels you have: throttle position and brake pressure are the first pair. Add lateral g when you are studying cornering consistency, spikes, or how fully you are using the car. Add steering angle if your system logs it and if you have learned enough about that channel to trust it. Add a track map panel and make sure the cursor position on the graph corresponds to the cursor position on the map.
Keep the page clean enough that you can answer three questions quickly. Where did the time change? What changed in speed? What driver input changed nearby? If the display cannot answer those questions, simplify it. The Data for Drivers process is intentionally basic: overlay two laps, look for differences, use delta or compare time to prioritize, then identify the difference. That is not a beginner crutch. It is the discipline that keeps intermediate drivers from drowning in channels.
When you choose laps to compare, start with two laps that are close enough in context to make the comparison fair. The corpus points out that lap times can vary during a race because of tire degradation, fuel load, driver condition, endurance, traffic, track conditions, and consistency. Those factors do not make comparison impossible, but they change what you are allowed to conclude. If one lap was in traffic and the other was clear, a distance overlay can show the speed loss, but it cannot turn that into a pure driving-technique lesson. If one run had fresh tires and the other had tired tires, the speed and lateral-g differences may be real while the driver conclusion is weaker. Use session notes to protect yourself from false certainty.
The first-pass workflow
Start with two laps. One can be your best clean lap from the session and the other can be a lap you want to understand. Or one can be your lap and the other can be a coach, co-driver, or reference driver in the same car if you have that data. Use distance as the x-axis before you inspect anything else.
First, scan the speed traces. Do not explain yet. Just look for where the traces separate at the same distance. A separation in the braking zone means a braking, entry-speed, or approach-speed question. A separation through the middle of a corner means a minimum-speed, line, rotation, or grip-use question. A separation on exit means a throttle, steering-release, traction, or earlier-corner question. You are not proving the cause yet. You are identifying where the result changed.
Second, scan the time compare or time lost channel. This channel helps you prioritize. You do not need to chase every wiggle. Look for the biggest changes first, because those are the places most likely to matter. On many systems the time difference is cumulative, so a gain or loss remains visible later in the lap after it has occurred. Learn your software's sign convention, then use the shape of that channel to decide where to zoom in.
Third, zoom into one location at a time. Put the cursor at the beginning of the speed separation or the steepest change in the time compare channel. Use the track map or distance markers to identify where you are. This step is not optional. If your note says slower in the middle somewhere, you have not learned enough to change your driving. If your note says Turn 3 entry, braking begins 35 yards earlier, with similar peak pressure but longer brake duration, you have a usable practice target.
Fourth, compare the inputs at that same distance. Brake pressure tells you whether the speed reduction came with braking. Throttle position tells you whether it came from a lift or delayed application. Lateral g tells you whether the car was being asked for cornering load consistently from lap to lap. Steering angle, when available and trustworthy, can help you see whether a difference might be line or steering demand. The Data for Drivers material is careful here: after a speed drop, ask whether it came from throttle lift, braking, steering angle, line, traffic, vision, mental image, or perceived bravery. Data may show the input difference, but it does not always show the human reason behind it.
Fifth, write the smallest useful conclusion. A useful conclusion has a location, an observed result, an observed input difference, and a practice action. It should not try to explain your entire driving personality. For example: at the entry to the slow right before the back straight, the blue lap carries 4 mph more at the same distance. The red lap shows brake pressure beginning earlier and lasting longer. Next session, keep the same initial brake marker, but release sooner and verify that minimum speed and exit throttle do not get worse. That kind of conclusion can be tested. A vague note like need more confidence cannot.
Worked example: Silverstone speed overlay
The Silverstone example in the corpus is a clean model for your first pass. Two laps are overlaid. The instruction is to begin with the speed traces because every setup or driver change is meant to influence vehicle speed. Then you find where the gains and losses are with the time compare channel, and only after that do you find out why they occur.
Apply that sequence exactly. Imagine the speed traces separate before a braking zone. If the faster lap is still higher in speed at the same distance, do not immediately say the driver was braver. Check the brake pressure trace. The difference may be a later brake start, a lower peak pressure, a shorter brake duration, a different release shape, or a higher approach speed from the previous corner. Check throttle before the braking zone as well. The faster lap may simply have reached the braking area with better exit speed from the prior turn.
Now imagine the time compare channel shows the largest change on corner exit rather than entry. The speed trace may show similar minimum speed, but one lap's speed rises earlier after the corner. That points you toward throttle pickup and steering release, not just brake point. If throttle position opens earlier at the same distance and the car accelerates sooner, you have a practical target. If throttle opens earlier but speed does not improve, the cause may be elsewhere, such as grip use, line, or a channel you do not have. The distance overlay lets you keep those possibilities tied to the correct piece of road.
The key Silverstone lesson is procedural. Speed first. Time compare to prioritize. Supporting channels to explain. Distance axis throughout. If you reverse that order, you are more likely to defend a story than discover one.
Worked example: Nürburgring and the long-lap problem
The Nürburgring example matters because long laps punish time-based overlays. The corpus describes two speed traces overlaid around the Nürburgring and uses that example to show how vehicle speed can be compared directly for every location on the track. That phrase matters for your analysis habit. Every location on the track is exactly the job of a distance overlay.
On a long circuit, small time differences early in the lap can turn into large location differences later. If one lap is half a second ahead before a later complex, the same elapsed time no longer represents the same section of asphalt. A time overlay may still show two lines on top of each other, but the comparison has drifted away from the driving task. By contrast, a distance overlay lets you zoom into any later section and still ask the same question: at this part of the track, what was the speed and what did the driver do?
Use long-lap tracks to train discipline. Do not let the first sector dominate your interpretation of the rest of the lap. If the time compare channel shows an early gain, remember that the speed and input traces still need to be inspected by distance later on. A later loss might be hidden visually in a time plot because the laps are no longer aligned by place. A distance plot keeps the late-lap evidence readable.
This also protects you from overvaluing the final lap time. The final lap time tells you which lap was faster overall. It does not tell you whether the faster lap was better everywhere. A distance overlay can show a faster overall lap that still loses time in a specific section. That is valuable because your next improvement may come from the section where your best lap was weak, not from copying everything about the faster lap.
Worked example: Lime Rock Park, red lap versus blue lap
The Lime Rock Park chunk gives a realistic driver-analysis setup. The visible overlay includes GPS speed, throttle position, front brake pressure, and time lost plotted against distance, with red and blue laps and a track map. The teaching prompts ask what questions the overlay generates, what led to the reduction in speed on the red lap, and whether the cause was throttle lift, braking, steering angle, line, traffic, vision, mental image, or perceived bravery. It also reminds you that data does not give all the answers.
That is exactly how you should handle a distance overlay when the slower trace is obvious. Start with the red lap's speed reduction at the same distance. Do not treat the speed drop as the explanation. Speed is the symptom. Then look down to brake pressure. If the red lap shows brake pressure where the blue lap does not, or shows more pressure for longer, braking is part of the observed difference. Then look at throttle. If red lifts where blue stays open, the speed loss may have started before brake pressure. Then look at the time lost channel to see whether this difference is a small local wiggle or a major contributor to the lap.
The next step is not to pretend the graph can read your mind. If brake pressure explains the physical speed reduction, you still need the human why. Maybe you looked at the wrong reference. Maybe your mental image of the corner made you think the car could not carry more speed. Maybe there was traffic. Maybe you were managing risk. Maybe your line forced the brake. The data can narrow the question from slower somewhere to brake pressure began here while the comparison lap stayed off the brake. That is already a major improvement. But the final answer may require your memory, instructor feedback, video if available, or another lap.
The Lime Rock example also shows why you should not separate data analysis from practice planning. If the red lap lost time because of an unnecessary brake tap, the next-session target might be to drive three laps using the same turn-in reference while removing that brake tap only if the car remains settled. If the red lap lost time because throttle opened later after the corner, the target might be earlier eyes and earlier throttle pickup, verified by both throttle trace and speed rise. The distance overlay gives you a precise place to practice rather than a vague feeling to chase.
Sub-skill 1: hold the distance-axis discipline
The first sub-skill is simply refusing to analyze a lap overlay on the wrong axis. That sounds basic, but it is where many bad conclusions begin. Your rule is: if the question is about driving at a location on the track, use distance on the x-axis. If your software defaults to time, change it. If a screenshot from a friend is plotted by time, ask for the distance version before making a driver judgment.
This discipline is especially important when two laps are different enough to be interesting. The moment one lap gains time, the laps separate in physical position when viewed by elapsed time. That is the same moment you most want the comparison to remain trustworthy. Distance alignment keeps the evidence tied to the racetrack.
A useful self-check is to move the cursor through the overlay and watch the track map. If the traces are being compared at the same distance, the map position should make sense as a shared location. If the display shows time location and distance location, use the distance value for your driving notes. You are not trying to remember that something happened 42.6 seconds into the lap. You are trying to remember that it happened at the entry, middle, or exit of a specific section.
Sub-skill 2: separate where from why
Intermediate drivers often jump straight from a trace difference to a coaching conclusion. The bonded material points you toward a better order. First find where the gains and losses are. Then find out why they occur. This order matters because a why without a where is hard to practice, and a where without a why is just a marker on a graph.
Use the time compare channel for where, not as the whole explanation. A rising or falling time-difference shape tells you that something important happened around that distance. The speed trace tells you how the result changed. Then the other channels help with why. If the time compare changes while speed traces are similar, the cause may be subtle or may be outside the channels you have. If speed changes sharply and brake pressure also changes, the first why loop is more direct.
Do not demand that every why be final in one pass. The Data for Drivers material explicitly pushes you to ask why and confirm issues with other channels. That is enough for one cycle. Your first pass should produce a testable hypothesis, not a courtroom verdict.
Sub-skill 3: use speed as the result channel, not the whole story
Speed is the best first scan because it contains the outcome you care about. A driver input that does not change speed, time lost, or consistency may still be interesting, but it is not the first priority when you are looking for lap-time improvement. The speed trace shows whether the car was faster or slower at the same location.
But speed does not tell you cause by itself. A lower speed at corner entry could come from earlier braking, more brake pressure, a lift before the brake zone, a worse previous exit, traffic, or a deliberate risk choice. A higher minimum speed could be good, or it could compromise exit if throttle pickup is delayed. A faster straight could come from earlier throttle, better exit speed, or simply carrying more speed onto the straight. That is why you scan speed first and then move immediately to the related channels.
The practical habit is to phrase speed observations without causation at first. Say: this lap is 5 mph slower at this distance. Then look for the input difference. Only after that do you say: the slower lap is 5 mph slower here and also has brake pressure beginning earlier. That wording protects you from making the trace say more than it knows.
Sub-skill 4: prioritize with delta or compare time
The compare-time channel is your triage tool. A lap has too many small differences to inspect all of them deeply. The Data for Drivers process tells you to use delta or compare time to look for the biggest differences and prioritize. That is how you keep analysis short enough to use between sessions.
Start with the two or three largest changes in time compare. For each one, identify the beginning of the change, not just the peak value later. Because some systems calculate cumulative time difference, the graph may show the accumulated result after the cause has already happened. Put the cursor where the slope begins to change, then inspect speed and inputs around that distance.
This is also how you avoid vanity analysis. It is tempting to stare at a dramatic-looking trace that did not cost time, or to defend a favorite corner because it felt good. The compare-time channel keeps the review tied to the lap. If a section produced the largest loss, it gets attention first. If a section looked messy but did not change time much, it can wait unless it has safety or consistency implications.
Sub-skill 5: confirm with other channels
The corpus specifically says to confirm lateral-g issues with other channels when available, and the same idea applies to every channel in this lesson. A single trace can mislead. A speed difference plus brake pressure difference is stronger than speed alone. A lateral-g spike plus steering change is stronger than lateral g alone. A throttle delay plus slower speed rise is stronger than throttle alone.
Use channel groups that match the question. For straight-line acceleration after a corner, speed and throttle are obvious. Brake pressure may still matter if the car is being held on the brake too long before exit. For corner entry, speed, brake pressure, and steering angle are more relevant. For mid-corner consistency, speed and lateral g may show whether the car is reaching similar peak loads from lap to lap. For understeer or oversteer analysis, the source list groups speed, throttle, front lateral g-force, rear lateral g-force, steering angle, and understeer angle, but only use those if your logger actually records them and you understand their reliability.
The goal is not to display every channel. The goal is to bring in the next channel that can confirm or challenge your current explanation. If adding a channel does not change what you will practice, it may not belong in the first pass.
Sub-skill 6: protect the comparison from context
Distance alignment makes the overlay spatially correct, but it does not make every lap equally comparable. The corpus notes that lap time and car-driver performance can change with tire degradation, fuel load, driver condition, endurance, traffic, track conditions, and consistency. These factors matter because they can create real trace differences that are not caused by the specific skill you are trying to improve.
Before drawing a technique conclusion, ask whether the compared laps were in a similar context. Same session is often better than different day. Clear lap is better than traffic lap for pure driver comparison. Similar tire life is better than fresh versus worn. Similar fuel load is better than full tank versus light tank if you are evaluating small differences. You do not need perfect laboratory conditions, but you need enough context to know what kind of conclusion you are making.
This is where session notes earn their place. If you know one lap had traffic, write that into the analysis. If the tires were old, write it. If the lap came late in a run when the driver was tired, write it. The overlay may still teach you something, but your conclusion should name the limitation.
Common mistakes
The first mistake is comparing by time because the graph looks familiar. What bad looks like: you line up two laps on elapsed seconds, see a difference late in the lap, and treat it as a driver-input difference. What good looks like: you replot by distance before judging any location-based event.
The second mistake is treating speed as the cause. What bad looks like: you say the red lap was slower because it had less speed. That is a result, not an explanation. What good looks like: you use speed to locate the loss, then inspect throttle, brake pressure, lateral g, steering, and context to explain it.
The third mistake is chasing small wiggles before large losses. What bad looks like: you spend twenty minutes on a tiny throttle difference while the time compare channel shows the biggest loss in a different section. What good looks like: you use delta or compare time to choose the first two or three areas of review.
The fourth mistake is making a human conclusion from a sensor trace alone. What bad looks like: you see extra brake pressure and decide the driver lacked bravery. What good looks like: you state the observed input difference, then ask why the driver made that input. Vision, mental image, traffic, and line may be the real practice topics.
The fifth mistake is ignoring lap context. What bad looks like: you compare a clean lap to a traffic lap or a fresh-tire lap to an old-tire lap and treat every difference as technique. What good looks like: you use notes and session context to limit the conclusion.
The sixth mistake is using an overloaded display. What bad looks like: twelve channels stacked so tightly that you cannot see the beginning of a gain or loss. What good looks like: a prepared template with speed, time compare, throttle, brake pressure, one or two relevant support channels, and a track map.
Drill: the two-lap distance-overlay pass
At your next event, do this drill after a session with at least two clean laps. The count is three passes through the same two-lap overlay. The total time limit is fifteen minutes. The success criterion is a written practice target with one location, one observed result, one observed input difference, and one next-session action.
Pass one is the location pass. Overlay two laps by distance. Put speed and time compare on the display. Without looking at throttle or brake yet, mark the three largest places where the time compare changes. Use the track map or cursor to name each location in driving language.
Pass two is the result pass. At each marked location, inspect the speed trace. Write only what changed in speed at the same distance. Higher, lower, earlier rise, later rise, deeper minimum, shallower minimum. Do not write a cause yet.
Pass three is the why pass. Add throttle and brake pressure. For each marked location, ask whether the speed difference lines up with a throttle difference, a brake-pressure difference, or neither. If neither explains it, add one relevant support channel such as lateral g or steering angle if available. If the channels still do not explain it, write that the data is inconclusive and name the context you need.
At the end, choose one practice target, not three. The target should be small enough to drive. For example: in the second braking zone, keep the same brake start but shorten the release by comparing brake pressure end point and minimum speed. Or: on the exit of the left-hander, verify earlier throttle pickup at the same distance without losing speed before the next straight. After the next session, repeat the overlay by distance and check whether the trace changed where you intended.
Calibration cues: how you know the skill is improving
You are improving when your notes become location-specific. Early notes sound like slower in sector two. Better notes say the loss begins at a specific distance or named track section, then identify the first visible change in speed or input. That precision comes directly from the distance overlay.
You are improving when you stop arguing from lap time alone. The faster lap is not automatically better in every section. You should be able to point to where it gains, where it loses, and which differences are worth practicing. The time compare channel should help you prioritize rather than replace your thinking.
You are improving when your explanations require more than one channel. Speed identifies the result. Brake pressure, throttle, lateral g, steering, and context help explain it. If every conclusion comes from one trace, you are probably over-reading the data.
You are improving when your review gets faster without getting shallower. The corpus emphasizes drawing the right conclusions quickly from large data sets. A good distance-overlay routine should let you produce one useful practice target in minutes. It should not become an hour of wandering through every graph.
You are improving when your practice target can be checked in the next overlay. A good target leaves evidence. If the target is to remove an unnecessary lift, the throttle trace should show it. If the target is to carry more speed at the same part of the track, the speed trace should show it. If the target is to improve consistency, the lap-to-lap traces should look more repeatable in the relevant section.
Where this lesson connects to the siblings
This lesson is not the whole data-analysis method. It is the alignment rule that makes the rest of the method trustworthy. The sibling lesson on channel trust belongs before any serious conclusion. If a brake-pressure channel, GPS speed channel, or lateral-g trace is unreliable, distance alignment will not save the interpretation. It only makes the comparison spatially valid.
The sibling lesson on the why loop belongs after this lesson. Distance overlay tells you where the difference happened and what changed in the traces. The why loop asks what caused the driver to create that trace. The Lime Rock example makes that boundary clear: the graph may show brake pressure and speed reduction, but the reason may be vision, mental image, traffic, line, or another human factor.
Keep the relationship straight. Distance overlay answers same place. Speed answers what result. Delta or compare time answers how much it mattered. Supporting channels answer what changed. The why loop turns that evidence into a driving plan.
The bottom line
Overlaying by distance is not a software preference. It is the rule that makes a lap comparison meaningful. You drive through space. The car brakes, turns, loads the tires, and accelerates at places on the racetrack. If you compare laps by elapsed time, the two traces can represent different places, especially once one lap has gained or lost time. If you compare by distance, the graph asks the question a driver can use: what happened here?
Use that rule every time. Plot laps by distance. Start with speed. Use compare time to prioritize. Zoom to the beginning of the gain or loss. Confirm with throttle, brake pressure, lateral g, steering, and context. Write one practice action. Then go drive and verify it on the next overlay.
Worked example: Silverstone speed overlay
The Silverstone example gives the cleanest workflow. Overlay two laps by distance, begin with speed, use the time compare channel to find the important gains and losses, and then inspect the supporting channels to learn why. If the speed traces separate before a braking zone, brake pressure and throttle are the first checks. If the traces separate on exit, throttle pickup and the earlier corner phase become the first suspects. The value of the example is not a special Silverstone trick. It is the order of operations: result, priority, cause, all at the same distance.
Worked example: Nürburgring and long-lap drift
The Nürburgring example shows why long laps make the distance rule more important, not less. When a lap gains or loses time early, a time-axis overlay compares different physical locations later in the lap. A distance-axis overlay still lets you compare speed at every location on the track. Use that discipline on long tracks by zooming into late-lap sections by distance, even if the overall lap-time story was decided much earlier.
Worked example: Lime Rock Park red lap versus blue lap
The Lime Rock Park overlay uses GPS speed, throttle position, front brake pressure, and time lost against distance. The useful question is not simply which lap is faster. The useful question is what created the red lap's speed reduction at that location. Brake pressure may show the input that reduced speed. Throttle may show a lift or delayed pickup. The time lost channel tells you whether the difference matters. The final human reason may still require context such as vision, mental image, line, traffic, or risk choice.
Common mistakes
The common failures are predictable: comparing laps by time, treating speed as the cause instead of the result, chasing small trace wiggles before the largest time changes, making a human judgment from one channel, ignoring context such as traffic or tire condition, and overloading the display with channels that do not change the next practice action. Good analysis does the opposite. It plots by distance, starts with speed, prioritizes with compare time, confirms with relevant channels, protects the conclusion with session context, and ends with one testable driving target.
Drill: the two-lap distance-overlay pass
After your next session, choose two clean laps and give yourself fifteen minutes. First, overlay them by distance with speed and time compare visible, then mark the three largest changes in the time compare channel. Second, write the speed difference at each marked location without explaining it yet. Third, add throttle and brake pressure and identify which input difference lines up with the speed change. If neither explains it, add one relevant support channel. Success is one written practice target with a location, an observed speed result, an observed input difference, and a next-session action.
Calibration cues
You are improving when your notes become location-specific, when the compare-time channel prioritizes your review, when your explanations use more than one channel, and when your practice targets can be verified on the next distance overlay. The goal is not to produce a longer analysis. The goal is to draw the right conclusion quickly from the data you already have.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Analysis Techniques for Racecar Data Acquisition | 298d8370-448d-3f4a-4164-cc740c02801e | 7 | 1 | uio_books_raw_v1 |
| 2 | Analysis Techniques for Racecar Data Acquisition | 2eefac2f-4698-d1cf-0f29-7c28c364bf3a | 6 | 1 | uio_books_raw_v1 |
| 3 | Data-for-Drivers-PRINT | c76265b3-e38e-d9dd-45b1-10446beb0a9b | 11 | 1 | uio_books_raw_v1 |
| 4 | Data-for-Drivers-PRINT | fffb9a6c-a16c-115d-f335-b680b9202b47 | 10 | 1 | uio_books_raw_v1 |
| 5 | Analysis Techniques for Racecar Data Acquisition | be2d8954-f3d6-95a0-e682-04b9cf37b698 | 6 | 1 | uio_books_raw_v1 |
| 6 | Analysis Techniques for Racecar Data Acquisition | e9455a82-2815-f3a9-fbe0-aedf29951909 | 6 | 1 | uio_books_raw_v1 |
| 7 | Analysis Techniques for Racecar Data Acquisition | 9998c72b-304d-0767-6517-dc3b82cea9fe | 6 | 1 | uio_books_raw_v1 |
| 8 | Data-for-Drivers-PRINT | 96a12794-6a20-0aa3-31d3-f6f0a4a1c964 | 15 | 1 | uio_books_raw_v1 |
| 9 | Analysis Techniques for Racecar Data Acquisition | 15474906-387d-234d-cb57-341d5efc4d3a | 5 | 1 | uio_books_raw_v1 |
| 10 | Analysis Techniques for Racecar Data Acquisition | 5eeea298-6191-0fb2-1054-b10fe574a804 | 2 | 1 | uio_books_raw_v1 |
| 11 | Analysis Techniques for Racecar Data Acquisition | 39682334-bcf0-1be4-aea0-3c7df650fbac | 20 | 1 | uio_books_raw_v1 |
| 12 | Analysis Techniques for Racecar Data Acquisition | 02718e3c-4223-992b-27c1-5d7766fc6883 | 20 | 1 | uio_books_raw_v1 |
| 13 | Analysis Techniques for Racecar Data Acquisition | 41138569-fa56-a0a4-38c5-301475e4131a | 21 | 1 | uio_books_raw_v1 |
| 14 | Analysis Techniques for Racecar Data Acquisition | d0db9128-dc9a-aec3-14a8-5f101654753f | 3 | 1 | uio_books_raw_v1 |
| 15 | Analysis Techniques for Racecar Data Acquisition | ad559d04-3651-61c2-d02b-5455aba0d7cc | 7 | 1 | uio_books_raw_v1 |
| 16 | Analysis Techniques for Racecar Data Acquisition | 52e7d5ab-412b-acc5-fb49-cb0e8d5511b1 | 6 | 1 | uio_books_raw_v1 |
| 17 | Data-for-Drivers-PRINT | b80dc634-a0a7-d6de-d470-353aed47e2a6 | 17 | 1 | uio_books_raw_v1 |