[computer-go] How to design the stronger playout policy?

[Mark Boon]

On 5-jan-08, at 11:48, Gian-Carlo Pascutto wrote:
> >
>> Would you explain the details of the playout policy?
>
> (1) Captures of groups that could not save themselves last move.
> (2) Save groups in atari due to last move by capturing or extending.
> (3) Patterns next to last move.
> (4) Global moves.
>

Is this what is meant by 'heavy playout'?

I suppose it slows down the playout considerably. Just keeping track  
of actual liberties instead of pseudo-liberties should probably be  
three times slower by itself. But in itself I think the idea is  
interesting. I've always felt programming Go would go towards several  
layers of playing engines. Each one a bit more sophisiticated built  
on top of a more primitive one.

Mark