# flappedear/telemetry architecture

> Architecture diagram of the GitHub repository flappedear/telemetry, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-10-03). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/flappedear/telemetry
- Repository: https://github.com/flappedear/telemetry

## Overview

FlappedEar Telemetry is a cross-platform track-day analysis app. The main workflow is to import RaceChrono recordings, calculate laps and day results, then explore maps, charts, comparisons and derived reports. The README documents these product capabilities, but the supplied source excerpts do not include the Flutter UI or most runtime implementation. Accordingly, links between product stages below reflect documented behavior; the available core package path is the only source location shown for its recording and analysis model.

Main entry points: [`packages/telemetry_core`](https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core) (Telemetry core)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_import["Recording import"]
  node_import_day["Import a day"]
  node_recordings["VBO / RCZ recordings"]
end

subgraph group_analysis["Lap analysis"]
  node_core["Telemetry core"]
  node_lap_timing["Lap timing"]
  node_segments["Approved segments"]
end

subgraph group_exploration["Results exploration"]
  node_day_results["Day results"]
  node_lap_view["Lap map and charts"]
  node_comparison["Lap comparison"]
  node_corner_analysis["Corner Analyzer"]
  node_theoretical_best["Theoretical best"]
  node_time_losses["Time losses"]
  node_consistency_progression["Consistency and progression"]
  node_driving_insights["Driving insights"]
  node_day_report["Day report"]
end

subgraph group_persistence["Day data"]
  node_saved_day["Saved day"]
  node_day_store[("Day storage")]
end

node_driver(("Driver"))

node_driver -->|"chooses recordings"| node_import_day
node_recordings -->|"supplies files"| node_import_day
node_import_day -->|"prepares recordings"| node_core
node_core -.->|"calculates laps"| node_lap_timing
node_core -->|"proposes segments"| node_segments
node_import_day -->|"shows results"| node_day_results
node_day_results -->|"opens lap"| node_lap_view
node_day_results -->|"compares laps"| node_comparison
node_comparison -->|"analyzes corners"| node_corner_analysis
node_day_results -->|"shows segment losses"| node_theoretical_best
node_day_results -->|"ranks losses"| node_time_losses
node_day_results -->|"summarizes trends"| node_consistency_progression
node_comparison -->|"shows driving metrics"| node_driving_insights
node_day_results -->|"presents report"| node_day_report
node_driver -->|"saves or opens"| node_saved_day
node_saved_day -->|"reads and writes"| node_day_store

click node_core "https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core"
click node_lap_timing "https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core"
click node_segments "https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_import_day,node_recordings toneBlue
class node_core,node_lap_timing,node_segments toneAmber
class node_day_results,node_lap_view,node_comparison,node_corner_analysis,node_theoretical_best,node_time_losses,node_consistency_progression,node_driving_insights,node_day_report toneMint
class node_saved_day,node_day_store toneRose
class node_driver toneIndigo
```

## Components

### Recording import

- **Import a day**
- **VBO / RCZ recordings**

### Lap analysis

- [Telemetry core](https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core): `packages/telemetry_core`
- [Lap timing](https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core): `packages/telemetry_core`
- [Approved segments](https://github.com/flappedear/telemetry/tree/main/packages/telemetry_core): `packages/telemetry_core`

### Results exploration

- **Day results**
- **Lap map and charts**
- **Lap comparison**
- **Corner Analyzer**
- **Theoretical best**
- **Time losses**
- **Consistency and progression**
- **Driving insights**
- **Day report**

### Day data

- **Saved day**
- **Day storage**

### Other components

- **Driver**

## Connections

- Driver → Import a day: chooses recordings (evidence: `README.md`)
- VBO / RCZ recordings → Import a day: supplies files (evidence: `README.md`)
- Import a day → Telemetry core: prepares recordings (evidence: `README.md`)
- Telemetry core → Lap timing: calculates laps
- Telemetry core → Approved segments: proposes segments (evidence: `README.md`)
- Import a day → Day results: shows results (evidence: `README.md`)
- Day results → Lap map and charts: opens lap (evidence: `README.md`)
- Day results → Lap comparison: compares laps (evidence: `README.md`)
- Lap comparison → Corner Analyzer: analyzes corners (evidence: `README.md`)
- Day results → Theoretical best: shows segment losses (evidence: `README.md`)
- Day results → Time losses: ranks losses (evidence: `README.md`)
- Day results → Consistency and progression: summarizes trends (evidence: `README.md`)
- Lap comparison → Driving insights: shows driving metrics (evidence: `README.md`)
- Day results → Day report: presents report (evidence: `README.md`)
- Driver → Saved day: saves or opens (evidence: `README.md`)
- Saved day → Day storage: reads and writes (evidence: `README.md`)
