This spreadsheet shows the setter distribution depending on the setter’s location while he/she was setting the ball. You can also see the effect of the attack from these balls. Moreover, court graphics illustrate the reception locations and attack directions.
This spreadsheet can be filtered by:
setter,
setter call,
rotation,
opponent rotation,
point range,
point difference,
player order,
phase (reception quality and transition decision),
setter location,
side-out,
reception zone,
serve type.
How to use it?
Legend:
green - in this rally, the ball was set to zone 4
yellow - this rally, the ball was set to the middle
red - (if the backrow color filter is NO) - in this rally, the ball was set to zone 2 or zone 9
blue - in this rally, the ball was to pipe
black - (if the backrow color filter is YES) - in this rally, the ball was backrow attack
pink - in this rally was the setter dump
cross - this rally ended with kill attack
circle - in this rally the ball in play after the attack
diamond - this rally ended with attack error or blocked attack
Below the court, you can see the number of attempts, setter distribution percentages, %kills, and attack efficiency from a particular zone, setter dump, and total attack numbers.
In this example, most balls were set to zone 4 and the least to zone 6. The highest percentage of kills and attack efficiency were from pipe, and the lowest attack efficiency was from the right side of the court.
Below the reception court, you find the passing numbers depending on the reception zone. The bold black number (Ex: 23) shows the number of receptions in this zone, and the percentage under it gives the %SO (Ex: 74%). The bold percentage shows the %FBSO (Ex: 65%), and the percentage under it is %ESO (74%).
The last court in the row shows the attack directions, “SPIKE DIRECTIONS”. Above the court and next to “SPIKE DIRECTIONS”, you can choose the visualization form from a dropdown selection. It could be visualized with the arrows or the heatmap.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article