Looking again, I was confusing a followup post with the original description of the pebbles rule. I have not tested this exact rule. Sorry for my confusion.
- Dave Hillis -----Original Message----- From: [email protected] To: [email protected] Sent: Sun, 7 Jun 2009 9:39 pm Subject: Re: [computer-go] Tweak to MCTS selection criterion The policy is only risk free on a per-move basis. For the game as a whole, using more time on one move means there will be less time available for later moves. Back when I tested this rule in my own program, I didn't see any significant difference in strength. YMMV. - Dave Hillis -----Original Message----- From: Brian Sheppard <[email protected]> To: [email protected] Sent: Sun, 7 Jun 2009 6:05 pm Subject: [computer-go] Tweak to MCTS selection criterion > check if overtaking the leading move is mathematically impossible? Yes. Pebbles does this. Please note that the discussion has veered into time control policy, which is not the subject of the original post. The original post discusses move selection policy: when your program stops, for whatever reason, which move should it select? Pebbles' policy is to select the move that has the most wins, rather than the most trials. Pebbles policy is a risk-free improvement over the standard policy of selecting the move that has the most trials. Brian _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/ Wanna slim down for summer? Go to America Takes it Off to learn how. _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
_______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
