Glossary

Trail braking means keeping some brake pressure applied as you tip into a corner, rather than releasing the brakes completely before turning. The term describes an overlap between brake application and cornering; it does not say how much pressure or overlap is appropriate for a particular rider, corner, motorcycle, or condition.

In LapBrain, you can see whether you are trail braking by looking at the overlap between recorded brake pressure and the turn's cornering measurement. LapBrain shows trail braking only when your file includes a brake-pressure channel that overlaps the cornering measurement. Speed or deceleration alone does not prove brake application.

The braking point is the location where recorded brake application begins for an upcoming corner. Comparing that location across clean laps can show whether it repeated or moved. Later is not automatically faster or safer; the useful interpretation depends on the complete corner, conditions, and rider guidance.

In LapBrain, you can compare braking-point location across laps when your file includes a brake channel. A point from the best lap shows what happened once; it is not an automatic target for another lap.

An apex is an inside reference point for a cornering line. Its useful location depends on the track layout, the linked corners, and the question being compared; it is not universally the geometric midpoint or the minimum- speed point, and "later" is not automatically better.

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 displays the apex references from its track map and your measured line in the turn detail view. Read the line and time together rather than treating one point as a universal target.

Turn-in is the transition where the motorcycle begins changing direction into a corner. Its location and rate can be compared across laps, but telemetry does not turn "quick," "late," or brake overlap into a universal instruction.

In LapBrain, the turn-in point is visible in the turn detail as the beginning of the cornering transition. A recommendation may highlight a measured location difference without claiming to know its cause.

A throttle chop is a sudden drop in directly recorded throttle position during a corner. The trace shows that the input changed; it does not establish whether the change was planned, why it happened, or what the rider felt.

LapBrain marks a throttle chop when the throttle channel shows that drop inside the corner. Read the trace beside any recommendation; speed or longitudinal acceleration cannot fill in a missing throttle channel.

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 recorded roll-on describes throttle position increasing through part of a corner exit. It does not prove the entry, line, available grip, or correct timing for another lap.

In LapBrain, the accel phase can show throttle roll-on when the data logger recorded that channel. Without direct throttle data, the app can describe measured acceleration but not the control input that caused it.

Over-braking is a bounded comparison label for a pattern of recorded brake application and speed loss. It describes how the cited lap differed from its reference; it does not define a safe speed, estimate the rider's potential, or mean that less braking is always appropriate.

LapBrain shows the label only when the named comparison includes the required measurements. Review its Why and Check details rather than treating the best lap or one minimum-speed number as an instruction.

Under-braking is a bounded comparison label for a measured entry and speed-loss pattern. The measurement does not establish what speed the rider could manage, predict a line outcome, or identify why the pattern occurred.

In LapBrain, any control claim requires the corresponding recorded channel. The debrief keeps the recorded comparison, recommendation, and next-session check separate.

Early braking compares the location of directly recorded brake onset with a named reference lap or comparison range. "Early" is relative to that comparison, not an optimal or universally correct point.

LapBrain compares where braking began across clean laps when your file includes a brake channel. The distance difference shows what happened in those laps; it does not prove that moving the marker later is safe or that the full difference is available time.

Mid-straight coast happens when a rider lifts off the throttle in the middle of a straight for a moment, then applies it again. The throttle trace records the input change but does not identify why it happened or whether a different input was appropriate in the session context.

LapBrain marks mid-straight coast when the throttle channel shows a clear drop through the middle of the straight. Acceleration cannot fill in a missing throttle channel.

Early throttle release is a measured gap between directly recorded throttle release and a named braking-onset reference. It differs from early braking, which compares the brake onset itself. The measurement does not establish when either input should have occurred.

LapBrain marks early throttle release when the throttle drops before that braking-onset reference. It reports the measured gap without assigning a rider background, intention, or universal fix.

