Circuit of the Americas (COTA) · Motorcycle not specified

Your riding review

Your practice priorities and review areas

Practice priorities

Latest day · December 01, 2024 · 14 laps. Ranked by observed section time impact, with repeated evidence required. Showing all sections with at least 0.50 s of associated time difference.

Why this many priorities?

0 sections passed the repeated-evidence test before the time cutoff. A smaller cutoff admits smaller differences; a larger cutoff removes more. Each technique comparison requires at least two distinct laps on each side within one session, with similar approaches and matching channels. A three-lap session cannot supply both groups. Exit timing can still suggest useful review questions without identifying a repeated technique pattern.

No repeated similar-approach comparison meets the 0.50 s minimum time-impact cutoff.

Where exit timing differs

Also review these exits: their timing varies repeatedly across sessions. These are useful review areas alongside the practice priorities, even without enough evidence to identify a specific technique pattern. The two kinds of differences are not added together.

Exit review

R8

0.85 s between the middle-ranked and quickest exit runs, typical across 4 sessions.

Exit review

R14

0.28 s between the middle-ranked and quickest exit runs, typical across 4 sessions.

Exit review

R7

0.19 s between the middle-ranked and quickest exit runs, typical across 4 sessions.

Exit review

R3

0.17 s between the middle-ranked and quickest exit runs, typical across 4 sessions.

What are your turn-in and exit references in these corners? Are your eyes moving ahead so you can get the bike pointed and build drive smoothly as the turn opens?

What these exit differences mean

Compatible own laps only. Use algorithmically detected gentle runs after bends. Within each session with at least three laps, compare the actual middle-ranked run with its quickest recorded run. Report the median difference across at least two sessions, retaining windows with at least 0.10 s difference. Time is measured between the same window boundaries, so a lead accumulated before the window is excluded. Incoming speed and line are not matched; these are observed timing differences, not promised gains or proof of a throttle/braking problem. Do not add them together.

Your best pieces together

Latest-day best 3:17.7s · Conditional lap 3:17.7s · Difference 0.00 s.

No compatible improvement from the selected priority blocks was found.

Recorded sections joined with similar speed, position, heading and acceleration. A conditional estimate, not a promised lap time.

Which sections make this lap?

Baseline: 20241201T224214-L3. Unselected blocks stay on this lap; each block is counted once.

  • R1 · 20241201T224214-L3 · 2.69 s
  • R2 · 20241201T224214-L3 · 13.58 s
  • R3 · 20241201T224214-L3 · 10.89 s
  • R4 · 20241201T224214-L3 · 11.10 s
  • R5 · 20241201T224214-L3 · 8.99 s
  • R6 · 20241201T224214-L3 · 6.09 s
  • R7 · 20241201T224214-L3 · 19.70 s
  • R8 · 20241201T224214-L3 · 34.46 s
  • R9 · 20241201T224214-L3 · 15.37 s
  • R10 · 20241201T224214-L3 · 11.48 s
  • R11 · 20241201T224214-L3 · 12.08 s
  • R12 · 20241201T224214-L3 · 14.07 s
  • R13 · 20241201T224214-L3 · 17.60 s
  • R14 · 20241201T224214-L3 · 19.63 s
How priorities and estimates are calculated

Latest-day own laps only. Each contrast stays within one session and uses matching available channels. Compare repeated lower and higher counts of one observed event family, or compare higher and lower minimum speeds with at least a 3 mph gap and slowest points within 25 m, away from block boundaries. The latter flags possible excess speed loss, not confirmed over-braking. This is broader than exact full-sequence matching. At least two distinct laps on each side must pass approach matching, and most matched differences must favour the lower-count or higher-minimum-speed group. Section elapsed times are measured from the same start, so an accumulated lead before it is not counted. Approach speed, position and heading are matched, not all conditions. Rank by median matched section time difference; support and post-corner run relevance break ties. Show every qualifying block above the configured minimum time-impact cutoff, without a fixed count. Gentle runs do not establish technique quality. Counts, thresholds, source laps and rejected candidates are retained. Association is not causation; GPS noise, shifts, hills, traffic and intent remain possible explanations. No measured throttle, brake or intended apex.

