LION wrote: Thu Apr 04, 2024 6:41 am
Thank you, it works.
But after compilation there is now no Hypnos.exp file.
It’s a pity that now there is no Development, where all the changes were taken into account and there was no need to make changes manually.
An experience file is created after the first game is completed. Everything appears normal. exp is growing after several games. Should be fine.
Everything is correct.
Initially, the path to the experience file is specified in the engine settings.
And if this file does not exist, then there is nothing to grow.
If you examine the source (experience.cpp/experience.h), you will find that a new experience file is created at the end of a game if one is not found in the engine path's folder. The default path is the engine's folder in the code.
Try it. Start HypnoS with no experience file in the engine's folder. Play one game. Check the folder. You will see a newly created experience file. Use the HypnoS Experience Tool to check the contents prior to a defrag.
Then play some games. Check the experience file again. You find that it has grown.
Marco is now working on two versions. One uses the learning file from Eman and the other (legacy) from Brainlearn. You can download both latest versions with source code on my homepage:
Note: To compile the Eman version you need to use the Makefile and evaluate.h from the above June 22 version. Some entries in the two files need to be changed to avoid an error message.
For HypnoS Iccf 180824 M.Z. gives the following recomendations:
To be used in the HardPositions Test Suites:
Optimal example of Test Suite configuration
Fluid MultiPV=true
Fmpv Difference=1000
Fmpv Max MultiPV"=8
High Tal=true
Materialistic Evaluation Strategy=-7
Positional Evaluation Strategy=5
FluidMultiPV makes HypnoS able to consider more moves (if they aren't much less valuable than first pv move). Fluid means that it depends on position, HypnoS is using multipv value depending on next options and not all the time;
Fmpv Difference - how much other moves differs in score from first pv. Default 10 means there isn't big difference, but if user choose 1000 (max value) it makes HypnoS to use multipv always because there will be almost all the time moves in this range. Value 0 would mean it will turn on multipv only for equal in score moves. I hope these explanations are enough.
Fmpv Max MultiPV - here we decide how many moves it should consider for fluid multipv. Range from 2 to 8, default 4. If user for example pick 2,HypnoS will use max multipv 2 even if in set FmpvDifference there would be more moves meeting the criteria.
From these recommendations use what is adaptable! Or use Hypnos Iccf for Position tests.
