Maharani wrote: After move 34, I had to stop analyzing for the day. When I returned to the game and played KataGo's suggestion at move 35, it started its analysis from scratch at 0 playouts. This seems regrettable to me.
That is correct, and it is also a known limitation of all popular go engines right now. Bots use internal memory to store their calculation progress. If you move up/down the game tree Leela Zero and KataGo will still remember their progress for previous calculations and will be able to resume new calculations from where they left off earlier. But unfortunately:
- If you restart a bot, all progress is gone. And you have to restart calculations from scratch next time.
- After a long time of calculation, the limit of the memory can be reached. When that happens, it will start clean parts of its memory.
- The memory cannot be dumped/exported to a file right now.
ZBaduk's limitations are roughly the same. It has a pool of running leela zero and katago applications. And if you connect, it assigns a couple of those instances to your session (one per bot). So, each session gets its own instances (each with their own memory). In general, those instances are yours until you disconnect. Consequently, your progress will be gone after a reconnect. Of course ZBaduk does store statistics in your game record, which can be saved to the ZBaduk server. But those results cannot be resumed, as there is just no way to communicate this information to Leela Zero / KataGo.
Even though there have been experiments to load/save memory to files, and it hasn't been supported by leela zero and katago yet. So, right now, I think it is better to just wait and do nothing about this.
While ZBaduk cannot provide a solution. It does use a cache to store the results for the first 40 moves. This cache instantly offers millions of playouts without having to calculate anything.
But still, if you want to supersede those results, the only way, is to give the server time to calculate everything again, starting from 0. But at least it means that you do not have to calculate the first 40 moves again for each and every game.
Maharani wrote: LeelaZero's top move and all of KataGo's moves are also frozen (meaning all >1k moves).
Anyway, like most tools, ZBaduk will only replace results if the amount of playouts increases. So, if you let ZBaduk re-analyse a position, you won't see much changes at first. You will only start seeing changes once the existing statistics are superseded in playouts. (And because ZBaduk's cache only stores statistics for moves with >1k playouts, moves with <1k playouts will indirectly give away that the system is in fact calculating.)
|
One minor remark: the "sequence" displayed in the right-most chart column assumes that the vertical coordinates are arranged in ascending order, even if descending is selected in the UI settings. This is especially strange since the "move" in the left-most chart column assumes that vertical coordinates are arranged in descending order (as is customary), although this column does adapt to the chosen UI settings.