{
  "min_group_laps": 2,
  "min_time_difference_s": 0.1,
  "approach_speed_mps": 2.5,
  "approach_position_m": 5.0,
  "approach_heading_deg": 12.0,
  "gentle_curvature_per_m": 0.006,
  "run_gap_m": 60.0,
  "run_start_window_m": 150.0,
  "meaningful_run_m": 150.0,
  "bend_prominence_per_m": 0.003,
  "bend_curvature_per_m": 0.008,
  "bend_spacing_m": 75.0,
  "geometry_bonus_max": 0.75,
  "geometry_run_cap_m": 400.0,
  "positive_pair_difference_s": 0.05,
  "minimum_speed_gap_mph": 3.0,
  "minimum_speed_location_gap_m": 25.0,
  "minimum_speed_boundary_margin_m": 15.0,
  "min_priority_gain_s": 0.5
}

Named blocks may span several turns. Numbers retain the supplied map convention; distances follow the recorded lap. Start/finish can split a corner.

All regions considered
  • R1 · gentle run 0 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R2 · gentle run 30 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R3 · gentle run 155 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R4 · gentle run 35 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R5 · gentle run 45 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R6 · gentle run 0 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R7 · gentle run 325 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R8 · gentle run 900 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R9 · gentle run 70 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R10 · gentle run 30 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R11 · gentle run 35 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R12 · gentle run 0 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R13 · gentle run 125 m · No repeated same-session contrast with similar approaches and a meaningful time difference.
  • R14 · gentle run 400 m · No repeated same-session contrast with similar approaches and a meaningful time difference.

Practice language focuses on smooth transitions. Optional reading: Champ School on getting the bike pointed for the exit. These telemetry observations are not a Champ School assessment.

Where B is faster or slower than A

Green means B is faster; purple means A is faster. This compares speed at the same track location (B − A), so you can see where the advantage changes hands before looking at the time gained.

Approach and exit patterns

These callouts follow the selected A/B laps. A slower patch before the bend followed by a faster exit patch is a useful review question; it does not show that entering slower caused the exit advantage.

How these patterns are measured

Approach means section start to the shared reference bend marker; exit means the geometry-detected gentle run afterward. A patch needs at least 1 mph difference held for 0.5 seconds in both laps. Each phase shows its longest sustained patch, with median speed difference. The entry column shows a slower patch when present, even if other approach points favor B. Section time is the change in A − B elapsed time across the full section, excluding the lead carried in. These are selected-pair observations, not repeated technique findings, measured throttle/brake inputs or potential gains. Missing bend/exit geometry is shown explicitly. The color scale stays fixed at ±6 mph; larger differences saturate, with exact values on hover.

Where the lap-time gap opens

Read this curve from left to right. When it rises, B gains time on A; when it falls, A gains on B. A flat curve means their gap stays about the same. A rise after a corner shows time accumulating along the exit, even if the difference began in the bend. The height is the lead carried so far; the change across a section is the time gained there.

Where the speed advantage begins

This follows the selected A and B laps above. Compare where their speeds separate with where time is gained.

Checkpoint speeds and slowest points

How these locations are determined

The bend marker and exit-run start come from the reference track geometry and are shared by both laps. They are approximate landmarks, not measured turn-in, apex or throttle points. Where no exit run is detected, the view uses two parts split at the bend marker. Without reference bend geometry, it explicitly uses the section midpoint instead. A speed difference counts when it reaches 1 mph and lasts at least half a second in both laps. This is a display filter, not a practice threshold. Speed and elapsed time are interpolated at the same track distances; the slowest points are found independently in each lap. This pair explains a recorded difference, not its cause or repeatability.

