Cricist A VR based decision sports system for batsmen selection

Project Title

Cricist A VR based decision sports system for batsmen selection

Project Area of Specialization Augmented and Virtual RealityProject Summary

Problem	Selection of team especially the batsmen is the most difficult task to do because of the following reasons: A batsman scoring centuries or half-centuries in the one region of the world does not mean that he will necessarily perform the same in the pitches of other regions of the world. As in subcontinent regions, pitches are slower and more batsmen-friendly. On the other hand, the English pitches have bounce and the conditions that usually do not favor batsmen. Even if we consider the same region e.g. Pakistan, the pitches in northern parts of Pakistan are not batsman-friendly but other parts are like Indian pitches i.e. batsmen friendly. In addition to that, pitches also behave differently in two innings of the same match.
Affects	Because of wrong selection and not up to the mark performance of the individual player, the pressure of the match will be on other team players which will affect their performance too.
Solution	In order to solve above discussed problem, it is necessary that the management have the knowledge of how a batsman responds to different pitches because the players who usually play in slow pitches usually have slow reflexes as compared to the player who plays in fast pitches and the players will find it difficult while playing in uncommon conditions. So, a decision sports system is necessary to help in the selection procedure.
Unlike	To select the best possible options for the team different recommendation systems are used. These systems work by analyzing the previous data of the batsman against certain regions and then recommend optimal players accordingly. For example, if a player named Malik played well in England then he will be recommended for the tours which have similar conditions to that of England's matches. But there is quote in cricket world:                                        "Cricket is Uncertain" The best example of the above quote is Pakistan's test batsman Nasir Jamshed. He scored his only three centuries against India and that was the reason he was selected against India in the 2015 ICC cricket World Cup but failed to score there. So, these systems provide uncertainty in following points: Cannot deal with the new batsmen (COLD START problem). If a player performed well in certain conditions, it does not mean that he will do it again as after 5 years there will be factors of age, fitness, and most importantly current cricket form which will affect his game.
Our Product	Cricist provides a virtual environment with the help of Leap Motion, Kinect, physical bat and VR head set where a batsman will involve in the almost same batting environment, he can face in the real world. So that the factors of age, reflexes against shots and current cricketing form for a specific region can be tested in the present day. Similarly, the cold start problem can also be solved as the newcomer will be tested the same way as experienced players are being tested.

Problem

Affects

Solution

Unlike

Our Product

Project Objectives

1. To deal with the new batsmen selection with non-existent or nominal previous records (COLD START problem).
2. If a player performed well in certain conditions, it does not mean that he will do it again as after 5 years there will be factors of age, fitness, and most importantly current cricket form which will affect his game. So the most important objective of cricist is to generate report of player’s current performance with respect to selected pitch.
3. To provide a virtual environment to player for his practice session of different pitches.

Project Implementation Method

For cricist we will follow RUP (Rational Unified Process). It has four phases:

• Inception
• Elaboration
• Construction
• Transition

Inception: In this phase we will be creating artifacts such as a vision Document, an initial use case model, an initial business case and a business model. After this phase we will be able to gather requirements based on the primary use cases that we have created as part of this phase.

Elaboration: In this phase analyzing our problem domain, determining the scope of our system which is Major functional and nonfunctional requirements. At the end of this phase we will have a use case model which is nearly complete in which we have identified how many actors and use cases are part of our system.

Construction: During this phase cricist major components and applications features will be developed and integrated, also this phase will include the testing of the product.

Transition: This phase will include rolling out our product to community. Once the product has been handed over to the end user, arising issues and feedback will be recorded which will in turn lead to developing new releases and correcting problems.

There will mainly be three users who will interact with the system i.e. the player who will be tested, the admin who will control the test conducted for the team management and the third user will be from the selector who will be able to view live test session and the profile of any player. The admin will set up the test conditions i.e. selection of regions or pitch types and even testing by providing manual conditions on the demand of team management. Once the test is ended a statistical report on batsman’s performance will be generated based on the data gathered and processed (using pre-processing techniques) in the testing session. And the stats will be stored in a local database.

Benefits of the Project

PCB (Pakistan Cricket Board) is the main organization who can use cricist in a productive way, also business opportunities of cricist can be created in following domains:

• Private Cricket Academies:

The cricket academies have usually limited resources in terms of international standard pitches. So, the system will help in the development of the batsmen by providing the virtual environment for practice and test sessions of international pitches.

• International Cricket Boards:

International Cricket Boards can afford international pitches but it costs a lot of money. By using Cricist they can test and practice their players with low cost, also Cricist is a virtual assistant which will help test and select batsmen for their upcoming tours.

• Entertainment:

Slightly modified version of the system can also be used for fun purpose as in homes and Shopping malls it can be installed for enjoyment purposes especially for women who do not have that much access outdoor or physical games.

Technical Details of Final Deliverable

We will build major parts of cricist in python. For machine & deep learning we will use tensorflow & pytorch. We will do image processing task with the help of opencv. We will use unreal game engine because its graphics quality is better than other game engines like unity, also it has free assets. We will use two devices i.e. Kinect & Leap Motion for vision system to recognize bat. We will use oculus virtual reality headset.

On average it takes following time to reach a ball from bowler to batsmen:

• 0.5 Sec for Fast Bowlers
• 9.5 Sec for Spin Bowlers

System shall recognize and perform processing within their respective time interval.

Final Deliverable of the Project HW/SW integrated systemCore Industry OthersOther Industries IT Core Technology Augmented & Virtual RealityOther Technologies Artificial Intelligence(AI), Wearables and ImplantablesSustainable Development Goals Industry, Innovation and Infrastructure, Partnerships to achieve the GoalRequired Resources

Elapsed time in (days or weeks or month or quarter) since start of the project	Milestone	Deliverable
Month 1	Elicitation report Analysis of elicitation report	Vision Document 1.0
Month 2	Analysis of quality attributes	Software Quality/Test plan
Month 3	Observation of changes	Vision document 2.0
Month 4	Analysis of vision document	Core Architecture implementation
Month 5	Core architecture analysis	Analysis/Use case models
Month 6	requirement analysis	Software Requirement specification IEEE 830
Month 7	observation of system working	Initial prototype
Month 8	Creation of test cases	Test Design specification
Month 9	verification & validation of test cases	Test case specification
Month 10	execution of test cases	First working version with major functionality
Month 11	fix bugs	Final working system Beta testing & deployment
Month 12	Study major bugs of system	User manuals