Stepped acceleration means the measured longitudinal acceleration rises and falls repeatedly across part of a straight. Throttle input, surface, grade, electronics, sensor behavior, and motorcycle response can all affect that trace; the shape alone does not prove hesitant throttle or identify a fix.

LapBrain marks stepped acceleration when longitudinal acceleration reverses direction two or more times across the middle of a straight on most of your laps. One reversal, from speeding up to topping out, is normal. The repeated shape does not establish which control produced it.

Squaring off describes a GPS path with a sharper direction change than a broad continuous arc. Whether that shape is useful depends on the corner and linked sections; the term is descriptive, not a claim that every corner should use a rounder line.

The GPS line can establish the path shape, but not why the rider chose it or which brake, throttle, steering, or comfort factor produced it.

In LapBrain, squaring off is visible in the GPS trace as a sharp inflection in the line through a corner. Any recommendation needs its own recorded measurements; the GPS shape alone cannot establish a control instruction.

Roll speed (sometimes called mid-corner speed or maintenance speed) is a speed measurement in the middle of a corner. A higher value in one lap does not by itself establish a better line, a safer target, or a time gain; compare the complete corner and following time delta.

In LapBrain, roll speed is shown as the minimum speed during the maintenance phase of each turn. Compare it across clean laps and beside the full-corner time; do not treat one value as a number to chase on track.

A survival reaction is the rider-facing safety frame for a bounded abrupt control pattern when the required recorded channel exists. The label does not mean LapBrain measured fear, attention, confidence, a slide, body position, or the reason for the input.

In LapBrain, the underlying measured input remains visible. Review the cited trace and session context; use qualified instruction for any riding response.

LapBrain breaks each turn 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 (the approach), Decel (measured speed falling), Maintenance (the minimum-speed region), Accel (measured speed rising), and Exit (the end of the corner). Direct brake or throttle claims still require those recorded channels; phase position alone does not prove a control input.

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 corner or continuous change-of-direction region. Turns use designations such as T5 (Turn 5). LapBrain's designation can differ from a circuit's official map, so use the in-app map to locate the physical corner. Each turn can be divided into entry, decel, maintenance, accel, and exit measurement phases.

Turn metrics can include entry speed, roll speed, apex references on the map, exit speed, line, and directly recorded control channels. Which observations and recommendations appear depends on the channels and comparisons available.

In LapBrain, turns are shown on the track map with their designations and are the primary way coaching organizes its recommendations. A focus item names the turn and shows the laps, channels, and priority behind it.

A complex is a group of two or more turns that are linked closely enough that the path and time measurements in one can affect the starting state of the next. Complexes use designations such as C1 (Complex 1). A chicane is a common example.

In LapBrain, complexes are analyzed both as a whole and turn-by-turn, so you can compare the measured sequence without assuming a universal compromise line or technique.

A straight is a low-curvature section between corner regions. Straights use designations such as ST1 (Straight 1). The label describes track geometry; it does not prove that the motorcycle was upright, that the throttle was fully open, or why speed changed.

In LapBrain, straight analysis can show speed, acceleration, time, and any directly recorded control channels. Compare the preceding exit and the full straight together before interpreting where a time difference arose.

A sector is a defined portion of the track used for timing comparisons. Sectors use designations such as S1 (Sector 1). Their boundaries split a lap into stable segments so elapsed times can be compared across laps and sessions.

In LapBrain, sector times appear in timing and comparison views. A sector delta locates part of a pairwise time difference; it does not by itself identify the rider input, cause, or next action.

An involvement zone shows which part of the track is included in the measurements for a turn, complex, or straight. The solid center marks the main area; the translucent ends include the approach and exit where they overlap the neighboring part of the track.

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. Use the highlight to see where that area's timing, line, and channel measurements begin and end.

The entry phase is the first part of a turn, ending where the main measured deceleration begins. It locates the approach and early direction change without assuming a brake input that was not recorded.

In LapBrain, the entry phase is the first of five phases shown in the turn detail view. Available metrics may include entry speed, line, and direct control channels when the data logger recorded them.

