Does it hurt the integrity of a UCT tree if you update it in a way that is contrary to the standard traverse-simulate-backup strategy? For example, what if many simulations were run on a certain node deep in the tree and then all those results are backed-up the tree without doing any new traversals in between? Aside from the time it takes to do all of those simulations, would that be a bad thing for the tree? Or would the tree benefit from the increased information?
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/

Reply via email to