RE: [computer-go] November KGS online results
> On Tue, 2006-11-07 at 10:20 -0500, House, Jason J. wrote: > > I believe there's an alternate to option #3. Force the bot to play > > only one game at a time and respawn. If leaving by timeout doesn't > > cause an exit from kgsGtp, it does at least cause a call to > > kgs-game_over which can cause the bot to exit. > > Bot does not exit from KGS, it just leaves game and starts waiting for > another. So next thing seen in the log file is start of the next game. For some reason, I thought there was a parameter in the kgsGtp configuration file that would allow the bot to play one game and then exit. That's not there. It seems that kgs-game_over is intended to be the solution to detecting a clean opportunity to disconnect. If the opponent leaves (or doesn't show up) for 5 minutes, it'll call kgs-game_over before waiting around for another game. In a tournament, if the bot always exits when it receives that command (and then gets respawned by whatever is calling kgsGtp), then the bot will reconnect back in its tournament game. ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
RE: [computer-go] November KGS online results
On Tue, 2006-11-07 at 10:20 -0500, House, Jason J. wrote: > I believe there's an alternate to option #3. Force the bot to play > only one game at a time and respawn. If leaving by timeout doesn't > cause an exit from kgsGtp, it does at least cause a call to > kgs-game_over which can cause the bot to exit. Bot does not exit from KGS, it just leaves game and starts waiting for another. So next thing seen in the log file is start of the next game. >From kgsGTP viewpoint opponent escaped. Normally it would mean just that but in tournament games clock keeps running and the bot whose kgsGTP got bored loses on time. > > -Original Message- > It seems that GoComputer was away for more than 5 minutes which makes > opponent > bot to leave game permanently even in tournament. > This means that there must be human in attendance to > reconnect bot before it runs out of time :-( > > There are 3 alternative solutions to this problem: > 1) kgsGtp is fixed so that it does not leave tournament games even when > opponent bot is absent for more than 5 minutes. > > 2) If opponent crashes for more than 5 minutes or is not present for 5 > minutes at start of game and thus makes its opponent to leave game and > lose on time: Crashing or initially absent opponent should forfeit > game. > > 3) Bot authors make some code that monitor kgsGtp.log-0.log file for > "Leaving game." -message and then deliberately exit bot. This would > make > bot disconnect from server and with rejoin script around calling kgsGtp > bot would then reconnect and rejoin game. Alternatively human is > following game and makes it reconnect. > ___ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ -- Aloril <[EMAIL PROTECTED]> ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
RE: [computer-go] November KGS online results
I believe there's an alternate to option #3. Force the bot to play only one game at a time and respawn. If leaving by timeout doesn't cause an exit from kgsGtp, it does at least cause a call to kgs-game_over which can cause the bot to exit. -Original Message- It seems that GoComputer was away for more than 5 minutes which makes opponent bot to leave game permanently even in tournament. This means that there must be human in attendance to reconnect bot before it runs out of time :-( There are 3 alternative solutions to this problem: 1) kgsGtp is fixed so that it does not leave tournament games even when opponent bot is absent for more than 5 minutes. 2) If opponent crashes for more than 5 minutes or is not present for 5 minutes at start of game and thus makes its opponent to leave game and lose on time: Crashing or initially absent opponent should forfeit game. 3) Bot authors make some code that monitor kgsGtp.log-0.log file for "Leaving game." -message and then deliberately exit bot. This would make bot disconnect from server and with rejoin script around calling kgsGtp bot would then reconnect and rejoin game. Alternatively human is following game and makes it reconnect. ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] November KGS online results
On Mon, 2006-11-06 at 19:29 +, Nick Wedd wrote: > The results of yesterday's KGS bot tournament are now reported at > http://www.weddslist.com/kgs/past/20/index.html > > Congratulations to MoGo! > > Nick Resign in won position -- Fun fact: In MoGoBot-SimpleBot game at one point SimpleBot was sure it was going to lose: move made: b g3 0.147s B+0.4 win G3 prob. 0.000 O to move: ABCDEFGHJ +-+ 9|.XOXXOO.O| 9 8|.XOXXXOO.| 8 7|XOXXX| 7 6|OXX.X| 6 5|XXO..| 5 4|X.XXXOOOX| 4 3|X..XOOXOO| 3 2|X..XO...O| 2 1|.OOO.| 1 +-+ ABCDEFGHJ Reason is that it doesn't play inside unconditionally decided areas in random games in UCT. This was problem because scoring at end of game didn't score unconditionally dead stones correctly. This means that if I had enabled resigning for tournament, SimpleBot would have resigned above instead of playing G3. When both sides are unconditionally decided it uses old Python code so no problems later in the game. Forfeit games in KGS3 - In new KGS3 you can look at unfinished games too, so forfeit is not problem for viewing games as it was with KGS2. For example: http://files.gokgs.com/games/2006/11/5/GoComputer-HBotSVN.sgf Leaving game after 5 minutes About IdiotBot losing by time: http://files.gokgs.com/games/2006/11/5/GoComputer-IdiotBot.sgf It seems that GoComputer was away for more than 5 minutes which makes opponent bot to leave game permanently even in tournament. This means that there must be human in attendance to reconnect bot before it runs out of time :-( There are 3 alternative solutions to this problem: 1) kgsGtp is fixed so that it does not leave tournament games even when opponent bot is absent for more than 5 minutes. 2) If opponent crashes for more than 5 minutes or is not present for 5 minutes at start of game and thus makes its opponent to leave game and lose on time: Crashing or initially absent opponent should forfeit game. 3) Bot authors make some code that monitor kgsGtp.log-0.log file for "Leaving game." -message and then deliberately exit bot. This would make bot disconnect from server and with rejoin script around calling kgsGtp bot would then reconnect and rejoin game. Alternatively human is following game and makes it reconnect. In this case it was IdiotBot that lost and nobody cares about it ;-) However, what if it was for example MoGoBot as black in above game? That might have changed winner to firstgo. I think something like this happened in test tourmnament too, but that time game length was 3 minutes which is less than 5 minute threshold. I think that sometime in future it will happen in some important game too. My personal preference is 1, 2 and 3. 1: I think this is bug in kgsGtp 2: Better this way, because crashing/being absent is more fixable than fixing kgsGtp by bot author. Log file (see at 9:35:03 and 9:40:01): Nov 5, 2006 9:34:00 PM org.igoweb.igoweb.client.gtp.P FINE: Starting game as black against GoComputer Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Command sent to engine: boardsize 9 Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Command queued for sending to engine: clear_board Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Command queued for sending to engine: komi 7.5 Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Command queued for sending to engine: kgs-time_settings absolute 780 Nov 5, 2006 9:34:00 PM org.igoweb.igoweb.client.gtp.P i WARNING: Opponent has left game. Will give them 5 minutes to return. Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Got successful response to command "boardsize 9": = Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Queued command sent to engine: clear_board Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Got successful response to command "clear_board": = Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Queued command sent to engine: komi 7.5 Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Got successful response to command "komi 7.5": = Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Queued command sent to engine: kgs-time_settings absolute 780 Nov 5, 2006 9:34:00 PM org.igoweb.kgs.client.gtp.GtpClient d FINEST: Got successful response to command "kgs-time_settings absolute 780": = absolute 780 estimated max moves: 38 Nov 5, 2006 9:34:55 PM org.igoweb.igoweb.client.gtp.P i WARNING: Opponent has left game. Will give them 5 minutes to return. Nov 5, 2006 9:34:57 PM org.igoweb.igoweb.client.gtp.P h FINE: Opponent has returned. Nov 5, 2006 9:34:57 PM org.igoweb.igoweb.client.gtp.P h FINE: Opponent has returned. Nov 5, 2006 9:34:58 PM org.igoweb.igoweb.client.gtp.P i WARNING: Opponent has left game. Will give them 5 minutes to return. Nov 5, 2006 9:35:00 PM
Re: [computer-go] November KGS online results
Nick Wedd wrote: The results of yesterday's KGS bot tournament are now reported at http://www.weddslist.com/kgs/past/20/index.html Thank you Nick for the report. I think there is a little bug in the formal division results: aya and gnu have respectively 48 and 47 wins, which is quite a lot for 6 rounds ;-). Sylvain ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
