PlayerDNA · Single-Player Match Analysis
Aiden Peelle — #84 · Match Report, Period 1
Every number below was extracted from the actual match video by the tracking pipeline and is read through Aiden's player profile — a 2009 outside back developing as a modern attacking fullback. Fields the video cannot measure are shown as what they are — coach and player inputs — not fabricated.
Physical & participation summary
Where he played
Positional heatmap while visibly tracked (cross = average position). Camera-side flank occupancy: 82% near/right flank, 18% central, 0% far flank. Thirds split: 70% defensive third, 27% middle, 3% attacking.
Estimated speed across the period. Gaps are honest — moments the player wasn't visible or calibration wasn't available; nothing is interpolated.
Highlight clips (auto-selected)
Windows chosen automatically around his fastest sprint events; each clip renders the yellow #84 marker and
motion trail. Files in outputs/trace-full/.
match 03:10 · 10s · sprint 34 km/h · 13 m
match 12:16 · 10s · sprint 34 km/h · 9 m
match 15:31 · 10s · sprint 34 km/h · 11 m
match 21:09 · 10s · sprint 34 km/h · 9 m
Development goals × match evidence
Aiden's stated goal is to develop as a modern attacking outside back. That gives this analysis its lens — the question isn't "how fast is he," it's "does he get forward, and does the data show it."
| Development goal | What this match shows | Status |
|---|---|---|
| Join the attack from fullback | 10 attacking-third entries and 41 forward sprint runs while visibly tracked — the overlap habit is measurable and trendable game over game. | measured |
| Possession & offensive build-up | Receiving under pressure, circulation, progressive passing need ball tracking — phase 2. The positional data (flank fidelity, thirds) already frames where build-up involvement happens. | phase 2 |
| Chance creation & set-piece delivery | Crosses, key passes, and free-kick outcomes require ball + event detection. Highlight clips capture set-piece moments for manual coach tagging today. | phase 2 |
| Two-footed play | Not resolvable at Trace camera distance — stays a coach-evaluation field with clip evidence. | coach |
| College recruiting pathway | This report is one entry in a longitudinal record: same metrics, every game, trending across the season — the PlayerDNA core value. | started |
Your development framework — what this analysis covers
| Category (your framework) | Status today | Notes |
|---|---|---|
| 1 · Player profile & context | provided | Full profile on file (age group, positions, foot, build, injury history, goals) — drives the interpretation above. |
| 2 · Participation & playing time | measured | Minutes visible, position, flank — from tracking. Selection/availability needs roster input. |
| 3 · Technical performance | needs ball tracking | Passes, touches, dribbles require reliable ball detection + event recognition — phase 2. Honest zero today. |
| 4 · Defensive performance | needs ball tracking | Duels/interceptions likewise. Positioning components partially derivable from tracking data now. |
| 5 · Physical workload | estimate | Distance / sprints / speeds from calibrated video — labeled estimates, visible-time only. GPS would upgrade this. |
| 6 · Tactical intelligence | input | Coach 1–5 ratings. Video evidence clips (below) support the assessment. |
| 7 · Mental & behavioral | input | Coach + player self-assessment forms. |
| 8 · Wellness & readiness | input | 1–5 self-reports; session load = duration × RPE. Not a video problem. |
| 9 · Video evidence | measured | Auto-cut, timestamped, position-tagged clips — this report's clips are the first samples. |
| 10 · Coach evaluations | input | Periodic forms; video clips attach as evidence. |
| 11 · Goals & development plans | input | 2–3 active goals; video metrics become baselines/targets where measurable. |
MVP per-game dataset — source of each field
| Field (your MVP list) | Source | This game |
|---|---|---|
| Minutes played | video | 20.9 min visible (subs/availability need roster) |
| Position | video | right back, camera-side flank |
| Goals & assists | ball tracking (phase 2) | — |
| Passes attempted / completed | ball tracking (phase 2) | — |
| Progressive passes / chances | ball tracking (phase 2) | — |
| Dribbles / shots | ball tracking (phase 2) | — |
| Defensive duels / interceptions | ball tracking (phase 2) | — |
| Ball losses | ball tracking (phase 2) | — |
| Distance / sprints / top speed | video estimate | 2.85 km · 107 sprints · 28.8 km/h |
| Coach game rating | coach | form field |
| Player self-rating | player | form field |
| 3–5 tagged video clips | video | 4 auto-cut clips attached |
Method & honesty notes
- Identity: #84 confirmed by readable back number at 14:10, then carried by an appearance-gated tracklet chain (161 segments). Chain cleaned of a look-alike teammate (#2, distinguished by hair brightness) across 5 automated iterations, then spot-checked visually; residual identity risk is flagged, not hidden.
- Calibration: the Trace camera pans, so a homography was computed every 2 s from pitch line keypoints (93% of samples valid, 22 cm median reprojection error). Positions use the nearest valid sample.
- Distance is visible-time distance. When he's off-frame or uncalibrated, nothing is counted or interpolated. Full-match totals require full-field static coverage (or fusing periods).
- Pitch size assumed 105×68 m — if the actual field differs, distances scale linearly; enter true dimensions to correct.
- Speeds above 34 km/h are discarded as calibration jitter; sprint threshold 19.8 km/h (youth-configurable).
Bottom line: from one unattended Trace recording, the pipeline produced participation, physical-load estimates, positional analysis, and tagged highlight clips for one selected player — the four video-derivable pillars of your framework. The technical/defensive stat block is a ball-tracking problem (phase 2), and everything human stays human.