The decel phase covers the portion of the turn where measured speed is falling. The speed trace does not establish brake pressure, trail braking, control smoothness, or tire load on its own.

In LapBrain, the decel phase is the second of five turn phases. Coaching uses that region to locate a finding. Compare its speed, time, line, and any directly recorded brake channel across clean laps.

The maintenance phase is the minimum-speed region between the main measured deceleration and acceleration regions. It does not by itself establish brake release, throttle position, maximum lean, or available grip.

In LapBrain, the maintenance phase is the third of five turn phases. Compare its speed, time, line, and available direct-control channels across clean laps rather than treating a higher minimum speed as an automatic target.

The accel phase covers the portion of the turn where measured speed begins increasing after the minimum-speed region. A recorded throttle channel can add input context; acceleration alone does not prove throttle timing or a rider action.

In LapBrain, the accel phase is the fourth of five turn phases. Compare the speed, time, line, and any directly recorded control channels together.

The exit phase is the last part of a turn. Exit speed is one measurement carried into the following element; the phase does not prove full throttle, line quality, or that an earlier phase caused an exit difference.

In LapBrain, the exit phase is the fifth and final turn phase. Exit speed is a key metric to compare beside the following time delta, line, and any recorded control channels.

Apex mode describes how many inside references a turn has and how they relate: single has one reference, double has two references within a same-direction turn, and opposite links references across direction changes.

LapBrain assigns the mode automatically. Use the mode to tell which inside reference a line or timing measurement belongs to. No reference is automatically a target line.

Braking distance is the arc distance, measured along the track surface rather than a straight line, from the corner region's peak-speed point to its minimum-speed point. Despite the display name, it is derived from speed and distance; it does not establish brake application or pressure.

A shorter or longer distance describes where those two measured points fell. It does not by itself establish control input, safety, or which lap used the better technique.

LapBrain shows braking distance when the speed and distance channels provide both points. Compare it with the time, line, and recorded brake trace rather than treating the shortest value as "best."

The apex-to-min-speed distance measures how far the minimum-speed point is from the apex reference shown on the map.

A value near zero means the two measured references are close. A negative value places minimum speed before the apex reference; a positive value places it after. The sign does not prove brake application, trail braking, a line error, or a technique target.

In LapBrain, use the metric as location context beside the trace and time comparison. A direct brake channel is required for any trail-braking claim.

Turn length is the total distance of a corner, measured as an arc along the track surface from the corner entry point to the exit point. It provides geometry context for comparing phase durations and distances; length alone does not prescribe braking, turn-in, throttle, or line technique.

A longer maintenance region can be expected in some long turns, but the complete geometry and measured trace determine what a particular lap shows. No fixed length threshold establishes whether a corner should be ridden one way or another.

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.

In LapBrain, elevation change is shown in the Turn Info section when altitude data is available from the GPS trace. It is geometry context; an entry-to-exit altitude difference does not describe the local grade at every point or explain a braking, suspension, grip, or rider response.

A hairpin is a tight corner with a small radius, often close to 180 degrees.

A standard corner does not fit one of the more specific hairpin, sweeper, kink, or radius-change shapes.

A sweeper is a longer turn with a relatively large radius and sustained curvature.

A kink is a short, gentle curve in an otherwise straight section of track.

A decreasing-radius corner starts wide and gets progressively tighter toward the exit.

An increasing-radius corner starts tight and opens up as you approach the exit.

A chicane is a pair of closely linked turns in opposite directions, typically a left-right or right-left sequence. The measured end state of the first turn supplies the start context for the second, so pair and complex comparisons can be useful.

In LapBrain, chicane analysis can consider both turns together and separately. Use the combined view to see how the exit of the first turn connects to the entry of the second.

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 chain three or more direction changes.

LapBrain shows the line, time, and other measurements for the linked sequence.

