Minimal Coding Standards

A step-by-step guide to the Australian Cricket coding process, so every match is coded consistently and to the required standard.

In this article

Basic coding requirements
Bowler and batter events
Keeper events
Overthrows
Fielding events
Additional options
Where to go next

Basic coding requirements

Code these for every delivery.

Pitch map coding screen — **Pitch map:** where did the ball land on the pitch?

Beehive coding screen — **Beehive:** where did the ball arrive at the batter?

Runs coding screen — **Runs:** how many runs were awarded to the batting team?

Wagon wheel coding screen — **Wagon wheel:** where did the ball end up on the field? Only needed if runs were scored.

Bowler and batter events

These events are common and must be tagged whenever you see them. You'll find them in the left panel of the coding window when you select the runs outcome.

The minimum events to tag are:

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

See Coding Standards for what each event means and when to use it.

Keeper events

If you select To Keeper instead of runs, the keeper events panel appears.

Event	When to tag it
Drop	A fumble the keeper didn't recover, where taking it cleanly wouldn't have been a dismissal.
Missed stumping	Usually coded along with a drop or fumble, and batter movement.
Fumble	A small juggle where the keeper regains control of the ball.
Dive stop	The keeper dives to one side to stop the ball.
Leg side	Tagged automatically when you select WK (leg) in the runs screen. If the keeper took the ball down the leg side and it isn't tagged, check your beehive is accurate.

Dropped catches: if taking the ball would have been a dismissal, don't code a drop here. Code the delivery as 0 runs with a contact error and an opportunity, then record the dropped catch in the fielding screen.

More than one keeper event can happen on a single delivery, so watch until the ball is dead.

Overthrows

Overthrows count as runs but are recorded separately. If the batters ran a single and a fielding error then allowed a second run, select 1 in the runs table and 1 overthrow. It isn't 2 runs off the bat. Make sure the runs cost is assigned to a fielder.

Fielding events

These events are common and must be tagged whenever you see them. You'll find them in the left panel next to the wagon wheel.

The minimum events to tag are:

Dive stops
Catches taken or dropped
Run-outs made or missed
Fumbles and misfields
Runs saved or cost

See Fielding Event Standards for what each event means and when to use it.

Some fielding events take time to record accurately. It's fine to leave them until you have time to enter everything, such as at the end of an over or at the innings break.

Additional options

These aren't required on match day, but they make the data more accurate when you can use them.

Ball speed

If a speed gun is available and you can record speeds live, select Record ball speed.

Also select Record before events. The speed screen then appears straight after you place the beehive, so you can capture the speed before it disappears from the stadium screen.

Record ball speed and Record before events settings — Record ball speed settings

AthleteAI

If the venue and coder are set up to run AthleteAI, use it: it improves the accuracy of the X/Y placements.

In the coding screen, select View > Athletes AI to start reading in the ball-tracking data.
Data can arrive slightly behind live play. Leave the coding screen open for a few minutes after the end of each innings so every delivery is imported.

Data not importing? In your match shell, check that Athletes AI Write requests and Read are ticked, and that the correct match ID has been entered in AthleteAI.

View menu with Athletes AI — View > Athletes AI

Incoming data feeds (live)

You can import Hawk-Eye, Virtual Eye, Collaborative Coding, CricViz and Opta data while the match is in progress.

In the coding screen, select View > Incoming Data Feeds.
Select Manage Feeds, tick the feeds you want and select OK.
Select Enabled. The files are read in as they become available.

Incoming Data Feeds window — Incoming Data Feeds

Importing data feeds after the match

Exit the coding screen and select Reference, then the data that's ready to import.
Fill in the descriptors at the top to filter the available matches, and select Apply.
Select the match, then Identify, Overlay and Upload. The data is read into the matching deliveries.

Reference screen with data ready to import — Reference: data ready to import

Filtering matches and the Identify, Overlay and Upload buttons — Filter, then Identify, Overlay and Upload

Where to go next

Coding Standards: what each event means and when to use it.
Match Day Top 8: the key things to get right on match day.
Incoming and Outgoing Feeds: setting up the data feeds into and out of Analyzer.