Laskos wrote:Laskos wrote:Wow, Little Blitzer is buggy when adjudicating 50 move draw. The missed Win cases are hard to reproduce. I will check later this night when I get back home.
Although for Wins I am still getting some draws with Texel (one in 500 games or so) in Cutechess-cli, I observe some odd behavior, the draws seem to cluster and appear at the start of the run. Also, the wrong move is the first move in the game. I guess it's UI-engine communication. Here are 2 games:
From the first game:
After 0.42 seconds texel had not been able to finish the depth 2 search. I guess this happens because the DTZ files are on a mechanical disk and they have not been used recently enough to be in cache. The texel TB implementation prefers to not use TBs if it would overstep the allocated thinking time too much, but the stockfish implementation would probe DTZ at the root regardless of how much time that would take I think.
So this seems to be a combination of using hyper bullet time control, starting from a position already in the TBs, having the DTZ tables on a slow (mechanical) disk drive, and using an engine that prefers not using the TBs over using too much thinking time.
In a game not starting from a TB position, the first DTZ probe in texel would typically happen inside a deep search when texel has proven a TB win and starts trying to optimize the DTM score. Using the same hardware, there would likely be 0.42s delay there too, but that would not really matter because the search has already found a forced win, and when starting a new search after the opponents next move, the required part of the DTZ table would already be cached.