cwevent: Expanded event descriptor¶
cwevent is a command-line tool which extracts detailed
information about individual events (plays) in the data file. These
are grouped into two categories. There are 97 fields which are
compatible with the Retrosheet BEVENT event descriptor tool. These
are specified using the -f
command-line flag. In addition, cwevent
offers a number “extended” fields which expand upon or give more
detailed information not easily accessed via the standard
fields. These are are specified using the -x
command-line flag.
Note
cwevent guarantees that the standard field numbers will match those used by BEVENT. Standard field numbers therefore can be treated as stable, and it should be safe to write scripts referring to them. Extended fields are provisional, and extended fields may be added or withdrawn in future versions. Extended fields are assigned numbers to maintain a logical cohesion, with related fields being grouped. Therefore, extended field numbers are not promised to be stable. It is recommended to use the field labels instead in writing scripts to process the output of cwevent extended fields.
Field number |
Description |
Header |
---|---|---|
0 |
Game ID |
|
1 |
Visiting team |
|
2 |
Inning |
|
3 |
Batting team |
|
4 |
Outs |
|
5 |
Balls |
|
6 |
Strikes |
|
7 |
Pitch sequence |
|
8 |
Visitor score |
|
9 |
Home score |
|
10 |
|
|
11 |
|
|
12 |
|
|
13 |
|
|
14 |
|
|
15 |
|
|
16 |
|
|
17 |
|
|
18 |
Catcher |
|
19 |
First baseman |
|
20 |
Second baseman |
|
21 |
Third baseman |
|
22 |
Shortstop |
|
23 |
Left fielder |
|
24 |
Center fielder |
|
25 |
Right fielder |
|
26 |
Runner on first |
|
27 |
Runner on second |
|
28 |
Runner on third |
|
29 |
Event text |
|
30 |
Leadoff flag |
|
31 |
|
|
32 |
Defensive position |
|
33 |
Lineup position |
|
34 |
|
|
35 |
Batter event flag |
|
36 |
|
|
37 |
Hit value |
|
38 |
|
|
39 |
|
|
40 |
Outs on play |
|
41 |
Double play flag |
|
42 |
Triple play flag |
|
43 |
RBI on play |
|
44 |
Wild pitch flag |
|
45 |
Passed ball flag |
|
46 |
Fielded by |
|
47 |
Batted ball type |
|
48 |
Bunt flag |
|
49 |
Foul flag |
|
50 |
Hit location |
|
51 |
|
|
52 |
|
|
53 |
|
|
54 |
|
|
55 |
|
|
56 |
|
|
57 |
|
|
58 |
|
|
59 |
|
|
60 |
|
|
61 |
|
|
62 |
|
|
63 |
|
|
64 |
|
|
65 |
|
|
66 |
Stolen base for runner on first |
|
67 |
Stolen base for runner on second |
|
68 |
Stolen base for runner on third |
|
69 |
Caught stealing for runner on first |
|
70 |
Caught stealing for runner on second |
|
71 |
Caught stealing for runner on third |
|
72 |
Pickoff of runner on first |
|
73 |
Pickoff of runner on second |
|
74 |
Pickoff of runner on third |
|
75 |
|
|
76 |
|
|
77 |
|
|
78 |
New game flag |
|
79 |
End game flag |
|
80 |
Pinch-runner on first |
|
81 |
Pinch-runner on second |
|
82 |
Pinch-runner on third |
|
83 |
Runner removed for pinch-runner on first |
|
84 |
Runner removed for pinch-runner on second |
|
85 |
Runner removed for pinch-runner on third |
|
86 |
Batter removed for pinch-hitter |
|
87 |
Position of batter removed for pinch-hitter |
|
88 |
|
|
89 |
|
|
90 |
|
|
91 |
|
|
92 |
|
|
93 |
|
|
94 |
|
|
95 |
|
|
96 |
Event number |
|
Field number |
Description |
Header |
---|---|---|
0 |
home team id |
|
1 |
batting team id |
|
2 |
fielding team id |
|
3 |
half inning (differs from batting team if home team bats first) |
|
4 |
start of half inning flag |
|
5 |
end of half inning flag |
|
6 |
score for team on offense |
|
7 |
score for team on defense |
|
8 |
runs scored in this half inning |
|
9 |
number of plate appearances in game for team on offense |
|
10 |
number of plate appearances in inning for team on offense |
|
11 |
start of plate appearance flag |
|
12 |
truncated plate appearance flag |
|
13 |
base state at start of play |
|
14 |
base state at end of play |
|
15 |
batter is starter flag |
|
16 |
result batter is starter flag |
|
17 |
ID of the batter on deck |
|
18 |
ID of the batter in the hold |
|
19 |
pitcher is starter flag |
|
20 |
result pitcher is starter flag |
|
21 |
defensive position of runner on first |
|
22 |
lineup position of runner on first |
|
23 |
event number on which runner on first reached base |
|
24 |
defensive position of runner on second |
|
25 |
lineup position of runner on second |
|
26 |
event number on which runner on second reached base |
|
27 |
defensive position of runner on third |
|
28 |
lineup position of runner on third |
|
29 |
event number on which runner on third reached base |
|
30 |
responsible catcher for runner on first |
|
31 |
responsible catcher for runner on second |
|
32 |
responsible catcher for runner on third |
|
33 |
number of balls in plate appearance |
|
34 |
number of called balls in plate appearance |
|
35 |
number of intentional balls in plate appearance |
|
36 |
number of pitchouts in plate appearance |
|
37 |
number of pitches hitting batter in plate appearance |
|
38 |
number of other balls in plate appearance |
|
39 |
number of strikes in plate appearance |
|
40 |
number of called strikes in plate appearance |
|
41 |
number of swinging strikes in plate appearance |
|
42 |
number of foul balls in plate appearance |
|
43 |
number of balls in play in plate appearance |
|
44 |
number of other strikes in plate appearance |
|
45 |
number of runs on play |
|
46 |
id of player fielding batted ball |
|
47 |
force play at second flag |
|
48 |
force play at third flag |
|
49 |
force play at home flag |
|
50 |
batter safe on error flag |
|
51 |
fate of batter (base ultimately advanced to) |
|
52 |
fate of runner on first |
|
53 |
fate of runner on second |
|
54 |
fate of runner on third |
|
55 |
runs scored in half inning after this event |
|
56 |
fielder with sixth assist |
|
57 |
fielder with seventh assist |
|
58 |
fielder with eighth assist |
|
59 |
fielder with ninth assist |
|
60 |
fielder with tenth assist |
|
61 |
unknown fielding credit flag |
|
62 |
uncertain play flag |
|
Result batters and pitchers (fields 10-17)¶
In most cases, the pitcher and batter charged or credited with the event (when a batter event) are the ones in the game when the event occurs. However, Rules 10.17 and 10.18 have special clauses discussing how to charge walks to pitchers when a relief pitcher enters in the middle of the plate appearance, and how to charge strikeouts to batters when a pinch hitter enters in the middle of the plate appearance. The batter and pitcher fields always give the identity of the batter and pitcher in the game at the time of the event; the result batter and result pitcher give the batter and pitcher credited or charged with the event.
There is one known bug in the Retrosheet-provided tools regarding the result pitcher. When a relief pitcher enters the game, and then the next batter is retired on a fielder’s choice, the pitcher responsible for the runner put out is shown in the result pitcher field. While it is correct that the batter reaching base in this case would be charged to the former pitcher should he score, the purpose of the result pitcher field is to indicate the pitcher charged with the outcome of this particular event. In this case, for example, the relief pitcher is awarded one-third of an inning pitched; therefore, he should be the result pitcher, and then the previous pitcher should be (and is) listed in the responsible pitcher field for the batter in subsequent events.
In the case of switch-hitters, the batter hand and result batter hand fields are set to L or R, as appropriate, based upon the hand with which the pitcher throws. If the pitcher’s throwing hand is unknown, or if the batter’s batting hand is unknown, a question mark appears in these fields.
Pinch-hit flag (field 31)¶
This field is T if the batter is a pinch-hitter, and F if he is not. If a player enters the game as a pinch-hitter, and then bats again in the same inning because his team bats around, this field will be F for the player’s second plate appearance. To identify the cases where this occurs, consult the defensive position field (field 32), which will continue to be equal to 11 (or 12 for a pinch-runner) until that player assumes a defensive position.
Event type code (field 34)¶
All plays are categorized by their primary event type. Here is a list of all types and the corresponding codes used in this field. Codes marked “obsolete” are no longer used, or no longer appear in Retrosheet-produced play-by-play files.
Code |
Primary event |
---|---|
0 |
Unknown (obsolete) |
1 |
None (obsolete) |
2 |
Generic out |
3 |
Strikeout |
4 |
Stolen base |
5 |
Defensive indifference |
6 |
Caught stealing |
7 |
Pickoff error (obsolete) |
8 |
Pickoff |
9 |
Wild pitch |
10 |
Passed ball |
11 |
Balk |
12 |
Other advance/out advancing |
13 |
Foul error |
14 |
Walk |
15 |
Intentional walk |
16 |
Hit by pitch |
17 |
Interference |
18 |
Error |
19 |
Fielder’s choice |
20 |
Single |
21 |
Double |
22 |
Triple |
23 |
Home run |
24 |
Missing play (obsolete) |
Sacrifice flags and eras (fields 36, 38, 39)¶
Chadwick in all cases applies the modern rules concerning the awarding of sacrifice hits, sacrifice flies, and official times at bat, regardless of the year indicated with the -y flag.
Plays on runners (fields 58-65)¶
Fields 58 through 65 give the destination of all runners, including the batter, as well as the fielding play made on them, if any. For the purposes of the destination fields, a code of 5 indicates the runner scored, and is charged as unearned, and a code of 6 indicates the runner scored, and is charged as unearned to the team, but earned to the pitcher. These codes only appear when the (NR) or (TUR) modifiers are explicitly used on the advancement code. There is no internal logic in Chadwick to ferret out which runs should be earned or unearned, as in many cases there is insufficient information, or the situation requires the judgment of the official scorer. Runners which are put out are reported as having an advancement of 0.
In most cases, the play on a runner indicates the fielding credits involved in putting him out. Chadwick also reports a fielding play on a runner when the runner is safe on a dropped throw, such as 3E1 or FC6.1X2(6E4).
Fielding errors (fields 51-57)¶
Up to three errors can be indicated in cwevent output. Supported error types are F for generic fielding errors, and T for throwing errors; no distinction is made between bobbled batted balls, muffed throws or fly balls, and so forth.
Pitcher responsibility for runs (fields 75-77)¶
The Official Rules for charging runs to pitchers stipulate that if a pitcher is relieved in the middle of an inning with runners left on base, he is charged with runs if those runners (or the ones who replace them in the event of fielder’s choices) subsequently score in the inning. The current rule is Rule 10.16(g), the comment on which in the rules states:
It is the intent of Rule 10.16(g) to charge each pitcher with the number of runners he put on base, rather than with the individual runners. When a pitcher puts runners on base and is relieved, such pitcher shall be charged with all runs subsequently scored up to and including the number of runners such pitcher left on base when such pitcher left the game, unless such runners are put out without action by the batter.
Chadwick implements this by assigning “responsibility” for runners, and shifting those runners after fielder’s choices as appropriate to implement the rule. Fields 75 through 77 report the pitcher currently “charged” with runners on base using this method.
There is one special case to note in reporting these fields. As noted, a fielder’s choice does not absolve a departed pitcher for responsibility for a potential run. Ordinarily it is good enough to report the shift in responsibility at the start of the next play. However, consider the following scenario: The bases are loaded, with the runner on third (R3) the responsibility of Pitcher A and runners on second and first (R2 and R1) the responsibility of Pitcher B. The batter hits a ground ball and R3 is forced at home. Then, the catcher throws wildly trying to complete the double play, and as a result R2 scores. In this case, the run scored by R2 is charged to Pitcher A, not Pitcher B, i.e., the responsibility shifts in the middle of the play. In order to facilitate calculation of runs and earned runs allowed correctly from cwevent output, in this case, the record for the play will report R2 as being the responsibility of Pitcher A, i.e., it will report the responsibility after the mid-play shift.
This convention will not affect most applications. Indeed, the Official Rules technically do not have a concept of assigning responsibility to particular runners, and the contents of fields 75-77 only have meaning on plays in which the corresponding runners score. This convention may confuse certain calculations, however, including those which try to track what happens to inherited runners, if one does not take appropriate care to handle this very unusual case.
Fielding credits (fields 88-95)¶
The order in which Chadwick and the Retrosheet-provided tools list putouts and assists may vary. The number of plays on which this occurs is quite few, and generally in cases where there is a putout in the primary event as well as one in the baserunning modifiers. The words “first”, “second” and so on do not necessarily indicate chronological order of the credits, though in most cases they do.