I found the problem!
The problem in specific engine (Integral v4) occurs when in tournament check "Overide engine options" and then check "disable own book".
But there was no problem in earlier versions.
Myracle GUI
Moderator: Ras
-
SSTATHIS
- Posts: 56
- Joined: Tue Jun 22, 2010 7:55 pm
Re: Myracle GUI
In a new tournament after 1560 games failed to load an engine (Zappa Mexico II). The tournament stop. I just close the warning window and uncheck pause. The tournament continue with no problem. But many hours are lost because of tournament stop.
I think that its the best if after warning (can not load an engine) the tournament must continue automaticly and no stopping (like it was until version 131)
I think that its the best if after warning (can not load an engine) the tournament must continue automaticly and no stopping (like it was until version 131)
-
mar
- Posts: 3015
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: Myracle GUI
hmm, could you please describe the error why it failed to load? was it something related to the new default option change check?
I'll investigate later today when I come back from work. if an engine fails to load the tournament is paused because the GUI assumes the engine is misconfigured
and would fail to load again, strange that it continued normally after resume...
I'll investigate later today when I come back from work. if an engine fails to load the tournament is paused because the GUI assumes the engine is misconfigured
and would fail to load again, strange that it continued normally after resume...
-
mar
- Posts: 3015
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: Myracle GUI
just got a note from Gunther that Integral throws an exception if it encounters an unknown UCI option; I changed the override behavior a bit
this is a problem in Myracle and will be fixed in an upcoming build
-
SSTATHIS
- Posts: 56
- Joined: Tue Jun 22, 2010 7:55 pm
Re: Myracle GUI
It just failed. That's why the tournament continues normally after uncheck pause. Before that 1560 games played without problem for Zappa mexico ii or any other engine....mar wrote: ↑Wed Sep 23, 2026 6:38 am hmm, could you please describe the error why it failed to load? was it something related to the new default option change check?
I'll investigate later today when I come back from work. if an engine fails to load the tournament is paused because the GUI assumes the engine is misconfigured
and would fail to load again, strange that it continued normally after resume...
-
mar
- Posts: 3015
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: Myracle GUI
ok thanks, so if it wasn't related to the new default option change check, then maybe the engine failed to load from a network drive?
if it's on a normal disk then this is a bit odd.
it could also be caused by a startup timeout, possibly interrupted by some external CPU-heavy process. but by default engines get 20 seconds to start up and it should be plenty I think
-
SSTATHIS
- Posts: 56
- Joined: Tue Jun 22, 2010 7:55 pm
Re: Myracle GUI
Myracle, engines, tb are all at the same local ssd.mar wrote: ↑Wed Sep 23, 2026 10:49 amok thanks, so if it wasn't related to the new default option change check, then maybe the engine failed to load from a network drive?
if it's on a normal disk then this is a bit odd.
it could also be caused by a startup timeout, possibly interrupted by some external CPU-heavy process. but by default engines get 20 seconds to start up and it should be plenty I think
2000 games more and zapa Mexico ii is ok.
-
mar
- Posts: 3015
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: Myracle GUI
build 135 is up:
- fix: don't send options that the engine doesn't support (Integral plays now fine with book overrides)
- add elapsed/remaining time in tournament tab
this is an important milestone because I consider the GUI feature-complete now so from now on bugfixes only
EDIT: the localization files have been updated so it's necessary to update both gui_data.zip and the executable
- fix: don't send options that the engine doesn't support (Integral plays now fine with book overrides)
- add elapsed/remaining time in tournament tab
this is an important milestone because I consider the GUI feature-complete now so from now on bugfixes only
EDIT: the localization files have been updated so it's necessary to update both gui_data.zip and the executable
-
Modern Times
- Posts: 3945
- Joined: Thu Jun 07, 2012 11:02 pm
Re: Myracle GUI
Fantastic work Martin, yes this is a very full-featured GUI. No more Cutechess for me. I just noticed the stats button today:
Interesting information there.
Code: Select all
Name Depth/move Time/move Nodes/move Nodes/second
-----------------------------------------------------------------------
Heimdall 1.5.1 30.2 2.74 2 406 k 877 k
Tarnished v6.0 29.4 2.96 2 569 k 867 k
Clover 9.1 39.8 2.84 4 438 k 1 564 k
Raphael 4.2.0 26.0 2.52 2 240 k 890 k
-
mar
- Posts: 3015
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: Myracle GUI
thanks Ray. yes - Andres asked for Banksia-style stats some time ago... so I shamelessly borrowed the idea from Nguyen.
in fact the above mentioned problem with Princhess was found thanks to the stats where it was showing unusually low time/move.
turns out if was a problem with default option value when replacing existing engine binaries;
this is now treated as an error and the tournament would pause if some default option differs from a saved default in engine config.
of course those who always do a fresh engine install for each new version (ideally using a separate folder) would never even experience the problem
in fact the above mentioned problem with Princhess was found thanks to the stats where it was showing unusually low time/move.
turns out if was a problem with default option value when replacing existing engine binaries;
this is now treated as an error and the tournament would pause if some default option differs from a saved default in engine config.
of course those who always do a fresh engine install for each new version (ideally using a separate folder) would never even experience the problem