1 / 44

Little League Statistics Tracking System

Little League Statistics Tracking System. Group 8: Corey Cowart Nicholas Rimer Sean Martin Brian McCauley Sponsor: Pete McAlindon. Project Goals and Objectives. Replace the currently used dugout score-sheets. Provide an online database for all players on teams using the system.

kyna
Download Presentation

Little League Statistics Tracking System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Little League Statistics Tracking System Group 8: Corey Cowart NicholasRimer Sean Martin Brian McCauley Sponsor: Pete McAlindon

  2. Project Goals and Objectives • Replace the currently used dugout score-sheets. • Provide an online database for all players on teams using the system. • Allow fans to easily follow the teams and players • Provide in depth statistics for scouts and officials.

  3. Overall Block Diagram

  4. Possible Benefits • Minimizing the training for score keeping. • Allow parents to remotely follow their children’s games when not present. • Instantaneous data synchronization. • Prevent lost statistic from data sheets being lost. • Better drafting into higher leagues based on real stats rather than superficial figures.

  5. Umpire Device

  6. Goals and Objectives • Create a device that is ergonomic and similar in size to the existing device. • Maintain all functions currently recorded on Umpire indicator. • Display values for balls, strikes and outs on the device. • Simplify the recording of play data to minimize training time of the current system.

  7. Specifications • Choose components that run off 3.3V to simplify power schemes. • Have battery life of greater than 15 hours with low battery indication. • Have range of over 30ft to connect with coaching tablets. • Dimensions no larger than 5” x 3”. • Displays able to show digits 0 – 4 for balls, strikes and outs

  8. Current Umpire Device • Dimensions of 2.5” x 4” • Scroll wheels for selecting numbers of balls, strikes and outs. • New digital umpire device will have push buttons for incrementing these counts.

  9. Block Diagram

  10. Display Schematic PIC24HJ12GP202 4511 4511 4511

  11. Microcontroller • Chosen microcontroller is the PIC24HJ12GP202 • 21 I/O pins when 18 pins needed. • Programmed in C language. • Cost effective at $2.24. • Programmed on the Microstick development board costing $24.99

  12. Bluetooth Connectivity LinkMatik 2.0 from FlexiPanel • Connects with up to 4 devices at a time. • Up to 100 meter range. • Small footprint. • Sleep mode with ~370uA current draw.

  13. Power • Device needs to be battery powered. • Multiple Umpires using same device so power options need to be flexible. • All chipsets chosen to use 3.3V. • LD1117V33 can supply up to 950mA of current.

  14. Coach Application

  15. Goals and Objectives Pregame: • Allow a team’s coach to view and edit their team roster within the application. • Create batting and fielding lineups for upcoming games. • Display season and overall statistics for each player in a detailed view. • Allow for database search on player creation to keep tracking stats as players change teams.

  16. Goals and Objectives In-game: • Immediately reflect any change in state from the umpire device. • Keep track of all statistics that are currently recorded on the dugout score-sheets. • Account for all possible on field events such as player substitutions, pinch hitting, etc. • Upload all tracked statistics in real time on a play by play basis.

  17. Goals and Objectives Post-game: • Implement a league-wide player search function that displays detailed statistics on all players similar to that in the pre-game interface. • Allow for side-by-side team comparisons for any other team in the league that is implementing the system. • Present in-depth team statistics for any other team implementing the system in the league.

  18. Block Diagram

  19. Program Life Cycle • Baseline: Android v2.2 • Optimized for 1024x600, high • pixel density screen. • Does not interfere with any of the • built-in android buttons. • Developed in eclipse IDE using • the ADT Android plug-in.

  20. Class Layout • 6 main activities. • All inherit from Android’s Activity class. • Each will have corresponding xml files to specify UI layout. • Pass Intents for inter-app communication.

  21. Data Structures • Additional data classes will be used to facilitate data clarity within the app. • A local database will be utilized to ensure that player and lineup data is not lost when the app’s onDestroy() method is called.

  22. User Interface – Home Screen

  23. User Interface – Roster Management

  24. User Interface – At Bat

  25. User Interface - Fielding

  26. Hardware Implementation • Viewsonic G Tablet • Android 2.2 (Froyo). • ~10 hours of battery life using internet connection. • Large screen for less cluttered layout of prototype.

  27. Fan Application

  28. Goals and Objectives • Communicate with the database • Provide information for games, teams and players. • Regularly update stats from the database • Be quick and user friendly

  29. Class Diagram

  30. User Interface Flow

  31. User Interface

  32. Database

  33. Objectives • Organize and store data to optimize access speed. • Maintain and backup current and previous games. • Source client recognition and validation. • Minimize bandwidth. • Migrate data between multiple databases.

  34. Specifications • Independent team and game databases. • Implemented in MySQL. • Remote cloud server (via Amazon).

  35. Local vs. Remote Local: + Direct control + Customizable + Faster - Expensive - Maintenance Remote: - Limited Options - Accessibility - Bandwidth + Cheaper + Self-maintaining Decision: Remote

  36. Class Diagram: Team DB

  37. Class Diagram: Game DB

  38. Data Organization • Split data to minimize access time. • Smaller database requires less searching. • Faster writes to known locations. • Smaller backups. • Pricing schemes: • Amount of databases, size, and usage. • Uptime.

  39. Activity Diagram: Fan

  40. Activity Diagram: Coach

  41. Activity Diagram: Umpire

  42. Budget Breakdown

  43. Question How does the umpire indicator communicate with the coach application? • A) WiFi • B) Bluetooth • C) ZigBee • D) USB

More Related