Glossary

Trail braking means keeping some brake pressure applied as you tip into a corner, rather than releasing the brakes completely before turning. This loads the front tire, giving it more grip for turning, and allows you to carry more speed into the corner entry.

Most riders release the brakes fully before turn-in because it feels safer. The problem is that releasing the brakes suddenly unloads the front tire right when you need it most, at the start of the turn. Trail braking solves this by gradually tapering brake pressure as lean angle increases, keeping the front tire loaded throughout the entry phase.

As a practical example, imagine entering Turn 5 at a typical track. Without trail braking, you brake in a straight line, release fully, then tip in. With trail braking, you begin tipping in while still on the brakes, smoothly releasing pressure as the bike leans. The result is a later, faster entry with more front-end confidence. Learning to trail brake typically unlocks 0.3-0.5 seconds per corner.

In LapBrain, you can see whether you are trail braking by looking at the overlap between brake pressure and lean angle in the turn detail view. When coaching suggests "no trail braking detected," it means you are releasing the brakes before the bike begins to lean.

The braking point is the specific location on track where you first apply the brakes to slow down for an upcoming corner. Getting this right is one of the most important skills in track riding. Brake too early and you lose time on the straight, brake too late and you enter the corner too fast to make a clean turn.

Consistent braking points are more important than aggressive ones. A rider who brakes at the same spot every lap can build confidence and refine their entry speed gradually. A rider whose braking point wanders by 20 meters from lap to lap never builds that confidence base. This is why most coaches teach picking a visual reference (a crack in the pavement, a track marker, or a shadow) and aiming for it every lap.

As you get faster, your braking point moves later (closer to the corner). This happens naturally as your trail braking improves, because trail braking lets you carry braking deeper into the corner. But chasing a later braking point without the skills to manage corner entry speed is a common cause of running wide.

In LapBrain, braking point consistency is tracked across laps. You can see how your braking point compares between your fastest laps and your average laps, and coaching may suggest adjustments when your braking point is significantly earlier than your own best performance shows is possible.

The apex is the innermost point of your line through a corner, where the bike passes closest to the inside of the track. It is usually near the geometric middle of the turn, though many corners reward a late apex (clipping the inside edge past the midpoint) because it sets up a better exit.

The apex matters because it defines the shape of your entire corner. An early apex feels fast going in but forces you to run wide on exit, often requiring a throttle chop to stay on track. A late apex feels slower on entry but opens up the exit, letting you get on the throttle earlier and carry more speed down the following straight. Since straights are where you gain the most time, a slightly late apex is almost always faster overall.

Different corners call for different apex strategies. A single-apex turn has one clear inside point. A double-apex corner, common in long sweepers, has two distinct inside points with a brief straightening in between. An opposite-apex complex links two turns in opposite directions, requiring a compromise line.

LapBrain identifies your actual apex position by finding the minimum-speed point or the closest point to the inside of the turn. The turn detail view shows where your apex falls relative to the track geometry, so you can see whether you are apexing early, late, or on target.

Turn-in is the moment you commit to the corner by initiating lean. It marks the transition from straight-line or braking to actual cornering. A decisive turn-in, quick and confident, sets up the rest of the corner. A hesitant or gradual turn-in often leads to a poor line and lost time.

The turn-in point is closely related to the braking point and trail braking. Ideally, you begin turning in while still lightly on the brakes, so the front tire is loaded and ready to grip. The combination of a consistent braking point and a confident turn-in is what separates smooth, fast corner entries from nervous, inconsistent ones.

In LapBrain, the turn-in point is visible in the turn detail as the beginning of lean angle increase. Coaching may highlight inconsistent turn-in points across laps, which often signals uncertainty about corner entry speed or line choice.

A throttle chop is a sudden, unplanned closing of the throttle while the bike is leaned over in a corner. It typically happens when a rider enters a corner too fast or apexes too early, realizes they are running wide, and instinctively snaps the throttle shut. This abrupt deceleration shifts weight forward, compresses the front suspension, and can cause the rear tire to lose traction, exactly the opposite of what you want mid-corner.

The key issue is that throttle chops are reactive, not planned. Smooth riding means managing speed before the corner so you never need to chop the throttle once you are leaned over. If you find yourself chopping throttle frequently in the same corner, it usually means your entry speed is too high or your apex is too early.

In LapBrain, throttle chops are detected by looking for sudden drops in throttle position while lean angle is significant. When coaching highlights throttle chops, the recommended fix is almost always about improving the corner entry (better braking, a later turn-in, or more trail braking) rather than trying to manage the chop itself.

Roll-on refers to the smooth, progressive application of throttle from the apex through the exit of a corner. Rather than snapping the throttle open, you gradually increase it as the bike stands up and the contact patch grows, matching throttle to available traction.

A good roll-on is one of the most satisfying parts of track riding. It means you nailed the entry, hit a good apex, and now the bike is driving forward with increasing speed and stability. The throttle goes from closed (or maintenance) at the apex to wide open by the time you reach the exit and the bike is fully upright.

In LapBrain, the accel phase of each turn shows your throttle application from apex to exit. Coaching may suggest earlier or smoother roll-on when it detects hesitation or choppy throttle application in this phase.

Over-braking means scrubbing off more speed than the corner requires. The rider arrives at the turn-in point significantly slower than necessary, then has to accelerate back up through the corner. This wastes time both on the approach (braking longer than needed) and through the corner (accelerating from an unnecessarily low speed).

Over-braking is extremely common among developing riders. It feels safe, since you can never crash from going too slow, but it represents one of the biggest sources of lost lap time. A rider who over-brakes by even 5 km/h in every corner can easily lose 1-2 seconds per lap compared to their own potential.

In LapBrain, over-braking is identified by comparing your minimum corner speed against your own best laps. When coaching highlights over-braking, the suggestion is typically to carry a bit more speed into the entry, often by improving trail braking rather than by braking later.

Under-braking means not slowing down enough before the corner, so you arrive at the turn-in point carrying more speed than you can manage through the turn. This usually results in running wide, a throttle chop, or excessive lean angle to make the corner work. Under-braking is less common than over-braking for most track riders, but it does occur, especially when riders try to push their braking point later without the skills to support it.

In LapBrain, under-braking appears as elevated entry speed relative to your successful fast laps, often followed by a throttle chop or wide exit line. Coaching may suggest an earlier or harder initial brake application.

Early braking means applying the brakes significantly before the point where braking actually needs to begin for the upcoming corner. The rider loses time on the straight by decelerating sooner than necessary. This is closely related to over-braking but specifically refers to where braking starts rather than how much total speed is lost.

Early braking is one of the most common habits among riders moving from the street to the track. On the street, braking early is smart because it builds in a safety margin. On the track, that safety margin is pure lost time. Coaching recommendations for early braking focus on gradually moving the braking point later, using consistent visual references, rather than trying to make a dramatic change all at once.

In LapBrain, early braking is detected by comparing where you begin braking relative to where your fastest laps show braking is needed. The delta between your typical braking point and your best braking point shows exactly how much margin you are leaving on the table.

