questions on using cutechess

[Mateusz]

Hi,
I have the same problem with Atak and ping command.

C:\cutechess-cli\cutechess-cli.exe -fcp name=Atak cmd=Atak.exe dir=C:\atak\release\ proto=xboard -scp cmd=gosu-016 dir=C:\Engines\Gosu\ proto=xboard -both tc=80/12 -games 2 -debug -pgnout games.pgn

Message after game:
Engine "Atak" failed to respond to ping.

[Kempelen]

Hi,
I have the same problem with Atak and ping command.

C:\cutechess-cli\cutechess-cli.exe -fcp name=Atak cmd=Atak.exe dir=C:\atak\release\ proto=xboard -scp cmd=gosu-016 dir=C:\Engines\Gosu\ proto=xboard -both tc=80/12 -games 2 -debug -pgnout games.pgn

Message after game:
Engine "Atak" failed to respond to ping.

My engine Rodin has the same problem. It show that message too after the game ends.

[ilari]

Sorry about taking so long to fix this, I had some more urgent things to do.
But I think I've solved the problem now. Some details:

- Cutechess-cli does NOT send the "ping" command to engines that don't send the "ping=1" feature string. The reason you may see the "failure to respond to ping" error is because of some trickery that we must do to make sure that a new game can be started.
- This is a serious bug, but it's in the Qt 4.5.0 libraries, not in cutechess-cli. The bug causes timers to misfire under certain conditions, and it was apparently fixed in Qt 4.5.1.
- The bug is specific to the Windows version of Qt, which is why I didn't catch it in my testing. I do over 90% of my testing in Linux.

So Mac and Linux users don't have to do anything. Windows users should either download the binary package again (it now uses Qt 4.5.3), or update their Qt version to 4.5.3 if they're compiling from source. Engines like Atak and Rodin should then work just fine.

The updated cutechess-cli package for Windows: http://koti.mbnet.fi/~ilaripih/bin/cute ... -win32.zip

[Kempelen]

Sorry about taking so long to fix this, I had some more urgent things to do.
But I think I've solved the problem now. Some details:

- Cutechess-cli does NOT send the "ping" command to engines that don't send the "ping=1" feature string. The reason you may see the "failure to respond to ping" error is because of some trickery that we must do to make sure that a new game can be started.
- This is a serious bug, but it's in the Qt 4.5.0 libraries, not in cutechess-cli. The bug causes timers to misfire under certain conditions, and it was apparently fixed in Qt 4.5.1.
- The bug is specific to the Windows version of Qt, which is why I didn't catch it in my testing. I do over 90% of my testing in Linux.

So Mac and Linux users don't have to do anything. Windows users should either download the binary package again (it now uses Qt 4.5.3), or update their Qt version to 4.5.3 if they're compiling from source. Engines like Atak and Rodin should then work just fine.

The updated cutechess-cli package for Windows: http://koti.mbnet.fi/~ilaripih/bin/cute ... -win32.zip

In a quick test seems to work. thanks

[ilari]

In a quick test seems to work. thanks

I'm glad to hear that, because I almost lost my mind trying to find the non-existent bug in our source code. At least I learned not to blindly trust libraries, even if they're extensively tested like Qt.

[Mateusz]

Hi,
It seems that it works.
This line is ok.
C:\Engines\cutechess-cli\cutechess-cli.exe -fcp name=Atak cmd=Atak.exe dir=C:\atak\release\ proto=xboard -scp cmd=gosu-016 dir=C:\Engines\Gosu\ proto=xboard -both tc=80/5 -games 2 -pgnout games.pgn

but...
I have changed engine to Matacz and it not works with this engine.

C:\Engines\cutechess-cli\cutechess-cli.exe -fcp name=Atak cmd=Atak.exe dir=C:\atak\release\ proto=xboard -scp cmd=Matacz dir=C:\Engines\Matacz\ proto=xboard -both tc=80/1 -games 2 -pgnout gamesM.pgn -debug

Started game 1 of 2
0 <Atak(0):
0 <Atak(0): ATAK 6.7
0 <Atak(0): (c) 2009 Mateusz Luksik
16 <Atak(0):
16 <XboardEngine(1):
16 <XboardEngine(1): feature done=0
16 <XboardEngine(1): feature setboard=1

[ilari]

but...
I have changed engine to Matacz and it not works with this engine.

C:\Engines\cutechess-cli\cutechess-cli.exe -fcp name=Atak cmd=Atak.exe dir=C:\atak\release\ proto=xboard -scp cmd=Matacz dir=C:\Engines\Matacz\ proto=xboard -both tc=80/1 -games 2 -pgnout gamesM.pgn -debug

Started game 1 of 2
0 <Atak(0):
0 <Atak(0): ATAK 6.7
0 <Atak(0): (c) 2009 Mateusz Luksik
16 <Atak(0):
16 <XboardEngine(1):
16 <XboardEngine(1): feature done=0
16 <XboardEngine(1): feature setboard=1

Did cutechess-cli crash there? If not, it's probably waiting for "done=1". I'll try Matacz tomorrow...

[Mateusz]

Hi,
"Did cutechess-cli crash there?" - No.

Regards,
Mat

[Mateusz]

One more bug [Black "XboardEngine"] ?

[Event "?"]
[Site "?"]
[Date "2009.11.30"]
[Round "1"]
[White "AtakTEST"]
[Black "XboardEngine"]
[Result "0-1"]
[PlyCount "112"]
[TimeControl "80/5"]

[ilari]

One more bug [Black "XboardEngine"] ?

[Event "?"]
[Site "?"]
[Date "2009.11.30"]
[Round "1"]
[White "AtakTEST"]
[Black "XboardEngine"]
[Result "0-1"]
[PlyCount "112"]
[TimeControl "80/5"]

That's probably not a bug. I the engine doesn't use the "myname" feature, cutechess-cli will just call it "XboardEngine". You can define a name with the "name" command line argument:

Code: Select all

cutechess-cli -fcp cmd=matacz.exe name=Matacz