SSCAIT game result error
Look closely at this line from the latest SSCAIT results. (I edited it slightly so the links work from my site. The formatting is of course different.)
Steamhammer (Zerg, AI_MODULE) | Jakub Trancik (Protoss, AI_MODULE) | Bot 1 | 2019-01-12 14:06:58 | .rep / watch |
It claims to describe a game between Steamhammer and Jakub Trancik, but the replay and watch links point to a game between Steamhammer and Martin Rooijackers.
I haven’t seen an error like this before. I made a brief check of nearby game results, and they looked correct. The game numbers proceed in sequence. The replay is a genuine new Steamhammer-Martin Rooijackers game and the result is correct; only the opponent name is listed incorrectly. The unofficial crosstable shows Steamhammer as 0-2 versus Martin Rooijackers and 1-1 versus Jakub Trancik, although including this game I believe the results should be 1-1 and 0-1 respectively—I see only 3 games played in these two pairings. The only other sign of error I can find is that the replay does not appear on Steamhammer's SSCAIT page. Is it a one-off error, or are there other confused game results? Does it affect pairings?
I’ll report it directly to SSCAIT.
Update: Michal Certicky reports back that it is now fixed: It was a bug in choosing the replay file, not a mislabeled game bug. See the comment.
Comments
MicroDK on :
Jay Scott on :
How many mislabeled games are there?
MicroDK on :
Michal Certicky on :
You see, the game results table in our DB doesn't contain the replay URLs (they're generated by TM manager elsewhere), so we need to search for the correct files in the replays folder. And that folder was originally meant just as a one-way file dump. It wasn't meant to be searched, so it's structure is stupid. The problematic function sometimes returned some other, older file, if its name contained the ID of the searched game. For example, that Steamhammer vs. Martin Rooijackers game was an old game from before the tournament. I fixed it now, so it shouldn't happen any more.
Once again, the results were not affected by this - it was just serving a wrong replay file for download.
Jay Scott on :