Mid-straight coast happens when a rider lifts off the throttle in the middle of a straight for a moment, then rolls back on to full throttle. The lift is often very brief, sometimes just a fraction of a second, and can feel invisible to the rider. On track, it adds up to lost speed on the straight and a slower approach to the braking zone.

There are a few common reasons for a mid-straight lift: easing off to check a mirror, responding to a bike that felt unsettled, or an instinctive reaction to a bump in the surface. The fix is awareness: once a rider knows the lift is happening, holding full throttle through the middle of the straight is almost always the right answer.

In LapBrain, mid-straight coast is detected when throttle drops below about 80 % for more than a fraction of a second in the middle half of a straight on most of your laps. Short straights do not produce this flag because there isn't enough room to meaningfully lift and re-apply.

Early throttle release is when a rider lifts off the throttle well before the point where brakes actually need to be applied. The bike coasts for a longer stretch than it needs to, covering ground at a decelerating speed when it could still be accelerating or holding terminal speed.

This pattern is different from early braking. Early braking means the brakes come on too soon; early throttle release means the throttle goes off too soon, with braking starting at the right time. The rider has effectively added a coasting phase between full throttle and braking, which is time lost.

The habit often comes from wanting to stabilise the bike before braking, especially after moving up from the street. The fix is a single clean transition: throttle off and brakes on together, not separated by a coasting pause.

In LapBrain, early throttle release is detected when the throttle drops below 95 % at least 30 metres before the sample where braking actually begins, on most of your laps.

Stepped acceleration means the bike speeds up, slows a little, speeds up again, slows a little, and so on as it travels down a straight. Instead of one smooth ramp from corner exit to the braking zone, the throttle is being pulsed or eased on and off in small steps.

Riders rarely notice this consciously. It can come from a nervous throttle hand, adjusting for bumps, or an engine-management character that rewards feathering. On a lap timer, the effect is small, but smooth continuous acceleration always beats stepped acceleration for the same average throttle, because the bike's momentum carries cleanly forward.

The fix is awareness plus a steadier right hand: roll on once, hold, and don't second-guess until it's time to brake. If the bike genuinely feels unhappy with continuous throttle, that's usually a suspension or traction-control setting worth checking.

In LapBrain, stepped acceleration is detected when longitudinal acceleration reverses direction two or more times across the middle of a straight, on most of your laps. One reversal (speeding up then topping out) is normal; two or more suggests the throttle isn't being held steady.

Squaring off a corner means riding it as if it were a sharp angle rather than a smooth arc. The rider brakes hard in a straight line, makes an abrupt direction change at the turn-in point, then accelerates out in a roughly straight line. The result is a V-shaped path through what should be a smooth curve.

Squaring off usually happens because the rider is not comfortable trail braking. Without the ability to brake and turn simultaneously, the only option is to finish all braking before any turning begins, which creates the V-shape. Improving trail braking naturally rounds out the corner and eliminates the square shape.

In LapBrain, squaring off is visible in the GPS trace as a sharp inflection in the line through a corner. Coaching recommendations focus on developing trail braking and a smoother transition from braking to turning.

Roll speed (sometimes called mid-corner speed or maintenance speed) is the minimum speed you carry through the middle portion of a corner. Higher roll speed means you spend less time accelerating back up to straight-line speed, which directly translates to faster lap times.

Roll speed is arguably the most important number in any corner. A rider who carries 5 km/h more roll speed through a corner will be faster on exit by more than 5 km/h, because they start accelerating from a higher base. Over a full lap with 10-15 corners, small roll speed gains compound into significant time improvements.

In LapBrain, roll speed is shown as the minimum speed during the maintenance phase of each turn. Comparing roll speed between your laps, and especially between your best lap and your average, reveals where the biggest time gains are available.

A survival reaction is your body's instinctive response when something feels wrong on the motorcycle, like the bike running wide, the tire sliding, or you suddenly feel like you are going too fast. Common survival reactions include chopping the throttle, grabbing the front brake while leaned over, stiffening your arms on the bars, and looking at the thing you are afraid of hitting instead of where you want to go.

The problem with survival reactions is that they almost always make the situation worse. Chopping the throttle mid-corner upsets the chassis. Grabbing the brake while leaned over can cause a front-tire slide. Stiff arms prevent the bike from self-correcting. These reactions are deeply wired and take deliberate practice to override.

In LapBrain, survival reactions show up as sudden throttle or brake inputs mid-corner. Coaching highlights these events so you can identify which corners trigger them and work on building confidence through those sections.

LapBrain breaks every corner into five phases that describe the progression through a turn. Understanding these phases helps you read your corner analysis and act on recommendations.

The five phases are: Entry (turn-in speed), Decel (trail braking zone), Maintenance (minimum speed through the apex), Accel (drive out of the corner), and Exit (speed carried onto the following straight). Each phase has its own metrics and its own coaching recommendations.

Not every corner has all five phases equally represented. A fast sweeper may have a very short decel phase, while a tight hairpin has a long one. The phase breakdown adapts to each corner's geometry.

A turn is a single corner on the track, one continuous change of direction. Turns are identified by designations like T5 (Turn 5), which correspond to the track's official or commonly used numbering. Every turn is broken down into phases (entry, decel, maintenance, accel, exit) for detailed analysis.

Turns are the fundamental unit of analysis in LapBrain. Each turn has its own set of metrics (entry speed, roll speed, apex position, exit speed) and its own coaching recommendations. Your lap time is essentially the sum of how well you ride each turn plus how fast you carry speed down each straight.

In LapBrain, turns are shown on the track map with their designations and are the primary way coaching organizes its recommendations. When coaching says "focus on T5," it means the analysis has identified that corner as your biggest opportunity for improvement.

A complex is a group of two or more turns that are linked closely enough that the line through one directly affects the next. Complexes are identified by designations like C1 (Complex 1). In a complex, you cannot optimize each turn individually. You have to find the best compromise line through the whole sequence.

For example, a chicane (left-right or right-left combination) is a typical complex. Trying to apex perfectly in the first turn might leave you out of position for the second. The fastest line through the complex often means sacrificing some speed in the first turn to set up a better exit from the last turn, since that exit leads onto a straight where speed matters most.

In LapBrain, complexes are analyzed both as a whole and turn-by-turn, so you can see how your line choices in one turn affect your performance in the next.

A straight is a section of track between corners where you are traveling in a roughly straight line, typically at full throttle. Straights are identified by designations like ST1 (Straight 1). Your speed on a straight is primarily determined by how well you exited the preceding corner, so a good corner exit translates directly into higher straight-line speed.

In LapBrain, straights show your top speed and how quickly you reach it after the preceding corner exit. Comparing straight speeds between laps is a quick way to see whether corner exit improvements are translating into real time gains.

A sector is a defined portion of the track used for timing comparisons. Sectors are identified by designations like S1 (Sector 1). Most tracks are divided into three or four sectors. Sector times let you compare performance in specific parts of the track across laps and sessions, making it easier to pinpoint where you are gaining or losing time.

In LapBrain, sector times appear in the lap comparison view. If your overall lap time improved but Sector 2 got slower, you know exactly where to focus. Sector analysis is especially useful across sessions. You can see which parts of the track improved as you learned the layout.

