Eighty-sixth KGS Computer Go Tournament

In the table above,
   0 is a loss
   1 is a win
   J is jigo
   left superscript is the player's colour
   right superscript is the round in which the game was played
   a subscript shows how the result was determined:
      R for resignation
      T for time
      F for forfeit
      a number for the points difference after counting.
All the 0s, 1s and Js are links to the game record.

Nine players registered for the tournament. To make the numbers even, I added 'gnugo3pt8', a build of GNU Go running on one processor of my own Windows system.

I have been advised that I should not compete in these events myself, as it might prejudice my decisions. But GNU Go is not mine, and I believe I am not biassed towards it. I merely think that a game against GNU Go is better than a bye. I believe GNU Go has advantages for use in this way:

It is well-behaved. It makes legal moves, and handles the clean-up procedure correctly.
It is not strong enough to beat any player that has a chance of winning.
It is not so weak that it loses all its games

Results


AyaMC vs gnugo3pt8
At end of game

In its round 6 game with gnugo3pt8, AyaMC showed that the middle of a 13×13 board is bigger than the edges, as seen to the right.


ManyFaces1 vs StoneGrid
After both players first passed in turn

In the round 7 game between ManyFaces1 and StoneGrid, both players passed in the position shown to the left, and marked the dead stones as shown. They then disagreed about the status of some stones, so play resumed. In this clean-up phase, StoneGrid captured two white stones in the top left, but ManyFaces1 did not capture any of the three dead black groups. Therefore the game was scored as a win to StoneGrid, although ManyFaces1 coul;d have won by removing the three dead black groups.

In round 10, Zen19S lost its only game of the tournament, to ManyFaces1.


Orego12 vs stv
Move 68

In round 14, Orego12 played the move shown to the right, against stv. This looks so strange that I wonder if it was caused by a bug.


AyaMC vs StoneGrid
Move 17


StoneGrid vs AyaMC
Move 16

In both rounds 14 and 15, AyaMC played StoneGrid. In both games, StoneGrid chased AyaMC's stones in a ladder which was broken by a stone belonging to AyaMC. AyaMC won both games. A position from each game is shown to the left.

Also in round 15, MCark failed to join its game with Orego12, and lost on time.

Annual points

Players receive points for the 2012 Annual KGS Bot Championship as follows:

Zen	8
Many Faces of Go	4
pachi	4
Aya	2
StoneGrid	1

Details of processor numbers, power, etc.

AyaMC: Aya, running on 6 cores of an i980X, at 3.3GHz.
gnugo3pt8: GNU Go, running on one Intel i5-2500 CPU @ 3.30GHz.
ManyFaces1: Many Faces of Go, running on an Amazon EC2 Cluster Compute Eight Extra Large Instance, 2 x Intel Xeon E5-2670, using 16 cores, 16 threads, and 48 GB of memory.
MCark: MC_ark version 6.0, running on Core-i7 2600K 3.40GHz*4core (8 threads) 16GB RAM)
nomiBot: nomitan, running on a machine with 2 Xeon 5680 processors (total of 12 cores).
Orego12: Orego, running on one of the five nodes of a custom Linux cluster build by PSSC Labs: the node has two AMD Six Core Dual Opteron 2427 2.2 GHz (12 cores total), 8 GB RAM, Centos Linux.
pachi: pachi, running on an Intel i7-2600 (4 cores, 8 threads) with 16GiB RAM.
StoneGrid: StoneGrid, running on an Intel Core i7-2600.
stv: Steenvreter, maybe running 46 threads each at 2.2 GHz, on a system whose use was generously provided by the Maastricht games and AI group.
Zen19S: Zen, running on a mini computer cluster of a dual 6-core Xeon X5680@3.6 GHz 24GB RAM, a 6-core i7 3930K@4.2 GHz 16 GB RAM, a 6-core Xeon W3680@4 GHz 12 GB RAM, and a 4-core i7 920@3.4 GHz 6 GB RAM PC connected via a GbE LAN. 4 PCs (28 cores) total.