Your personal best (PB) is your fastest recorded lap time at a particular track in the bike history you are viewing. Personal bests persist across sessions, so your PB from three months ago still counts until you beat it.

A PB is a real recorded lap and can be a useful comparison. Pairwise deltas show where another lap differed from it; read those deltas beside the conditions and cited traces.

A PB should not be confused with a best lap (fastest in a single session) or an ideal lap (a descriptive sum of sector minima). A PB is one complete recorded lap.In LapBrain, your personal best is shown prominently in session summaries and can be selected for comparisons. Pace percentile uses the fastest lap that qualifies for that rider-group comparison. 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 can appear under Unassigned. LapBrain can still analyze them and compare them with the same bike class when a specific bike identity is unavailable.

Your best lap is the fastest lap you recorded in a particular session. It is one useful reference for pairwise comparisons. 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 reference when analyzing other laps in the same session. Its turn-by-turn breakdown shows what was measured on that pass; it does not declare every difference correct, safe, or repeatable.

An ideal lap adds the quickest on-pace time recorded in each sector, even when those times came from different laps. Every sector time was observed, and the fixed sector boundaries make the sum a valid descriptive session diagnostic.

The result is not a prediction or a guaranteed lap time. Adjacent sector traces can meet with different position, speed, heading, or controls, so the gap to your best lap is not automatically available time, inconsistency, or a riding target. Use a real lap for a pairwise comparison without assuming it is an achievable target in the next conditions.

LapBrain shows the ideal lap in detailed timing analysis. Coaching and wins do not claim that you can simply join the sectors together.

An on-pace lap is close enough to the session's usual pace to compare fairly with its other laps. Out-laps, in-laps, interrupted laps, and unusually slow or fast laps may sit outside that group.

LapBrain identifies on-pace laps from the pace recorded in that session and uses them for consistency and selected coaching comparisons. The session lap list shows which laps were included.

Delta is the time difference between two laps, typically expressed as seconds gained or lost relative to the lap you're comparing against. 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.

A full-lap delta tells you how two laps compare overall, while a sector or turn delta locates where the cumulative elapsed-time gap changed. If one lap was 0.8 seconds slower and the sector deltas show +0.9s in Sector 2 and -0.1s in Sector 3, the pair lost net time in Sector 2 and regained some in Sector 3.

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. That makes T5 the largest measured difference in that pair. Open T5's cited laps and traces to see how the measurements differ.

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 the lap you're comparing against.

Pace percentile is a number from 0 to 100 that shows how your best lap stacks up against other riders' best laps at the same track on the same class of bike. A pace percentile of 75 means you were faster than about 75% of the recorded riders in that group; a pace percentile of 30 means only about 30% were slower than you. 100 is the front of the field, 0 is the back.

The comparison is against other riders, not your own history. It is drawn from the distribution of every contributing rider's personal best at that track and bike class, so a brand-new personal best can still land at a low percentile when the rest of the field is quicker. To compare against your own history, use your personal best and your pace trend instead.

Because it depends on who else has ridden the track, pace percentile is a snapshot of that group, not a technique grade. It is influenced by the rider population at that track, the weather, tire choice, and bike setup. Read it alongside your exact lap times and your own history.

Across sessions at the same track and bike class, the percentile trend shows how that relative position changed as both your best lap and the group snapshot changed. LapBrain may also show sector- or turn-level comparisons when enough riders contributed the required measurements.

Consistency describes the spread of a measured value across comparable laps. A narrower spread means that measurement repeated more closely; a wider spread means it varied more.

In LapBrain, consistency is measured at both the lap level (how tight is your lap time distribution) and the turn level (how repeatable is a particular corner measurement). A wide spread may appear in the analysis while another finding ranks higher in the focus list.

A coaching thread starts the first time LapBrain identifies an issue it tracks across sessions. Current threads cover repeatability, section-time, and charging issues, kept separate by track and bike.