An involvement zone is the band along the track where LapBrain evaluates your riding against a specific turn, complex, or straight. Inside the solid core, everything you do counts in full toward that corner's numbers and issue detection. The translucent edges ramp from 0 to 100% so that braking approach into a corner and throttle roll-on out of it are captured smoothly, without a sharp cutoff that would throw off timing comparisons.

On the map you can see these zones as soft gradient fills. In Turn mode the zone around a single corner is highlighted; in Circuit and Sector modes the zones for complexes and straights fill in the same way, so you can see how analysis coverage is distributed across the lap. Short straights render as a flat band instead of a gradient because there is not enough room for a meaningful ramp.

The zone is how the app turns your continuous lap trace into per-turn, per-complex, and per-straight numbers without double-counting around the boundaries where one element hands off to the next.

The entry phase is the first part of a turn, starting where you begin to set up for the corner and ending where significant deceleration begins. It covers the transition from straight-line riding into the corner: the approach, initial brake application, and the start of directional change.

The entry phase sets the tone for the entire corner. A smooth, confident entry with the right speed leads to a good apex and a strong exit. A rushed or inconsistent entry cascades into problems through the rest of the turn. This is why most coaching focuses heavily on entry technique. getting the entry right makes everything else easier.

In LapBrain, the entry phase is the first of five phases shown in the turn detail view. Key metrics for the entry include speed at the start of braking, how much trail braking overlap exists, and consistency of the entry line across laps.

The decel phase covers the portion of the turn where the bike is actively losing speed, from the hardest braking through the taper of brake pressure as the bike leans in. This is where trail braking happens, and where the front tire is working hardest.

The decel phase is critical for setting your roll speed. How much speed you scrub off here, and how smoothly, determines what speed you carry into the middle of the corner. Over-braking in the decel phase means arriving at the maintenance phase too slowly. Under-braking means you carry too much speed and have to correct mid-corner.

In LapBrain, the decel phase is the second of five turn phases. Coaching recommendations about trail braking, over-braking, and braking consistency relate primarily to what happens in this phase.

The maintenance phase is the middle of the corner where you are neither braking nor accelerating significantly. You are maintaining speed through the turn. This is typically the slowest part of the corner and where the bike is at or near maximum lean angle. The apex usually falls within or near the maintenance phase.

Roll speed, the minimum speed during this phase, is one of the most important metrics for any corner. Higher roll speed means less time spent at the slow point of the corner and a head start on the following acceleration. Even small improvements in roll speed (2-3 km/h) can translate to meaningful lap time gains.

In LapBrain, the maintenance phase is the third of five turn phases. The key metric here is roll speed, and coaching may suggest ways to carry more speed through this phase, such as improved trail braking technique or a different line choice.

The accel phase covers the portion of the turn from the apex onward, where you are progressively opening the throttle and the bike is accelerating. This phase is all about the roll-on: smoothly and progressively applying throttle as the bike stands up and the contact patch grows.

The accel phase directly determines your exit speed, which in turn determines your speed down the following straight. Getting on the throttle earlier and more smoothly means higher exit speed and a faster straight. This is why a slightly late apex often produces faster lap times. It opens up the accel phase and lets you get on the throttle sooner.

In LapBrain, the accel phase is the fourth of five turn phases. Coaching recommendations about throttle application, roll-on smoothness, and exit speed relate to this phase.

The exit phase is the last part of a turn, where the bike is straightening up and transitioning back to full throttle. Exit speed here determines how fast you enter the following straight, making it one of the most impactful parts of any corner.

A clean exit is the payoff for a good entry, a solid apex, and a smooth roll-on. If you nailed all the preceding phases, the exit phase takes care of itself. You just continue opening the throttle as the bike stands up. Problems in the exit phase (running wide, throttle chops) almost always trace back to something that went wrong earlier in the corner.

In LapBrain, the exit phase is the fifth and final turn phase. Exit speed is a key metric, and large variations in exit speed across laps often point to inconsistency in the earlier phases.

Apex mode describes the shape of a corner in terms of how many distinct apex points it has and how they relate to each other. The three modes are:

Single apex: The most common type. One smooth arc with one closest point to the inside. Most corners on most tracks are single-apex turns.

Double apex: A longer corner with two distinct inside points separated by a brief straightening or opening of the line. Common in long sweeping turns. You effectively ride two mini-corners within one turn, with a short transition between them.

Opposite apex: A complex of two turns in opposite directions, for example, a left-right chicane. Each turn has its own apex, but the line through the first turn must set up the second. Opposite-apex complexes require compromise lines where you sacrifice performance in one turn to gain it in the next.

In LapBrain, the apex mode is shown for each turn in the track overview. Understanding the apex mode helps you interpret coaching recommendations, since the optimal technique differs for each mode.

Braking distance is the arc distance, measured along the track surface rather than a straight line, from where you first apply the brakes to the apex of the corner. It captures how much track you use to slow down.

A shorter braking distance means you are braking later, carrying more speed on the straight, and committing to a harder stop before the turn. A longer braking distance can mean early braking (leaving time on the table on the straight) or gentle braking over a longer zone (sometimes appropriate for fast sweepers).

In LapBrain, braking distance is shown in the turn metrics panel as an average across visible laps, with the best (shortest) value highlighted. A large gap between your average and best braking distance suggests inconsistency in your braking point, so focus on picking a consistent reference marker.

The apex-to-min-speed distance measures how far your minimum speed point is from the geometric apex of the corner. It is one of the most telling metrics for corner technique.

A value near zero means your slowest point coincides with the apex, the classic textbook technique. A negative value means you reach minimum speed before the apex, which often indicates releasing the brakes too early or over-slowing on entry. A positive value means your minimum speed is past the apex, which usually indicates trail braking, carrying brake pressure deeper into the corner.

In LapBrain, this metric is colour-coded: green for positive values (trail braking), neutral for near-zero, and orange for negative values (early minimum speed). Working toward a slightly positive apex-to-min-speed distance is a good progression target for intermediate riders.

Turn length is the total distance of a corner, measured as an arc along the track surface from the entry point to the exit point. Longer turns require more patience and a different approach than short, sharp corners.

Short turns (under 50 meters) tend to reward aggressive braking and quick direction changes. Long turns (over 150 meters) reward smooth inputs, patience through the maintenance phase, and careful throttle application. Understanding turn length helps you calibrate expectations for maintenance time and exit drive. A long sweeper with extended maintenance is normal, not a sign of poor technique.

In LapBrain, turn length is shown in the Turn Info section of the corner metrics panel when track geometry data is available.

Elevation change is the difference in altitude between the entry and exit of a corner. A positive value means the corner goes uphill; a negative value means downhill.

Elevation matters because it changes the physics of the corner. Downhill corners compress the suspension and load the front tire on entry, making trail braking easier but making it harder to judge braking distance visually. Uphill corners lighten the front end and can reduce front-tire grip on entry, but they naturally slow the bike and make late braking more forgiving.

In LapBrain, elevation change is shown in the Turn Info section when altitude data is available from the GPS trace. Use it to understand why certain corners feel different. A corner that feels sketchy on entry may simply be downhill, which changes the grip balance rather than indicating a technique problem.

