On May 7, 2008, at 4:54 PM, Gian-Carlo Pascutto <[EMAIL PROTECTED]> wrote:
Evan Daniel wrote:
It is entirely within the power of the other bots to not lose on
time.
I am not sure that is true.
LeelaBot should be perfectly capable of playing about 12 moves per
second in the default configuration.
However, it seems either KGS or kgsGtp do not (correctly) account
for connection lag, or the interface adds lag of its own. If it is
indeed connection lag that is the problem, KGS is about 150ms from
the tournament machine, which means Leela can't actually play more
than 6 or 7 moves per second at best, even if the engine itself
would move at infinite speed. I think that in the actual game, the
speed was closer to 2 moves per second and this was not enough to
avoid the time loss.
I was under the impression that KGS gives no assistance with lag
except in sometimes when passing.
I probably overengineered my time management, but I measure the lag,
time left, and moves remaining while the game is going on and adjust
my safety buffer. Ending a game with 3 seconds left (like occurred in
the tornament) is not atypical for me. I lost a game on time in this
past tournament from poor undo handling (losing more than a minute)
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
