Pitcher Performance Tracking

1. Button Key TOG = toggle stat displayed INN = toggle inning displayed P = pitch (foul ball on full count) B = ball S = strike NPO = non pitch-incrementing out (pickoff or double/triple play) Inn = inning increment (relief pitcher) DTS = dropped third strike RST = reset Display Key BB = walks SO = strikeouts P/Out = pitch per out P = pitches B = balls S = strikes • System Overview • After the outcome of each pitch, the user pushes one of the buttons at the bottom of the device (see key). This input will increment the appropriate display. • The displays are arranged such that: • The top row of displays are fixed and show total game statistics for pitches, balls, and strikes • The second row allow the user to toggle walks, strikeouts, and pitches per out for the entire game and for the current inning • The third row shows pitches, balls, and strikes for the current inning • The last row of displays allows the user to toggle all of the statistics for different innings in order to analyze pitcher performance trends over time Pitcher Performance Tracking • Hierarchical Design Methodology • This methodology allows the designer to: • Transform a schematic into a module • Use submodules to create new modules from scratch • Interconnect modules with buses • These features facilitate the design by: • Reducing the complexity required to represent the circuit • Allowing the reuse of modules • Allowing designers to debug at the submodule level • For example, shown to the right is a bit-wise AND schematic • that was created by ANDing the respective bits of two 8-bit buses and then rebussing the result. • This schematic was transformed into the module • “BitwiseAnd18” and can be used in other schematics. • System Flowchart • Pushbutton Inputs allow user to control the device • Debouncing ensures that unintentional on/off toggling (bouncing) is ignored • OnePulse Logic makes certain that the input is read only once even if the button is held for more than one clock cycle • If a data input is pressed then the signal is relayed to One At Bat State Logic, display inputs go to Display Gate and State Logic, and all inputs are sent to Reset Logic • Reset Logic requires the RST input to be pressed three times in a row in order to make it more difficult to accidentally reset the device • One At Bat State Logic uses data input to track a single at bat, and increment the appropriate registers based on the at bat situation and a single data input • Support Gate Logic helps other functions by keeping track of the situational data “current inning” and “outs in the current inning” • Register Bank stores all of the pitcher’s statistical data • Display Gate and State Logic uses display inputs to determine what data the user wants to view on each display • Display Multiplexers retrieves the proper data and sends one bit display data to single LEDs and eight bit numbers to the Display Decoders • Display Decoders formats eight bit numbers for 7-segment display outputs Abstract In both amateur and professional baseball, coaches monitor the performance of pitchers by counting the total number of pitches thrown in a game. This pitch count helps coaches prevent injury in younger pitchers, as well as track the expected fatigue of older and professional players throughout a game. The problem is that a straight pitch count does not factor in the weather, the type of pitches thrown, or the initial state of the pitcher. A device that tracks the pitch count as well as balls, strikes, walks, strikeouts and the pitch per out ratio for each inning and in total would give coaches access to more information and allow them to evaluate actual pitcher performance. In addition, amateur baseball teams would be able to, like professional teams, collect statistics in real time for coaching decisions. In the chosen approach, digital logic is implemented on a field-programmable gate array (FPGA) board. Multiple push buttons are used to input data. In order to keep the device user-friendly, the user only presses one button after the outcome of each pitch. These inputs increment the appropriate registers for the event. The logic also automatically accounts for the end of innings and recognizes every possible outcome of the current pitch. The statistics per inning and in total are outputted on 7-segment LED displays. The full implementation of the system calculates and displays pitches, balls, strikes, walks, strikeouts, and pitches per out per inning and in total.  It also allows the user to toggle through these statistics on multiple displays in order to compare data from multiple innings for tracking and analysis purposes. Group 12 Authors Michael Costa EE ’08 Alexis Wong SSE ’08 Advisor Dr. Jan Van der Spiegel Demo Times Thursday, April 24, 2008 9:00 AM – 12:00 PM University of Pennsylvania Department of Electrical and Systems Engineering Control Logic The state diagram is a simplified version of our One At Bat State Logic. This version only accounts for the pitcher walking or striking out the batter. Our implemented logic also accounts for hits, fly and ground outs, pickoffs, double plays, and in the event of a dropped third strike, even credits the pitcher with a strikeout and acknowledges a new batter while not incrementing the number of outs. This diagram shows that strikeouts only occur when there are two strikes and walks occur when there are three balls. The actual state logic is significantly more intricate because most of the other possible events can occur during any “count” state. System Flowchart State Diagram