A hairpin is a tight corner with a small radius, often close to 180 degrees. Hairpins demand the heaviest braking on the track, the most lean angle, and the slowest minimum speed. Getting the entry speed right and placing the apex precisely are critical, since small errors in apex position have a large effect on exit speed because the radius is so tight.

In LapBrain, hairpin corners are identified by their turn geometry and typically produce the most coaching recommendations around braking and apex placement.

A standard corner has a moderate radius and represents the most common type of turn found on most circuits. These corners require a balanced combination of braking, turn-in, and throttle application. Neither extremely tight nor extremely fast, standard corners reward smooth, consistent technique.

In LapBrain, standard corners are the baseline turn type. Coaching for standard corners focuses on consistency and line optimization.

A sweeper is a long, flowing corner with a large radius. Sweepers are taken at high speed and often require minimal or no braking. Instead, a slight roll off the throttle and smooth turn-in are enough. The key challenge is maintaining speed and confidence through a sustained lean.

In LapBrain, sweeper analysis focuses on throttle consistency, line smoothness, and maintaining speed through the arc.

A kink is a very gentle curve in an otherwise straight section of track. Kinks require almost no speed reduction and minimal steering input. At high speeds, however, even a small kink demands precise body position and smooth inputs to maintain stability.

In LapBrain, kinks may not generate coaching recommendations since they rarely involve significant braking or cornering technique.

A decreasing-radius corner starts wide and gets progressively tighter toward the exit. These are among the most challenging corners because the natural tendency is to enter too fast because the corner looks open at first, then tightens. The correct approach requires patience: a later turn-in, later apex, and often trail-braking deeper into the corner.

In LapBrain, decreasing-radius corners often produce coaching recommendations around early squaring off, late apex placement, and consistent braking through the tightening arc.

An increasing-radius corner starts tight and opens up as you approach the exit. These corners reward an earlier apex and progressive throttle, and as the radius increases, you can add speed through the exit. The entry may feel tight, but the expanding radius lets you accelerate earlier than in a constant-radius turn.

In LapBrain, increasing-radius corners typically generate fewer issues than decreasing-radius turns, with coaching focused on maximizing exit speed.

A chicane is a pair of closely linked turns in opposite directions, typically a quick left-right or right-left. Chicanes require rapid weight transfer and direction changes. The key challenge is that the line through the first turn must set up the second, so you often sacrifice some speed in the first part to gain it back in the second.

In LapBrain, chicane analysis considers both turns together and coaching recommendations account for the trade-offs between them.

Esses (or S-curves) are a series of linked turns alternating left and right in quick succession. Unlike a chicane (which is typically just two turns), esses may chain three or more direction changes. The key to fast esses is rhythm: smooth, flowing transitions between directions with minimal disruption to the bike's balance.

In LapBrain, esses analysis focuses on smoothness, consistency across the sequence, and maintaining momentum through the chain of turns.

Your personal best (PB) is your fastest recorded lap time at a particular track. It represents your current peak performance, the one lap where everything came together. Personal bests persist across sessions, so your PB from three months ago still counts until you beat it.

Personal bests matter because they give you a concrete, achievable target. Your PB proves you are capable of that speed because you have done it before. When coaching compares your current laps to your PB, it is comparing you to yourself at your best, not to some theoretical ideal. This makes PB comparisons especially useful: every difference between your current lap and your PB is time you have already demonstrated you can recover.

A PB should not be confused with a best lap (fastest in a single session) or an ideal lap (a theoretical composite). Your PB is real. You actually rode that lap. It changes only when you go faster.

In LapBrain, your personal best is shown prominently in session summaries and is the primary reference for delta comparisons and pace percentile calculations. When you set a new PB, the app highlights it as a milestone in your progress.

A per-bike personal best is your fastest recorded lap time at a track for one specific bike identity. If you ride the same track on different bikes, LapBrain keeps those PBs separate so each bike has a fair benchmark.

This matters because a lap set on one bike may not be the right target for another. Different bikes can have different power, gearing, handling, tires, or setup, and your career dashboard reflects that by showing separate PB tiles for each known bike identity.

Older sessions and sessions without a bike assignment are still supported. Those laps can appear under Unassigned, and LapBrain can still analyze them with class-scoped comparisons when a specific bike identity is not available.

Your best lap is the fastest lap you recorded in a particular session. It is the reference point for that session, and other laps are compared against it to understand where you gained or lost time. If your best lap in a session also beats your personal best, it becomes your new PB.

In LapBrain, the best lap is highlighted in the lap list and used as the default comparison target when analyzing other laps in the same session. The turn-by-turn breakdown of your best lap shows what you did right in each corner on your fastest pass.

An ideal lap is a composite. It takes your fastest time through each sector or turn from any lap in the session and adds them up. The result is a theoretical lap time that represents what you could achieve if you rode every section of the track as well as your best attempt at each section. You never actually rode this lap, but each piece of it is real.

The gap between your best lap and your ideal lap reveals consistency. If your best lap is 1:42.0 and your ideal lap is 1:40.5, it means you have 1.5 seconds of potential locked up in inconsistency. You know how to ride each section fast enough, you just have not done it all on the same lap yet. This is a very actionable insight: the speed is already in you, you just need to connect the dots.

In LapBrain, the ideal lap is shown alongside your best lap and personal best. The sector-by-sector breakdown shows exactly which sectors your best lap fell short of your ideal, giving you specific targets for your next session.

An on-pace lap is a lap that falls within a reasonable range of your best pace in the session, close enough to represent genuine riding rather than a cool-down lap, a warm-up lap, or a lap with a mistake or traffic. On-pace laps are the laps that matter for analysis, because they reflect what you are actually doing when you are trying.

Filtering for on-pace laps is important because a typical session includes many laps that are not representative: the out-lap as you leave pit lane, the cool-down lap at the end of a stint, laps where you encountered slower riders, or laps where you went off line. Including these in your analysis would distort your averages and make coaching recommendations less useful.

In LapBrain, on-pace laps are automatically identified and used as the basis for consistency analysis, coaching recommendations, and pace percentile calculations. You can see which laps were considered on-pace in the session lap list. The threshold adapts to your session and is based on your actual pace distribution, not a fixed cutoff.

Delta is the time difference between two laps, typically expressed as seconds gained or lost relative to a reference lap. A delta of -0.5s means you were half a second faster; a delta of +1.2s means you were 1.2 seconds slower. Deltas can be calculated for the full lap or broken down by sector or turn.

Delta is the most fundamental tool for understanding where time is gained and lost. A full-lap delta tells you how two laps compare overall, but a sector delta or turn delta tells you exactly where the difference came from. If your lap was 0.8 seconds slower than your best, and the sector deltas show +0.9s in Sector 2 and -0.1s in Sector 3, you know the entire deficit came from one part of the track.

Turn-level deltas are even more specific. If your Sector 2 delta is +0.9s and it contains three turns, the turn deltas might show +0.6s in T5, +0.2s in T6, and +0.1s in T7, telling you that T5 is where the real problem is.

In LapBrain, deltas are shown at the lap, sector, and turn level. Color coding makes it easy to see at a glance where you gained (green) or lost (red) time relative to your reference lap.

