I start with one move, and slowly add moves to the pool of moves to be
considered, peaking at considering 30 moves.
My current schedule looks like:
visits 0 2 5 9 15 24 38 59
90 100 ... 2142
moves 1 2 3 4 5 6 7 8
9 10 ... 20
I didn't find that strength is very sensitive to the schedule. Many Faces
is a pretty good heuristic for selecting good moves, so if you are just
using RAVE to do move ordering you might need to widen faster.
> -----Original Message-----
> From: computer-go-boun...@computer-go.org [mailto:computer-go-
> boun...@computer-go.org] On Behalf Of Petr Baudis
> Sent: Tuesday, September 29, 2009 7:07 AM
> To: firstname.lastname@example.org
> Subject: [computer-go] Progressive widening vs unpruning
> I'm a little unclear on this, so I'd like to make sure I'm not missing
> any important technique - is "progressive widening" and "progressive
> unpruning" synonymous?
> I have looked both into the pMCTS and the CrazyStone papers and it
> seems that "widening" differs from "unpruning" in that certain number of
> simulations is first made before limiting the number of searches. Which
> of the variants is commonly used? What "speed" of widening works for you
> Petr "Pasky" Baudis
> A lot of people have my books on their bookshelves.
> That's the problem, they need to read them. -- Don Knuth
> computer-go mailing list
computer-go mailing list