How nvsclub/knnpitchcontrol works
This repository is a notebook-led soccer tracking and pitch-control analysis project. Its apparent workflow is to combine tracking datasets, run pitch-control models across matches, visualize results, and compare model runtimes or core usage. The library implements KNN, Spearman, and Fernandez pitch-control approaches, plus pitch drawing. The notebook names and files indicate these capabilities, but no README or notebook contents were provided, so notebook-to-notebook and notebook-to-library connections are shown as unverified rather than asserted.
Main entry points: pitch_control.py Pitch-control models · 103 Running all datasets.ipynb Run datasets · 101 Merging Datasets.ipynb Merge datasets · 102 Running all models.ipynb Run models
Components 10
Notebook analysis
- Merge datasets
101 Merging Datasets.ipynb - Run models
102 Running all models.ipynb - Run datasets
103 Running all datasets.ipynb - Generate visualizations
104 Generate Viz.ipynb - Compare runtimes
105 Times.ipynb - Compare core usage
106 No-cores vs cores.ipynb
Pitch-control library
- Pitch-control models
lib/pitch_control.py - Pitch drawing
lib/draw.py
Tracking data
Other components
- Analyst
Connections 14
- Analyst → Merge datasets: runs
- Analyst → Run models: runs
- Analyst → Run datasets: runs
- Analyst → Generate visualizations: runs
- Analyst → Compare runtimes: runs
- Analyst → Compare core usage: runs
- Merge datasets → Match tracking datasets: uses data
- Run models → Pitch-control models: runs models
- Run datasets → Match tracking datasets: uses data
- Run datasets → Pitch-control models: runs models
- Generate visualizations → Pitch-control models: visualizes results
- Compare runtimes → Pitch-control models: times models
- Compare core usage → Pitch-control models: compares execution
- Pitch-control models → Pitch drawing: imports
lib/pitch_control.py