Have you considered outputting your tree to SGF? You can put as much (or as little) information in the tree comments and, assuming you have a good SGF viewer, it is easy to navigate the tree and figure out what the engine was 'thinking.' Oakfoam has this functionality and I have used it in the past to great effect. -- Francois van Niekerk Email: [email protected] | Twitter: @francoisvn Cell: +2784 0350 214 | Website: http://leafcloud.com
On 22 December 2013 21:47, Petr Baudis <[email protected]> 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 > [email protected] > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
