Volker Pittlik wrote:I couldn't reproduce these false draw claims. Possibly there was something wrong with version 22.0 (unlikely in my opinion) or with the draw detection tool?
No. The matches were run under Winboard (unless Leo has changed something recently, which I doubt), which means that there is no draw detection tool involved. Winboard just accepts draw claims from the engine, and instantly stops the game. These stalemate claims must be originating in Crafty; there is no other possibility. Leo's Windows binary of Crafty must be broken somehow.
Because Leo doesn't seem to visit this forum often, it is probably better to continue the discussion on the WBEC forum.
Volker Pittlik wrote:I couldn't reproduce these false draw claims. Possibly there was something wrong with version 22.0 (unlikely in my opinion) or with the draw detection tool?
No. The matches were run under Winboard (unless Leo has changed something recently, which I doubt), which means that there is no draw detection tool involved. Winboard just accepts draw claims from the engine, and instantly stops the game. These stalemate claims must be originating in Crafty; there is no other possibility. Leo's Windows binary of Crafty must be broken somehow.
Because Leo doesn't seem to visit this forum often, it is probably better to continue the discussion on the WBEC forum.
Tord
I guess my post did serve some purpose.. I have never seen crafty doing the above things, so I was surprised when I saw them at Leo's site. Then again, I dont ever check the games for any errors, I just assume that Arena handles them correctly..
Tord Romstad wrote:... there is no draw detection tool involved. ... These stalemate claims must be originating in Crafty; there is no other possibility....
I mean this: "Analyze result:* {no draw found}". That is from LGpgnver and it seems to be a "false negative" alarm.
I have checked all Crafty games I have played here. Unfortunately there is no single stalemate among them.
Best would have been if a bug report would have been send to Bob in the first place.
Tord Romstad wrote:... there is no draw detection tool involved. ... These stalemate claims must be originating in Crafty; there is no other possibility....
I mean this: "Analyze result:* {no draw found}". That is from LGpgnver and it seems to be a "false negative" alarm.
Volker
Why ? It's not a stalemate, it's not insificient material, it's not a repetition nor 50 moves rule. So "no draw found"