Cute Chess 0.9.0 (GUI) released

[ilari]

It happens, when I start a human vs Komdodo 9.x game, an engine-engine game or a tournament.

When I want to start a game, the error appears immediately after I click OK in the New Game dialog and I am prompted to the default tab.

When I am running a tournament everything works fine until the first game with Komodo. The engine process and the tournament gets stopped.

I don't have Komodo 9.x but I made a new Windows executable that launches a console where you can see all of Cute Chess' warning and debug output. Can you try it and report the console output to me: https://github.com/cutechess/cutechess/issues/126

[ilari]

Have you created a manual for the GUI yet?

No - things are changing so quickly that any manual would always be full of outdated information. And I think manuals are old-fashioned anyway. I'm planning on making some videos where I show how to do different things with Cute Chess, once we have a stable 1.0 release.

[pferd]

It happens, when I start a human vs Komdodo 9.x game, an engine-engine game or a tournament.

When I want to start a game, the error appears immediately after I click OK in the New Game dialog and I am prompted to the default tab.

When I am running a tournament everything works fine until the first game with Komodo. The engine process and the tournament gets stopped.

I don't have Komodo 9.x but I made a new Windows executable that launches a console where you can see all of Cute Chess' warning and debug output. Can you try it and report the console output to me: https://github.com/cutechess/cutechess/issues/126

Unfortunately I am running Linux, so I cannot use this executable.

Is there a quick way how I can do a debug compile?

In the meantime I tested cutechess on my second machine with Ubuntu and encountered the same problem.

[Guenther]

It happens, when I start a human vs Komdodo 9.x game, an engine-engine game or a tournament.

When I want to start a game, the error appears immediately after I click OK in the New Game dialog and I am prompted to the default tab.

When I am running a tournament everything works fine until the first game with Komodo. The engine process and the tournament gets stopped.

I don't have Komodo 9.x but I made a new Windows executable that launches a console where you can see all of Cute Chess' warning and debug output. Can you try it and report the console output to me: https://github.com/cutechess/cutechess/issues/126

Unfortunately I am running Linux, so I cannot use this executable.

Is there a quick way how I can do a debug compile?

In the meantime I tested cutechess on my second machine with Ubuntu and encountered the same problem.

Does Komodo 9.x work from the console?

It is possible that it refuses to start, because somehow it thinks it is not registered, even when you have bought a legal copy.
(BTW I don't know how much working copies can be moved to different computers)

[Guenther]

Just another suggestion:

It would be nice to have a count number in the engine installation dialogue.

[pferd]

Does Komodo 9.x work from the console?

It is possible that it refuses to start, because somehow it thinks it is not registered, even when you have bought a legal copy.
(BTW I don't know how much working copies can be moved to different computers)

Komodo 9.x does work for me from command-line, cutechess-cli and scidvs-pc but not in cutechess.

I downloaded komodo 9.x again earlier this week, but that did not change things.

[ilari]

It happens, when I start a human vs Komdodo 9.x game, an engine-engine game or a tournament.

When I want to start a game, the error appears immediately after I click OK in the New Game dialog and I am prompted to the default tab.

When I am running a tournament everything works fine until the first game with Komodo. The engine process and the tournament gets stopped.

I don't have Komodo 9.x but I made a new Windows executable that launches a console where you can see all of Cute Chess' warning and debug output. Can you try it and report the console output to me: https://github.com/cutechess/cutechess/issues/126

Unfortunately I am running Linux, so I cannot use this executable.

Is there a quick way how I can do a debug compile?

In the meantime I tested cutechess on my second machine with Ubuntu and encountered the same problem.

Sorry, I made the wrong assumption. On Linux you already get the console output if you just run the "cutechess" or "/usr/games/cutechess" command from the command line.

EDIT: If you want to make a debug build you can pass the "-debug" parameter to "qmake". Or "CONFIG+=debug" if plain "-debug" doesn't work.

[ilari]

Just another suggestion:

It would be nice to have a count number in the engine installation dialogue.

Good idea. I always forget that some people have a ton of chess engines on their computer.

[pferd]

EDIT: If you want to make a debug build you can pass the "-debug" parameter to "qmake". Or "CONFIG+=debug" if plain "-debug" doesn't work.

Neither of these options did work for me. I did add -g directly to the Makefile, compiled again and attached it to gdb.

I am no programmer, although I coded a bit in my free time. So I am not sure if the following helps at all.

Here is the output if I try to start a komodo9 vs human game:

Code: Select all

gdb ./cutechess
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./cutechess...sdone.
(gdb) set follow-fork-mode child
(gdb) run
Starting program: /home/tobias/chess/tuning/cutechess/projects/gui/cutechess 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeaf0a700 (LWP 20223)]
[New Thread 0x7fffdd576700 (LWP 20224)]
[New Thread 0x7fffd7fff700 (LWP 20225)]
[New Thread 0x7fffd53de700 (LWP 20226)]
[New Thread 0x7fffd4bdd700 (LWP 20227)]
[New Thread 0x7fffcd4d1700 (LWP 20228)]
[New Thread 0x7fffcccd0700 (LWP 20229)]
[New Thread 0x7fffcc11b700 (LWP 20230)]
[New process 20231]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 20231 is executing new program: /home/tobias/chess/engines/Komodo/komodo-9_11b14c11/Linux/komodo-9.02-linux
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe1977700 (LWP 20232)]

