Elements of the ULTIMATE Chess GUI?

Discussion of anything and everything relating to chess playing software and machines.

Moderators: bob, hgm, Harvey Williamson

Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
User avatar
hgm
Posts: 23718
Joined: Fri Mar 10, 2006 9:06 am
Location: Amsterdam
Full name: H G Muller
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by hgm » Fri Apr 26, 2019 8:55 am

Dann Corbit wrote:
Fri Apr 26, 2019 8:25 am
So winboard.INI has been done away with? Providing the same information on the command line does not count. Don't get me wrong. I think winboard is fabulous and I use it a lot. And configurations are broadly improved. But his complaint makes sense to me unless I have missed new developments (not unlikely).
Of course winboard.ini has not done away with. You cannot have persistent settings without saving them on disk. Any GUI that is not totally amnesic has such a file, and hackers will always be able to modify it behind the GUIs back (with a good chance to wreck things).

The point is that it for legitimate use one should never ever touch such files, and preferably not even be aware they exist.

In WinBoard this is not a 'new' development; it has been true for at least 5 years that all settings relevant for what I consider 'normal' use are controlled through the GUI menus. (An example of something that I would consider to go beyond normal use would be to configure WinBoard so that default variant becomes mini-Shogi rather than Chess, and that it would use a special USI mini-Shogi adapter instead of Polyglot. This still requires preparation of a dedicated winboard.ini file for system settings by the one creating the software package.)

Spill_The_Tea
Posts: 22
Joined: Mon Dec 17, 2018 2:33 am
Full name: Jase de Lace

Re: Elements of the ULTIMATE Chess GUI?

Post by Spill_The_Tea » Fri Apr 26, 2019 10:25 am

hgm wrote:
Fri Apr 26, 2019 7:00 am
Spill_The_Tea wrote:
Thu Apr 25, 2019 7:50 pm

Code: Select all

- THINGS THAT ARE ANNOYING TO AVOID
	- don't lag and don't cause losses on time, like Arena does
	- don't force user to work on text files, hand-type engine paths etc. like Winboard does
	- exit gracefully, killing the engine processes (problems with Arena again)
	
This is pure and malicious libel. WinBoard doesn't force the user to work on text files or type engine paths at all. GUIs like Shredder and Fritz do that.
Honey,
Most of that list, was taken from a summary you made on page 6 of this thread found here:
viewtopic.php?f=2&t=65485&start=50#p736348

Which includes the comment verbatim about winboard. It is not my personal opinion, but someone in this thread did find it mildly pesky. Because the nature of this thread is to ask for elements of a more perfect gui, it is also asking on how to improve from existing guis. If anything, be proud that winboard is actually mentioned. It means people are using it because there are many that are not.

The reason I do not use winboard, is because I am on macOS, and while I could use it through wine, I find it easier to pursue alternatives. But this is also the same reason I avoid Tarrasch and Arena. Which says nothing about the quality of either gui, but rather their portability.

User avatar
hgm
Posts: 23718
Joined: Fri Mar 10, 2006 9:06 am
Location: Amsterdam
Full name: H G Muller
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by hgm » Wed May 01, 2019 7:08 am

No, that is completely insane. One should not be 'proud to be mentioned' if newspapers print you are a child molester.

It was already pointed out by me in the thread you refer to that WinBoard doesn't "force user to work on text files, hand-type engine paths etc. like Winboard does". I am not accusing you of making it up (just of careless reading), but no matter who made it up, it still is malicious libel, you propagate it, and its nature should be revealed to all no matter where it appears.

If someone finds things that do not occur in real life 'mildly pesky', he just qualifies as an idiot, and there is no reason to address the non-existent problem.

BTW, WinBoard is available for Mac, as XBoard. It is even released as an OSX App.

Javier Ros
Posts: 181
Joined: Fri Oct 12, 2012 10:48 am
Location: Seville (SPAIN)
Full name: Javier Ros

Re: Elements of the ULTIMATE Chess GUI?

Post by Javier Ros » Wed May 01, 2019 9:05 am

I think that one important thing for testing chess engines is the different time control for each side.

As far as I know only cutechess-cli and aquarium have this feature.

Is it so difficult to program this?
The love relationship between a chess engine tester and his computer can be summarized in one sentence:
Until heat do us part.

