pedrox wrote: ↑Sun Aug 08, 2021 10:38 amI forgot to configure the "danacfg.txt" file for the xboard protocol, since I normally use the uci protocol. So effectively if the xboard protocol is used it is necessary to modify the evaluation file and put dananet2.nnue.
I have noticed that if I leave it at dananet.nnue (that is, without the serial number), it does not complain but says it has loaded dananet.nnue. That's odd because there is no such file in the folder.
If I give a random nnue name it complains that no nnue file has been loaded.
But the main problem is that if I want to use both Danasah 8.8 and Danasah 9.0 in WinBoard mode I must use the same config file and, consequently, the same network. Or I have to put the two versions in different folders, which I don't want. Unless they both use their default nets.
Last edited by Gabor Szots on Sun Aug 08, 2021 11:57 am, edited 1 time in total.
Gabor Szots wrote: ↑Sun Aug 08, 2021 11:53 am
But the main problem is that if I want to use both Danasah 8.8 and Danasah 9.0 in WinBoard mode I must use the same config file and, consequently, the same network. Or I have to put the two versions in different folders, which I don't want.
Gabor Szots wrote: ↑Sun Aug 08, 2021 11:53 am
But the main problem is that if I want to use both Danasah 8.8 and Danasah 9.0 in WinBoard mode I must use the same config file and, consequently, the same network. Or I have to put the two versions in different folders, which I don't want.
Why not run them in UCI mode ?
Every time an engine is capable of both I use it in WinBoard mode under Arena. The reason is simply to check if it is not broken in that mode.
I forgot to configure the "danacfg.txt" file for the xboard protocol, since I normally use the uci protocol. So effectively if the xboard protocol is used it is necessary to modify the evaluation file and put dananet2.nnue.
The executable in the zip does not have the option to limit the playing force, so it is not affected by the limitstrenght option (this is prepared for another executable that I did not include in the package, maybe a bit confusing but I tried to make it serve the same file of configuration for the 2 executables).
As someone else already said I using UCI and your latest brainchild is doing extremely well for the GRL, see:
pedrox wrote: ↑Sun Aug 08, 2021 10:38 amI forgot to configure the "danacfg.txt" file for the xboard protocol, since I normally use the uci protocol. So effectively if the xboard protocol is used it is necessary to modify the evaluation file and put dananet2.nnue.
I have noticed that if I leave it at dananet.nnue (that is, without the serial number), it does not complain but says it has loaded dananet.nnue. That's odd because there is no such file in the folder.
If I give a random nnue name it complains that no nnue file has been loaded.
But the main problem is that if I want to use both Danasah 8.8 and Danasah 9.0 in WinBoard mode I must use the same config file and, consequently, the same network. Or I have to put the two versions in different folders, which I don't want. Unless they both use their default nets.
I have modified the executables so that each version can have a different configuration file for the xboard protocol. I think the engine works fine in this protocol, although now I use the uci protocol more.
I forgot to configure the "danacfg.txt" file for the xboard protocol, since I normally use the uci protocol. So effectively if the xboard protocol is used it is necessary to modify the evaluation file and put dananet2.nnue.
The executable in the zip does not have the option to limit the playing force, so it is not affected by the limitstrenght option (this is prepared for another executable that I did not include in the package, maybe a bit confusing but I tried to make it serve the same file of configuration for the 2 executables).
As someone else already said I using UCI and your latest brainchild is doing extremely well for the GRL, see:
This is much more than expected, I am not sure if it has to do with the fact that the previous network only had depth 5 and the new one reaches 9, perhaps in a gambit that difference is important, I do not know it.
But I think that in other lists the difference will be smaller.
pedrox wrote: ↑Sun Aug 08, 2021 10:38 amI forgot to configure the "danacfg.txt" file for the xboard protocol, since I normally use the uci protocol. So effectively if the xboard protocol is used it is necessary to modify the evaluation file and put dananet2.nnue.
I have noticed that if I leave it at dananet.nnue (that is, without the serial number), it does not complain but says it has loaded dananet.nnue. That's odd because there is no such file in the folder.
If I give a random nnue name it complains that no nnue file has been loaded.
But the main problem is that if I want to use both Danasah 8.8 and Danasah 9.0 in WinBoard mode I must use the same config file and, consequently, the same network. Or I have to put the two versions in different folders, which I don't want. Unless they both use their default nets.
I have modified the executables so that each version can have a different configuration file for the xboard protocol. I think the engine works fine in this protocol, although now I use the uci protocol more.
I forgot that in addition to the configuration file for the xboard protocol it is also possible to enter the options directly on the command line (without needing danacfg.txt)
pedrox wrote: ↑Sun Aug 08, 2021 2:46 pm
I forgot that in addition to the configuration file for the xboard protocol it is also possible to enter the options directly on the command line (without needing danacfg.txt)