Comments on: Gameday, get yr Gameday

By: Wells

Wells — Sat, 06 Feb 2010 19:44:02 +0000

RZ – I just made an update. Now there are two columns added to the pitch table – ‘b’ and ‘s’ – for the count at the beginning of the pitch. Let me know if you find any issues, but it seems to work well. You can download the newest at github: http://github.com/wellsoliver/py-gameday/archives/master

By: RZ

RZ — Sat, 06 Feb 2010 18:30:09 +0000

I have a MySQL database using Mike Fast’s method with Perl. The problem I have with it is the long process of parsing the data into the database which takes a very,very long time.

That is why I am interested in your setup. But without having the balls and strike count for each pitch doesn’t make it worth to use your method until you add that in.

By: Wells

Wells — Sat, 06 Feb 2010 17:12:34 +0000

RZ – if you have the 2009 data loaded, you can run this query:

SELECT
*
FROM pitch
WHERE game_id = ‘gid_2009_06_08_pitmlb_atlmlb_1′
ORDER BY num ASC;

Each pitch is grouped into an atbat by the pitch.num column. You can derive the count this way, also using pitch.type (S = strike, B = ball).

I could update the script to do this, tally the count per pitch. I will look into that.

By: Wells

Wells — Sat, 06 Feb 2010 17:02:01 +0000

RZ- yeah, this is similar to BBOS. The database table ‘atbat’ contains two columns – ‘b’ and ‘s’ – that contain the balls and strikes information at the time of the event (described by ‘des’ and ‘event’ columns).

Let me know if this helps.

By: RZ

RZ — Sat, 06 Feb 2010 16:48:11 +0000

Very cool. Two questions:
Is this like Baseball on Stick where is parses the data directly into the database?
I looked over the database structure and couldn’t find the balls and strike count for each pitch. Is it update pitch by pitch in the atbats table? If not, one could not find the pitch by pitch count which makes any run value formulas worthless.