Exercise metrics, penalties and comparative reports built from real telemetry sessions.
CONTEXT
Context and objective
A comparative activity requires more than recording a trace: times, angles and penalties must be associated with consistent exercises and runs, then returned in a readable and verifiable form.
SYSTEM
Architecture
Field devices acquire each session. The analysis links participant, exercise and run, calculates consistent metrics and produces a structured dataset and summary report.
Devices and sensors
- HDA telemetry units
- GNSS and inertial sensors
- Field operations station
- Result dataset and report
Connectivity and protocols
- GNSS/IMU acquisition
- Transfer into analysis tools
- Tabular processing
- PDF reporting and web visualisation
Dashboards and operations
- Run and exercise association
- Times and average angle
- Penalty management
- Comparison and final reporting
HDA contribution
- Field-device operations
- Exercise structuring
- Metric calculation and checks
- Reporting and data visualisation
Data extract / 2025-03-05
Comparative report
Average time · track hairpin
EVIDENCE
Outcomes and evidence
The dataset and report dated 5 March 2025 document four exercises for six participants. Names are anonymised on the site and are not turned into performance claims.
TRUST
Role of Trusted Data
The link across acquisition, participant, exercise, run, penalty and summary formula must be preserved. Calculation transparency comes before any notarisation technology.