Each thread links to the laps and channels behind the finding. Later comparable sessions extend it when LapBrain evaluates the same issue again.

If entry-speed spread appeared at T5 last month and LapBrain checks that same measurement when you return, the thread shows how it changed. The status moves between Active, Intermittent, and Mastered as the issue appears or stays absent in checked sessions.

Open a track from Dashboard to see its thread history. A current debrief may also show thread context beside the matching focus item.

A coaching thread becomes Mastered when its issue is absent from three consecutive sessions in which LapBrain checks the same measurement at that track. On the third session, the debrief marks that issue "Resolved over time" and reports that it was absent for three sessions.

Each track and bike keeps its own thread history. If the issue appears again, the same thread returns to Active and retains the earlier Mastered period.

Mastered threads remain visible in your track history.

LapBrain asks about prior riding or driving experience during registration and in Settings. You can choose none, street riding, car track / HPDE, returning bike racer, or Prefer not to say.

The setting helps LapBrain choose more relevant wording for strengths and safety context. Your pace numbers, focus ranking, and feature access stay the same.

LapBrain uses only the answer you provide; it does not infer your background from telemetry. You can update or clear it at any time from Settings → Profile → Rider Background.

When you choose Street riding as your prior experience, LapBrain can use that background while explaining measured strengths and safety context. The measurements and focus ranking still come from your track session.

The related help guide introduces track vocabulary and points to qualified instruction for technique.

When you choose Car track / HPDE as your prior experience, LapBrain can use familiar track vocabulary while explaining motorcycle-specific measurements. The measurements and focus ranking still come from your motorcycle session.

The related help guide separates familiar track concepts from motorcycle technique and points to qualified instruction.

LapBrain adds safety context when a session contains repeated measurements worth reviewing carefully or incident laps alongside those measurements. The note tells you what appeared and how often so you can inspect the relevant laps and discuss them with a qualified coach.

The note is there for review, not as a riding instruction. Use the cited laps and channels, incident review, and qualified coaching before making a technique change.

Focus recommendations are the coaching areas LapBrain suggests you work on next. LapBrain ranks them by how clearly the pattern appeared, the measured time opportunity when one is available, and relevant session history. They answer the question every rider asks after a session: "What should I focus on next time?"

The top item is the highest current priority in the data. Suggested actions use a rider-controlled action or visible reference, such as "use the same visible turn-in reference at T7." Other items may ask you to inspect a measurement without prescribing a riding change.

Focus recommendations change as the recorded pattern changes. A later comparable session may produce a follow-up measurement, keep the item active, or show a different priority.

In LapBrain, focus recommendations are shown prominently in the debrief. Each names the relevant track area and evidence. A suggested action and time estimate appear when the finding supports them.

A precise line means the measured corner path varied little across the cited comparable laps.

A repeated line gives later comparisons a stable measured reference. It does not prove what the rider saw, intended, or did with unrecorded controls.

Strong trail brake is a positive label for recorded brake application that overlaps the cornering transition. It describes the cited measurement; it does not estimate tire grip, confidence, ability, or how another lap should be ridden.

A consistent entry means measured entry speed stayed in a tight range across the cited comparable laps.

The narrow measured spread makes the entry easier to compare with the rest of the corner. It does not establish why the speed repeated or whether that value is a target.

Clean technique marks a strength in a directly recorded control pattern. Open the cited laps and channel to see the input behind the label.

Confident cornering marks a strength in maintenance speed and line across the cited laps. Open those laps to see the measurements behind the label.

Strong exit drive is a positive label for measured acceleration through a corner exit. LapBrain names throttle timing or smoothness only when your file includes a direct throttle channel. The label does not estimate available grip or prescribe the timing for another lap.

Measured motion jerk is the rate at which recorded acceleration changes. A higher or lower value describes the motion trace, not a throttle, brake, or steering input.

