Data Handling for February 23-27, 2026

I have placed data quality notices on the games from February 26 and 27 as each published box score contains an identifiable error. J-ometry data from these games uses corrected information, and if you use the CSV that contains box score data, that data will match information from the broadcast and not the published boxes.

On February 26, Patrick’s FJ wager and final score are reversed. On February 27, Diana’s DD2 wager is recorded incorrectly. In both cases, I found these errors through consistency checks with J-Archive and then verified the correct information with the broadcast.

Additionally, for the game on February 23, I have removed the attempt and buzz for Zach that ultimately resulted in neither gain nor loss on a ruling that he should have been asked to be more specific. (I slightly disagree with this ruling, in which he gave a constellation name instead of the necessary star name, but the constellation name is contained in the star’s designation and so I can see the justification.) Removing the attempt and buzz keeps metrics such as accuracy from penalizing Zach in the same manner as for an incorrect response, although it means the site data and the box score are inconsistent. I don’t consider this the same sort of issue as for February 26 and 27, but I have handled and noted it similarly.