Jun 2009 5:07 pm
Subject: Re: [computer-go] Tweak to MCTS selection criterion
Another strategy to be considered is to not allow the thinking to
cease until the maximum win rate and the maximum visit count agree
on the same move. Obviously this requires some extra code to make
I think all principles I use in the time management for Valkyria came
up in this thread more or less.
1) Valkyria selects move that has been searched the most.
2) It is given a base time for example 20 seconds early on on 9x9 CGOS
3) The base time is adjusted down if the program is winning
2009/6/6 dhillism...@netscape.net
I had the early stop rule and didn't know if anyone else had thought of
it. But I never considered the pebbles rule,
which somewhat conflicts with the early stop rule. But as I layed out
above I think you could do both.
This is probably one of those
To: computer-go computer-go@computer-go.org
mailto:computer-go@computer-go.org
Sent: Sat, 6 Jun 2009 5:07 pm
Subject: Re: [computer-go] Tweak to MCTS selection criterion
Another strategy to be considered is to not allow the thinking to
cease until the maximum win rate
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
When a UCT search is completed, the usual selection criterion is
choose the move that has the most trials. This is more stable
than choosing the move that has the highest percentage of wins,
since it is possible to have an unreliably high percentage if the
number of trials is small.
I have a
Another strategy to be considered is to not allow the thinking to cease until the maximum win rate and the maximum visit count agree on the same move.
Obviously this requires some extra code to make sure you don't lose on time, etc.
Brian Sheppard wrote:
When a UCT search is completed, the
On Sat, Jun 6, 2009 at 5:07 PM, Michael Williams
michaelwilliam...@gmail.com wrote:
Another strategy to be considered is to not allow the thinking to cease
until the maximum win rate and the maximum visit count agree on the same
move. Obviously this requires some extra code to make sure you
allows the search to be stopped early. It can save a lot of time for forced
moves.
- Dave Hillis
-Original Message-
From: Michael Williams michaelwilliam...@gmail.com
To: computer-go computer-go@computer-go.org
Sent: Sat, 6 Jun 2009 5:07 pm
Subject: Re: [computer-go] Tweak to MCTS
