The Decision Review System (DRS) is a technology-based process to assist on-field match officials with their decision-making. Team captains may request that the third umpire consider a decision of the on-field umpires also known as Team review. Each team is limited to 2 unsuccessful reviews per innings.
The data has been collected from ESPNCricinfo - Match Flow section. Here is an example of Match 31: Kolkata Knight Riders vs Rajasthan Royals
- Ask an interesting question. (i) What is the goal? (ii) What would you do if you had all the data? (iii) What do you want to predict or estimate?
- Get the data. (i) How were the data sampled? (ii) Which data are relevant? (iii) Are there any privacy issues?
- Explore the data. (i) Plot the data (ii) Are there anomalies (iii) Are there patterns?
- Model the data. (i) Build a model. (ii) Fit the model. (iii) Validate the model.
- Communicate and visualize the results. (i) What did we learn? (ii) Do the results make sense? (iii) Can we tell a story?
- Python
- Pandas
- Seaborn
- Matplotlib
- BeautifulSoup4 (for data extraction)
- Day 1: Total number of reviews taken in each innings.
- Day 2: Total number of reviews taken in each over.
- Day 3: Total number of reviews taken per type.
- Day 4: Total number of reviews taken by batting or fielding sides.
- Day 5: Total number of reviews taken per umpire.
- Day 6: Total number of reviews taken in each match.
- Day 7: Total number of reviews taken per team and Number of successful/unsuccessful reviews by each team.
- How has the trend of review taking changed over the course of the season?
- Running average number of reviews over the course of the season?