shot editing v.next

Latest iteration of shot editing.

Data quality has come a long way, but it’s not reflected in the app. The JSON schema now has a reliable way of distinguishing a knockback from a serve. A one-shot rally with the winner flag unset indicates a knockback. It allows them to be easily filtered from the results.

Furthermore, any rally without the winner flag set is suspicious. In my testing, about 50% of these rallies should be excluded (interrupted by a ball-on, for example), and there may be around 2 per game.

There are occasional misattributions, concentrated in stack unwinds. Ball tracking errors are almost exclusively on outdoor recordings, but many of these are also caught in that same suspicious rally filter.

If these filters are reliable and already in the data, they should be exposed in the app. Filter out the knockbacks and don’t include them in the stats. For suspicious rallies, simply throw up a pop-up the first time it’s viewed: “This rally looks suspicious. Should we include it in your stats?” Simple yes/no. No fancy shot editing.