Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Darren Cook
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+ stones

[computer-go] Re: Myungwan Kim 8P versus Many Faces of Go

2009-08-06 Thread Ingo Althöfer
Terry McI announced: On Friday, August 8th, at 3 PM Eastern Daylight Time, Myungwan Kim 8P will play against Many Faces of Go. One question, do you mean Friday, August 7th, 2009 or Saturday, August 8th, 2009 or another year ;-) Thanks for informing us. Cheers, Ingo. -- Neu: GMX

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Harry Fearnley
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

Re: [computer-go] Re: Myungwan Kim 8P versus Many Faces of Go

2009-08-06 Thread terry mcintyre
Friday the 7th. You may check ManyFaces1 on KGS -- this is the program which will be playing - it is using 8 cores now - may be using more cores by Friday. Terry McIntyre terrymcint...@yahoo.com “We hang the petty thieves and appoint the great ones to public office.” -- Aesop

[computer-go] Re: self atari

2009-08-06 Thread Dave Dyer
It's easy to construct self-atari of unlimited size that both can occur and should be played, if the capturing move that follows the self-atari is then recaptured in a snapback. ___ computer-go mailing list computer-go@computer-go.org

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Michael Williams
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

RE: [computer-go] Re: Myungwan Kim 8P versus Many Faces of Go

2009-08-06 Thread David Fotland
We got 32 cores working yesterday so it will use at least 32 cores. At last year’s world championship we used 32 cores because more cores was weaker (even though we had 1024 cores available). Today’s version should scale better, so if we have time today we’ll play 32 vs 64 and see if 64 cores

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Christian Nentwich
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

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Peter Drake
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:

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Jason House
On Aug 6, 2009, at 12:19 PM, Peter Drake dr...@lclark.edu 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.

[computer-go] RAVE problems

2009-08-06 Thread Martin Mueller
While RAVE is a very strong heuristic, in Fuego it occasionally suppresses the only good move. Do others have similar experiences? Here are two cases that I just added to our regression tests. Does anyone have more?

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Nick Wedd
In message 333558b6-c030-4656-8c35-0b766185a...@lclark.edu, Peter Drake dr...@lclark.edu 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

RE: [computer-go] Double/Triple Ko situation

2009-08-06 Thread David Fotland
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

Re: [computer-go] Double/Triple Ko situation

2009-08-06 Thread Isaac Deutsch
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

Superko vs transposition table (was Re: [computer-go] Double/Triple Ko situation)

2009-08-06 Thread Peter Drake
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

RE: Superko vs transposition table (was Re: [computer-go] Double/Triple Ko situation)

2009-08-06 Thread David Fotland
I check for superko during the UCT tree part of the search, but just simple ko during playouts. -Original Message- From: computer-go-boun...@computer-go.org [mailto:computer-go-boun...@computer-go.org] On Behalf Of Peter Drake Sent: Thursday, August 06, 2009 11:42 AM To: computer-go