Re: [computer-go] still an outstanding command

[Jacques Basaldúa]

I think it is OK to lose the one game where it crashes, but it should  
be able to restart for new games at least.



Martin


You can restart everything Ok, but you have to kill the process java.exe
and then run kgsgtp again.

When the program crashes, the clock is still running, I think.
If it is so, I think it is correct to be able to continue the game.
You lose the time involved and any online learned info. Looks fair to me.

Jacques.

___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/

[computer-go] still an outstanding command

[Martin Mueller]

This is caused by the fact that both CzechBot and Fuego (probably)  
were

stuck up in reading, probably either getting dead-locked or stuck in
some infinite loop; so in fact the outstanding command was genmove,  
and

neither of these ever chose which move to play. CzechBot wasn't even
printing out any progress lines.

I think the problem here is that when kgsGtp reconnects, it does not
restart the engine; I think doing that would help a lot in these
situations, since a stuck engine would be restarted by the reconnect.
Right now, after reconnecting, kgsGtp was still waiting for the  
original

genmove command from old connection to finish.


Yes, FuegoEx had crashed as well in that game, due to a bug I recently  
introduced.


I think it is OK to lose the one game where it crashes, but it should  
be able to restart for new games at least.


Martin___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/