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/