Thread 2.1 "komodo-9.02-lin" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7fc0600 (LWP 20231)]
0x00007ffff71f9b64 in fclose@@GLIBC_2.2.5 () from /usr/lib/libc.so.6
(gdb) Engine Komodo 9.02 64-bit(0) failed to respond to ping
Terminating process of engine Komodo 9.02 64-bit(0)
quit
A debugging session is active.

        Inferior 2 [process 20231] will be killed.

Quit anyway? (y or n) y

And here the same with komodo8:

Code: Select all

gdb ./cutechess 
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./cutechess...done.
(gdb) set follow-fork-mode child
(gdb) r
Starting program: /home/tobias/chess/tuning/cutechess/projects/gui/cutechess 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeaf0a700 (LWP 19863)]
[New Thread 0x7fffdd576700 (LWP 19864)]
[New Thread 0x7fffd7fff700 (LWP 19865)]
[New Thread 0x7fffd53de700 (LWP 19866)]
[New Thread 0x7fffd4bdd700 (LWP 19867)]
[New Thread 0x7fffcd4d1700 (LWP 19868)]
[New Thread 0x7fffcccd0700 (LWP 19869)]
[New Thread 0x7fffcc11b700 (LWP 19870)]
[New process 19871]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 19871 is executing new program: /home/tobias/chess/engines/Komodo/komodo-8_2cceec89/Linux/komodo-8-linux
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe1977700 (LWP 19872)]
[Thread 0x7fffe1977700 (LWP 19872) exited]
[Inferior 2 (process 19871) exited normally]

I tested it on my main machine (arch linux) and my laptop (ubuntu) and the output does look similar on both.

And here you can see it running a game on cutechess-cli

Code: Select all

gdb ./cutechess-cli 
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./cutechess-cli...done.
(gdb) set follow-fork-mode child
(gdb) r -engine name="Komodo 9.02 64-bit" cmd=/home/tobias/chess/engines/Komodo/komodo-9_11b14c11/Linux/komodo-9.02-linux -engine name="Stockfish 070916 64 BMI2" cmd=/home/tobias/chess/engines/Stockfish/src/stockfish  -each proto=uci tc=5+0.05 -pgnout ./test.pgn
Starting program: /home/tobias/chess/tuning/cutechess/projects/cli/cutechess-cli -engine name="Komodo 9.02 64-bit" cmd=/home/tobias/chess/engines/Komodo/komodo-9_11b14c11/Linux/komodo-9.02-linux -engine name="Stockfish 070916 64 BMI2" cmd=/home/tobias/chess/engines/Stockfish/src/stockfish  -each proto=uci tc=5+0.05 -pgnout ./test.pgn
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff2693700 (LWP 20884)]
[New process 20885]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 20885 is executing new program: /home/tobias/chess/engines/Komodo/komodo-9_11b14c11/Linux/komodo-9.02-linux
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe1977700 (LWP 20888)]
Started game 1 of 1 (Komodo 9.02 64-bit vs Stockfish 070916 64 BMI2)
Finished game 1 (Komodo 9.02 64-bit vs Stockfish 070916 64 BMI2): 0-1 {Black mates}
Score of Komodo 9.02 64-bit vs Stockfish 070916 64 BMI2: 0 - 1 - 0  [0.000] 1
ELO difference: -inf +/- nan
Finished match
[Thread 0x7fffe1977700 (LWP 20888) exited]
[Inferior 2 (process 20885) exited normally]
(gdb) 

[Ferdy]

Suprise surprise, there were still bugs in the 0.9.1 release so I've fixed them and released version 0.9.2: https://github.com/cutechess/cutechess/ ... /gui-0.9.2