Pace percentile is a score from 0 to 100 that shows where a particular lap or turn falls within your own range of performance. A pace percentile of 95 means that lap or turn was in the top 5% of your own attempts, very close to your best. A pace percentile of 40 means it was below your own average.

The key thing about pace percentile is that it compares you to yourself, not to anyone else. A beginner rider and an expert rider can both have a lap at the 90th percentile. It just means each rider was riding near their own personal best on that lap. This makes pace percentile a fair, motivating metric at any skill level.

Pace percentile is especially useful for identifying consistency patterns. If most of your laps cluster between the 70th and 90th percentile, you are riding consistently. If they are scattered from the 20th to the 95th, you have high variability, which usually means there are specific corners where you are inconsistent.

In LapBrain, pace percentile is shown for each lap and can be broken down by turn. It is the primary metric used to assess consistency and to identify which turns have the most variation in your performance.

Consistency measures how repeatable your riding is from lap to lap. A consistent rider posts similar times through the same corners on every lap. An inconsistent rider has wide swings, like a great T5 followed by a poor T5 followed by an average T5. Consistency is often more important than raw speed for improving lap times, because you cannot build on a technique you cannot repeat.

The reason consistency matters so much is that improvement requires a stable baseline. If your corner entry speed varies by 15 km/h from lap to lap, you cannot meaningfully work on carrying more roll speed because the variation drowns out any progress. But if your entry speed is within 3 km/h every lap, even a 2 km/h improvement is visible and sustainable.

Consistency also reveals where your attention is and where it is not. Most riders are very consistent in corners they are comfortable with and highly variable in corners that challenge them. The inconsistent corners are where the biggest gains live.

In LapBrain, consistency is measured at both the lap level (how tight is your lap time distribution) and the turn level (how repeatable is each corner). The coaching system prioritizes inconsistent turns because they represent the easiest path to faster, more reliable lap times.

A coaching thread is a focused area of improvement that LapBrain identifies from your data. Rather than overwhelming you with dozens of observations, the coaching system groups related findings into threads, coherent topics you can work on. A thread might be "trail braking in T5," "over-braking into the back straight chicane," or "consistency through Sector 2."

Each coaching thread contains the evidence (what the data shows), the recommendation (what to try), and the expected impact (how much time it could be worth). Threads are prioritized by potential time gain, so the most impactful improvement is always at the top.

Coaching threads persist across sessions when you return to the same track. If you were working on "trail braking in T5" last month and return to that track, LapBrain shows your progress on that thread, including whether the issue has improved, stayed the same, or gotten worse. This continuity is important because real riding improvement happens across sessions, not within a single day.

In LapBrain, coaching threads appear in the coaching section of your session analysis. Each thread links to the specific turns and laps that illustrate the finding, so you can see the evidence and understand exactly what the data is telling you.

A coaching thread is marked "resolved" when the issue it tracks has not appeared in your last three consecutive sessions at that track. The three session threshold exists because a single clean session is not strong evidence of a real habit change, two clean sessions could still be luck, but three in a row is a signal worth trusting. The moment your third clean session is processed, LapBrain surfaces "Resolved over time: {issue} at {turn}" in your paddock debrief wins, along with the per-lap time you saved on the way to clearing the habit.

Resolution is scoped per track. If you resolved "over-braking in T5" at one circuit, that thread is closed for that track. It does not mean the same habit cannot return at a different circuit, because technique habits often have circuit-specific triggers.

If the issue returns at a resolved thread's track, LapBrain flags the new focus item as a regression rather than a new issue. The distinction matters: regressions are usually about tire, setup, or confidence changes rather than about re-learning the fundamentals. You have already proven you can do the thing right, so the framing of the recommendation shifts toward "what changed?" instead of "here is how to do this."

Resolved threads remain visible in your track career history so you can look back on the habits you have worked through over time.

LapBrain asks a single optional question on registration and in settings: any prior performance-driving background? The choices are deliberately broad: none, street riding, car track / HPDE, returning bike racer. The rider can decline ("Prefer not to say") with no consequence. The default is the same as declining.

The setting exists because some skills cross domains and others don't. A car-track driver coming to bikes already trusts grip and brakes hard, but the throttle-first habits common in cars fight bike-style trail braking. A street rider has high reading of traffic and surface but tends to sit up under threat, a survival reflex that costs corner time on track. Coaching adapts the framing of safety-tagged events and the wording of strengths to those starting points; nothing about pace, lap times, or feature visibility changes based on this answer.

Privacy: the field is rider-declared, never inferred from telemetry. It can be updated or cleared at any time from Settings → Rider Background.

Street time builds reflexes that help on track (surface reading, hazard awareness, smooth control inputs near unknown grip), and a few that work against it. The biggest is the survival-instinct sit-up: when something feels wrong mid-corner, street muscle memory pulls you upright and onto the brakes to widen your line. On track that response loses corner time and unsettles the bike at the moment it most needs to stay loaded.

The other shifts are more mechanical. On track you commit to a line and stay on it; on street you keep options open in case the surface or traffic changes. Track riding rewards trail braking deeper into the corner; street riding rewards finishing the brake before turn-in. And track speeds load the tire envelope further than street pace ever does, so the same lean angle that felt at-the-limit on the street sits well inside a session-warmed track tire's grip.

Coaching adapts in two places. Safety-tagged events get a kinder frame that names the street reflex without scolding it ("settle the entry" rather than "carry more speed"). Strengths that come from your street time (clean visual references, smooth control modulation, hazard reading) get phrased as carry-over wins, not generic praise. Pace coaching is unchanged; the goal is recalibration, not retreat.

Car-track experience covers a lot of bike-relevant ground: line theory, trail braking, corner-vision discipline, the difference between race pace and qualifying pace. Two-wheel mechanics shift the rest. Lean angle is the bike's primary cornering input and the contact patch is small, so brake and throttle modulation drive grip far more than weight transfer does. The trail-brake reflex that loads a car's front under a steady hand load pivots a bike around its front tire. That's useful, but unforgiving when it overlaps with too much lean.

A common transfer error is throttle-first commitment. Cars reward early throttle to settle the chassis on corner exit. Bikes punish it: opening the throttle while still leaned past mid-corner sends torque into a tire that has not yet recovered grip from the lean. The bike fix is to delay the pick-up until the bike is rolling out of lean. A second pattern is braking grip headroom: bikes have less of it than performance cars at the same pace, so the heavy late-brake that worked in the car loads the bike's front past where it can also turn.

Coaching uses the prior-experience signal to phrase technique calls in shared vocabulary ("trail braking", "rotation", "corner exit") instead of explaining them from scratch. Strengths that come from your car-track time (calibration, line discipline, race-craft) get prefixed as carry-over wins. Safety-tagged events get a kinder frame that respects the experience without assuming every habit transferred cleanly.

Some sessions show patterns where the bike's behaviour is running ahead of the rider's inputs: late braking the bike isn't ready to absorb, recoveries from running wide, or a cluster of safety-tagged corners on the same lap. When LapBrain detects that pattern, the affected focus cards switch from pace-optimisation wording to a kinder frame: "settle the entry" rather than "carry more speed."

The frame is rider-protective, not punitive. The focus card still appears, the corner is still flagged, the evidence is still cited. The change is in the call to action. Pace-side coaching on those specific corners is set aside until the entry settles.