Explore the charts

How to read this view

Compare complete laps at the same physical locations. Select A and B: positive time advantage means B is ahead of A. Lap times use minutes:seconds; time differences are seconds. Distance is metres; speed is mph.

How to read this view

Review what you can deliberately practice: progressive release, a coherent transition, sustained drive and fewer corrections. More speed, later braking or greater lean alone does not establish improvement.

Pace outcomes · supporting context

What your own laps tell us

Jump to acceleration maps · Jump to speed differences · Jump to time differences · Jump to elevation context · Jump to load demand

Detailed corner execution · selected laps

Repeatable corner execution

How to read this view

Same-session patterns provide repeatability evidence. A detected disturbance may be intentional or geometry-related; absence of a flag does not prove good technique. Compare the full approach, turn and exit at a comfortable pace.

Repeated patterns with fewer disturbance candidates

Expand a region below to review the selected pair in detail.

Execution review method and limits

Shared corner inspector

How to read this view

Select a region to focus the paired distance charts on its full recorded bounds, including the approach and exit contained in that block. Start/finish can split a linked corner. Click a distance trace or a map sample to pin the shared location. Teal A and orange B markers show the matched positions on the maps; overlapping positions may hide one marker. Clicking outside a focused region switches to the region containing that location. Map zoom stays independent.

Braking, release and acceleration events are inferred proxies, not measured brake pressure or throttle. Lean is the exported estimate; lateral G is the device Y axis. GPS separation colors show the size of the recorded A/B difference, not confidence that the riding lines differ.

Map labels and travel direction

Turn labels and map source

Analysis blocks can span several turns. Their boundaries and timing remain unchanged. Outlined diamonds show the strongest smoothed GPS curvature in each block, not a verified riding apex.

GPS line comparison

How to read this view

A is the solid teal line; B is the dashed orange line. Dots on B show the recorded separation from A at the same reference distance, using a continuous light-to-dark scale from 0 to 10 m. Larger gaps use the darkest color. Hover on either line or a dot for A/B speeds, B − A speed difference and separation. Switch the dot overlay to speed difference to see whether the wider line is faster or slower at the same place. Thin gray connectors join matched samples about every 15 m. Zoom to inspect the two lines.

Path length, speed and time through the exit

How these exit windows are compared

Each window runs from the shared reference bend marker to the end of its detected exit run. Path length comes from each lap’s cumulative own GPS distance, not the shared reference distance. Mean recorded speed averages the exported speed channel over elapsed time. Time is measured between those same boundaries. The pattern summary uses at least 1 m shorter and 0.05 s quicker as display filters, not a GPS precision or significance claim. Line separation and path length are different measurements; a shorter GPS path does not determine which side of the track is inside, or prove why time was gained. GPS noise, alignment and the choice of window affect these small differences. Missing geometry or channels remain unavailable.

Chart context and measurement limits

The scale has no special cutoff at 3 m. Separation includes GPS error and alignment uncertainty as well as possible riding-line differences; it is a horizontal point-to-point gap, not necessarily a perpendicular distance across the track. Gap colors show separation magnitude. In speed mode, green means B is faster and purple means A is faster, with colors saturating at ±6 mph; hover shows the exact difference. Neither overlay establishes which line caused a time gain.

Where you gain and lose speed

How to read this view

Acceleration shows how speed is changing, rather than how fast you are going. Red means slowing, pale means near steady speed, blue means gaining speed. Both maps use a fixed −6 to +6 m/s² scale across all laps; stronger values saturate at the end colors, with exact values on hover. Extreme values right at lap boundaries may be derivative artifacts. Hover for speed and acceleration; R markers identify region starts and diamonds mark GPS curvature peaks (apex proxies, not verified racing apexes).

How to read this view

Positive acceleration after a bend can help locate drive building. Deceleration beyond a diamond is a review prompt, not proof of late braking: trail braking, line choice, hills and rider inputs all affect the trace. This is smoothed GPS-speed acceleration, not measured throttle or brake pressure.

