You are on page 1of 17

DECISION REVIEW SYSTEM

Submitted in partial fulfillment of the requirements


of the degree
BACHELOR OF ENGINEERING IN
COMPUTER ENGINEERING

By
Alkaif Mukri (201041057)-
Aabhushan Chavan (201041020)-
Anuj Gawade (201041030)-
Sandip Narbat(201041026)-
Supervisor
Prof. Sandhya Awate

Department of Computer Engineering

A. C. Patil College of Engineering, Kharghar


University of Mumbai
(AY 2020-21)
CERTIFICATE
This is to certify that the Mini Project entitled “Decision Review
System” is a bonafide work of Alkaif Mukri(37), Sandip Narbat(40),
Anuj Gawade(13), Aabhushan Chavan(8) submitted to the University
of Mumbai in partial fulfillment of the requirement for the award of
the degree of “Bachelor of Engineering” in “Computer
Engineering” .

(Prof. Sandhya Awate)


Supervisor

(Prof. Manoj Deshpande) (Dr. V. N. Pawar)


Head of Department Principal
Mini Project Approval

This Mini Project entitled “Decision Review System” by Alkaif


Mukri(37), Sandip Narbat(40), Anuj Gawade(13), Aabhushan
Chavan(8) is approved for the degree of Bachelor of Engineering in
Computer Engineering

Examiners
1……………………………
(Internal Examiner Name & Sign)

2……………………………
(External Examiner name &
Sign)

Date:

Place:
Abstract
Umpire Decision Review System is basically the reviewing
of the series of events that happen during a match that the
umpire himself cannot foresee correctly and accurately so if
any rash decisions are to be made the on-field umpire can
ask to look at the recorded footage of the event and can
make pinpoint accurate decisions that goes with the spirit of
playing sports. The second option is an opportunity granted
to each of the teams for reviewing the decision on the on
field umpire if they are unsatisfied with the same and want
to check for themselves
List of Figures
Fig 3.2 Framework of 11
Fig 3.3 Process Design of 12
Fig 3.5.1 14
Fig 3.5.2 14
Fig 3.5.3 15
Fig 3.5.4 15
Contents
1 Introduction
1.1 Introduction
1.2 Motivation
1.3 Problem Statement & Objectives
1.4 Organization of the Report
2 Literature Survey
2.1 Survey of Existing System
2.2 Limitation Existing system or research gap
2.3 Mini Project Contribution
3 Proposed System (eg New Approach of Data Summarization
3.1 Introduction
3.2 Architecture/ Framework
3.3 Algorithm and Process Design
3.4 Details of Hardware & Software

3.5 Experiment and Results


3.6 Conclusion and Future work.
References
Chapter 1

Introduction

1.1 Introduction
The Umpire Decision Review Method (UDRS) is a strategy
used in cricket or any other sport to circumvent the on-field
umpires' contentious decisions about ruling a batsman out or
not (in cricket). The accuracy of UDRS comes to around
90%. It uses number of specific simulations such as Super
Slow-Motion and other video replay etc. On-field Umpires,
Batsmen, Fielding Captains and TV Umpires are instruments
within a dynamic system of contact protocols. With the help
of a live cam, the Third Umpire DRS will help the umpires
evaluate the case and will allow him to use functions such as
reviewing, pacing it quickly, pacing it slowly, and pacing it
very slowly to help him determine the original decision's
outcome. It will make decision making clearer and easier. It
is cost effective, easily implemented and doesn’t require any
complex AI technology.
1.2 Motivation
Our mission is to create system with which we can easily
check, is player out or not out. And to overcome the
drawback in the game of cricket which is one of the major
issues of time constraints as well as accuracy.

1.3 Problem Statement and Objectives

Problem Statement: Our project aims to develop a


computer system that helps the umpire for making a
decision in cricket at a low cost and can be used at
various competitions, academies and even in gully
cricket.

Objectives:
• Rational Decisions
• Reduce Needless Aggression
• An Extra Helping Hand
Chapter 2
Literature survey

2.1 Survey of the existing system


A new Decision Review System was initiated by the Indian
Test Series in Sri Lanka in July 2008 (DRS). Of the twelve
decisions reversed in the context of the DRS, India served
only one. Former India batsman Virender Sehwag (lbw) was
the first decision reversed there under the UDRSS in 2008,
and was officially launched by the International Cricket
Council (ICC) on 24 November 2009, during the first Test
between New Zealand and Pakistan at the University Oval
in Dunedin. It was first used in One Day Internationals
(ODI) in January 2011 during England's tour of Australia.
The ICC initially made the UDRS mandatory in all
international matches, but later made its use optional, so that
the system would only be used if both teams agree. The ICC
has agreed to continue to work on the technology and will
try to incorporate its use into all ICC events.
2.2 Limitation of existing system or Research gap:

DRS technology is not completely reliable just like any other


technology and has glitches of various types. Players have
called it inaccurate and even viewers have found that some
of the times, the decisions were tampered. There is room
for minor glitches that escape the human eyes and cricket
has never been free of it. There is only a small chance that
the on-field umpire will be delivering an erroneous review
and that is being said to be solved by the DRS. However, the
error rate comparison between the two has always been
more in favour of on-field umpires and not the technology
that has room for more errors. The whole purpose of
having an on-field umpire will soon be lost if DRS is given a
prominent place in cricket.

2.3 Mini Project Contribution


In this project the contribution of contents are as we have
used python, we divided our work according to the
requirements of our project there are no specific roles as
whenever needed.
Chapter 3
Proposed System
3.1 Introduction
Our project “DRS system” is implemented using
Python and Tkinter. GUI of our project i.e. DRS
gives options to choose from to the user which
contains Stump out, Run out, and LBW decisions.
Stump out and Run out can be decided by playing
the source video in slow or fast motion. Further
decisions like LBW can be implemented by
extracting frames through the source video. Ball
detection and Batsman height detection is done
from the extracted frames. The detected ball
coordinates are further used for ball tracking. 3D
coordinates are mapped into 3D coordinates and
smoothen using regression techniques.
Visualization is implemented through Vpython
which shows results for all these decisions.
3.2 Architecture/Framework

Fig(3.2): Framework Of DRS system


3.3 Algorithm and Process design

Process Design:

Fig(3.3): Process design of DRS System


3.4 Details of Hardware & Software
Software requirements
Anaconda
Windows 7
Python 3.10.0
Hardware requirements
RAM: 4 GB or more
Hard disk: 1 TBor more

3.5 Result and Discussions


Fig(3.5.1):

Fig(3.5.2):

Fig(3.5.3):
Fig(3.5.4):

3.6 Conclusion and Future work:


There’s quite a lot it takes when creating every efficient
third umpire review system so everything we’ve learned
here will help us create a simple and very efficient DRS
system applicable in a wide range of outdoor sports. Without
any fancy equipment and with the help of just a computer
system and a camera this system can run efficiently, thus
making it compatible for all scale tournaments. This project
is only an infant and there is always room of improvement
and modifications making it more ready to go out and rock
the gully cricket world.
References:
Ijarsct.co.in

http://www.stackoverflow.com

www.tutorialspoint.com

www.pythonprogramming.com

You might also like