Badminton smash biomechanics analysis on 240 FPS mobile capture — a dual-output pipeline that classifies the smash into 6 kinematic phases at 95% accuracy and measures shuttle exit speed at 90% accuracy versus ground truth. MediaPipe Pose for the body, TrackNet for the shuttle, a Savitzky-Golay denoiser between them — coach-grade biomechanics without a mocap lab.
Cricket bowling has a mature biomechanics framework — six well-defined phases (run-up, impulse, jump, back-foot contact, front-foot contact, release, follow-through), each with its own measurable kinematics. Coaches use it. Sports scientists publish papers about it. Badminton smash analysis, by comparison, was nowhere close to that maturity.
The hypothesis going in (from the original R&D ticket): "Can we replicate bowling side-action analysis to badminton smash?" The answer turned out to be yes, with adaptations — but the harder problem was making the analysis run on 240 FPS mobile capture, not lab-grade motion capture rigs. Coaches at academy level don't have mocap labs. They have phones.
The job: take MediaPipe Pose (33 skeletal keypoints, mobile-friendly) and our production TrackNet shuttle detector (TFLite, on-device), fuse them into a single biomechanics pipeline, and produce coach-grade metrics. No external sensors. No mocap markers. Just a phone, a tripod, and a 240 FPS recording.
The same 240 FPS clip produces two independent measurements: a temporal segmentation of the smash motion into six biomechanical phases, and an event-driven measurement of the shuttle's exit speed at the contact moment. Both run from the same MediaPipe + TrackNet substrate.
State-machine-driven segmentation on smoothed pose data. Detects six distinct phases: Preparation, Loading, Jump, Acceleration, Contact, Follow-through — each with its own measurable kinematics (knee flexion, takeoff angle, shoulder angular velocity, follow-through arc).
Not ML. A state machine reading thresholds on vertical velocity and wrist position. The benefit: interpretable, deterministic, debuggable. The annotator confirms phase boundaries; the model learns nothing about the segmentation itself.
Wrist-based speed proxies are unreliable. The wrist decelerates after contact; the shuttle accelerates from it. So instead of estimating shuttle speed from the wrist, we use an event-driven approach: once the Contact Phase is detected by Output 01, TrackNet locks onto the shuttle for the next 5 frames and computes the displacement-based speed in km/h.
The 90% accuracy vs ground truth is the result. The architectural decision — let the phase classifier trigger the speed measurement — is why it works.
Phase boundaries are detected by a state machine reading vertical velocity, wrist position, and shoulder angular velocity off the smoothed MediaPipe pose stream. The transition triggers are deterministic; the metrics within each phase come from vector geometry on the keypoints.
What actually happens between a raw 240 FPS clip and a phase-classified, speed-measured, coach-ready output.
PIXELS_PER_METER constant is derived from a known reference object in frame (e.g., the net pole height) to convert pixel distances into real-world meters. A high frame rate — 240 FPS — ensures the time-step calculations (dt) are precise enough for the high-speed motion the smash produces.
14,000°/s due to a 2-pixel keypoint wobble at 240 FPS. The fix: a Savitzky-Golay filter (window size 9, polynomial order 2) applied to the keypoint trajectories. Smooths the high-frequency noise while preserving the actual peaks of the smash motion.
Δdistance / Δtime) using the smoothed signal. Take the 95th percentile rather than absolute max — filters remaining outliers and produces realistic elite-level reference numbers.
EliteStandards dictionary — ranges derived from professional badminton biomechanics literature (e.g., Jump Height > 0.5m, Knee Flexion 40-90°, Shoulder Angular Velocity > 1500°/s). The system classifies each metric as Excellent / Good / Needs Improvement based on these thresholds.
An early version of the pipeline reported a peak shoulder angular velocity of 14,000°/s on a club-level player. That number is physically impossible — elite professional badminton smash velocities top out around 7,000–9,000°/s. The pipeline was confidently reporting a number twice that of any human ever measured.
The cause: at 240 FPS, the time-step between frames is roughly 4.17 milliseconds. A MediaPipe keypoint wobbling by just 2 pixels frame-to-frame, with the upstream pixel-to-meter conversion applied, produced a derivative spike in the angular velocity calculation that dwarfed the actual motion. The faster the capture rate, the more sensitive the derivative is to noise.
The fix: a Savitzky-Golay filter (window size 9, polynomial order 2) applied to the keypoint trajectories before any kinematic calculation. The filter smooths the high-frequency noise floor while preserving the genuine peaks of the smash motion. Post-filter velocity numbers came down to the realistic 1500–2200°/s range that matches the literature.
The lesson worth surfacing on the resume: high-frame-rate biomechanics is fundamentally a signal-processing problem, not a computer-vision problem. Detection works fine; differentiation breaks. Anyone shipping pose-based kinematics without a signal smoothing pass has the same 14,000°/s waiting for them.
EliteStandards dictionary (Jump Height > 0.5m, Knee Flexion 40-90°, etc.) is derived from published professional badminton biomechanics studies. Hardcoded is appropriate because the underlying physics doesn't change — an elite player's jump height isn't going to be different next season. If sports science updates the standards, we update the dictionary in one place. Learning the standards from data would have required a labelled corpus of elite-vs-amateur smashes we don't have.
PIXELS_PER_METER constant is derived from the net pole height being in frame. Recordings without a clearly visible reference can't be calibrated, which means absolute metrics (jump height in meters, smash speed in km/h) can't be computed — only relative ones.