Re: [computer-go] 2nd KGS Computer Go Tournament

["William M. Shubert" <wms@xxxxxxxxxx>]

Yes, correct. This is a bug, but not quite in the way that you suspect.
Actually, KGS is supposed to not allow programs to play tournament games
unless they can answer the final_status_list command, which is why that
command is mis-managed in tournament games. Now that Nick has run a
tournament already where this requirement wasn't there, I will talk with
him about the best way to do it. Since he is administering these
tournaments, I'll let him decide how best to do things.

On Mon, 2005-05-09 at 11:17 +0200, Karol Golab wrote:
> On Mon, May 09, 2005 at 10:05:03AM +0100, Nick Wedd wrote:
> > If the problem were genuine disagreement, I would agree with John.  But 
> > it isn't.  Some bots have game-end-handling code which is much worse at 
> > assessing status than their actual playing code.  For instance, LeGoBot 
> > plays at around 20k, but in its first-round game, it claimed at the 
> > game-end that its one-liberty black group, entirely surrounded by 
> > unkillable white groups, was alive.  LeGoBot's playing engine knew it 
> > was dead, the error was merely in its scoring engine.
> 
>   I think that the actual problem was more on KGS side - as far
> as I know LeGoBot did not return any status at all (it does not
> implement final_status_list command from what its author said).
> The problem occured because tlsBot returned the status and LeGoBot not.
> I would assume that the KGS engine interprets this as 'all stones
> live' which led to a disagreement.
> 
>   Cheers,
>   Karol
> 

_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/