On Tue, 2007-03-27 at 20:49 -0400, Álvaro Begué wrote: > I don't like the idea of giving extra time every move. The effect is > very similar to adding a fixed amount of time, since go games have > fairly constant lengths. Lags are probably tiny these days for most > people anyway. And you do get an update of how much time you have > left, so if you do something simple like spending a constant fraction > of the time left each turn, your program will adjust itself to the lag > and not run out of time. In short, I don't see what problem this > solves.
There is a fixed amount of overhead that is being charged to the programs unfairly even under the very best of conditions, and I'm just trying to compensate for that. The idea is to guarantee that the time actually spent computing the move is an upper bound on the time the server believes was spent. Without some small fudge this is clearly impossible. Based on the times being reported on CGOS, I believe that factor should be much smaller than the 1 second I was adding. So I decreased to 1/4 second. I have also had two separate reports of programs losing on time despite the fact that they were playing "instantly" due to various factors which might include interface speed, network lag, even CGOS server overheads (although this appears to be quite small.) I don't want programs to lose that way. So a tiny fudge is subtracted from time spent as long as it doesn't drop it below zero. - Don _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
