[computer-go] Dynamic komi at high handicaps

After many (hand-operated) games with dynamic komi in high handicap situations I have - amongst other things - found the following for board size 19x19, when the side who has to catch up uses dynamic komi: (i) At handicap 7 the dynamic komi seems to give at least one additional level (one stone)

Re: [computer-go] Dynamic komi at high handicaps

Good work Ingo. But why should it be near 50%? If it is, the komi is too large.(if giving handicap) You just have to reserve some thinking time for reruns, in case the komi estimate from the last move doesn't fit anymore. Stefan (ii) Also on 13x13 board dynamic komi seems to help, although

Re: [computer-go] MoGo policy: capture stones anywhere?

On Aug 31, 2009, at 10:12 PM, terry mcintyre wrote: If you maintain a list of strings ( connected groups ) of stones and their liberty counts - or perhaps the actual liberties - it should be fairly quick to find a string with just one liberty. I'm currently using pseudoliberties, so that

[computer-go] MoGo policy: capture stones anywhere?

IIRC, Fuego has an urgent rule that captures the last-played stone. That rule applies before any others. Then the mop-up capture rule applies just before playing randomly. Mop-up capture is facilitated by a list of strings in atari. Pebbles keeps such a list, like Many Faces. Having such a list

RE: [computer-go] MoGo policy: capture stones anywhere?

I use real liberties. I think if you want the playouts to do much computation on groups based on liberty count you should switch to using real liberties. I don't think any of the strong programs use pseudoliberties. From: computer-go-boun...@computer-go.org

RE: [computer-go] MoGo policy: capture stones anywhere?

But note that Fuego is using a GNU license, so if you incorporate any of the Fuego code into your own app, you will have to make your own app available under the GNU license and distribute source to your customers. David I strongly recommend reading the Fuego source code. Their ideas and

Re: [computer-go] MoGo policy: capture stones anywhere?

On Sep 1, 2009, at 8:11 AM, David Fotland wrote: I don’t think any of the strong programs use pseudoliberties. Interesting! Can those involved with other strong programs verify this? My board code is descended from my Java re-implementation of libEGO. I tried writing one using real

Re: [computer-go] MoGo policy: capture stones anywhere?

I never tried pseudoliberties in Valkyria. It actually stores arrays of the liberties in addition to the count. This make programming complex algorithms simple, but perhaps not the most efficient way. -Magnus Quoting Peter Drake dr...@lclark.edu: On Sep 1, 2009, at 8:11 AM, David Fotland

[computer-go] KGS bot tournaments

I have announced the schedule for the bot tournaments on KGS, for the rest of the year: http://www.weddslist.com/kgs/future.html September Sunday 20th 9x9 October Sunday 4th 19x19 November Sunday 8th 19x19 December Sunday 6th 9x9 Nick -- Nick Weddn...@maproom.co.uk

Re: [computer-go] MoGo policy: capture stones anywhere?

2009/9/1 Peter Drake dr...@lclark.edu: On Sep 1, 2009, at 8:11 AM, David Fotland wrote: I don’t think any of the strong programs use pseudoliberties. Interesting! Can those involved with other strong programs verify this? My board code is descended from my Java re-implementation of libEGO. I

[computer-go] MoGo policy: capture stones anywhere?

Interesting! Can those involved with other strong programs verify this? Pebbles isn't a particularly strong program, but using real liberty counts is better. I have recently taken Pebbles offline to renovate internals. I am adding lists of liberties, too. I am convinced that the richer