In the recent kgs tournament, I noticed there is a slight difference between cgos and kgs on time_left command.I think it worths pointing out. Hope it will be helpful for new go developers on understanding of the time control commands.
cgos always sends time_left command right before genmove command. kgs always sends time_left command right after genmove command. In the tournament, StoneGrid assumed the cgos sequence, assuming the last time_left command was the accurate one, and simply ignored the time_settings command. Since I had tested StoneGrid primarily on the cgos, I assumed kgs will send the commands in the same sequence. The consequence of the oversight is when the previous game finished, and next game started, StoneGrid used the time_left command from last game, and rushed to generate the first move. It is not an issue if it plays black, since it plays the center point anyway. But if it plays white, it picks less optimal move. Obviously I need to fix my program to reset the time controls on the time_settings command, and should not always expect a time_left command after the time_settings command on the first move. _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