User avatar
hgm
Posts: 23718
Joined: Fri Mar 10, 2006 9:06 am
Location: Amsterdam
Full name: H G Muller
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by hgm » Wed May 01, 2019 10:45 am

WinBoard/XBoard support time odds as well, of course. Just not different TC modes. Not because it would be difficult to program, but because it seems completely useless, or even worth discouraging.

Raphexon
Posts: 92
Joined: Sun Mar 17, 2019 11:00 am
Full name: Henk Drost

Re: Elements of the ULTIMATE Chess GUI?

Post by Raphexon » Wed May 01, 2019 3:10 pm

hgm wrote:
Wed May 01, 2019 10:45 am
WinBoard/XBoard support time odds as well, of course. Just not different TC modes. Not because it would be difficult to program, but because it seems completely useless, or even worth discouraging.
It's interesting to test with different TCs.
Even if it has no real use. Just different numbers.
It's like "playing" an idle clicker game. Total waste of time and electricity but sometimes you just have that urge to know what kind of time advantage Igel needs to beat Stockfish.

User avatar
Guenther
Posts: 3046
Joined: Wed Oct 01, 2008 4:33 am
Location: Regensburg, Germany
Full name: Guenther Simon
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by Guenther » Wed May 01, 2019 3:29 pm

Raphexon wrote:
Wed May 01, 2019 3:10 pm
hgm wrote:
Wed May 01, 2019 10:45 am
WinBoard/XBoard support time odds as well, of course. Just not different TC modes. Not because it would be difficult to program, but because it seems completely useless, or even worth discouraging.
It's interesting to test with different TCs.
Even if it has no real use. Just different numbers.
It's like "playing" an idle clicker game. Total waste of time and electricity but sometimes you just have that urge to know what kind of time advantage Igel needs to beat Stockfish.
Note that HGM spoke off different TC 'modes' not plain time odds like you seem to suggest for your tests.
I have to admit though that I ran into some problems with time odds in WB.
Current foe list count : [97]
http://rwbc-chess.de/chronology.htm

User avatar
hgm
Posts: 23718
Joined: Fri Mar 10, 2006 9:06 am
Location: Amsterdam
Full name: H G Muller
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by hgm » Wed May 01, 2019 4:30 pm

For clarity, 'TC mode' means classical (M minutes per session of N moves), incremental/sudden death (M minutes + S sec/move) or fixed time per move. I don't see any legitimate use case for playing, say, 40 moves/min vs 2 sec/move. Or even 40 moves/min vs 30 moves/45sec.

As I said, normal time odds (= same mode, but all times multiplied by a factor for one of the players) is supported by WinBoard, and is what you would use to measure how much more time Igel needs than Stockfish to become equally strong. I am not aware of any problems with it; in the past I used it often (e.g. to fill the gaps in a rating list for a variant that only a handful of engines of wildly different strength could play).

User avatar
Guenther
Posts: 3046
Joined: Wed Oct 01, 2008 4:33 am
Location: Regensburg, Germany
Full name: Guenther Simon
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by Guenther » Wed May 01, 2019 4:51 pm

hgm wrote:
Wed May 01, 2019 4:30 pm
I am not aware of any problems with it; in the past I used it often (e.g. to fill the gaps in a rating list for a variant that only a handful of engines of wildly different strength could play).
viewtopic.php?f=2&t=62034&p=696247&hili ... rd#p696247
Current foe list count : [97]
http://rwbc-chess.de/chronology.htm

User avatar
hgm
Posts: 23718
Joined: Fri Mar 10, 2006 9:06 am
Location: Amsterdam
Full name: H G Muller
Contact:

Re: Elements of the ULTIMATE Chess GUI?

Post by hgm » Wed May 01, 2019 5:59 pm

Guenther wrote:
Sat Aug 05, 2017 2:39 pm
There still seems to be a bug in TimeOdds?
I wanted to create a little tournament about how balanced/drawish usual start positions are regarding time odds,
but in that tournament the time odds did not follow a player but a specific colour.
(To make this visible I marked the side with 8* more time to play in my example pgn bold + blue)

May be it was not intended for what I did, namely playing each start position twice with colours reversed in a tournament with more than 2 players?
This was the WB 01/2017 release.

