Don wrote: > On Mon, 2007-07-16 at 11:16 -0400, Jason House wrote: > > I would. It could even be used as an opportunity to go run on another > > server for a bit (discussed previously). I guess if this option was > > done, however, a small delay between the end of the last game and the > > start of the next round would be needed. Otherwise, the two players > > in the final game would miss the next round on the server if they take > > the opportunity to shut down. > > There is a several second delay. But it doesn't matter, I don't > remember the details but the client does the right thing if you exit > properly, with a sentinal file. There is no race condition that will > cause you to lose a game. I seem to remember that you must respond to > a command before you will get scheduled for the next round, even if you > don't disconnect.
For what it's worth I've on several occasions seen the last two players in a round be skipped in the scheduling of the next round (but reappear after that), where at least MonteGNU responded as quickly as it could to the gameover message. > I hate to separate this, they go together in a natural way. You > probably would not implement one without the other. GTP used to have a > separate genmove command for each color and combined them and I can't > see having 4 commands or even 2. I also don't want to have to hit > programmers with several commands to be implemented. > > However, it might be good to separate the ELO rating by making this > command have 4 parameters instead of 2: > > cgos_gameinfo FatMan 1800 ggmc-x86-1.3Q 2008 > > Even though this will always be a cgos extension due to the fact that it > is a cgos rating, I wouldn't mind getting the opinion of the GTP > creators on whether they consider one form more correct than another. > One could imagine adding extra parameters such as the color and doing it > like this: > > cgos_gameinfo white FatMan 1800 > cgos_gameinfo black ggmc-x86-1.3Q 2008 > > or > > cgos_gameinfo white name Fatman > cgos_gameinfo white elo 1800 > ... etc > > or separate commands like you propose: > > cgos_white-elo > cgos_white-name > cgos_black-elo > cgos_black-name > > or cgos_name white Fatman > cgos_elo white 1800 > > > If Gunnar gives his opinion, I will probably take his advice. My opinion is that this information has no business in the engine in the first place but should be handled at the client level. But if it must go to the engine I don't see any point in splitting it up. I prefer the cgos-gameinfo FatMan 1800 ggmc-x86-1.3Q 2008 form (and with a dash after cgos as has already been pointed out). --------- Unrelated, except that it took place in CGOS, 9x9 game 75117 http://cgos.boardspace.net/9x9/SGF/2007/07/16/75117.sgf featured a somewhat rare seki on the board near the end, until ggmc broke it with a superko violation. The type of seki, two one-eyed groups versus one without (proper) eyes, is of course well-known but it usually comes with fewer strings and false eyes. A B C D E F G H J 9 . O . O O . O . . 9 8 . O O O . O O O O 8 7 O O + O O X O X O 7 6 . O O X X X X X X 6 5 O . O O X X . X X 5 4 O O O X O X X X . 4 3 X O X X O X O O X 3 2 X X X . O X O O . 2 1 X . X O . O . O O 1 A B C D E F G H J /Gunnar _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
