Ujin Kwon · 권우진

Numerical solvers, telemetry systems, control, and real-time engineering

MATLAB · Multi-log telemetry analysis · Replay · Segment metrics

Racing Analyze GUI is a segment-based telemetry workbench for loading multiple runs, comparing the same track region across runs, replaying them in time, and extracting metrics for coaching-oriented review.

Racing Analyze GUI

Workflow

Track Buildreference core + segment definition from a track file
→
Log Loadscan root folders, filter includes, cache selected runs
→
Segment SliceAll, S0, S1..Sn, S(n+1)
→
Replay + PlotsXY, TS, MAP, POLAR, KDE, GG with synchronized replay
→
Metricssegment time, speed stats, acceleration indicators

What I Built

  • Track-core and segment workflow so repeated runs can be compared against the same reference structure.
  • Multi-log loading and caching for quick switching after one analysis pass.
  • Synchronized replay system with time slider, play/pause/stop, speed control, and pane-aware markers.
  • Flexible pane system with XY, TS, MAP, POLAR, KDE, and GG views plus per-pane rerender/pop-out tools.
  • Channel-flexible visualization where arbitrary logged channels can be assigned to axes or color.
  • Metrics extraction for segment time, speed statistics, and acceleration-related indicators.

Metrics Exposed In The App

  • segTime: selected-segment time
  • vmin / vmean / vmax: speed min / mean / max
  • vin / vout: speed at segment entry / exit
  • arms / a95 / amax: acceleration magnitude statistics for quick comparison

What This Project Proves

  • Tool-building discipline: I can turn raw telemetry into a reusable inspection workflow rather than a temporary notebook or script pile.
  • Domain-aware analysis: the app is built around track segments, replay, and coaching review, not generic plotting alone.
  • Stateful UI engineering: repeated workflows, pane state, replay control, and metrics output are treated as product features.

Evidence

  • The GUI is structured as an actual workbench, not a one-off plotting script: track build, run caching, segment slicing, replay, plots, and metrics are separate steps in one flow.
  • The app supports multiple analysis views and pane-level tools, which is stronger evidence of repeated real use than a single static screenshot.
  • The telemetry workflow is connected upstream to the Racing Telemetry Stack, so this page describes the analysis side of the same system.

Current Limits

  • This page still needs a short usage video or an applied case-study block to show how a comparison changes an actual driving/coaching decision.
  • I am keeping the claims here tied to implemented UI and metric features rather than inventing user-study style outcomes that are not currently published.