01
Point ledger
All downstream work is point-addressable and reviewable in the portal.
Full-match videoPoint windows + score stateOperationalBroadcast tennis computer vision
Video → point ledger → event anchors → rally geometry.
The current system segments matches, tracks score, follows the ball in image space, and localizes racket hits, bounces, and net interactions. The immediate work is making those 2D anchors exact enough to support 3D reconstruction.
Inspect real outputsCurrent gate: contact-level human audit
Execution graph
2026-07-24Full matchvideo + audio
→Point ledgerwindows + score
→2D trackframe observations
→Anchorshit · bounce · net
→3D rallyball + players
Every stage emits confidence.Every uncertain case reaches the portal.
System state
What is built, and what each stage hands forward.
The pipeline is the research object. Intermediate visualizations are part of the contract, not presentation added after the fact.
StageInputOutputState
02
2D ball track
The decoded track is treated as the measurement substrate, not something physics may overwrite.
Native-frame cropsDense image-space trajectoryOperational03
Event anchors
Each event carries frame, image position, confidence, witnesses, and an abstain path.
Track discontinuities + players + audioHit / bounce / net / artifactActive audit04
3D reconstruction
Existing physics and factor-graph prototypes are retained as tools, not promoted as the current system.
2D rays + court planes + player poseConnected rally geometryNextCurrent evidence
Scrub the measurements, not a polished reconstruction.
This replay uses the exact decoded coordinates and current event outputs from pt0143. The public site omits copyrighted broadcast pixels; the private audit portal places these same overlays on the source frames.
f194Fresh audit excerpt
Sub-frame predictions beside reviewer-selected frames.
Round three exposed one between-point false proposal, two one-frame placement gaps, and an occluded contact. The current revision addresses all four mechanisms.
| Point | Predicted frame | Type | Confidence | Primary witness | Human frame |
|---|---|---|---|---|---|
| pt0117 | 756.50 | racket_hit | 0.80 | horizontal reversal | 756 |
| pt0117 | 815.10 | bounce | 0.80 | ground vertical reversal | 815 |
| pt0143 | 201.68 | racket_hit | 0.80 | trajectory reversal | 202 |
| pt0143 | 457.50 | bounce | 0.80 | ground vertical reversal | 457 |
| pt0143 | 497.56 | racket_hit | 0.85 | wrist reach + occluded redirect | 498 |
Scope noteThese are reviewed development examples, not a broad generalization result. The next evaluation expands points, players, courts, and broadcast conditions only after the anchor flow is stable.
Website-first method
The review interface is part of the detector.
01
Propose
The pipeline emits a typed event, sub-frame timing, location, confidence, and witnesses.
02
Inspect
The reviewer scrubs the original point with track history and competing overlays visible.
03
Resolve
Confirm, adjust, reject, or add a replacement event. Every action is locally recoverable.
04
Regress
The exported labels become a frozen test and the same page is regenerated after each revision.