The summary looks good to me.

Just to clarify HouseBot's round 3 performance...

HouseBot would normally resign lost games, but it has a check in there
that prevents resignation when it has not thought deeply enough about
every move.  19x19 is such a big board that it does not hit that
threshold in before endgame.  In endgame, however, it contains logic
to stop thinking early when there's nothing to think about.
Unfortunately, the interaction of the two pieces of logic means that
it does not resign in endgame.  I guess it can be thought of as a
stress test for the time management in other bots ;)

It's time management code worked as expected.  Doing some quick number
crunching, I believe the time management code would want about 4.75
seconds left at such a late point in the game.  Relatively speaking, 6
seconds is viewed as a lot of spare time.

I was actually more worried about round 1 when HouseBot crashed at the
start of the cleanup phase with 24 seconds left.  I had to quickly
restart the bot.  That crash was because HouseBot had an internal
buffer overflow as it queued up commands as kgsGtp replayed the entire
game.  The 458-move game overflowed the 256 element command buffer.
Thankfully that didn't happen again when I restarted the bot.  I
increased the buffer size between rounds 1 and 2 to prevent that from
happening again.
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/

Reply via email to