Closed shenjian333333 closed 4 months ago
In the analysis, if depth and fixed time are given, then the target is the depth with the time limit. Nodes are too specific.
Thanks for your reply
But for gpu engines depths are doesn't make sense ,if I limit time ,Idont konw how many nodes did it ran,and I can
t know are the results reliable.
lc0 depth is not the same as other engines, it searches and makes a tree by using Monte Carlo graph search. depth is just an estimation but not really how far it is searched
this should probably be closed, there's not really a way to optimize other than adding an option for nodes per move
this should probably be closed, there's not really a way to optimize other than adding an option for nodes per move
So, should I close this issue or just keep it?
Better to keep it, as it reminds me that this possibility is pending, and it could be useful to someone.
Better to keep it, as it reminds me that this possibility is pending, and it could be useful to someone.
nodes per move is an option I've wanted for a while. as you might know, arena has it, but their app is clunky, and cutechess has it but they're kinda annoying. you might also want to look at arena's features and find some implementations. It has the elostat thing built in
Use depth to control GPU engine analyze sometimes is too slow,In some positions, LC0 can take 5 minutes or more to complete an 8 depths analysis,Maybe we can use nodes control analysis,for example ,10000nodes 1 PV,this analysis must be reliable. And kitibizers function can be turned into an analysis arrow orchange that window to can maximized.That's my suggestion,My English is not good, part of the text uses Google Translate, please forgive me. 😁😁
Happy new year!