I also noticed that time odds does not divide the inc, but only the main base time is divided, thus I started again with a smaller inc.
(May be I should try fixed time per move for this test though)

(There were other obstacles too, but mostly engine related - Andscacs e.g. had a 'too clever time management' for this kind of test and would
give unreliable results, because it uses already most of its time in the first 20 moves.
If the other engine survives the position until there with a non-decisive score it even remains with more time instead by factor x less)

[Event "RWBC"]
[Site "CAPPUCCINO"]
[Date "2017.08.05"]
[Round "1"]
[White "Fizbo_19-64"]
[Black "Booot_62-64#8"]
[Result "0-1"]
[TimeControl "240+0"]
[Number "1"]
[Annotator "2. +0.39 2... -0.58"]

1. e4 c6 2. d4 {+0.39/12 0.5} d5 {-0.58/20 10} 3. exd5 {+0.22/12 1.0} cxd5
{-0.29/19 7} 4. Nf3 {+0.41/11 0.9} Nf6 {-0.08/19 9} 5. c3 {+0.22/11 0.8}
Bf5 {-0.08/18 6} 6. Bd3 {+0.23/11 0.8} Bxd3 {-0.08/24 8} 7. Qxd3
{+0.13/14 0.5} Nc6 {-0.08/24 6} 8. Nbd2 {+0.39/13 1.2} e6 {+0.27/20 6} 9.
O-O {+0.32/14 1.3} Bd6 {+0.14/19 5} 10. Nb3 {+0.37/13 0.5} h6 {+0.40/19 6}
11. Be3 {+0.45/13 0.5} O-O {+0.37/18 7} 12. Rae1 {+0.29/14 0.9} Rc8
{+0.39/20 7} 13. Na1 {+0.30/14 0.9} Na5 {+0.61/19 7} 14. Bc1 {+0.47/13 0.7}
Ne4 {+0.69/20 13} 15. Re2 {+0.32/15 1.6} Qc7 {+0.77/19 5} 16. Rfe1
{+0.36/13 1.3} a6 {+0.71/19 4} 17. h3 {+0.09/13 0.7} b5 {+0.92/17 4} 18.
Nd2 {-0.05/12 0.8} Nf6 {+1.00/19 4} 19. Nf3 {-0.05/13 1.6} b4 {+0.78/20 3}
20. cxb4 {-0.27/14 0.9} Bxb4 {+0.76/21 4} 21. Rc2 {-0.33/15 0.6} Qb6
{+0.80/22 3} 22. Ree2 {-0.24/12 0.6} Bd6 {+0.67/22 6} 23. Be3
{-0.44/13 1.5} Nc4 {+0.69/21 5} 24. Bc1 {-0.63/14 1.0} Ne4 {+0.88/18 3} 25.
Re1 {-0.70/14 0.8} Rfd8 {+1.18/17 2.9} 26. Rce2 {-0.84/12 1.8} Qa5
{+1.09/17 3} 27. Qb1 {-0.88/13 1.9} Rc7 {+1.35/17 4} 28. a3 {-1.02/14 2.2}
Qb5 {+2.01/19 3} 29. a4 {-2.19/12 1.2} Qxa4 {+2.67/20 2.5} 30. Rc2
{-2.58/13 1.5} Qb5 {+2.86/21 3} 31. Qa2 {-2.77/14 1.2} Rdc8 {+2.67/22 3}
32. b3 {-3.11/14 1.4} Nb6 {+2.53/20 2.4} 33. Rxc7 {-3.00/14 1.4} Rxc7
{+2.42/20 2.4} 34. Qb2 {-3.03/14 1.3} a5 {+2.85/21 2.0} 35. Ne5
{-3.60/14 1.5} Bb4 {+3.54/20 2.3} 36. Rd1 {-5.22/13 1.1} a4 {+3.42/21 2.4}
37. Bf4 {-5.18/14 1.0} a3 {+3.99/19 2.5} 38. Qb1 {-5.33/14 1.3} Qe2
{+4.07/20 2.5} 39. Rf1 {-5.52/15 0.8} Bd2 {+4.66/19 1.9} 40. Ng6
{-7.74/14 1.7} Rc3 {+6.10/19 2.0} 41. Bxd2 {-8.40/14 1.1} Nxd2
{+6.73/23 2.0} 42. Re1 {-9.50/15 0.9} Nxb1 {+7.07/24 2.0} 43. Rxe2
{-10.01/16 0.8} Rc1+ {+7.14/22 2.2} 44. Kh2 {-11.54/20 0.9} Nc3
{+7.20/23 2.1} 45. Rc2 {-11.33/19 0.5} Rxa1 {+7.34/23 1.8} 46. Rxc3
{-11.33/1} a2 {+7.82/22 1.5} 47. Ne7+ {-12.42/19 1.0} Kf8 {+9.09/23 3} 48.
Rc7 {-12.65/21 1.6} Rh1+ {+9.13/23 1.7} 49. Kxh1 {-13.62/18 0.8} a1=Q+
{+9.40/22 1.3} 50. Kh2 {-14.31/18 0.9} Qxd4 {+9.55/23 1.4} 51. Rb7
{-14.82/17 1.8} Qxf2 {+9.54/21 1.3} 52. h4 {-15.13/17 0.9} Qxh4+
{+10.52/20 1.3} 53. Kg1 {-15.13/1} Qe1+ {+10.87/19 1.4} 54. Kh2 {-15.13/1}
Qe5+ {+10.97/19 1.4} 55. Kh3 {-15.11/14 0.5} Qf4 {+11.30/17 1.0} 56. Ra7
{-16.61/15 1.0} g5 {+12.86/17 1.1} 57. g4 {-17.37/16 1.2} Qf3+
{+13.58/17 1.4} 58. Kh2 {-17.37/1} Qf2+ {+14.13/17 1.4} 59. Kh3
{-18.37/17 1.3}
{Xboard adjudication} 0-1