Rider controls, track surface, corner geometry, sensor noise, and bike response can all affect the measurement. LapBrain may show it as late-session or cross-session context, but the value alone does not prove input quality, rider fatigue, available tire grip, or what caused a change.

LapBrain uses one neutral coaching vocabulary when you have not declared prior riding experience.

Explicitly declared prior experience may add relevant context, such as noting that a car-track or street-riding background is context for a review. That background is never treated as proof of what caused a telemetry pattern.

Coaching detail is separate. In Settings, choose Quick for the essentials, Standard for the usual review, or Deep dive for the full breakdown with numbers up front. Default adapts the amount of detail to the session.

A persistent issue appeared on the same turn or straight in at least two of your day's sessions. Repetition makes the measured pattern more useful to review than a one-session observation, but it does not by itself identify a technique gap or what caused the pattern.

Persistent issues appear in the Patterns section of your day review, ranked by how many sessions they appeared in (for example, "3 of 4 sessions"). One may also become your next focus for the following track day.

A consistent strength is a positive measurement on the same turn or straight in at least two of the day's sessions. It describes repetition within that day.

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.

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 is clear enough to show them. It draws from your persistent issues and the top-ranked coaching priorities, and only appears on a strong signal. A calm day gets no next-focus item.

Each item names the reason 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 fastest session best occurred before the last session). The label summarizes the order of measured session-best times; it does not identify why they took that shape.

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 show clearly.

Warmup adaptation measures the gap between your first flying lap and your session pace, then watches how that gap moves across the day. When it shrinks, the first flying lap was closer to that session's pace; when it grows, it was farther away. The shape does not establish learning, preparation, fatigue, tire behavior, conditions, or rider intent.

In LapBrain, this appears on the day review with a coaching message and the first- and last-session gaps in seconds. It does not appear when the day stays inside the 0.30 s noise band.

Every dot is one measured acceleration sample from a corner in the visible laps. Left to right is lateral-acceleration magnitude; up is measured deceleration and down is measured acceleration. Those axes do not identify brake pressure, throttle position, or which control caused a change.

The dashed arc is the largest combined-G value observed in the visible laps. It is not a theoretical tire limit, proof of available grip, a safety margin, or an instruction to add load. A shaded upper range, when present, is a session percentile relative to that observed peak—not grip in reserve.

The full sample cloud appears when the session includes sample-level G-G data. Older sessions with fewer measurements may show a simpler apex-only plot.

A "universal" issue for one bike means LapBrain found 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 per-bike coaching thread shows that cross-track recurrence without turning it into a claim about an unmeasured habit or cause.

This differs from "universal across bikes" (see the related entry). Here, the bike stays the same while the tracks change. Across-bikes recurrence needs the same measured issue on more than one bike.

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 at the per-bike level. Neither label explains why the observation repeated.

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. It is a cross-bike recurrence signal, not proof that technique alone produced the pattern or that bike, setup, track, and session context can be excluded.

This differs from the per-bike "universal" label (see the related entry). The per-bike label follows one bike across tracks; the across-bikes label needs the same observation on more than one bike. That makes the recurrence clearer, not its cause.

LapBrain compares the pattern separately on each bike, so it does not blend their raw performance. The cross-bike wording tells you when the bikes have different performance-class estimates or when an estimate is missing.

Without enough comparable history across bikes, the cross-bike item stays hidden.

Rider-career coaching looks for the same measured pattern across your bikes. LapBrain still keeps each bike's personal bests, lap times, and other performance comparisons separate. The cross-bike view asks only whether the same coaching label recurred on more than one bike.

LapBrain compares the pattern separately on each bike, so a 600's raw performance is never blended with a 1000's. You may see a cross-bike item when the same pattern appears on both bikes or has a different status on each. A Resolved label means the pattern stayed absent in recent comparable sessions; it does not prove why it changed.

Cross-bike coaching appears after you have enough comparable history on at least two of your own bikes. Loaner-bike sessions do not count. Until then, your normal coaching and history still work for each bike.

