Cutechess 1.20 released

[Gabor Szots]

I'm still hoping. I have to switch off my PC very often so that feature is most important to me.

Hi Gabor,

you can use the "start" command if you are using startpositions for the testmatches.
I do so very often.

Best wishes,
G.S.
(CEGT team)

Hi Gerhard,

Thanks for the hint, I'm going to try it next time.

Best,
Gabor

We may have a misunderstanding here, I talk about running a tournament, stopping it, shut down the computer, then later resume the same tournament.

[MikeB]

I'm still hoping. I have to switch off my PC very often so that feature is most important to me.

Hi Gabor,

you can use the "start" command if you are using startpositions for the testmatches.
I do so very often.

Best wishes,
G.S.
(CEGT team)

Hi Gerhard,

Thanks for the hint, I'm going to try it next time.

Best,
Gabor

We may have a misunderstanding here, I talk about running a tournament, stopping it, shut down the computer, then later resume the same tournament.

I have a written script that could handle that in sort of rudimentary fashion, but it would take a little bit of planning , is not fully automatic and one must not be script adverse. Probably not what you're looking for.

[Gabor Szots]

I have a written script that could handle that in sort of rudimentary fashion, but it would take a little bit of planning , is not fully automatic and one must not be script adverse. Probably not what you're looking for.

Thanks Mike. I am not script adverse but the other requirements are not suitable for me. And I meant the GUI, not cli anyway.

[Krzysztof Grzelak]

How to install the engine Pirarucu 3.3.5 in the program Cutechess 1.20 .

[Modern Times]

The biggest issue I have with cutechess GUI is that I go to the screen to set up a new tournament, select all my engines and then realise that I have concurrency set to the wrong value, or don't know what I last set it to. So I have to cancel out of that screen, go into settings and check/change concurrency, and then set up the tournament all over again. I guess this is also related to not being able to save and resume tournaments, and that is a big piece of development work, but to fix just this issue would just require surfacing the concurrency value on the tournament set-up screen. That should be quite easy and would be my request for the next version to the kind people who give their time to this project.

[Guenther]

The biggest issue I have with cutechess GUI is that I go to the screen to set up a new tournament, select all my engines and then realise that I have concurrency set to the wrong value, or don't know what I last set it to. So I have to cancel out of that screen, go into settings and check/change concurrency, and then set up the tournament all over again. I guess this is also related to not being able to save and resume tournaments, and that is a big piece of development work, but to fix just this issue would just require surfacing the concurrency value on the tournament set-up screen. That should be quite easy and would be my request for the next version to the kind people who give their time to this project.

In my quite recent dev compile, including several pull requests compiled from a test branch by alwey, there are a lot of settings memorized now
in the cutechess.ini file.
Concurrency is currently not one of them and I doubt it would make sense to add it as it is very sensible and if a user would forget he had set it to a high value it would make the whole tourney unreliable.

Anyhow, I think most other things are memorized now already and probably concurrency is the only one you might have to check again, thus you would lose just one second now and you don't have to fill in all other stuff as before.

Here is an example from my installation and what is already saved there:

Code: Select all

[games]
default_pgn_output_file=test
draw_adjudication\move_count=10
draw_adjudication\move_number=80
draw_adjudication\score=15
game_length\max_moves=200
resign_adjudication\move_count=10
resign_adjudication\score=1200
resign_adjudication\two_sided=true
time_control\moves_per_tc=40
time_control\time_per_tc=40000
time_control\time_per_move=0
time_control\increment=0
time_control\ply_limit=0
time_control\node_limit=0
time_control\expiry_margin=0
time_control\infinite=false
time_control\hourglass=false
second_time_control\time_control\moves_per_tc=40
second_time_control\time_control\time_per_tc=40000
second_time_control\time_control\time_per_move=0
second_time_control\time_control\increment=0
second_time_control\time_control\ply_limit=0
second_time_control\time_control\node_limit=0
second_time_control\time_control\expiry_margin=0
second_time_control\time_control\infinite=false
second_time_control\time_control\hourglass=false
opening_suite\depth=6
opening_suite\file=C:/Program Files (x86)/cutechess/3M_rand.pgn
opening_suite\random_order=true
use_tb=true

[pgn]
site=RWBC-CAPPUCCINO

[tournament]
games_per_encounter=2
recover=true
repeats=2
result_format="Rank,Name,Elo,Points,Games,Score"
rounds=100
wait=1