[Event "RWBC"]
[Site "CAPPUCCINO"]
[Date "2017.08.05"]
[Round "2"]
[White "Booot_62-64#8"]
[Black "Fizbo_19-64"]
[Result "0-1"]
[TimeControl "240+0"]
[Number "2"]
[Annotator "2. +0.69 2... -0.25"]

1. e4 c6 2. Nf3 {+0.69/15 2.0} d5 {-0.25/15 4} 3. e5 {+0.55/14 0.9} Bf5
{+0.06/15 4} 4. d4 {+0.64/14 1.0} e6 {+0.01/15 7} 5. Be2 {+0.50/15 1.0} Ne7
{+0.07/14 6} 6. O-O {+0.53/13 0.7} Bg6 {-0.12/14 4} 7. Nc3 {+0.85/14 1.1}
Nd7 {+0.12/15 7} 8. Bf4 a6 {+0.36/15 10} 9. a3 {+0.56/14 0.6} Nf5
{+0.52/15 7} 10. g4 {+0.55/13 1.4} Ne7 {+0.70/17 5} 11. b4 {+0.44/15 1.3}
h5 {+1.01/16 4} 12. h3 {+0.46/15 0.6} hxg4 {+0.60/15 9} 13. hxg4
{+0.57/14 0.6} a5 {+0.49/16 7} 14. Qd2 {+0.52/13 0.6} Nc8 {+0.40/17 8} 15.
Na4 {+0.29/12 0.6} Be4 {+0.62/16 5} 16. Rfb1 {+0.03/13 0.6} axb4
{+0.75/15 7} 17. axb4 {+0.21/15 0.6} Ne7 {+0.42/16 9} 18. Nc5
{+0.43/15 0.6} Rxa1 {+0.08/17 6} 19. Rxa1 {+0.50/17 0.5} Nxc5 {+0.09/18 5}
20. bxc5 {+0.53/18 0.6} Ng6 {+0.03/18 4} 21. Bg3 {+0.37/17 0.5} Be7
{+0.03/16 5} 22. Qb4 {+0.48/17 0.5} b5 {-0.14/17 8} 23. Ra6 {+0.67/16 0.5}
Qc7 {-0.44/17 10} 24. Ra8+ {+0.53/15 0.5} Bd8 {-0.50/19 5} 25. Qb1
{+0.44/15 0.5} Qe7 {+0.01/17 7} 26. Bh2 {+0.43/11 0.4} f5 {+1.59/15 5} 27.
Qb3 {-0.88/12 0.4} fxg4 {+2.83/17 4} 28. Nd2 Nf4 {+5.21/17 7} 29. Bxb5
{-2.23/14 0.4} Rxh2 {+25.26/17 8} 30. Nxe4 {-0.82/11 0.4} Qh4 {+99.81/17 7}
31. Ng3 Qh3 {+99.85/18 4} 32. Bxc6+ {-1000.09/17 0.4} Kf7 {+99.85/19 4} 33.
Bxd5 {-1000.08/19 0.4} Nxd5 {+99.87/18 5} 34. Ra7+ {-1000.07/24 0.4}
{Xboard adjudication} 0-1