Where acceleration differs · B minus A

Teal means B is gaining speed more quickly, or slowing less, than A at this location. Purple means B is gaining speed less quickly, or slowing more. Pale means similar acceleration. A positive difference does not necessarily mean either lap is accelerating, or that B is faster. Hover for both laps’ acceleration and speed; click to pin the location. The difference scale stays fixed at −3 to +3 m/s²; colors saturate beyond that range. This compares the existing smoothed GPS-speed acceleration, not throttle or brake pressure.

Where B is ahead or behind on time

How to read this view

Imagine both laps starting together. Green: B reaches this point sooner. Purple: B reaches it later. Pale means approximately even. This is accumulated time advantage since the start, not time gained only at that spot. Positive A − B means B is ahead; negative means B is behind. The finish value is the whole-lap difference. Hover for both elapsed times and the gap, or click to inspect the location below.

Chart context and measurement limits

On the speed/terrain chart, R labels mark region starts. Teal diamonds mark A’s maximum-curvature locations; orange open circles mark B’s. Hover a marker for its region, distance and speed. These are curvature peaks within analysis regions, not verified racing apexes.

Chart context and measurement limits

The gray profile is the median relative GPS height across your valid laps, after removing each lap’s vertical offset. Its right-hand axis is height; the left-hand axis is speed. Use the profile together with your knowledge of the track: a known near-level stretch makes terrain a less likely explanation for a substantial acceleration change, while a climb or descent supplies a clear additional influence. At the same location on a similar line, both laps experience approximately the same gravitational contribution, which makes A/B acceleration differences especially useful evidence of other differences. Speed, gear, aerodynamic drag and cornering still matter; the trace cannot distinguish brake application from rolling off or engine braking. Diamonds are curvature peaks; minimum speed and the rider’s chosen apex can occur elsewhere.

Turning, slowing and accelerating

Each dot is one point in the selected section: left/right shows turning demand, and up/down shows acceleration/slowing. Select a section, click a dot to locate it on the track, or play through it. Use “Turn peaks only” to compare one labeled point per turn for each lap. Peaks are selected by the strongest GPS turning demand, not the largest combined G. Teal is A; orange is B. The rings show G magnitude, not available tire grip.

Review question: where does slowing ease, and does drive build smoothly as the turn opens? These GPS-based demands show the recorded sequence, not brake pressure, throttle position or unused grip. A smaller slowing peak than turning peak does not tell us to brake harder. The circle shows combined demand; its rings are not a tire-grip limit.

Compare recorded demand by section

Full-section 95th percentile / peak across all distance samples in the selected direction, regardless of the point filter. Click either lap's values to inspect its peak. A single peak is not evidence of sustained demand or available grip.

What repeated laps add to the review

Source laps and transition locations
Transition comparison method

Where these measurements come from

RaceBox exports three accelerometer axes and three gyroscope axes. Raw X/Y follows the device as the bike leans; it is not the same frame as the GPS view. Raw XYZ magnitude includes gravity. Neither view measures tire grip remaining.

Turn-peak windows extend halfway toward adjacent mapped turns and stop at the lap boundaries. Map labels are approximate. Each lap supplies its own maximum absolute GPS turning-demand point within each window; missing raw readings at that point are omitted in the raw view. Tracks without mapped turns use labeled analysis sections instead. The peak is located before applying section and direction filters, so filtering never substitutes a different point.

Suspected upshifts

How to read this view

Triangles mark brief acceleration dips followed by recovery: open triangles are suspected upshifts; filled triangles are rider-confirmed. Teal is A; orange is B. These are review candidates, not measured gear changes. Select a location below or click a triangle on the speed, acceleration or GPS line charts to inspect it together. Confirmation records your recollection; dismissing hides that candidate from the charts.

How to read this view