Suggestion:
Add Termination tag pair in the tag section for games that are not terminated normally, so that it is easier to notice visually looking at the tag section and easier to parse by scripts.

In the case below that can be,

Code: Select all

[Termination "Illegal move"] 

In other case,

Code: Select all

[Termination "Time forfeit"] 

Code: Select all

[Event "CCVA Double Elim Tour Nr 4"] 
[Site "i7-2600K"] 
[Date "2016.09.10"] 
[Round "1"] 
[White "TJchess 1.3 64bit"] 
[Black "Sjeng 11.2 32bit"] 
[Result "1-0"] 
[PlyCount "65"] 
[TimeControl "60"] 
[Variant "crazyhouse"] 

1. d3 {book} e6 {book} 2. Nf3 {book} Nc6 {book} 3. e4 {book} Nf6 {book} 
4. Nc3 {book} Bb4 {book} 5. Bg5 {book} h6 {+0.22/7 2.9s} 6. Bd2 {-0.27/10 1.1s} 
d6 {+0.52/7 2.7s} 7. Be2 {-0.13/10 0.83s} Ng4 {+0.87/7 1.5s} 
8. O-O {+0.44/10 0.98s} Bd7 {-0.39/7 3.9s} 9. Na4 {+0.37/11 6.9s} 
Bxd2 {+0.97/8 2.0s} 10. Qxd2 {+0.48/10 0.59s} Nce5 {+0.12/7 3.5s} 
11. Nxe5 {+0.31/10 1.5s} Nxe5 {+0.54/7 1.5s} 12. Nc3 {+0.43/10 1.8s} 
N@d4 {-0.76/6 1.2s} 13. B@e3 {+0.50/10 1.6s} Nxe2+ {+0.79/6 1.4s} 
14. Qxe2 {+0.55/10 1.1s} B@b4 {+0.22/7 1.9s} 15. N@h5 {+0.97/10 1.4s} 
Rg8 {-1.08/6 1.5s} 16. N@g4 {+1.07/10 2.3s} Qh4 {+0.90/6 1.9s} 
17. Nxe5 {+1.25/9 0.95s} dxe5 {+0.54/4 0.048s} 18. N@b5 {+1.51/8 0.67s} 
B@b8 {+0.05/5 0.65s} 19. Nxc7+ {+2.42/9 0.88s} Bxc7 {+0.36/6 0.80s} 
20. P@h7 {+0.69/9 1.6s} Rh8 {-1.74/6 1.0s} 21. Nxg7+ {+1.64/9 1.5s} 
Kd8 {-0.58/6 1.8s} 22. Nxe6+ {+2.66/9 1.4s} fxe6 {-1.06/6 1.0s} 
23. P@g7 {+3.01/8 0.49s} Rxh7 {-2.22/6 1.2s} 24. g8=Q+ {+3.44/9 0.88s} 
N@f8 {-2.23/5 1.1s} 25. P@g7 {+2.93/9 1.2s} Rxg7 {-4.15/6 0.82s} 
26. Qxg7 {+4.74/9 2.4s} P@f4 {-4.00/5 1.3s} 27. R@h5 {+6.21/8 1.6s} 
Qe7 {-3.16/6 0.76s} 28. Qxe7+ {+6.76/9 0.56s} Bxe7 {-4.17/5 0.43s} 
29. Bxf4 {+6.58/9 0.97s} exf4 {-1.30/4 0.048s} 30. P@g7 {+8.81/9 0.77s} 
P@b4 {-4.02/4 0.45s} 31. Nb5 {+8.63/8 0.41s} Bxb5 {-3.99/4 0.47s} 
32. Rxb5 {+9.16/7 0.43s} B@c6 {-5.09/5 1.5s} 
33. B@f6 {+9.24/7 0.62s, Black makes an illegal move: q@e8} 1-0

PGN Standard Reference:

http://opensource.apple.com//source/Che ... andard.txt

Code: Select all

9.8.1: Tag: Termination

This takes a string that describes the reason for the conclusion of the game.
While the Result tag gives the result of the game, it does not provide any
extra information and so the Termination tag is defined for this purpose.

Strings that may appear as Termination tag values:

* "abandoned": abandoned game.

* "adjudication": result due to third party adjudication process.

* "death": losing player called to greater things, one hopes.

* "emergency": game concluded due to unforeseen circumstances.

* "normal": game terminated in a normal fashion.

* "rules infraction": administrative forfeit due to losing player's failure to
observe either the Laws of Chess or the event regulations.

* "time forfeit": loss due to losing player's failure to meet time control
requirements.

* "unterminated": game not terminated.