On Nov 3, 2006, at 8:10 AM, Rémi Coulom wrote:
You can try multiplying uncertainty by a well-chosen constant
value. This way, you can tune how selective your search is. I found
that using a constant < 1 improves the search on 9x9 for Crazy
Stone (I use 1/sqrt(10), if I recall correctly). I wonder what is
the experience of other UCT programmers, by the way.
Whee, parameter tweaking! :-)
Do you have some reason for choosing this value, or did it just work
well in practice?
Also, are people pruning any move for which (average +
uncertainty) is less than the (average - uncertainty) of some
other move?
I am not sure what you mean. In UCT, you only search the move that
has the highest average + uncertainty, and you don't search any
other at all.
By "prune" I mean "remove from the stored tree", making the memory
used on that branch available for something else.
Peter Drake
Assistant Professor of Computer Science
Lewis & Clark College
http://www.lclark.edu/~drake/
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/
