You always need to be extremely careful about these kind of
heuristics. Especially in MC programs they can be detrimental very
easily.
But I believe you can come up with a reasonable rule to prevent some
self-atari's. I have one which is something along the following lines:
- puts itself into ata
This case is of course not pruned by Valkyria, simply because the the
pattern here is completely different from what we discussed. :) This
sacrifice prevents an eye to be made.
-Magnus
Quoting Christian Nentwich :
|- - - - - - -
|. * * o . . .
|* . * o * . *
|o . o o * . .
|o * o . * . .
>- puts itself into atari
>- has four occupied neighbours, one of which is its own color
>- does not put the opponent in atari
In the Ko in question, J6 does put the opponent in atari, so this
rule is not applicable. But I will make a note of it for future reference.
>Another rule I just thought
Your example is very clever, but the recapture doesn't technically bring
us back to where we started, as Magnus required.
>|- - - - - - -
>|. * * o . . .
>|* . * o * . *
>|o . o o * . .
>|o * o . * . .
>|o o o * . . .
>|. * * * . . .
>|. . . . . . .
>|. * . . . . .
>Black to play and kill :)
>
|- - - - - - -
|. * * o . . .
|* . * o * . *
|o . o o * . .
|o * o . * . .
|o o o * . . .
|. * * * . . .
|. . . . . . .
|. * . . . . .
Black to play and kill :)
Christian
On 01/07/2009 17:41, Magnus Persson wrote:
In this case one needs to check that after the two stones are captured
the cap
In this case one needs to check that after the two stones are captured
the capturing single stone can be recaptured bringing us back to where
we started. If it is a "big eye" there is no recapture.
-Magnus
Quoting Brian Sheppard :
For black I think I prune this kind of two stone suicide
al
uld be suicide. For the moment, H5 is an
> > eye.
> >
> > David
> >
> >> -Original Message-
> >> From: computer-go-boun...@computer-go.org [mailto:computer-go-
> >> boun...@computer-go.org] On Behalf Of Brian Sheppard
> >> Sent: Wednesday, Ju
>For black I think I prune this kind of two stone suicide
>always no matter what the situation is (exception is ko). These
>prunings are probably wrong in some extremely rare cases.
How can you tell the difference between this kind of two-stone
self-atari, and a self-atari of two stones within
omputer-go-boun...@computer-go.org [mailto:computer-go-
boun...@computer-go.org] On Behalf Of Brian Sheppard
Sent: Wednesday, July 01, 2009 4:09 AM
To: computer-go@computer-go.org
Subject: [computer-go] Complicated seki with Ko
With X to move, Many Faces immediately gives about a 1% win rate, and
> To: computer-go@computer-go.org
> Subject: [computer-go] Complicated seki with Ko
>
> >With X to move, Many Faces immediately gives about a 1% win rate, and
> after
> >a few seconds, resigns, showing 23742 playouts with 0.5% win rate. 10
ply
> >principal variation, sta
Valkyria behaves the same as Many Faces in this position. It sees
maximum 1% winrate for Black.
The seki is not really detected by Valkyria, J6 is simply pruned for
both players. For white it is just stupid suicide with too many
stones. For black I think I prune this kind of two stone suici
>With X to move, Many Faces immediately gives about a 1% win rate, and after
>a few seconds, resigns, showing 23742 playouts with 0.5% win rate. 10 ply
>principal variation, staring with A7. I don't have any special code to
>detect superko or give-2, get-1 in playouts, but the playouts don't
gene
To: computer-go@computer-go.org
> Subject: [computer-go] Complicated seki with Ko
>
> Here is a position that exposed some bugs in Pebbles. Maybe it will help
> you.
>
> 1 2 3 4 5 6 7 8 9
> A - O - O X - - X -
> B - X O - O X - O O
> C - O O - O - X O -
> D X X X
ter-go.org] On Behalf Of Jason House
> Sent: Tuesday, June 30, 2009 10:25 AM
> To: computer-go
> Subject: Re: [computer-go] Complicated seki with Ko
>
> Is it possible to explicitly use a monospace font? I can't read your
> board positions.
>
> I haven't heard of an
Not sure this helps, but...
I found send-two receive-one, as in your example, to be the most
common non-simple ko cycle in my program. The program was heavy, so
forbidding "send two" added little to the total cost. Specifically,
the rule forbade playing on an isolated empty intersection that
neigh
It might, but the iPhone mail viewer does not.
Sent from my iPhone
On Jun 30, 2009, at 2:00 PM, Álvaro Begué
wrote:
Jason,
Gmail has an option "show in fixed width font" that is perfect for
these situations.
Álvaro.
On Tue, Jun 30, 2009 at 1:25 PM, Jason House> wrote:
Is it possible to
zen builds sekis, and occasionally wins games that way.
s.
On Tue, Jun 30, 2009 at 1:25 PM, Jason House wrote:
> Is it possible to explicitly use a monospace font? I can't read your board
> positions.
>
> I haven't heard of any handling of seki in playouts except for Remi's
> CrazyStone. I don't
Jason,
Gmail has an option "show in fixed width font" that is perfect for
these situations.
Álvaro.
On Tue, Jun 30, 2009 at 1:25 PM, Jason House wrote:
> Is it possible to explicitly use a monospace font? I can't read your board
> positions.
>
> I haven't heard of any handling of seki in playou
Is it possible to explicitly use a monospace font? I can't read your
board positions.
I haven't heard of any handling of seki in playouts except for Remi's
CrazyStone. I don't think he's ever given specifics on how he did it.
Maybe he'll respond to your e-mail?
Sent from my iPhone
On Jun
Here is a position that exposed some bugs in Pebbles. Maybe it will help
you.
1 2 3 4 5 6 7 8 9
A - O - O X - - X -
B - X O - O X - O O
C - O O - O - X O -
D X X X O O O O O O
E - O X X X O X O O
F - - O X O X X X X
G - - X X O O X X -
H - O X O - O O X X
J - O X O O - X - X
X to play.
20 matches
Mail list logo