[ui]
board\border_color=#844f23
board\coord_text_color=#ffffff
board\dark_square_color=#bb8156
board\light_square_color=#eccba2
board\piece_size_factor=70
display_players_sides_on_clocks=true
mainwindow\geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\xff\xff\xff\xf8\xff\xff\xff\xf8\0\0\a\x87\0\0\x4?\0\0\0\0\0\0\0\0\0\0\a\x7f\0\0\x4(\0\0\0\0\x2\0\0\0\a\x80\0\0\0\0\0\0\0\x13\0\0\a\x7f\0\0\x4\x37)
tb_path=C:/Syzygy_5
mainwindow\window_state=@ByteArray(\0\0\0\xff\0\0\0\0\xfd\0\0\0\x3\0\0\0\0\0\0\x1]\0\0\x2\xfa\xfc\x2\0\0\0\x1\xfb\0\0\0\x18\0M\0o\0v\0\x65\0L\0i\0s\0t\0\x44\0o\0\x63\0k\x1\0\0\0\x16\0\0\x2\xfa\0\0\0]\0\xff\xff\xff\0\0\0\x1\0\0\x3\x90\0\0\x2\xfa\xfc\x2\0\0\0\x1\xfc\0\0\0\x16\0\0\x2\xfa\0\0\x1\x30\0\xff\xff\xff\xfc\x1\0\0\0\x2\xfb\0\0\0\x10\0T\0\x61\0g\0s\0\x44\0o\0\x63\0k\0\0\0\x2\xd5\0\0\x1\\\0\0\0P\0\xff\xff\xff\xfc\0\0\x3\xf0\0\0\x3\x90\0\0\0P\0\xff\xff\xff\xfc\x2\0\0\0\x2\xfb\0\0\0\x1a\0W\0h\0i\0t\0\x65\0\x45\0v\0\x61\0l\0\x44\0o\0\x63\0k\x1\0\0\0\x16\0\0\x1n\0\0\0\x96\0\xff\xff\xff\xfb\0\0\0\x1a\0\x42\0l\0\x61\0\x63\0k\0\x45\0v\0\x61\0l\0\x44\0o\0\x63\0k\x1\0\0\x1\x88\0\0\x1\x88\0\0\0\x96\0\xff\xff\xff\0\0\0\x3\0\0\a\x80\0\0\x1\x11\xfc\x1\0\0\0\x2\xfb\0\0\0\x1e\0\x45\0n\0g\0i\0n\0\x65\0\x44\0\x65\0\x62\0u\0g\0\x44\0o\0\x63\0k\0\0\0\0\0\xff\xff\xff\xff\0\0\0P\0\xff\xff\xff\xfb\0\0\0\x1e\0\x45\0v\0\x61\0l\0H\0i\0s\0t\0o\0r\0y\0\x44\0o\0\x63\0k\x1\0\0\0\0\0\0\a\x80\0\0\0P\0\xff\xff\xff\0\0\x2\x8b\0\0\x2\xfa\0\0\0\x4\0\0\0\x4\0\0\0\b\0\0\0\b\xfc\0\0\0\x1\0\0\0\x2\0\0\0\x1\0\0\0\x10\0G\0\x61\0m\0\x65\0T\0\x61\0\x62\0s\0\0\0\0\0\xff\xff\xff\xff\0\0\0\0\0\0\0\0)

I can send it to you for checking out how much work you still have to do except setting up the concurrency value.
Just PM me.

BTW this is my current board view now:
https://user-images.githubusercontent.c ... 16a6fe.png

[MikeB]

The biggest issue I have with cutechess GUI is that I go to the screen to set up a new tournament, select all my engines and then realise that I have concurrency set to the wrong value, or don't know what I last set it to. So I have to cancel out of that screen, go into settings and check/change concurrency, and then set up the tournament all over again. I guess this is also related to not being able to save and resume tournaments, and that is a big piece of development work, but to fix just this issue would just require surfacing the concurrency value on the tournament set-up screen. That should be quite easy and would be my request for the next version to the kind people who give their time to this project.

I agree - just submitted an enhancement request to add concurrency setting to the tournament setting menu.

https://github.com/cutechess/cutechess/issues/614

[geko]

Hi all, I'm looking for CLI arm 32 / raspberry...

[MikeB]

Hi all, I'm looking for CLI arm 32 / raspberry...

That's doable - but your best bet is to compile it yourself. Al Scally and I both did it. Just follow the instructions. It will take some time.