Hi Ed.
That looks very interesting.
I have rewritten my engine today to expose all the serveral hundreds evaluation parameters as uci options and I have a question before running some tests with NICE:
Is it possible for mea.exe to start the engine with commandline parameter like
set EXE=engines\RubiChess.exe -evaloptions
...
mea.exe --engine "%EXE%" --name %NAME% ...
The evaluation parameters are only exposed to uci interface if engine is started with "-evaloptions".
If this is not possible I need to compile a binary with hardcoded -evaloptions enabled.
Rebel wrote: ↑Sat May 02, 2020 12:51 am
Hi Andreas,
I see 2 possibilities.
set EXE="engines\Rubi.exe -evaloptions"
or via OPTIONS
set OPTIONS="MultiPV=1,Mobility = 75"
or
set OPTIONS="MultiPV=1,Mobility = 75,Passed Pawns = 125"
Thanks. I did a first test by passing a very bad value for some parameter and it "failed" by getting the same score as the version with default values. Another problem might be that my eval options are given in the format "Value(20,40)" for midgame and endgame evaluation. The comma may confuse the parser of Mea so I will change it to "Value(20/40)".
Rebel wrote: ↑Sat May 02, 2020 12:51 am
Hi Andreas,
I see 2 possibilities.
set EXE="engines\Rubi.exe -evaloptions"
or via OPTIONS
set OPTIONS="MultiPV=1,Mobility = 75"
or
set OPTIONS="MultiPV=1,Mobility = 75,Passed Pawns = 125"
Thanks. I did a first test by passing a very bad value for some parameter and it "failed" by getting the same score as the version with default values. Another problem might be that my eval options are given in the format "Value(20,40)" for midgame and endgame evaluation. The comma may confuse the parser of Mea so I will change it to "Value(20/40)".
I am pretty sure that is the case.
90% of coding is debugging, the other 10% is writing bugs.
This is the result of two runs with variations of my Pawnpushthreatbonus parameter. The two runs used different epd sets (lcx-1.epd in the first, lcx-2.epd in the second), everything else was the same.
The default version finished last in the first run and first in the second. And also the other version are almost mirrored in the score board.
I took your a (a1...a8) example and ran 8 threads parallel on a Ryzen 3700x (8 cores, 16 threads with HT).
I also tried some other parameters with the same no-result.
So my idea is not to use a constant movetime of 100ms but a constant number of nodes. This would eliminate the unbalanced cpu problemes but it seems that mea doesn't support that?
Rebel wrote: ↑Sat May 02, 2020 4:55 pm
Not sure if MEA supports nodes (I don't think so) but it does support depth.
set OPTIONS="MultiPV=1,depth=20"
Secondly so far I have only used the SFX epd's after noticing they gave me better results.
Meanwhile I have some better (more reliable) results with fixed depth search (18 or 20) that showed default settings constantly with top position or at least head-to-head with the top position. So the Texel-tuning did a good job and your tool is also useful confirming these Texel-tuned parameters.