pohl4711 wrote: ↑Sun Mar 03, 2019 9:02 amA fixed movetime gives much higher search depths in endgame and does not depend on the chosen engine, the used hardware and the number of threads.
Where do you get that "go movetime N" is independent of engine and HW? A faster engine will reach higher depth with the same allocated time, similarly, faster HW or a higher thread count will have the same effect; you must know that.
Please, read once again my post about my test.
Ozymandias wrote: ↑Sun Mar 03, 2019 10:15 am
I for one, would prefer for both options to be kept on the table, let the user decide if they want to go with fixed depth or not.
There is no any obstacle to modify the source of Leelafish to fixed "depth" and fixed "movetime" being together and users can choose the method what they want.
As an earlier post I mentioned too much "help" for Leela may decrease the Elo of Leela.
It was confirmed by dkappe too.
Ozymandias wrote: ↑Sun Mar 03, 2019 10:15 amWhere do you get that "go movetime N" is independent of engine and HW? A faster engine will reach higher depth with the same allocated time, similarly, faster HW or a higher thread count will have the same effect; you must know that.
Ozymandias wrote: ↑Sun Mar 03, 2019 10:15 amWhere do you get that "go movetime N" is independent of engine and HW? A faster engine will reach higher depth with the same allocated time, similarly, faster HW or a higher thread count will have the same effect; you must know that.
Ozymandias wrote: ↑Sun Mar 03, 2019 10:15 amWhere do you get that "go movetime N" is independent of engine and HW? A faster engine will reach higher depth with the same allocated time, similarly, faster HW or a higher thread count will have the same effect; you must know that.
Ozymandias wrote: ↑Sun Mar 03, 2019 10:15 amWhere do you get that "go movetime N" is independent of engine and HW? A faster engine will reach higher depth with the same allocated time, similarly, faster HW or a higher thread count will have the same effect; you must know that.
We are sorry, but the requested file doesn't exist or has expired and is no longer available.
I am afraid you can not use this site.
After this message click on "download page" and type in the window File Id:
716842
and click "Download file" and type the password, etc.
Ozymandias wrote: ↑Sun Mar 03, 2019 10:15 amWhere do you get that "go movetime N" is independent of engine and HW? A faster engine will reach higher depth with the same allocated time, similarly, faster HW or a higher thread count will have the same effect; you must know that.
We are sorry, but the requested file doesn't exist or has expired and is no longer available.
I am afraid you can not use this site.
After this message click on "download page" and type in the window File Id:
716842
and click "Download file" and type the password, etc.
As I suspected, I can see Lc0's depths, but not the auxiliary engine's, which means no comparison can be made, in terms of depth reached with a fixed time per move TC.
Ozymandias wrote: ↑Sun Mar 03, 2019 5:25 pm
As I suspected, I can see Lc0's depths, but not the auxiliary engine's, which means no comparison can be made, in terms of depth reached with a fixed time per move TC.
This is not the part of Leela's pv.
The reached depth obviously depends on the value of the fixed movetime, the speed of PC and the actual number of moves at that position.
As I noted on my PC 100 ms movetime is about the average time to reach depth = 15.
Hello Killerducky, I have a special request for engine parameters : could you please modify the engine so that it can accept to use .bin opening book please ?
I know that it is possible from Stockfish to do it, like we have brainfish having those parameters.
This is because i make engine matches on the internet and unfortunately, using polyglot won't work.
Needed parameters would be :
Bookfile= <path of the engine>
Bestbookmove=<true or false, depending on if we want the best move to always be picked>
BookRandom=<true or false, depending on if we want best book move or not
BookDepth=<number of semiplies we want the engine to use the book>