> there's no obvious way to add knowledge if you don't like the current results
You have missed a key point. UCT is an ideal framework for integrating many potentially incomplete, contradictory, or even potentially wrong, knowledge sources. There are a zillion ways to add knowledge, and UCT guarantees that you won't pay an asymptotic price. Prior to MCTS, GO programmers would build rules and patterns, which would make their Go programs better but brittle. Inside an MCTS framework, however, creating new patterns is almost risk-free. If the pattern works, then it helps the program, and if it doesn't work then UCT quickly ignores it in *that* position. Build a rule base that biases move selection in the tree portion of the playout. Encode all of your human understanding there. Represent the strength of the rules as your initial W/L counters. _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
