It looks like the script cycles through directories, kicking off bots via a script file. Making that script file do some other server seems trivial. The trick in my mind is figuring out how to get things to terminate properly. I forsee two issues:
1. Supporting # of games to play before disconnecting This may require parsing data dumps while connected to a server. While the script currently handles CGOS, it becomes tougher to extend. kgsGtp can write a log file, and parsing of that log file is possible (even though in a different format). It may be possible to mix checks that are specific to different servers without conflict as long as the checks match... e.g. /gameover/ for CGOS and /kgs-game_over/ for KGS. It may be easier to delay writing a sentinel file until some set time after kicking off the bot. #2. Causing the bots to disconnect You're right that kgsGtp does not support a sentinel file, but kgs does send kgs-game_over following each game. It's relatively trivial to make the bot check a sentinel file and exit at the end of a game. I also wonder about when the CGOS client checks the sentinel file. This would affect the easy alternative in #1. Checks at the start of a game could make it disconnect just as the first round it'd play in begins. Checks at the end of the game would be more convenient. PS: Is there a bug in the script, it looks like GAMES=1 and GAMES=2 would cause the same effect. It may be correct to swap the following two lines to fix this (or GAMES-1 to GAMES) games += 1 File.new(TERM, "w") if games >= (GAMES-1) On 10/10/07, Urban Hafner <[EMAIL PROTECTED]> wrote: > > > On Oct 10, 2007, at 17:32 , Jason House wrote: > > > I get: > > 500 - Internal Server Error > > Sorry about that. It should work now (I hope). > > > I've wanted something like what you describe for running bots on > > CGOS and KGS. When I do see the script, I'll see what I can do > > about hacking in KGS support to it. > > I guess it shouldn't be too hard. Though I don't know if kgsgtp supports > the use of a sentinel file to stop after the current page. So you might > need to explicitly kill it. > > Urban > > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ > >
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
