Blocking reports

Disclaimer:
Use at your own risk. While every effort has been made to make the reports accurate, no warranty is given.

The results will be logged to help improve the app. Your DataVolley file (if uploaded) will not be kept.

Blocking report

The blocking analysis follows a number of steps:

The position of each player when they are in the front row is established according to their role. It is assumed that outside hitters block in position 4, middles in 3, and opposites/setters in 2. The exception to this is when the blocking team is receiving with the setter in position 1, in which case the opposite blocks in 4 and the outside in 2.

The blockers that are expected to participate in the block on a given attack is calculated based on the scouted attack combination code and start_zone of the attack. For example, for a high attack from position 4 (attack combination code V5) the middle and position-2 blockers would always be expected to block, and the position-4 blocker would be expected to join (to make a triple block) about half the time. For a faster-tempo outside attack (attack combination code X5) only the middle and position-2 blockers would be expected to block.

The accuracy of the blocking report for your particular data file will depend on how closely the blocking patterns of your team follow these patterns. Also note that only "standard" attack combinations (the DataVolley defaults) are generally recognized. Unknown codes will be flagged during the reporting.

Customized reporting

Variations to these assumptions are possible if your team does not follow the above patterns. For example, the position of each blocker can be inferred from the data, rather than assuming the blocking positions described above. For this or other functionality (e.g. recognizing your custom attack combination codes, or bulk processing of multiple files), contact
.