Re: Komodo 12 and MCTS
Posted: Wed May 16, 2018 1:19 am
Probably we will before too long, but not right away.CMCanavessi wrote: ↑Tue May 15, 2018 10:21 pm @mark and larry, now that K12 is out will you make 10 free?
Probably we will before too long, but not right away.CMCanavessi wrote: ↑Tue May 15, 2018 10:21 pm @mark and larry, now that K12 is out will you make 10 free?
Great option, one suggestion for all - when responding to someone being hostile, no need to quote the hostile remarks. They will soon be posting to themselves.
Does this happen after leaving it to analyze in infinite mode for a fairly long time, like an hour or so? If so it is because memory limits are reached. This isn't a bug, but perhaps we'll have a fix for it in a future update.Kaj Soderberg wrote: ↑Wed May 16, 2018 8:16 pm Thank you for this new engine, Mark and Larry.
MCTS is great fun to play around with, though K12 "normal" indeed seems stronger.
I notice that occasionally MCTS freezes, both on Windows and on Mac OS.
On my quad, it does not matter if 1 use 1, 2 or 3 threads or if i use more or less multi-pv.
The thing just sometimes freezes: the clock does not "tick" and the search depth remains the same.
Odd behavior or something fully explainable?
Thanks,
Kaj
Isn't a bug?! Is it expected behavior?
Just a bit of clarification. The engine freezes and causes the GUI to stop giving information. The PC is still responding.Jesse Gersenson wrote: ↑Wed May 16, 2018 8:45 pmIsn't a bug?! Is it expected behavior?
Komodo's causing his computer to freeze, that's a serious bug.
It seems odd to me that the GUI would stop working. Nothing we do in the engine should make the GUI stop. The GUI has its own clock. In MCTS mode, when the memory for MCTS nodes fills up, it simply stops searching and returns the best move. If you find a position where the GUI freezing is repeatable, please send me the position, the GUI you are using and your settings and I can try to reproduce on my machines.Kaj Soderberg wrote: ↑Wed May 16, 2018 9:08 pmJust a bit of clarification. The engine freezes and causes the GUI to stop giving information. The PC is still responding.Jesse Gersenson wrote: ↑Wed May 16, 2018 8:45 pmIsn't a bug?! Is it expected behavior?
Komodo's causing his computer to freeze, that's a serious bug.
Cheers, Kaj
Do you send the best move only after the GUI has sent the 'stop' command?mjlef wrote: ↑Wed May 16, 2018 10:13 pmIt seems odd to me that the GUI would stop working. Nothing we do in the engine should make the GUI stop. The GUI has its own clock. In MCTS mode, when the memory for MCTS nodes fills up, it simply stops searching and returns the best move. If you find a position where the GUI freezing is repeatable, please send me the position, the GUI you are using and your settings and I can try to reproduce on my machines.Kaj Soderberg wrote: ↑Wed May 16, 2018 9:08 pmJust a bit of clarification. The engine freezes and causes the GUI to stop giving information. The PC is still responding.Jesse Gersenson wrote: ↑Wed May 16, 2018 8:45 pm
Isn't a bug?! Is it expected behavior?
Komodo's causing his computer to freeze, that's a serious bug.
Cheers, Kaj