Two runs, the same kart, the same driver, and half a second between them. Before you credit anything you did, look up. On most days the weather and the track surface change more, over a few hours, than any setup change you're likely to make — which makes conditions the biggest single reason two runs don't compare. Comparing sessions fairly means accounting for all of it; this is a closer look at the part that moves the most, and at why you can't simply subtract it back out.

What actually changes, and how it moves grip

Grip is the thing conditions move, and on a given day several of them move it at once:

  • Track temperature and rubber. As a track is used, rubber lays down and, within a sensible range, grip climbs — the classic "green in the morning, rubbered-in by the afternoon." Track temperature matters more than air temperature here, and it swings across a day, so both the surface and its temperature are shifting under you.
  • Moisture. Damp, wet, and drying tracks are a different world of grip — not a small adjustment but a large, moving one, with a drying line that changes lap by lap.
  • Wind. A headwind onto the main straight or a tailwind off the last corner changes terminal speed and braking; a strong crosswind can unsettle a light kart mid-corner. It's smaller than temperature and rubber, but it's real and it shifts.
  • Debris, dust, and traffic laying or sweeping rubber, so grip isn't even uniform within a session.

The point isn't to memorize which way each one pushes. It's to notice that on any given day several are moving together, and their sum is often larger than the setup or driving difference you're trying to read.

Why you can't just subtract conditions out

It's tempting to reach for a correction — knock a bit off the cool morning laps, add a bit to the hot afternoon ones — and compare what's left. Don't. The relationship between conditions and lap time isn't a fixed number you can look up: it depends on your track, your tires, your class, and where in the day you are, and it isn't even a straight line. A correction precise enough to trust would have to be measured for your exact tire and circuit, on the day — at which point you've done more work than simply comparing like with like would have taken. And false precision is worse than none, because it looks like an answer. So treat conditions as a reason a comparison is weaker or impossible, not a number you can multiply away.

Compare like with like, or don't compare

Since you can't correct it out, you control for it instead. In rough order of how much you can trust the result:

  • Compare within the smallest window. Two runs a few minutes apart, in the same conditions, are the only genuinely fair comparison — which is exactly why a back-to-back test is worth the trouble. The tighter the window, the less the weather moved inside it.
  • Use a reference to gauge the shift. If you can re-run a benchmark you trust — a repeatable lap of your own, or a marker you know — you can feel how much the track moved between two points and read your other runs against that, not against the clock alone. It won't hand you a number to trust, but it tells you the direction and roughly the size of the shift.
  • Group by condition, and flag the mismatches. Lining up a session's runs, keep the ones that shared conditions together and set the odd ones aside, or mark them plainly as not comparable.
  • Know when to stop. A cool, green morning and a hot, rubbered afternoon — or dry against damp — often can't be compared on absolute time at all. When that's the case, the honest move is to compare relative improvement within each block, or simply not to compare, rather than force a verdict the data can't support.

That's the three-way judgment every comparison needs under changing conditions: a useful reference, a rough clue, or an unfair comparison.

Record it, so you can tell which case you're in

None of this works from memory. Every run, note the conditions — track and air temperature and their trend, wet or dry and drying, wind, how green or rubbered the surface is, and anything unusual. That record is what lets you look back and say "these two are comparable, those two aren't," instead of guessing months later. It's the same session record the rest of this cluster leans on, and conditions are the fields it can least afford to skip. Knowing your own circuit helps too: most tracks have a familiar daily arc, and learning a track includes learning how it comes to you.

Use it to plan the next run

Finally, turn the comparison into a plan rather than an argument. If conditions made a comparison unfair, the fix is usually to repeat the test in a matching window — a similar time of day, similar weather — not to haggle over the numbers you already have. If your track runs a predictable arc, time your important tests for when it's stable rather than when the grip is swinging fastest. And whatever you conclude, note how much the conditions clouded it, because "clean comparison" and "best guess in shifting grip" deserve different weight the next time you look back.

Weather and track conditions are the quiet author of most confusing comparisons — the reason a run looks like progress, or a regression, when nothing on the kart changed at all. You can't subtract them out with a tidy formula, so the craft is to control for them: compare within tight windows, gauge the shift against a reference, record the conditions honestly, and know when two runs simply can't be weighed against each other. Do that, and the weather stops quietly writing your conclusions for you.