FAQ
Straight answers.
We already track reps on a whiteboard. Why change?+
A whiteboard records what a player reports. NineReps records what the sensor detects. The difference is objectivity and history — you can't trend a whiteboard across a season.
Will players game the system?+
The sensor counts what physically passes through the machine, and an operator is present for every session. Gaming it requires actually catching more balls.
How accurate is the sensor?+
It polls at 240 Hz with a 50 ms debounce and an 80 ms refractory period. In testing it has not missed a throw or double-counted one.
What if the Wi-Fi goes down?+
The Raspberry Pi stores all data locally and syncs when connectivity returns. No session is lost.
Does it predict game performance?+
No — it shows correlation, not prediction. A signal-strength (R²) figure tells you how strong the practice-to-game relationship has been for each player. Some correlate strongly, some don't, and that itself is useful information.
Do coaches have to learn a new system?+
The operator selects a player and presses start. Coaches open a browser and read the dashboard. Analysts adjust thresholds. There's no new skill to learn.
What hardware is involved?+
A Raspberry Pi and a break-beam sensor, mounted on the JUGS machine. We provision the kit; it's sold, not leased, so your program keeps it.
Who owns the data?+
Your program does. We license you the software; you keep the data, it's isolated from other programs, and a standard export goes with you if you leave.
Can we host it ourselves?+
Yes. Cloud is the default, but for programs whose policy requires data to stay in-house, NineReps runs entirely on your own infrastructure, behind your firewall.
Does it require NCAA or conference data feeds?+
No. The analytics run on the reps your sensors capture and publicly licensed statistics. Nothing about NineReps depends on restricted league data.
See it on your machine.
A short walkthrough on a real session — leaderboard, dashboard, and the data behind both.