Whether you are setting up a match or downloading it from the cloud, it is important to understand relevant match details ensuring that they are completed to the required standard.
Match Setup
This will be the default screen when you create new or select a match. In the case of domestic matches - the majority of the information should be prefilled by selected Cricket Australia Representative. Most information is straight forward but helps align match to relevant filtering options.
Toss won by & Match Innings are essential fields to be filled before the start of play - ensure that correct details have been filled, required overlays have been indicated Coder/Reviewers are correct before proceeding. Coding Status should also be changed once beginning to code.
Lineups
Team Lineups will typically require coders/reviewers to select individuals involved in the match there are a number of fields that will need to be checked.
Selected Players - Players can be added or removed from selected team by double clicking. dropdown list allows you to streamline finding players - "All teams" and using search field can also help speed up navigating process.
Batting Hand - Batting hand can be updated with right click
Bowling Hand/Style - Can be adjusted with right click
Wicket Keeper/Captain - It is becoming more common that players bounce between more teams - ensure that only 1 keeper and captain have been selected.
Status - Indicated the role of player in the match, below are the options
Playing - Named as a player in the starting 11
12th - Named as 12th man and involved in match accordingly.
Substitute - Been involved in match as a substitute player
Concussion - Involved in match via concussion incident to another player
X-Factor - Substitute player used in relevant t20 leagues to impact match
Coach - Dropdown to indicate who the coach is. Yellow box allows you to create new coach if needed.
Option/Toggles
Within the select match setup, the option tabs provide a number of toggle options that enables the coder to customize their setup - below are some considerations for these.
Beehive Style - Allows coder to adjust beehive to a perspective (adjusting for players height) or flat style (fixed height).
Viewing from - Depending on the camera angle setup, coder will be viewing match from either behind bowlers' arm or alternating this enables coder to adjust their code window accordingly.
Sort Players - Allows individuals to have players sort by name or jumper. If coder isn't familar with players, it makes sense for the toggle to turned to jumper
Broadcast - To ensure vision is appropriately connected to wider system, coder/reviewer should confirm that "broadcast to Stats Server" is ticked.
AthleteAI - Read and Write Reponses to assist with automated ball tracking by 3rd Party AthleteAI
Pitch Layout - Data entry for pitch and venue dimensions to allow longitudinal insights to be drawn.
Powerplays
Limited over matches are played with restrictions on the number of fielders who are allowed to field outside the 30-yard cricle, these are known as powerplays.
When setting up a match it is important to cross-check the details of the powerplay and ensure they align with relevant playing condition documents.
BBL
WBBL
The details of each powerplay - the powerplay number, the starting and ending over numbers
during which they apply and the maximum permitted number of outfielders - are set up for each
innings, and the powerplay number and the maximum number of outfielders are then recorded on
each delivery automatically during the coding process.
This can also be adjusted in match in the coding screen or audit trail or post-match within match details, for my detailed functionality of Powerplays click here.
Session Details
All matches will require the coder to fill out the above visual at the beginning of sessions some of which provides valuable information for insights.
Day & Session - Indicates day and session of match, valuable for particular multi day matches.
Recording Conditions - Become an optional field for 2024/25 domestic season, allows coder to capture environmental conditions at venue
Bowling & Umpire Ends - The addition of Hawkeye data live at BBL & International matches, getting bowling end correct has provided valuable insights. The reviewer should provide communication to coder prior to first delivery being bowled.
Capture Details - Number of optional toggles for data capture. Ball speed and revolutions are dependent on having the right technology available for the coder.. Recording Stroke/Intent + Ball movement and X/Y data are dependent on the competency of the coder. available technology or 3rd partner data provides like AthleteAI, Hawkeye or Opta can overlay data in respective areas.
Results
Results tab has two main functions
1. Inning Closures - Collecting on metadata of inning status
1a. Declared - Strategic move in cricket where the batting team's captain voluntarily ends the innings before all wickets are lost, often to achieve a specific tactical goal
1b. All Out - End of a team's innings due to the loss of all ten wickets
1c. Unfinished - Occurs when a team does not complete its innings due to the conclusion of the match (whether due to time, weather, or other factors). The implications depend on the format of the game and the match situation.
1d. Compulsory Closure - Compulsory closure comes into play when certain conditions force an innings to end automatically, regardless of whether the team has been bowled out - This is usually due to a schedule end of play or over limit being reached.
1e. Not Started - Inning did not commence
2. Result
1st Inning Result - Should provide status of match from home team perspective.
Match Result - Depending on format should be limited to a few options from Win/Loss perspective.
0 comments
Please sign in to leave a comment.