Above the focus list you may see a short confidence-framing note explaining what LapBrain saw and how it shaped today's coaching. The note is dismissible at standard severity and acknowledged with a "got it" tap at firm severity. At soft severity it's a single inline line under your top focus card.

Why we frame it this way: scaring a rider off the track is also a failure. The kinder phrasing keeps the signal clear without collapsing your confidence. The corners flagged are real and worth working on, but the goal is recalibration, not retreat.

Focus recommendations are the coaching areas LapBrain suggests you work on next. Out of all the issues identified in your data, they are ranked by the best combination of potential time gain and achievability at your current skill level. They answer the question every rider asks after a session: "What should I focus on next time?"

LapBrain shows multiple focus recommendations rather than just one. The top item is the highest-impact change, but riders told us a single focus wasn't always enough, since sometimes two or three issues are related (e.g. braking and entry speed in the same corner) and working on them together makes more sense. Each recommendation is specific, like "carry 3 more km/h of roll speed through T7" rather than "go faster," giving you something concrete to work on.

Focus recommendations evolve as you improve. Once you make progress on your current focuses, new recommendations surface. This creates a natural progression path through your available improvements.

In LapBrain, focus recommendations are shown prominently in the debrief, ranked by impact. Each includes the specific corners involved, the evidence from your data, a clear description of what to try, and an estimate of the time gain if successful.

A skill band is a classification of where you currently sit in your own development at a particular track. It is not a ranking against other riders. It describes your current stage of learning and helps tailor how coaching communicates with you.

Skill bands matter because the right advice depends on where you are. A rider in the early stages benefits from foundational guidance: consistent braking points, smooth inputs, basic trail braking. A rider at an advanced stage needs more nuanced feedback: apex timing variations, phase-specific speed optimization, consistency under fatigue. Giving advanced advice to a developing rider is confusing; giving beginner advice to an advanced rider is patronizing.

Your skill band can differ by track. You might be well-developed at your home track where you have hundreds of laps, and still developing at a track you just visited for the first time. This is normal and expected.

In LapBrain, your skill band influences the language and specificity of coaching recommendations. As your skill band progresses, the coaching becomes more detailed and the metrics shown become more granular. You do not need to worry about selecting or managing your skill band. It is determined automatically from your data.

A persistent issue is one that fired on the same turn or straight in at least two of your day's sessions. The threshold matters: a single session can produce noise, but the same problem at T3 entry across three of four sessions is a technique gap, not a one-off slip.

In LapBrain, persistent issues drive the patterns section of your day review, ranked by how many sessions they appeared in (e.g. "3 of 4 sessions"), and feed into your next focus for the following track day.

A consistent strength is something you did well on the same turn or straight in at least two of the day's sessions. A single great lap can be a lucky stab; a strength that repeats across sessions means you have learned and internalised the move.

In LapBrain, consistent strengths appear in the wins section of your day review (e.g. "Strong trail brake at T5 in 3 of 4 sessions"), ranked by persistence rather than isolated peak performance, so the things you can actually count on next time show up at the top.

Next focus is the day review's forward-looking handoff: one primary area to work on next session, plus up to three secondary items when the data supports them. It draws from your persistent issues and the top-ranked coaching priorities, and emits only on strong signal. Calm days stay silent rather than invent urgency.

Each item carries evidence in plain terms (e.g. "appeared in 3 of 4 sessions"), a suggested action, and a label for where it came from. When you start the next track day, the track briefing picks this up so the handoff between today and tomorrow is explicit.

The arc narrative classifies how your session-best laps moved through the day into one of five shapes: steady improvement (each session beat the last), front-loaded gain (most progress came early), late breakthrough (the fast lap arrived in the final session), uneven curve (net improvement but a session got slower along the way), and best lap came earlier (the day peaked before the last session). The shape itself is the story.

In LapBrain, this appears at the top of your day review when you had at least three timed sessions and the spread is wide enough to support a claim.

Warmup adaptation measures the gap between your first flying lap and your session-best lap, then watches how that gap moves across the day. When it shrinks (improving), you are getting up to pace faster session by session. When it grows (slowing), each session takes longer to find the pace you ended the last one at, often a sign of fatigue, changing conditions, or tire drop-off.

In LapBrain, this appears on the day review with a coaching message and the first- and last-session gaps in seconds. Days inside the 0.30 s noise band are suppressed.

A skill snapshot is the day-level view of the same skill components you see on each per-session debrief: trail-brake quality, grip utilisation, consistency, smooth inputs, and a diamond score for braking technique. It is averaged across the day's sessions. A dimension that scores high on the snapshot is one you held up across the whole day, not just in one good stint.

In LapBrain, the skill snapshot appears on the day review when enough underlying components have data. A missing bar means "not enough data for this dimension on this day", not "zero".

A "universal" issue at the per-bike scope means LapBrain has detected the same coaching pattern (such as throttle chop or over-braking) at two or more different tracks while you were riding the same specific bike. The single-bike scope is what shows up in the per-bike coaching threads: a habit that follows you from one track to the next on that bike, rather than something specific to one corner.

This is distinct from the cross-bike "rider universal" scope (see the related entry). Per-bike universality says: "you do this everywhere on your 600." Rider universality says: "you do this on more than one of your bikes."

In LapBrain, per-bike universal issues appear in the career coaching view alongside the track count where the issue was active. Universal strengths work the same way: a strength that holds across multiple tracks for one bike is flagged as universal at the per-bike level.

A "universal across bikes" issue means LapBrain has detected the same coaching pattern on two or more of your bikes, for example throttle chop on both your 600 and your 1000. This is a rider-level signal: something about your technique that is not specific to a particular bike's setup, geometry, or class.

This is distinct from the per-bike "universal" scope (see the related entry). Per-bike universality says: "you do this everywhere on your 600." Rider universality says: "you do this on more than one of your bikes." That is a stronger signal because it suggests the habit is rider-level rather than bike-specific.

LapBrain pools rider-career evidence with bike-relative severity calibration so a 600 supersport and a 1000 naked are compared fairly. A confidence label is attached to every rider-career thread: "high" for two same-class bikes, "medium" for same-displacement different-class, and "medium with caveat" for cross-class cross-displacement (where the classes are different enough that the rider-level conclusion is weaker).

When there is not enough cross-bike evidence, rider-career suppression keeps this surface hidden rather than making a rider-level claim from too little data.

Rider-career coaching is the cross-bike layer of LapBrain's coaching. The per-bike views (career, track-career, event) keep your bikes strictly separate so two same-class bikes never blend their personal bests or mastery streaks. That is correct for performance-comparable signals. But some habits are rider-level: a throttle release that lags on both your 600 and your 1000 is a rider habit, not a bike habit.

The rider-career layer detects these patterns by pooling per-session events across all your assigned bikes (and any unassigned-class sessions) with bike-relative severity calibration so different-class bikes are compared fairly. It then surfaces threads that fire only when the cross-bike picture says something the per-bike threads do not: typically when an issue is sub-threshold on each bike but supra-threshold pooled, or when the issue is active on one bike and resolved on another (so the next coaching message is "you fixed this on your 600. Now let's tackle it on the 1000").

