.png)
When Is A Point Scored Not A Point Scored?
Introduction
We always want the performance statistics to reflect what it purports to measure. This is so the coach can make informed decisions to enhance performance. Points Scored is the sum of attack kills, service aces and block kills. So when looking at “points scored” stats, those points should be earned via good actions of the player and/or team. Point scored shouldn’t include points won through poor opposition actions. This is because it is not a good measure of how efficient a player is at point scoring. However, there are some situations where points are scored but are not earned.
Opposition Block Error = Automatic Attack Kill
When a player commits a block error, e.g. net touch or centre line fault, the spiker automatically gets awarded an attack kill. The philosophy behind this, according to the NCAA Volleyball Statisticians’ Manual, is the blocker committed the blocking error as a result of the attack attempt. However, a blocking error is an unforced error so this cannot lead to an earned point. I have statted situations where an attacker spikes the ball out of bounds but a block error was called. So the same action is either an attack error or an attack kill dependent on whether the blocker committed an error. In any case, the attacker certainly did not earn the point.
Because of this, I changed the way I stat these situations. If there is a block error, I would only stat a kill if spike would have resulted in a kill regardless if a block error is called. If it would not have resulted in a kill, I would stat an attack attempt for the spiker only, alongside a block error for the blocker. So if the attack resulted in a block out or missed dig then I would stat a kill for the attacker. For every other situation, an attack attempt is only charged alongside the block error.
Opposition Reception Error = Automatic Service Ace
If there is a service ace, an opposition reception error is also charged. When you check the match stats, aces and opposition reception errors has to be equal. I do agree with this for the most part (Mark Lebedew makes the case that reception errors are forced errors so therefore not a point lost). However, there are two situations when a reception error is called but the server did not earn the point. The first is when a positional error is called, e.g. the setter moved too early, and the second is when a rotational error is called, e.g. the setter is in zone 3 but should be in zone 2. In both cases, the error was an unforced error so it shouldn’t lead to an earned point. I have statted situations when a player served out of bounds or into the net but is still awarded an ace.
Because of this, I changed the way I stat these situations. If there is a reception error due to a positioning or rotational error, I would only stat an ace if the server would have got the ace even if the reception error was not called. In every other situation, just a service attempt is charged.
Conclusion
The situations above doesn’t happen often and will probably not affect the overall stats too much if you stat it the old way. However, I believe better data will lead to better decisions and if this leads to a 0.01% better chance at success then I will take it.
Comments