Cross-bike progress appears when the same measured issue has a different status on different bikes: for example, Resolved or Improving on one and still Active on another. The note names the bikes on each side so you know where to inspect the history.

When every bike has the same status, there is no separate cross-bike progress note. A status describes the recent measurements on that bike; it does not prove why the pattern changed or that a technique has been learned.

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.

An "also seen on N other bike(s)" note means the same measured pattern appears in the history for those bikes. The note names the issue, bikes or bike classes, and corner behind the comparison.

The note can also show when the issue has a different status on each bike. If their performance-class estimates differ, or at least one estimate is missing, the note says so. That is a reason to inspect each bike separately, not to read the recurrence as a raw performance comparison.

The note tells you that the pattern recurred. It does not blend the bikes' lap times or prove that rider technique alone caused it.

A Free account can sync an AiM Solo 2, Solo 2 DL, or RaceBox, bring AiM XRK/XRZ, MoTeC LD, or VBO files, keep a full session history, view lap times, inspect maps and lap lines, manage bikes, and keep setup profiles. Your own uploaded sessions remain viewable without a history cap.

Deeper coaching analysis, such as full finding details, lap-comparison analysis, Day Review, and career trends, is unlocked by Pro or by redeeming a Pro session pass on one of your own sessions.

Pro unlocks the session debrief: wins first, then your ranked focus items with the laps and measurements behind each one. It also unlocks full finding details and suggestions, coaching threads, lap-comparison analysis, racing-line analysis, setup-vs-lap-time analysis, Day Review, trends, and the career dashboard.

Pro gates deeper analysis, not access to a rider's own data. Uploaded sessions, lap times, maps, lap lines, and setup profiles remain available on Free.

A Pro session pass unlocks one of a Free rider's own locked sessions. It opens that session's full debrief, wins first and then the ranked focus items with the laps and measurements behind each one, plus the rest of that session's Pro analysis. The session stays readable even if the rider stays on Free.

The pass is tied to your account, applies to your own sessions, and cannot be moved after redemption. A new pass becomes available when the 30-day period resets.

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.

When you upload data, each recording becomes a session containing its laps, coaching, and turn-by-turn measurements. You can compare laps within one session or compare sessions to review changes across a day or season.

LapBrain labels each debrief Practice or Race automatically. Race appears when the opening GPS and speed traces show an on-track start and launch near start/finish. This can be a recorded grid stop or an unambiguous main-track moving launch when the data logger wakes after release. If the opening does not clearly show a race start, the debrief says Practice.

Day review may separately compare pace shapes across the day. A pace shape describes how the run unfolded; only a clear race-start sequence makes the debrief say Race.

Cross-session comparison puts the same measurements from multiple sessions beside one another, typically across a track day, multi-day event, or longer history. It can show whether measured pace, spread, location, or a recurring coaching pattern changed.

Comparisons require compatible track, bike, channel, and session context. A trend describes the recorded observations; it does not by itself establish learning, intent, a control change, or the cause.

A day review aggregates all your sessions from a single track day into one summary. It reports session-best shape, repeated cross-session patterns, repeated findings, and the available comparison context without assigning a cause to the day's changes.

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 measured session-to-session changes, and suggests a focus for your next visit when the pattern is clear enough.

An event review aggregates compatible sessions from a multi-day event, such as a race weekend, track-day series, or riding school.

In LapBrain, the event review pulls together day reviews into a broader summary of measured cross-day changes and repeated findings.

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.

An observed session shape is one of four measurements taken from a run's lap pattern: a steady multi-lap run, a short run that got faster late, a long run that got slower late, or an observed race-start sequence. These descriptions report patterns in the recording; they do not identify why the laps unfolded that way.

You may see these descriptions in the day review's pace-shape contrast card when it compares an earlier steady run with a later run that measured differently.

Bike assignment shows whether a session belongs to one of your bikes, a loaner, or no bike yet. Keeping the bike attached to the session makes lap-time and coaching comparisons more useful.