Loaner-bike sessions are excluded because they don't represent your own equipment. When the rider-career suppression gate fires, LapBrain hides the cross-bike surface rather than presenting a weak rider-level claim.

Rider-career suppression is the guardrail that keeps LapBrain from showing cross-bike coaching when the account does not have enough assigned-bike evidence. Rider-career coaching is meant to identify rider-level habits across bikes, so it needs more than one meaningful bike context before it can say "this follows you across the fleet."

The gate suppresses the rider-career surface for single-bike riders, loaner-only riders, and very low-volume accounts. Loaner sessions are excluded because they do not represent your own equipment. Low-volume accounts are held back because there is not enough cross-bike history to separate a real rider-level habit from one noisy session.

Suppression does not remove per-bike coaching. Your normal career, track-career, and event coaching still work inside each bike's own continuity scope. It only means LapBrain is not yet confident enough to add the rider-career layer on top.

Cross-bike progress is the narrative LapBrain surfaces when the same rider-level habit is heading in different directions on different bikes. The classic case is "you fixed throttle chop on your 600, now let's tackle it on the 1000". The issue is Resolved or Improving on one bike per its per-bike trend, while still Active on another. Coaching is more useful when it acknowledges the win on the bike where the work landed and points the next session at the bike that still needs it.

The narrative fires only when contributing bikes actually disagree on trend. When every bike on the rider-career thread shares the same trend (all active, all improving, all resolved), there is no divergence story to tell and the field is omitted. Bikes get bucketed into "resolved on", "improving on", and "still active on" lists so frontend copy can name the specific bikes (or bike classes, when only the class is known) on each side of the comparison.

Cross-bike progress can sit on either a standalone rider-career thread (the smooshing case where the issue is sub-threshold per bike but supra-threshold pooled) or on a corroboration link (the agreement case where each bike already has a substantive per-bike thread and the rider-career pass annotates rather than duplicates). See the related entries for how the rider-career layer chooses between those two surfaces.

Coaching context tells LapBrain that a session was connected to a human coach, coaching school, instructor, or outside riding advice. LapBrain still uses the telemetry normally, but it changes some wording so the debrief does not sound like it is overriding the guidance you were given.

When coaching context is active, focus items may defer the final technique choice to your coach, present the data as something to compare, or soften a recommendation that would otherwise sound absolute. Safety-framed coaching still takes priority when the same focus item is safety-sensitive.

You can set coaching context in account settings, or confirm it for a single upload when that session came from a school, instructor day, coaching session, or specific piece of advice you were practicing.

A coaching corroboration link is how LapBrain connects the per-bike coaching threads (your 600's career view, your 1000's career view) to the rider-career evidence pooled across your whole fleet. When the rider-career pass agrees with an existing per-bike thread (that is, each contributing bike already has substantive evidence the per-bike view would surface on its own), LapBrain does not emit a duplicate rider-career thread. Instead, the per-bike thread is annotated with "also seen on N other bike(s)" and the rider-career analysis carries a corroboration link back to that per-bike thread.

The link captures the issue kind, the per-bike threads being corroborated (with bike id, bike class, track family, and element label so the frontend can render context without a second roundtrip), the confidence inherited from the rider-career pooling, and, when bikes disagree on trend, a cross-bike progress narrative. Coaching copy MUST gate on the inherited confidence: "high" for two same-class bikes, "medium" for same-displacement different-class, and "medium with caveat" for cross-class cross-displacement.

The conservative-dedup posture (annotate one canonical surface rather than emit two parallel surfaces) keeps coaching prescriptive instead of repetitive. The smooshing case, sub-threshold on each bike but supra-threshold pooled, still emits a standalone rider-career thread, because there is no per-bike thread to corroborate. See the related entries for the per-bike and rider-career scopes that feed this annotation.

A session is one continuous recording from your data logger, typically covering a single on-track stint from when you leave pit lane to when you return. A typical track day might produce 4-6 sessions, one for each stint. Each session contains all the laps you rode during that stint.

In LapBrain, a session is the primary unit of organization. When you upload data, each recording becomes a session. Sessions contain your laps, coaching analysis, and turn-by-turn data. You can compare laps within a session or compare sessions against each other to track progress across a day or season.

Sessions are categorized by their purpose. Practice sessions are for learning the track, testing setup changes, and working on technique. Qualifying sessions focus on producing the fastest single lap for grid position. Race sessions are full competition runs where consistency and racecraft matter as much as raw speed.

In LapBrain, the session type helps tailor the analysis. Practice sessions emphasize learning and consistency trends. Qualifying sessions highlight your single fastest lap and what made it work. Race sessions focus on pace management and performance over the full race distance.

Cross-session comparison means looking at your data across multiple sessions, typically across a full track day, a multi-day event, or over a season, to understand how your riding is evolving. Single-session analysis shows what happened in one stint; cross-session comparison shows the trajectory of your improvement.

In LapBrain, cross-session comparisons reveal trends like improving consistency, progressively later braking points, or increasing roll speed in specific corners. This longer-term view is where the real value of data-driven coaching emerges: not just what happened today, but how today compares to last month.

A day review aggregates all your sessions from a single track day into one summary. It shows how your pace evolved through the day, which corners improved the most, and what coaching threads were most relevant. It is the answer to the end-of-day question: "How did today go?"

In LapBrain, the day review appears when you have multiple sessions from the same day at the same track. It highlights your best lap of the day, shows session-to-session progression, and surfaces the coaching focus for your next visit.

An event review aggregates all sessions from a multi-day event, such as a race weekend with practice, qualifying, and race sessions across two or three days. It shows your progression from first practice to race, highlighting where the biggest improvements came and what to work on for the next event.

In LapBrain, the event review pulls together day reviews into a broader narrative of your event performance.

A track briefing is a summary of a track's characteristics: its layout, key corners, sectors, and any notable features like elevation changes or blind crests. It is designed to help you prepare before you arrive at the track or before your first session of the day.

In LapBrain, the track briefing shows the track map with turn designations, sector boundaries, and notes about each section. If you have previous data at this track, the briefing also includes your personal history: best times, areas of strength, and coaching focus areas from past visits.

Session type is the label LapBrain applies to each session: Practice, Qualifying, or Race. The label is based on the rhythm of the data. It drives a session-row badge in the day review and changes how cross-day signals are interpreted: a Practice session that improved within itself followed by a Qualifying or Race session that got slower reads as a pressure response, because the rider intent was different.

In LapBrain, the type appears as a badge on each session row. When the data is ambiguous, the badge is omitted rather than guessed at; the session still analyses normally.

Bike assignment records which of three buckets a session belongs to: your assigned bike (tied to your profile, used to track technique trends), a loaner (a borrowed bike for a stint or two), or unassigned (typically a track-school or demo bike). The distinction matters because cross-session comparisons of lap times and technique only mean something when the bike is held roughly constant.

In LapBrain, the bike-assignment kind appears alongside the bike-class label on each session row in the day review, and coaching scopes its cross-session comparisons accordingly.

A data logger is the hardware that captures telemetry data from your motorcycle while you ride. It records information like GPS position, speed, lean angle, throttle position, brake pressure, RPM, and other channels depending on the logger and sensors installed. The logger stores this data to internal memory or a memory card, which you later download for analysis.

