Skip to content

Latest commit

 

History

History
182 lines (140 loc) · 7.2 KB

ChangeLog.md

File metadata and controls

182 lines (140 loc) · 7.2 KB
Raw

[0.11.0]

Behaviour changes

  • In cwgame, field 84 has been added to report the value of the new info,gametype field. To match BGAME behaviour this field is not reported by default. Any game that does not have an info,gametype record is assumed to be "regular".
  • Pitch types A (automatic strike) and V (automatic ball) are no longer counted towards pitches/strikes.
  • In cwevent, the extended fields UNKNOWN_OUT_EXC_FL and UNKNOWN_PLAY_EXC_FL are now quoted explicitly to be consistent with all other flag fields.
  • In cwgame, warnings on empty values for attendance and timeofgame has been removed. These are now output as 0 (instead of -1) to restore BEVENT compatibility.
  • In cwgame, "unknown" in now an accepted value for info,temp and info,windspeed. "unknown" values are output as 0 for BEVENT compatibility.
  • In cwevent, the implementation of the batter/runner "fate" extended fields was entirely incorrect. This has been corrected. (#45)
  • In handling rosters, treat blank or null values for batting or throwing side as if they were explicit question marks.

[0.10.0] - 2023-01-02

New features

  • Provides support for the presadj record type introduced by Retrosheet in the December 2022 release. This record reassigns responsibility for a runner to a specified pitcher, in cases in which the pitcher charged with a runner scoring was different than the one who would be under the modern rule.

Bug fixes

  • When a player has multiple identities in the game due to the DH+pitcher rule, ensure his baserunning stats are credited to his identity in the batting order
  • Corrects a regression in which pitchers were being charged with an earned run when an automatic runner scored.
  • When an automatic runner was retired on a FC and the subsequent batter homered (or otherwise scored on the ball he hit into play), the batter would also be shown as an automatic runner. This has been corrected.

[0.9.5] - 2022-05-04

Bug fixes

  • The use of runner code 7 for an automatic tiebreaker runner who scored, which was introduced in 0.8.1, was never implemented correctly, and so no advancement or fate records were emitted with this code. This corrects the typo which led to this problem, and the output is now correct.

[0.9.4] - 2022-04-21

Bug fixes

  • Patch behaviour of function to identify a player's lineup slot, to preference the identity in the batting order of a pitcher who is DHing for himself.

[0.9.3] - 2022-04-08

Behaviour changes

  • The new DH rule for the 2022 season allows a starting pitcher to DH for himself. Per the text of the rule, such a player has two identities in the lineup, one in his role as the DH in the batting order, and another as the pitcher in batting order slot zero (in DiamondWare terminology). DiamondWare files follow this convention by listing the player with two start records. This version separates the statistical tabulation for the two identities, with batting (and non-pitcher fielding) statistics for such a player appearing in his record in the batting order, and his pitching (and pitcher fielding) statistics appearing in his slot-zero entry.

[0.9.2] - 2022-01-10

New features

  • cwevent has been extended with a new field COUNT_TX, which reports the count string as it appears in the event file. Null values for balls or strikes in the count are reported as zero in BALLS_CT and STRIKES_CT for compatibility with BEVENT. This field allows for the diagnosis of missing count data (which is represented by a "?" in the count string.

[0.9.1] - 2021-10-20

Bug fixes

  • Corrects a regression in which automatic runners for the extra-inning tiebreaker were not being included in LOB calcuations.
  • Corrects the help message for cwcomment to list the default fields (these are now 0-9 as of the additions made for 0.9.0)

[0.9.0] - 2021-01-04

New features

  • With the 2020 release, Retrosheet has introduced two new metadata fields representing the scheduled number of innings and the tiebreaker rule in effect (if any). These currently appear only in the 2020 event files. These are now extracted by two new extended fields in cwgame.
  • cwcomment has been extended with new fields which record the contents of ejection and umpire change record, which in Retrosheet files are embedded in the comments.

Behaviour changes

  • Previously, cwcomment catenated all comments in a sequence into one record. To support the addition of ejection and umpire change record extraction, this behaviour has changed. Ejection and umpire change comments are not catenated to previous/subsequent comments. However, a series of comments which do not contain these special record type is still catenated as before.

Bug fixes

  • Fixed crash which would occur if running cwcomment on a boxscore file.

[0.8.1] - 2020-07-17

Behaviour changes

  • The record type radj is now a synonym for the cw:itb extension for placing automatic runners on base in the tiebreaker.
  • A new runner advancement code 7 has been introduced. This marks the case in which an automatic runner placed on base via an radj record scores. This run is always unearned. In the event an automatic runner is put out due to batter action, the subsequent runner becomes considered the automatic runner, just as with the rules for tracking pitcher responsibility for baserunners.

Bug fixes

  • Day of week was not being correctly reported by cwgame for games taking place prior to 1900; in some cases this could lead to core dumps due to accessing memory improperly. This has been fixed and the new algorithm is valid for any Gregorian calendar date.
  • cwgame was not reporting runs, hits, errors, LOB, or number of innings for games in the boxscore file format; these were all being reported as zero. This has been fixed.

Deprecations and removals

  • The cw:itb record type is now considered deprecated in favour of radj. Support for cw:itb will be removed at some point in future.

[0.8.0] - 2020-06-09

Behaviour changes

  • cwevent now reports FLD_CD = 0 on generic outs coded as "99" (unknown fielding credits). This is to match a change to the behaviour of BEVENT release in summer 2020.
  • Fielding credits on any play containing "99" are now suppressed, including such constructions as CS2(299).

Bug fixes

  • badj records are used to compute the batting hand of responsible batters who are removed with two strikes and then charged with the a strikeout in the plate appearance.
  • padj records were not being respected when computing the batting hand of switch-hitters.
  • Fixed bug in cwbox in which having more than 6 pitchers who were removed without retiring a batter in an inning would lead to a crash.
  • Made cwbox -X and cwbox -S robust to the absence of the team file or a roster file by implementing sensible defaults.

Enhancements

  • Implemented -n switch for cwcomment to print column headers.

Deprecations and removals

  • Support for the KE (strikeout + error) primary event type was removed. This was a very old Retrosheet code that has been deprecated long ago and has not appeared in any released files for years.