The assignment appears beside each session in the day review. LapBrain keeps cross-session comparisons within the relevant bike group.

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 data logger and sensors installed. The data logger stores this data to internal memory or a memory card, which you later download for analysis.

LapBrain imports AiM XRK/XRZ, MoTeC LD, and VBO files. The mobile app can also sync recorded outings from an AiM Solo 2 or Solo 2 DL over WiFi and from a RaceBox Mini S or Micro over Bluetooth. Available measurements depend on the data logger, its sensors, and its channel configuration.

LapBrain shows a missing-data message 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 data logger that records lateral acceleration can fill in these reference bands. The rest of the debrief still works from the channels that were recorded.

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 data 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 data 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 data 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 around the track. That trace connects each recorded sample to a location on the circuit.

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 makes dedicated data logging hardware popular in club racing and track days. LapBrain imports XRK/XRZ files and can sync the tested Solo 2 and Solo 2 DL models over WiFi from the mobile app.

MoTeC is a professional-grade data logging and engine management company. LapBrain imports LD log files exported from MoTeC i2 Pro.

The LapBrain mobile app also syncs recorded outings from a RaceBox Mini S or Micro over Bluetooth. Existing RaceBox cloud sessions can be downloaded as VBO files from the RaceBox website and uploaded separately. The plain RaceBox Mini does not store outings for direct Bluetooth sync with LapBrain.

Compound records the rider's tire category, such as DOT, slick, or intermediate, for each axle in a setup entry. Exact construction, operating range, pressure, and service guidance vary by tire model and manufacturer; the category alone does not establish available grip or a safe riding limit.

LapBrain keeps the value as setup context so riders can compare sessions with the configuration they recorded. It does not currently calibrate coaching thresholds or infer grip from this field.

An ECU map slot is the mode or map identifier shown by the motorcycle. What a slot changes depends on the motorcycle and ECU configuration, so two vendors' "Map 1" labels are not equivalent.

LapBrain captures the identifier as free text in the setup profile. It is available as recorded context when comparing sessions; it does not currently change coaching or let LapBrain distinguish rider input from electronics behavior.

Final drive ratio is the gearing between the gearbox output and the rear wheel, set by the front and rear sprocket sizes. Changing the ratio changes wheel-speed and wheel-torque relationships for a given engine speed, but the resulting acceleration and terminal speed also depend on the selected gear, engine, electronics, tire, load, and conditions.

In LapBrain, final drive ratio is derived from the front and rear sprocket counts captured in the setup profile. It is recorded comparison context; it does not currently calibrate coaching or explain a measured acceleration or top-speed difference by itself.

A heat cycle is one warm-and-cool sequence recorded for a tire. How cycles affect service life varies by tire, use, storage, and manufacturer guidance; use the tire manufacturer or supplier's guidance when deciding service life.

In LapBrain, heat cycles are captured per axle in the setup profile. For riders who do not track exact cycle counts, the setup profile also offers a simple tire age: Fresh, Used, or Worn. These fields are recorded setup context and do not currently change coaching thresholds or grip estimates.

A tire warmer is an insulated electric blanket that wraps around the tire and rim before a session. Whether to use one, the temperature setting, and the pressure procedure depend on the tire and manufacturer guidance.

Cold, warmer-set, and immediately-post-session pressures describe different measurement conditions. Record which one you used rather than treating the numbers as interchangeable.

In LapBrain, tire-warmer usage is captured at the profile level. Toggling it on switches the profile from cold-pressure to warmer-set pressure per side. The field preserves setup context; it does not currently calibrate coaching or estimate session-start grip.

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 the numbers describe different measurement conditions and should not be compared as if they were taken at the same state.

In LapBrain, warmer-set pressure is captured per side (front, rear) when the profile has tire-warmer usage enabled. It is stored as setup context; it does not currently change coaching thresholds or establish available grip.