On Jan 14, 2008 6:15 PM, Jason House <[EMAIL PROTECTED]> wrote:
> slow. UCT (or generically Monte Carlo) can "evaluate" a position fairly > quickly (maybe 1k-100k per second depending on how heavy the playout > is), they don't give a reliable estimate. To improve this, they end up > 1K ~ 100 K / sec is much faster than "a dozen" / sec of a conventional program. Do they calculate dragon safety (eyes, connections, patterns ...)? if not, the estimate will be VERY unreliable. But if they do, how can they be this fast compared to the more conventional programs? > reevaluating positions more than once (maybe 100 times?) to get a more > reliable estimate. > why "reevaluating" the same position? Sorry, I didn't go into their papers, can people who knows UCT, or actually working on UCT programs explain in a way that a layman can understand. Thanks.
_______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
