Match Day - Top 8

The purpose of this article is to provide greater context around the critical match components needed for match day processes & workflows for analysts within the Australian Cricket model.

This should expand on article Role of the Coder & Role of the Reviewer

1. Update your Analyzer and Receiver - 

Ensure that you have updated to the most recent version of Analyser applications to the latest versions. When opening Analyser it may prompt you to update, otherwise you can check by clicking Reference > Options > "Check Now". Alternatively updates for Analyser can also be found of the Fairplay Website.

 Check now option to search for most recent version of analyzer

2. Matchday & 3rd Party WhatsApp Channels

2a. Matchday WhatsApp Groups - Match Ops WhatsApp groups are created by states and provide critical information around team sheets, toss results & delays in play. If you are not on a relevant state WhatsApp and need to be reach out to the Home team match operation team or a member of the CA Performance Data & Tech team.

2b. Cricket 21/Coding Hub What’s App group - Coding channels on WhatsApp have been created to ensure that all coding requirements can be funneled into one channel to ensure transparent communication.

There should be WhatsApp for different domestic competitions, as well as International Mens & Womens (+A tours).

As the home team analyst you are responsible for the matchday coding. It is recommended that you confirm coder at least 4 hours prior to the match. Please consider that in the case of C21 time zones are up to 8 hours difference and therefore reaching out the day prior would be recommended

What’s App message to confirm Cricket 21 Coder Details

3. Pre Match Shell Setup

3a - Importing from the Cloud into Analyzer. Confirm that the match details are accurate, since the match shell was previously set up by Cricket Australia’s Performance Data and Tech Team. Note the official’s section should also be complete in the match txt file.

Import the Match Txt File from the cloud workflow

3b, Add the players to the match txt file in Analyzer ensuring that the players numbers are up to date and that their playing status is ‘P’ for playing. If Opposition players are unknown, add them when the team sheets are received on match day.

Adding players to the match txt file and checking the playing status is ‘P’

3c. After the toss, enter Toss Details and indicate which teams are batting first and second in the Analyzer's Match Tab.

Complete the Toss details in Analzyer – Match Tab

4. Video Sources

4a. Ensure that your video source is set up and turned on as per your venue’s or coding requirements.  i.e. Frog Box, Bar TV connections, IP Cameras, Fulcrum etc.

Test your video source using Analyzer>Reference>Video Capture>Pipeline (Media Foundation)>Video Source Dropdown (Select video converter/source)>Press OK.  If the video source is not functioning properly, conduct a thorough troubleshooting process of elimination. It is advisable to test your video source well in advance of the initial match delivery to ensure sufficient time for resolving any potential issues.

Video source test

4b. Streaming Links - In the case of particularly remote coding streaming links will be required. For this you will need access to Cricket Australia’s digital platform communication channel ‘Slack,’ -This is the broadcast source that External coders will use to code from. If you do not have access to this, please reach out the CA Performance data & technology team members.

Once you have access it should be a simple as copying the m3u8 video links and providing them to coders via the What’s App group.  Alternatively, you can utilize this footage in VLC if needed.

CA’s communication channel Slack – m3u8 video links

5. Pre/In Game Process & Workflows - Striker/Umpire Ends & Outgoing Feeds

5a. Match Information - Once the coder has received/setup match, they will require further information prior to match commencement to ensure that data is as accurate as possible.

Pitch No & Boundary Dimensions - Match ops / curators should be able to provide the pitch number (left to right) and boundary dimensions applicable to the match being played.

Striker End (nth/south) - Allows data to be collected on end

Umpire Ends - Indicate which umpire is at the bowlers end & therefore we tracked through the match

5b. Outgoing Feeds / Receiver - Once all match setup has been complete the coder will be setup on the coding screen & can ensure that outgoing feeds can be setup for analysts, coaches & match referees. This can be done through View > Outgoing Data Feed for coders

To check this on the downstream end (Analysts/Coaches/Match Refs) - Users will need to open an additional software called "Receiver".

Receiver will have a similar setup, but instead of an Outgoing it will be an Incoming Data Feed that will require you to connect, whilst selecting the correct match feed.

6. In Game - Coding Remediation 

6a. Track Coding accuracy during the match to prevent post-match corrections. If you notice any inaccuracies, promptly notify Cricket 21 via the What’s App group. 

7. Complete Post-Match Checks:

7a - Most update version of match -

• Import Coders final match txt file whether it is from the cloud or posted to the What’s App group that includes any last-minute editing from Cricket 21.  
• Close the Receiver Application.

7b - Coding/Player Status

Ensure that the Player listed under each team have the correct playing status applied – right click on the status cell to make any change.

7c - Complete Health Check

Review the Health Check Report in Matches>Health Check Coding and clear or suppress (right click on row) any entries listed.

7d. House Keeping & Match Shell Hyenine 

• Check the Scorecard (Reporting>Match>Scorecard) against a reputable cricket website and correct any discrepancies in scores, player statistics, or match details as needed.  
• In the Option Tab, click on the ‘Update Deliveries’ buttons to correctly aligned the match deliveries to the Power Play/s structure.
• Complete the Pitch Number + Block and Venue Dimensions in the Options Tab.
• Check the Result Tab information is correct for each innings of the match and make any necessary corrections as required. Cricket 21 will complete this section as part of their post-match workflow.
• Update any External Ids (where available) in the External Ids Tab by running ball tracking overlays in Analyzer, Opta overlay and CricInfo Ids found in the URL address. It is advisable to run the overlays, as details from third-party providers may be updated after a match.

8. Final Export & Transfer of Video/Data

• Once the Above has been complete change the coding status to 'Final'
• Run the missing clips utility in Match or in References>Utilities to flag any missing video clips in the match txt file.
• When you are satisfied that all details are true and correct, export the match txt file to the cloud through the Match>Export Data>To cloud
• Finally you may need to transfer vision to the blob storage container as it may have changed,