Monday, September 8, 2008

#27---CLE @ LAA, 4/8/2008




For this game, I used a Project Scoresheet scoresheet. I did not adhere to Project Scoresheet methodology; I used my own codes for hits, baserunner advancement, and the like. Of course, there are similarities between what I did and the official Project Scoresheet system. If you’d like to know more about their system, go to the sites of David Cortesi or Alex Reisner.

One need not use the exact syntax of Project Scoresheet to get an idea of whether their system suits you or not. I suppose I should point out for those who may not know that PS was an organization started by Bill James in 1984 to collect play-by-play data for all major league games. Initially, they accepted scoresheets of all kinds from fans, but eventually the organization adopted Craig Wright’s scoring system as its standard. The organization collapsed some time in the late 80s or early 90s, but its influence can still be seen in organizations like STATS, Baseball Info Solutions, and Retrosheet.

The system was certainly innovative, and its influence can be seen today beyond the people who still score using the method. MLB gametracker inputters use Project Scoresheet notation, or at least a derivative thereof, and Alex Reisner’s situational system was based on combining Project Scoresheet and traditional scoring methods.

Cosmetically, the scoresheet does not provide space for each batter to bat in each inning. Since most boxes in a 9x9 grid go unused, this allows for a more efficient use of space, and people have applied this concept to traditional scorekeeping. The scorebox itself is divided by three horizontal lines. The top line is used to record things that happen before the conclusion of the at bat, such as a runner advancing on a wild pitch or being caught stealing. The middle line is used to record the outcome of the at bat, and the bottom line is used to record things that happen after the at bat ends or the ball is put in play (baserunner advancement, stolen base on strike three, and the like).

The sheet I used here is a copy of one from one included in the 1987 Great American Baseball Stat Book, a short-lived annual that included data culled from the efforts of Project Scoresheet. It includes boxes to record each pitch, which I did, and so let’s start there. I used dots, dashes, and other symbols to record each pitch, whereas the official PS system uses descriptive letters (B for ball, S for swinging strike, etc.). I prefer symbols since I think the use of letters clutters the sheet and draws your focus to reading them. The symbols I used are somewhat similar to those that Alex Reisner uses, but his were designed for separate ball/strike columns and thus double up usage.

I used an open circle for a ball, a square for a pitchout/intentional ball (which was not used in this game), a triangle for a hit batter, a dot for a called strike, a dash for a foul, a plus for a swinging strike, and a x for a ball hit in play. I also put “b” to indicate a bunt attempt or show of a bunt coupled with a strike. Additionally, “N” stands for no pitch, and is used as a timing device. For example, the N in Gary Matthews’ first inning at bat tells us that the throwing error occurred between the third and fourth pitches. If an event occurs on a particular pitch, then the symbol for that pitch is circled (see Sizemore’s third inning at bat--the third ball is circled indicating that it was the wild pitch).

Let me just go through the sheet and point out some events and how the PS system (or at least my variation of it) records them. I will refer to the location on the scoresheet by the box number.

* Cleveland #4--Martinez singled, but the bottom line tells us that the runner was thrown out at home (1 indicates the runner was from first, X indicates an out, H indicates that it was at home), right to first to catcher [1xH(932)].

* Cleveland #9--[SB2] indicates that second base was stolen (one could write [1-2(SB)], but it should be obvious that it was the runner from first who stole second. This is written on the bottom line of the box since it occurred on the last pitch of the at bat, and thus there is no need to circle that pitch.

* Cleveland #10--The runner moved from second to third on a wild pitch [2-3(WP)].

* Cleveland #17--Blake's single advanced the runner at first to second [1-2].

* Cleveland #20--Cabrera's single scored runners from second and third [2-H, 3-H and I box the Hs to make runs easy to spot], and the batter (Cabrera) advanced to second on the throw [B-2(T)].

* Cleveland #30--Hafner hit into a double play, 361. This is marked as 36(1)1--the (1) indicates that the runner at first was retired 36.

* Cleveland #39--Hafner's home run not only scored the runner from first [1-H], but it scored the batter as well [B-H]. The principle is that the batter’s advancement is not marked unless it is beyond what is indicated by their event outcome (as in Cabrera hitting a single but advancing to second on the throw) or the batter scores (so that runs are easy to spot).

As I see it, there are two main strengths of the PS method. The first is that it is very easy to note substitutions, since each box has its own number. There’s no need to worry about what inning it is or which lineup slot is at the plate; instead, you just jot down the appropriate box number and you’re on your way.

The other main strength is that it is that there is no recording backtracking whatsoever. However, this is also the main weakness of the system in my eyes, because it makes reading the account of the game back a real chore. Baserunners are identified by the base on which they started the PA, so if you want to know who actually scored a run, or got caught stealing, you have to work backwards through the sheet to trace that runner’s progress to his PA-initial base.

On the game, note that Francisco Rodriguez was not pitching in the ninth; he had some minor injury and missed this game at the beginning of a season in which he would make a play for Bobby Thigpen's save record.

No comments: