On Fri, Aug 7, 2009 at 5:51 AM, Folkert van Heusden
wrote:
> >> What is superko?
> >> My program keeps a list of all board-positions and then if it whants to
> >> do a move it checks if the new board-position is in the list. If so, it
> >> throws that move away. Are there other checks I need to do
>> What is superko?
>> My program keeps a list of all board-positions and then if it whants to
>> do a move it checks if the new board-position is in the list. If so, it
>> throws that move away. Are there other checks I need to do as well?
>
> Superko involves repeating a previous board position.
>> What is superko?
>> My program keeps a list of all board-positions and then if it whants to
>> do a move it checks if the new board-position is in the list. If so, it
>> throws that move away. Are there other checks I need to do as well?
>
> Superko involves repeating a previous board position.
In message <20090807092625.gj15...@vanheusden.com>, Folkert van Heusden
writes
What is superko?
My program keeps a list of all board-positions and then if it whants to
do a move it checks if the new board-position is in the list. If so, it
throws that move away. Are there other checks I need t
> I fixed allowing multiple suicide in playouts, but it didn't make the
> many wasted playouts go away on Sheppard's position.
> On further investivation, the problem has to do with the interaction
> between superko and the transposition table.
> Currently, Orego checks only simple ko most of t
Subject: Superko vs transposition table (was Re: [computer-go] Double/Triple
Ko situation)
I fixed allowing multiple suicide in playouts, but it didn't make the
many wasted playouts go away on Sheppard's position.
On further investivation, the problem has to do with the interaction
betwe
I fixed allowing multiple suicide in playouts, but it didn't make the
many wasted playouts go away on Sheppard's position.
On further investivation, the problem has to do with the interaction
between superko and the transposition table.
Currently, Orego checks only simple ko most of the tim
I planned to enter the august tournament but development progressed
slower than expected. I plan to enter the september tournament. You'll
have 1 weak bot more ;)
___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mai
I plan to compete, probably.
-Original Message-
From: computer-go-boun...@computer-go.org
[mailto:computer-go-boun...@computer-go.org] On Behalf Of Jason House
Sent: Thursday, August 06, 2009 9:38 AM
To: computer-go
Subject: Re: [computer-go] Double/Triple Ko situation
On Aug 6, 2009, at
In message <333558b6-c030-4656-8c35-0b766185a...@lclark.edu>, Peter
Drake writes
Actually, it's even worse than this: following LibEGO, my playouts
allow (multi-stone) suicide!
I may fix this before this weekend's KGS tournament.
(Speaking of which, where are all the contestants?)
Unfortuna
On Aug 6, 2009, at 12:19 PM, Peter Drake wrote:
I may fix this before this weekend's KGS tournament.
(Speaking of which, where are all the contestants?)
I procrastinate, but I'll compete. I may enter more than one bot, but
that depends on how much prep time I have.
_
Actually, it's even worse than this: following LibEGO, my playouts
allow (multi-stone) suicide!
I may fix this before this weekend's KGS tournament.
(Speaking of which, where are all the contestants?)
Peter Drake
http://www.lclark.edu/~drake/
On Aug 5, 2009, at 8:10 PM, Peter Drake wrote:
This is probably the best route. Either this, or get rid of the rule.
This rule cannot be shown to be correct in general, it may work for most
life and death problems, but can be wrong in semeai. You may get a nice
ELO increase, but you are still actively building a wrong rule into the
progra
You should set the limit to whatever yields the highest ELO in YOUR program.
Harry Fearnley wrote:
Darren Cook wrote:
The largest nakade shape is the rabbity six. My wild guess would be to
outlaw self-atari for groups of 7+ stones.
The fun thing about computer go is how hard it is to make har
Darren Cook wrote:
The largest nakade shape is the rabbity six. My wild guess would be to
outlaw self-atari for groups of 7+ stones.
The fun thing about computer go is how hard it is to make hard and fast
rules:
http://senseis.xmp.net/?BiggestKnownEyeSpaceForWhichThereIsANakade
Outlawing self-
> The largest nakade shape is the rabbity six. My wild guess would be to
> outlaw self-atari for groups of 7+ stones.
The fun thing about computer go is how hard it is to make hard and fast
rules:
http://senseis.xmp.net/?BiggestKnownEyeSpaceForWhichThereIsANakade
Outlawing self-atari of 18+ stone
The largest nakade shape is the rabbity six. My wild guess would be to
outlaw self-atari for groups of 7+ stones.
Sent from my iPhone
On Aug 5, 2009, at 11:10 PM, Peter Drake wrote:
On Aug 5, 2009, at 6:15 PM, Brian Sheppard wrote:
Pebbles has the same ko rules as Orego, but it doesn't ha
On Aug 5, 2009, at 6:15 PM, Brian Sheppard wrote:
Pebbles has the same ko rules as Orego, but it doesn't have the same
search behavior.
If Orego rejects self-atari moves of large strings, then the left
side should become a seki almost always. If you are seeing 60% wins
then something must be wr
>Orego thinks it's probably a win for O (around 60%, with a lot of
>variance from one run to another).
>On most runs, almost all of the playouts are discarded, because they
>get caught in cycles and hit the maximum playout length limit.
>Following LibEGO, Orego doesn't check for superko durin
Brian Sheppard wrote:
> I analyzed the following position as a win for O, but there are
> two or three kos involved (A1/A2, H1/G1, and the bent four at J9),
> so I am wondering if there are any other opinions.
>
> 1 2 3 4 5 6 7 8 9
> A X - X X - X X X -
> B O X X O X - X O O
> C - O O O X X O O O
Sheppard
Sent: Wednesday, August 05, 2009 2:20 PM
To: computer-go@computer-go.org
Subject: [computer-go] Double/Triple Ko situation
I analyzed the following position as a win for O, but there are
two or three kos involved (A1/A2, H1/G1, and the bent four at J9),
so I am wondering if there are any other
Orego thinks it's probably a win for O (around 60%, with a lot of
variance from one run to another).
On most runs, almost all of the playouts are discarded, because they
get caught in cycles and hit the maximum playout length limit.
Following LibEGO, Orego doesn't check for superko during p
I analyzed the following position as a win for O, but there are
two or three kos involved (A1/A2, H1/G1, and the bent four at J9),
so I am wondering if there are any other opinions.
1 2 3 4 5 6 7 8 9
A X - X X - X X X -
B O X X O X - X O O
C - O O O X X O O O
D O O X - X O O O -
E X O - X X
23 matches
Mail list logo
