Minimal Coding Standards

In addition to the basic coding fields of pitch map, beehive, runs, and wagon wheel, there are some delivery events of particular importance to ensure accurate and consistent tagging.

Basic coding requirements:

Pitch Map                                                                                                                             

Where did the ball land on the pitch?                                                              

Beehive

Where did the ball arrive at the batter?

 Runs                                                                                                                      

 How many runs were awarded to the batting team?

Wagon Wheel

Where did the ball end up on the field? *Only required if runs were selected*

Event Specific Tags

Bowler/Batter events:

There are multiple event descriptors that are very common and must be tagged if observed. These selections can be found on the left panel of the coding window when selecting the runs outcome.

Minimum requirement events are:

• Play and Miss
• Contact Errors (edges, hit on pads)
• Batter movement
• Bowler variation
• Appeal
• Shot descriptions (reverse, paddle, sweep, switch, and ramp)
• Opportunity

Note: Refer to ‘Coding Standards’ to understand the descriptors and use cases for each event.

Keeper events:

If ‘To Keeper’ is selected rather than runs, a keeper events panel will appear.

• Drop: A fumble that was not recovered but would not have been a dismissal if taken cleanly.  Note: Dropped catches that would have been a dismissal should be coded as 0 runs (with a contact error and opportunity) and then a dropped catch within the wider fielding screen.
• Missed stumping: Likely coded in addition to a drop/fumble and batter movement.
• Fumble: A small juggle of the ball but able to regain control.
• Dive stop: Any time a keeper dives to one side to stop the ball.
• Leg side: automatically tagged if ‘WK (leg)’ is selected in the runs screen. If the keeper took the ball leg side and it is not already tagged, review your beehive selection to ensure its accuracy.

Multiple of these keeping events may be true in a single delivery so it is important to watch the delivery until the ball is dead.

Overthrows:

Overthrows count as a run but are recorded separately. If the striker ran a single before a fielding error allowed time for a second, 1 overthrow should be selected, in addition to the 1 in the general runs table (it is not simply 2 runs off the bat). Ensure a fielder is associated with the run cost.

Fielding events:

There are multiple fielding events that are very common and must be tagged if observed. These selections can be found on the left panel next to the wagon wheel.

Minimum requirement events are:

• Dive stops
• Catches taken / dropped
• Runouts made / missed
• Fumbles / misfields
• Runs saved / cost

Note: Refer to ‘Fielding Event Standards’ to understand the descriptors and use cases for each event.

Note: Some fielding events can take time to accurately record. In these cases, it is ok to leave them until there is time to enter all data (e.g: an over or innings break).

Additional Options:

Speed:

If a speed gun is available and can be recorded live manually, ‘Record ball speed’ should be selected.

This is an additional but useful tool to the regular match day coding requirements.

Selecting ‘record before events’ will result in the selection screen appearing after selecting the beehive X/Y coordinates to ensure the speed is capture before disappearing from the LED screen.

Athletes AI:

If the facilities and coder have the ability to set up for Athletes AI to run, this is a beneficial tool to ensure improved X/Y accuracy.

If being run live, select ‘View’ and ‘Athletes AI’ in the coding screen to begin reading in the ball tracked data. Data may be imported slightly behind live so leaving the coding screen up for a few minutes post the end of an innings ensures that all deliveries are successfully imported. 

Note: If the data is unable to be imported, check your match shell to confirm that Athletes AI ‘Write requests’ and ‘Read’ are ticked and that the correct match ID has been entered into Athletes AI.

CrickViz, Hawkeye, and Virtual Eye:

Select ‘View’ and ‘Incoming Data Feeds’ to import Hawkeye, VirtualEye, Collaborative Coding, CrickViz, and Opta data.

To select your desired feeds, select ‘Manage Feeds’, tick the required boxes and select ‘OK’ and ‘Enabled’. You will see the files being read in as they become available.

To import post-match:

Exit the coding screen and select ‘Reference’ and the available data ready for import.

Fill in the descriptors at the top to filter the available matches and select ‘Apply’. Select the desired match and ‘Identify’, ‘Overlay’, and ‘Upload’ to be read into the associated deliveries.