In Crazy Stone I have a gogui-analyze command that will dump the node of the tree for the current position. So I can just navigate with gogui and ask for the statistics of the current node. It is a bit primitive, but I find it usable enough, and the coding effort is very small.
Guillaume Chaslot made a gogui extension long ago, but it seems it disappeared from the web: http://www.mail-archive.com/computer-go@computer-go.org/msg06425.html Rémi On 22 déc. 2013, at 20:47, Petr Baudis <pa...@ucw.cz> wrote: > Hi! > > I'm wondering how are you investigating your MC game trees? For > example, I'm interested in why Pachi did not consider move X, in what > branches it _was_ considered and how did the simulations that considered > it end up, what are its RAVE stats, etc. So far, I have been relying on > debug prints and text dumps of the tree, but they are getting very > inconvenient to use for long thinking times and deep trees. > > My worst case scenario is developing some data format and writing a > few tools for visualization and investigation of game trees, but I'd be > more than happy to find out that something I could use already exists. > > Thanks, > > Petr "Pasky" Baudis > _______________________________________________ > Computer-go mailing list > Computer-go@dvandva.org > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go _______________________________________________ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