Common data loggers used in motorcycle track riding include AiM systems (such as the AiM Solo 2 or MyChron) and MoTeC units. Each logger records data in its own format, but they all capture the fundamental channels needed for lap analysis.

In LapBrain, you upload your data logger files and the system decodes them into a common format for analysis. LapBrain supports multiple logger brands and formats, so you can use whichever hardware suits your needs and budget.

LapBrain shows a missing logger placeholder when a session does not include the channel needed to calculate lean-related corner detail. This is common with bare-GPS uploads: speed and position are enough for lap timing and line analysis, but they cannot reliably reconstruct how much the bike was leaned in each part of the corner.

Future uploads from a logger or phone app that records lateral acceleration can fill in these reference bands. The rest of the debrief still works from the channels that were present; this placeholder only explains why the lean-specific row is absent for this session.

A telemetry channel is a single data stream recorded by your data logger. Each channel captures one measurement over time, for example speed, throttle position, lean angle, brake pressure, RPM, or coolant temperature. A typical logger records 10-30 channels simultaneously, sampling each one many times per second.

Channels are the raw ingredients of all analysis. Turn phases are identified from speed and position channels. Trail braking is detected from the overlap of brake pressure and lean angle channels. Throttle chops come from the throttle position channel. The more channels your logger records, the more detailed the analysis can be.

In LapBrain, available channels depend on your data logger and sensor setup. GPS-based speed and position are available from virtually all loggers. Channels like brake pressure and throttle position require additional sensors but unlock much deeper coaching insights.

A GPS trace is the recorded path of your motorcycle around the track, captured by the GPS receiver in your data logger. It records your latitude and longitude many times per second, creating a detailed map of your actual line through every corner. GPS traces are the foundation for position-based analysis, knowing where on track each data point was recorded.

In LapBrain, the GPS trace is used to map your data onto the track layout, identify turn boundaries, calculate racing lines, and compare lines between laps. The track map view shows your GPS trace overlaid on the track, color coded by speed or other metrics.

AiM and MoTeC are two of the most common data logging systems used by motorcycle track riders.

AiM makes dedicated data logging hardware popular in club racing and track days, including the Solo 2 (a standalone GPS lap timer) and MyChron series. AiM loggers record to XRK/XRZ format files.

MoTeC is a professional-grade data logging and engine management company. Their loggers are common in professional racing and record to LD/LDX format files. MoTeC systems typically offer more channels and higher sample rates than consumer units.

LapBrain supports data from both systems, as well as other common logger formats. You can use whichever system fits your needs and switch between them freely.

Compound is the type of rubber a tire is made from, and it determines how much grip you have, how the tire warms up, and what pressures you should run. There are three main categories. DOT tires are street-legal and work cold; many track-day riders use them. Slicks are pure race tires with no tread, made for warmers and a narrow temperature window. Intermediates sit between the two and are typically used in damp conditions.

Compound matters because every other tire decision flows from it. A slick wants warmers and warmer-set pressure tracking; a DOT runs cold and uses cold pressure. Heat-cycle expectations are different too. Race compounds retire after a handful of cycles, while DOT tires last for many sessions.

In LapBrain, compound is captured per axle in the setup journal. Coaching arms that depend on grip envelope (lean angle, throttle pickup, trail braking limits) use compound as the primary signal for what is realistic at a given lean.

Modern sportbikes ship with multiple selectable ECU maps that change how the engine delivers power. A typical bike has a full-power map for dry track use, a softer map for cold or damp conditions, and sometimes a rain map with reduced peak power and gentler throttle response. Switching maps is usually a button press on the dash, not a workshop job.

Riders pick a slot per session based on grip and confidence. A wet session calls for a softer map even on a fast bike. A new bike on a new track might warrant a softer map for the first session. Once the rider is comfortable, they switch up to a more aggressive map.

In LapBrain, the slot identifier is captured as free text because vendor numbering varies (BMW's Map 1 is not Yamaha's Map 1). The text is what the rider would read off the dash. Coaching arms that look at throttle pickup or chop frequency cross-reference the map slot to distinguish rider behaviour from electronics behaviour.

Final drive ratio is the gearing between the gearbox output and the rear wheel, set by the front and rear sprocket sizes. A higher ratio (more rear teeth or fewer front teeth) gives quicker acceleration out of corners but lowers top speed at the end of straights. A lower ratio trades acceleration for top speed.

Riders adjust final drive to match the track. Tight, twisty tracks with short straights reward higher ratios because corner exit acceleration matters more than terminal speed. Long-straight tracks reward lower ratios so the bike does not hit the rev limiter before the braking zone.

In LapBrain, final drive ratio is derived from the front and rear sprocket counts captured in the setup journal. It is not a hash input on its own. The underlying sprocket counts are. Coaching arms that look at corner-exit acceleration or top-speed shortfall reference the ratio when explaining what changed between sessions.

A heat cycle is one full warm-and-cool sequence on a tire: cold at the start of a session, up to operating temperature on track, then back to cold afterwards. Each cycle hardens the rubber slightly, even when there is no visible wear. A tire with low mileage but many heat cycles can be past its useful life.

Race compounds are most sensitive. Slicks are typically retired after 3 to 10 cycles depending on the specific compound, regardless of how much tread is left. DOT tires tolerate many more cycles. Tracking heat cycles matters more than tracking mileage for race compounds.

In LapBrain, heat cycles are captured per axle in the setup journal. For riders who do not track exact cycle counts, a coarser age_tier field (Fresh / Used / Worn) is the lower-literacy fallback. Coaching tone shifts when tires are deep into their cycle budget. Peak grip expectations come down.

A tire warmer is an insulated electric blanket that wraps around the tire and rim, holding it at operating temperature (typically 70-90°C) in the pits. Slicks and intermediates need warmers because they have no usable grip when cold. Without warmers a rider would crash on the first lap. DOT tires generally do not use warmers because they work cold by design.

When warmers are in use, the cold pressure of the tire is irrelevant. What matters is the warmer-set pressure: the pressure the rider sets the tire to while it is sitting on the warmer at temperature. That is the pressure the tire will start the session at.

In LapBrain, tire-warmer usage is captured at the profile level. Toggling it on switches the pressure tracking from cold-pressure to warmer-set pressure per side, since the two are not interchangeable. Coaching arms that depend on session-start grip use this flag to choose which pressure to cite.

There are three pressures a rider might cite for the same tire, and they are not the same number. Cold pressure is what the tire reads in the pits with no heat in it, used when no warmers are in play. Warmer-set pressure is what the rider sets the tire to while it is on the warmer at operating temperature, used when warmers are in play. Hot pressure is the peak pressure the tire reaches while running on track.

The distinction matters because a tire that reads 28 psi cold, 32 psi on the warmer, and 34 psi hot is the same tire. Three different numbers describe three different states. Coaching that confuses them gives bad advice.

In LapBrain, warmer-set pressure is captured per side (front, rear) when the profile has tire-warmer usage enabled. Coaching arms that talk about session-start grip cite warmer-set pressure rather than cold pressure when warmers are in use.