.png)
Using DataVolley Pro at the 2015 Sainsbury’s School Games
Introduction
DataVolley is the industry-standard performance analysis software for volleyball. I first heard of DataVolley back in 2011 when I saw a member of the opposite team using a computer to collect data (I have since learnt the Scout Man was actually Matt Bianco, former GB Women Volleyball Scout). I first got the chance to use DataVolley during the 2012 Sainsbury’s School Games (SSG). It was only the media version with limited functions but it was cool nevertheless to use another software system. Since DataVolley was expensive to licence, I never went back to it. I also had StatEasy, which was free and it did the main job I was looking for – it linked stats to video.
I have been thinking lately about the limitations of StatEasy, specifically the ability to display spatial data of attack directions. Then an opportunity came up for the 2015 SSG. If I live stat at the 2015 SSG, I could use DataVolley Pro (the full version) at the event and more importantly, I would be lent a licence key of both DataVolley and DataVideo owned by Volleyball England (VE) afterwards. The DataVideo is important because it links the stats to the video. This arrangement would resolve my need for higher level analyses. But before I go on, what did I learn at the 2015 SSG?
What Did I (Re)Learn at the 2015 SSG?
It did not take long to re-remember how to code in DataVolley. Although I completely forgotten how to input codes in DataVolley, it only took me a full match to be comfortable coding the basic stats (rating server/ receiver, who attacked, point ending action) without the help of a caller.
Coding is made easier if you know the players. I had to re-remember this when I shifted side to side to see who passed the ball. By the time I see the shirt number and coded it, I missed two attacks that has already happened. Clearly, this is not ideal if you are to make real decisions in real time based on incomplete data.
How to code attack directions. I was quickly pushed on to code attack directions since I was proficient at coding basic stats. This was really what I wanted to learn since DataVolley is able to show attack directions much better graphically then what I can do in StatEasy. The code is [home or away][player number][V][number of origin attack][number of destination attack]. For example, is the away team’s (player number six ( hit on the left side () straight down the line to zone 1 ().
Using the number pad to quicken live coding. For the basic stats, I could get away with using the number keys on the top. However, with more detailed stats, more numbers were needed to be coded and it was inefficient in crossing your hands to use the numbers on the top. So I was told to use the number pad so you are able to code more numbers efficiently. I practiced for the rest of day 1 and I found it was extremely difficult to get use to. It was like I had to learn to touch type all over again! Luckily on day 2, I was more used to it but it was still something to do get use to.
I later learnt that the Japanese statistician actually uses the number keys on the top because some people are able to touch type using numbers on the top too. So this is something to think about whether to keep going with the number pad or learn to touch type using the numbers on the top.
Starting finger stance. The next step was the starting finger stance. The four fingers on the left hand should be on the “shift”, “a”, “s” and “v” keys. Three fingers on the right hand should be on the “4”, “5”, and “6” keys. The thumb could be on the “0” key too. This was so most of the keys used were on those fingers.
Bumps on the “5”, “F” and “J” keys. I had issues when moving the right hand off the number pad to press the “-” or “#” key to indicate negative or positive reception back to the number pad. I was told that there is a little bump on the “5” key to help relocate your hand without looking at the keyboard. It was the same with little bumps on the “F” and “J” keys. And this should be on every keyboard. This was mind blowing to me as I have never noticed it before. I looked at all the laptop keyboards and it was there.
Remapping the key codes. I continued to have a huge problem with the “-” and “#” key because I have to physically look down for it. This mainly arises when I have to rate the reception and when I look down, I may have missed out who hit what to where (especially if they hit middle and it gets blocked) and then I am already behind in the coding! I was told the “z” and “x” key are free so that may be okay since it is within reach of the left hand. Or I may remap most of the keys so the most common keys are on the “A”, “S”, “D”, and “F” keys with the less commonly used keys above or below it.
The need for a delay feed. I normally have a delayed feed for live statting at Polonia. This makes things extremely useful when seeing things that I missed out, e.g. who hit the ball, who got the block kill etc. I did not bring my webcam at the SSG and I wish I did because I would have benefited so much from it and it would have been more realistic to how I would code normally.
Licence Key
I did receive the licence key at the London Legacy Volleyball Cup a week after the SSG. I really can’t wait to see what it can do and you can expect another blog post relating to my initial experience of using it.
Comments