[Event "RWBC"]
[Site "CAPPUCCINO"]
[Date "2017.08.05"]
[Round "3"]
[White "Fizbo_19-64"]
[Black "Booot_62-64#8"]
[Result "1-0"]
[TimeControl "240+0"]
[Number "3"]
[Annotator "2. +0.25 2... -0.03"]

1. e4 c5 2. d4 {+0.25/11 1.2} cxd4 {-0.03/18 9} 3. c3 {+0.31/11 0.4} e5
{-0.10/20 9} 4. cxd4 {+0.33/12 0.9} exd4 {-0.12/20 9} 5. Nf3 {+0.50/11 0.9}
Bc5 {-0.11/18 14} 6. Bc4 {+0.24/11 0.7} Nf6 {+0.22/19 6} 7. O-O
{+0.18/12 1.1} O-O {+0.08/21 7} 8. Bg5 {+0.17/12 0.4} h6 {+0.50/20 6} 9.
Bh4 {+0.18/12 0.5} g5 {+1.08/20 6} 10. Bg3 {+0.17/12 0.5} Nxe4 {+0.57/18 6}
11. Bd5 {+0.10/12 0.7} Nxg3 {+0.60/20 6} 12. hxg3 {+0.10/1} d6 {+0.86/19 6}
13. Nxd4 {+0.01/13 0.9} Nc6 {+0.73/20 6} 14. Nb3 {-0.32/12 0.8} Bb6
{+0.72/19 6} 15. Nc3 {-0.27/12 0.7} Bf5 {+0.64/18 7} 16. Na4 {-0.38/13 1.8}
Be6 {+0.55/17 5} 17. Nxb6 {+0.04/13 0.5} axb6 {+0.61/20 5} 18. Bxe6
{+0.14/14 0.7} fxe6 {+0.81/19 5} 19. Nd4 {+0.04/15 0.9} Qd7 {+0.72/19 4}
20. Re1 {+0.32/13 1.0} Rae8 {+0.42/17 4} 21. Qd3 {+0.39/13 0.6} Rf6
{+0.40/17 3} 22. Rad1 {+0.53/13 1.0} d5 {+0.48/20 4} 23. Nf3 {+0.59/12 0.9}
Ref8 {+0.49/17 3} 24. Rd2 {+0.40/14 1.8} Qf7 {+0.58/18 3} 25. Qc2
{+0.40/14 1.4} Ra8 {+0.47/18 6} 26. a3 {+0.61/13 0.7} Rf8 {+0.38/20 4} 27.
Qd1 {+0.53/14 2.3} g4 {+0.36/18 2.9} 28. Ne5 {+0.65/14 1.5} Nxe5
{+0.14/20 3} 29. Rxe5 {+0.65/1} Qg6 {+0.00/22 3} 30. Qc1 {+0.83/15 1.3} Rf5
{+0.08/17 2.9} 31. Ree2 {+0.83/15 1.8} h5 {+0.03/18 3} 32. Qc7
{+1.03/15 1.3} Qf7 {-0.11/17 4} 33. Qd6 {+1.65/16 1.9} Re8 {-0.15/18 2.1}
34. Qxb6 {+1.73/15 0.8} Re7 {-0.22/18 2.6} 35. Rc2 {+1.83/15 0.8} Kg7
{+0.00/21 2.6} 36. Rc8 {+1.58/15 1.3} e5 {+0.00/23 2.9} 37. Rec2
{+2.13/14 1.2} Qe6 {+0.00/23 2.1} 38. Qd8 {+1.92/15 1.2} Kg6 {+0.00/22 1.8}
39. R2c7 {+1.60/15 1.9} Rff7 {+0.00/21 1.8} 40. Rxe7 {+1.57/16 2.3} Rxe7
{+0.00/21 2.2} 41. Qh8 {+1.44/16 1.3} Rg7 {+0.00/22 2.2} 42. Re8
{+1.44/16 1.5} Qd6 {+0.00/22 1.7} 43. Rd8 {+1.61/16 1.3} Qe6 {-0.61/19 2.1}
44. a4 {+1.55/16 1.3} d4 {+0.00/21 1.8} 45. b4 {+1.66/15 1.0} Qf6
{-0.45/16 1.4} 46. a5 {+2.24/14 0.6} Qe6 {-0.97/17 1.6} 47. Re8
{+2.21/14 1.0} Qd6 {+0.00/19 4} 48. b5 {+2.85/16 1.8} Qf6 {-1.44/16 3} 49.
a6 {+2.96/14 1.0} bxa6 {-2.17/15 1.3} 50. bxa6 {+3.08/14 1.1} d3
{-2.50/15 1.4} 51. Rd8 {+4.12/14 1.1} d2 {-2.10/16 1.2} 52. Rxd2
{+4.66/14 0.6} Qxa6 {-2.55/14 2.7} 53. Qf8 {+5.13/16 0.6} Kh7
{-2.15/16 1.0} 54. Rd6 {+5.15/16 1.1} Qa1+ {-2.73/16 1.3} 55. Kh2
{+5.44/17 0.9} Qb1 {-2.88/19 1.1} 56. Re6 {+5.31/17 0.9} Qb5 {-2.54/16 0.9}
57. Qd6 {+5.31/15 0.9} Kg8 {-2.99/15 1.3} 58. Rxe5 {+6.02/14 1.0} Qd7
{-2.99/15 2.1} 59. Qb8+ {+6.35/14 0.6} Kf7 {-2.53/17 0.8} 60. Ra5
{+7.41/15 1.8} Qc6 {-3.15/15 1.0} 61. Qh8 {+7.41/13 0.7} Qb7 {-3.59/15 1.0}
62. Qxh5+ {+8.05/14 0.9} Rg6 {-3.75/17 0.9} 63. Qh7+ {+9.26/14 0.5} Rg7
{-6.39/15 0.8} 64. Qh8 {+9.86/15 0.6} Qc7 {-6.39/15 1.6} 65. Qh5+
{+10.08/15 1.0} Ke7 {-6.53/18 0.8} 66. Qf5 {+10.34/15 0.6} Qxa5
{-6.71/15 0.6} 67. Qxa5 {+10.34/1} Rh7+ {-6.76/14 0.7} 68. Kg1
{+10.70/16 0.5} Rg7 {-6.96/15 0.6} 69. f3 {+10.83/16 0.7} gxf3
{-6.95/13 0.6} 70. Qe5+ {+11.24/15 0.6} Kf8 {-7.09/14 0.7} 71. gxf3
{+11.29/16 1.1} Re7 {-7.51/14 0.7} 72. Qf6+ {+11.48/17 1.2} Rf7
{-7.68/13 0.6} 73. Qa1 {+11.48/16 0.5} Kg8 {-7.92/14 0.6} 74. Kg2
{+12.00/17 0.5} Re7 {-7.92/12 0.6} 75. g4 {+12.00/17 1.1} Rc7
{-7.94/13 0.6} 76. Kg3 {+12.67/16 0.5} Re7 {-10.80/13 0.6} 77. f4
{+14.90/17 0.8} Re3+ 78. Kh4 {+16.81/19 0.9} Re8 {-10.28/12 0.5} 79. f5
{+19.10/17 1.3} Kf7 {-10.70/12 0.5} 80. g5 {+22.21/17 1.3} Re4+
{-12.13/11 0.5} 81. Kh5 {+22.60/16 0.6} Ke7 {-19.94/11 0.5} 82. g6
{+23.47/15 0.8} Kd6 {-20.14/12 0.5}
{Xboard adjudication} 1-0

