> > My write-up of yesterday's KGS online computer Go tournament is now
> > available, at http://www.weddslist.com/kgs/past/22/index.html > > > > Congratulations to MoGoBot, undefeated winner of both divisions! > > > > Nick > > "HouseBot obtained a won position against IdiotBot. However > it does not > implement the kgsGtp clean-up instruction, so IdiotBot was > able to claim > that its dead stones were alive and win the game." > > IdiotBot seems OK in disputed position, from logfile: FINEST: Got > successful response to command "final_status_list dead": = N1 > M11 C3 H10 > B1 M8 C9 N6 F13 A9 M2 A13 M4 > > Actually I think all stones are simply assumed alive after cleanup > phase. I think this is done by kgsGtp and bot has no control > over this. > > >From log file: INFO: Cleanup mode has ended by passes. It will be > assumed that all dead stones > have already been removed. It's been a very long time since housebot got the final status list wrong at the end of a game. I'll check with "ujh" who was running the bots to see if we have a kgs log of what happened at the end of that game. By default, housebot 0.4 plays until all stones are decided by Benson's algorithm for unconditionally safe stones. Otherwise, housebot plays in the uncertain regions until it kills something or leaves itself in atari. That makes final status list very easy to answer. This is also why it filled its eye in the seki later on. There are a few scenarios where that method leads to a position it can't score correctly, but they're very rare and didn't come up in the idiotbot game. Going into cleanup (at all) seems rather strange to me since I have faith in both housebot 0.4 and IdiotBot's handling of the final status list dead. Alas, this is all speculation until I can see the logs. _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