Reviews are saved in this browser when storage is available. Export a file to keep a portable backup. Imports merge reviews, with imported decisions replacing matching local decisions. Reviews apply only to this dataset, aligned traces and detector version; adding laps or changing the alignment requires a fresh review.

How suspected upshifts are selected

How to read this view

GPS-speed acceleration is smoothed and sampled on the report’s distance grid. Candidate locations and durations are approximate; short shifts may be missed, and throttle changes, traction, terrain or noise may resemble a shift. This does not identify gears, prescribe shift points or calculate time lost.

Detailed reading of the selected traces

Reading the traces

Drive shortfalls and acceleration interruptions

How automatic observations are selected
How to read this view

Speed patches require at least three consecutive grid points with a difference of 1.24 mph or more. Up to three strongest patches per region are described in travel order. Mild slowing: −1.5 to −0.3 m/s²; stronger deceleration: at most −2 m/s², each sustained for at least three samples and 0.3 s. Approach windows cover 120 m before to 60 m after region starts; R1 uses the final 120 m of the selected lap. The first and last 25 m are excluded from event detection because of boundary derivative artifacts. These thresholds are review heuristics, not classifications of measured control inputs.

How to read this view

An interruption requires 0.3–2 s of −1.5 to +0.2 m/s² between sustained acceleration of at least +0.7 m/s² in the adjacent 0.7 s windows, with at least 0.62 mph lost relative to the other lap during the pause. A drive shortfall flags at least 0.3 s and three samples of −0.3 to +0.7 m/s² while the other lap accelerates at least +0.7 m/s² and at least 0.6 m/s² harder, with a relative speed loss of at least 0.62 mph. No flag does not rule out a mechanical issue. Gear/RPM data would be needed to distinguish clutch slip from a missed or normal shift.

Chart context and measurement limits

Distance charts below use the same landmarks: Block labels mark region starts; teal diamonds mark A’s maximum-curvature locations and orange open circles mark B’s. On the time-delta chart, both sets sit on the single A − B curve. Hover for the region, location and chart value.

Elevation context

How to read this view

Known terrain helps interpret the riding. On a near-level stretch, substantial acceleration changes are more suggestive of throttle, braking or gear changes. On a steady slope, gravity remains a background contribution; a change in slope can itself change acceleration. A small net elevation difference between two endpoints does not prove the section between them is flat. Use your track knowledge and the full profile together. GPS altitude helps locate broad hills, but vertical offsets drift between laps. Relative height subtracts each lap’s median altitude to compare profile shape. Neither view measures road grade accurately enough to correct braking or diagnose clutch slip.

Corner and region evidence

Blocks may span linked turns; R identifiers remain in the exported analysis data. Onsets require sustained thresholds and may be absent. The time difference is A − B: positive means B gained time.

Detailed measurements

Repeatability and progression

How to read this view

The pace chart shows every valid own session on the latest visit, including drizzle sessions, with a separate line and condition label for each. Changes across surface conditions are pace outcomes rather than proof of riding improvement. The heatmap, consistency table and GPS spread use the compatible analysis group stated at the top.

Detailed measurements
Detailed measurements
Detailed measurements
All section-time opportunities

Observed time differences · outcome context

Latest track day: actual middle-ranked section versus best observed section. These differences overlap and must not be added into a predicted lap gain.

Analysis-cohort all-region composite

Compatible theoretical best

Data quality, source validation and exclusions
Comparison rider interpretation
How to read this view

Line geometry and phase locations can be relatively transferable. Straight-line acceleration, peak deceleration and absolute corner speeds depend heavily on motorcycle, tires and setup. Even geometry depends on those factors. Never copy an expert’s control inputs or speeds. Opposite-direction or spatially incompatible laps are rejected; motorcycle information comes from the comparison configuration.

How to read this view

Generated locally. Plotly is bundled; no network connection or Python editing is needed to use this report. Normalized samples, grids and all metrics are available beside this file.