[Event "RWBC"]
[Site "CAPPUCCINO"]
[Date "2017.08.05"]
[Round "4"]
[White "Booot_62-64#8"]
[Black "Fizbo_19-64"]
[Result "0-1"]
[TimeControl "240+0"]
[Number "4"]
[Annotator "2. +0.58 2... -0.43"]

1. e4 c5 2. Nf3 {+0.58/15 2.0} e6 {-0.43/14 6} 3. Nc3 {+0.82/14 0.8} b6
{-0.02/16 5} 4. Bc4 {+1.00/15 1.8} Bb7 {+0.00/15 7} 5. d4 {+0.84/14 1.0}
cxd4 {+0.13/15 6} 6. Nxd4 {+0.66/15 0.9} a6 {+0.21/15 8} 7. Bf4
{+0.53/13 1.4} Nf6 {+0.32/14 8} 8. a3 {+0.50/13 1.1} Nxe4 {+0.79/16 5} 9.
Nxe4 {-0.10/14 0.6} Bxe4 {+0.79/1} 10. O-O {+0.04/13 0.6} Qf6 {+0.59/15 5}
11. Qd2 {-0.14/13 1.2} Bc5 {+0.70/15 4} 12. Nb3 {-0.28/13 0.7} Be7
{+1.03/16 6} 13. Rae1 d5 {+1.29/15 3} 14. Bd3 {-0.60/15 0.7} Bxd3
{+1.05/17 4} 15. Be5 {-0.54/16 0.6} Qg6 {+1.45/17 2.9} 16. cxd3
{-0.84/17 0.6} Nd7 {+1.35/17 7} 17. Bc3 {-0.59/15 0.6} O-O {+0.75/16 11}
18. f4 {-0.62/15 0.6} Nc5 {+1.13/17 8} 19. Nxc5 {-0.90/13 0.5} Bxc5+
{+1.55/17 4} 20. d4 {-0.67/13 0.6} Bd6 {+1.74/18 4} 21. Bb4 {-0.55/14 0.5}
Bxb4 {+1.64/17 3} 22. axb4 {-0.97/14 0.5} Rac8 {+2.06/17 5} 23. Rc1
{-0.92/13 0.5} h6 {+2.39/16 7} 24. Rc3 {-0.98/15 0.5} Rc4 {+2.70/16 4} 25.
b3 {-1.10/15 0.5} Rxc3 {+2.44/19 5} 26. Qxc3 Qe4 {+2.36/19 12} 27. g3
{-0.98/16 0.4} h5 {+2.29/18 7} 28. Re1 {-0.96/14 0.4} Qf5 {+2.27/18 4} 29.
Re5 {-1.00/15 0.4} Qh3 {+2.27/19 6} 30. Re2 {-1.00/15 0.4} h4 {+2.40/18 6}
31. Ra2 {-0.93/17 0.4} Qg4 {+2.48/18 12} 32. Qd3 Rc8 {+3.19/18 4} 33. Ra1
{-1.10/12 0.4} hxg3 {+3.63/19 4} 34. hxg3 {-2.16/14 0.4} Qh3 {+3.80/20 4}
35. Rb1 {-2.30/17 0.4} g6 {+4.24/20 4} 36. Rf1 {-1.87/15 0.4} Kf8
{+4.24/19 5} 37. Qe3 {-1.80/17 0.3} Qf5 {+4.57/18 5} 38. Rf2 Qb1+
{+4.79/17 4} 39. Rf1 Qb2 {+5.38/18 4} 40. Rf2 {-2.25/14 0.3} Qc3
{+5.60/18 2.0} 41. Qxc3 {-2.53/16 0.3} Rxc3 {+5.60/1} 42. Kg2
{-2.82/17 0.3} Rd3 {+6.30/19 3} 43. Ra2 Rxd4 {+6.30/18 4} 44. Rxa6 Rxb4
{+6.56/21 3} 45. Ra3 Ke7 {+6.81/18 1.8} 46. Kf1 Kf6 {+6.87/20 3} 47. Ke2
Kf5 {+6.87/18 1.8} 48. Kd2 f6 {+6.96/18 1.8} 49. Kc2 Kg4 {+7.81/17 1.5} 50.
Ra1 Kxg3 {+9.19/18 3} 51. Rg1+ {-3.73/14 0.2} Kf2 {+9.84/18 1.9} 52. Rxg6
{-3.80/13 0.2} Rxf4 {+9.91/18 2.8} 53. b4 {-3.94/12 0.2} Ke2
{+10.56/18 1.9} 54. Rg2+ {-3.97/12 0.2} Rf2 {+14.30/22 3} 55. Rg3
{-4.37/12 0.2} d4 {+15.43/21 2.9} 56. Rd3 {-5.72/15 0.2} e5 {+17.81/23 2.2}
57. Rd1 {-8.35/16 0.2} f5 {+18.65/22 1.2} 58. Rd3 {-8.64/16 0.2} f4
{+18.85/21 1.5} 59. Rd1 {-10.24/16 0.2} Ke3+ {+19.68/20 1.2} 60. Kb3
{-7.09/11 0.2} e4 {+19.91/20 1.1} 61. Kc4 {-9.23/12 0.2} d3 {+20.38/19 1.0}
62. Kc3 {-10.52/11 0.2} Rc2+ {+24.59/19 1.6} 63. Kb3 {-12.58/13 0.2} f3
{+26.33/19 2.6} 64. Rh1 {-15.36/12 0.2} f2 {+26.33/16 1.8} 65. b5
{-16.69/12 0.2}
{Xboard adjudication} 0-1

