Code: Select all
# nps=136533 bf=4.1 nodesQS=6786 (82.8%) nodesDepth0=4545 (55.5%) nodesDraw=0 ( 0.0%) nodesHashHit=146 ( 1.8%)
1. ...?
2. ...?
3. ...?
No, all wrong
WinBoard terminates the game with a draw. Can you see why? The line starts with a '#' which explicitly advises newer WinBoard versions to ignore the whole line according to the spec. However, it does not ignore it, no matter whether I specifiy the "/engineDebugOutput 1" command line option or not.
If I change the word "nodesDraw" into something that does not contain the word "draw" in any upper-lower-case combination then the game is not terminated (I did not try the words "result", "resign", "mated", or "quit", however ...).
I found this behaviour with quite an old WinBoard version (4.3.14k) as well as with the very recent 4.4.2b, so I guess it's an older bug.
Two problems involved IMO:
1) not ignoring "# comment" lines;
2) taking the occurrence of the string "draw" anywhere within an input line as a draw claim, which in turn triggers WB to terminate the game if it is configured this way.
I can get a decent ELO with those 50% against all world's top engines So I'm beginning to like that pro-amateur feature ...
Extract from winboard.debug:
Code: Select all
1344 <first : 4 23 0 994 e2e4 b8c6 g1f3 e7e5
1344 <first : 4 0 1 2276 e2e4 b8c6 b1c3 e7e5
1391 <first : # stopped search (timeout)
1391 <first : 5 0 6 8192 e2e4 b8c6 b1c3 e7e5
1391 <first : # nps=136533 bf=4.1 nodesQS=6786 (82.8%) nodesDepth0=4545 (55.5%) nodesDraw=0 ( 0.0%) nodesHashHit=146 ( 1.8%)
1391 <first : GameEnds(39, Draw, 5)
1391 >first : result 1/2-1/2 {Draw}
1391 >second: result 1/2-1/2 {Draw}