Code: Select all

"Booot_62-64" /fd=C:\Engines\UCI\Booot_62-64 -fn Booot_62-64 /fUCCI
"Booot_62-64#2" /fd=C:\Engines\UCI\Booot_62-64#2 -fn Booot_62-64#2 /fUCCI -firstTimeOdds 2
"Booot_62-64#8" /fd=C:\Engines\UCI\Booot_62-64#8 -fn Booot_62-64#8 /fUCCI -firstTimeOdds 8
...
"Fizbo_19-64" /fcp "Fizbo_19-64" /fd=C:\Engines\UCI\Fizbo_19-64 -fn Fizbo_19-64 /fUCCI
"Fizbo_19-64#2" /fcp "Fizbo_19-64#2" /fd=C:\Engines\UCI\Fizbo_19-64#2 -fn Fizbo_19-64#2 /fUCCI -firstTimeOdds 2
"Fizbo_19-64#8" /fcp "Fizbo_19-64#8" /fd=C:\Engines\UCI\Fizbo_19-64#8 -fn Fizbo_19-64#8 /fUCCI -firstTimeOdds 8

Code: Select all

-participants {Booot_62-64
Booot_62-64#2
Booot_62-64#8
Fizbo_19-64
Fizbo_19-64#2
Fizbo_19-64#8
}
-seedBase 390202624
-tourneyType 0
-tourneyCycles 1
-defaultMatchGames 20
-syncAfterRound false
-syncAfterCycle true
-saveGameFile "C:\Winboard_A\TO_Results.pgn"
-loadGameFile "C:\Winboard_A\Startpositions\TO.pgn"
-loadGameIndex -2
-loadPositionFile ""
-loadPositionIndex -2
-rewindIndex 0
-usePolyglotBook false
-polyglotBook ""
-bookDepth 3
-bookVariation 50
-discourageOwnBooks false
-defaultHashSize 256
-defaultCacheSizeEGTB 32
-ponderNextMove false
-smpCores 1
-mps 40
-tc 4:00
-inc 0.80
-results "--+-"
Umm, it seems I never noticed your last post in that thread. :oops:

The problem you encounter there is because of wrong use of the time-odds feature. When you want the time odds to follow an engine in a tournament, you have to install that engine with 'Extra WinBoard options' (in the Load Engine dialog) /firstTimeOdds=N . The time odds entries in the Time Control Options dialog are for first and second engine, but in a tournament (or simple match) you would never know for a given pairing which engine is first and which is second, and there might also be games in the tourney between engines that have no time odds at all.

This pretty much holds for every GUI setting that must follow the engine. E.g. whether it should use GUI book. If you would use the 'First/Second Engine has Own Book' checkboxes in the Common Engine Settings, they would not follow the engine, so you have to put the /firstXBook option with the engine in the engine list. Except that this was expected to be such a common desire that I provided a dedicated checkbox 'Must not use GUI Book' for it in the Load Engine dialogs, which adds the option automatically (if unticked), rather than having to type it as 'Extra WinBoard option'.

Post Reply