Samuel Stewart wrote: > My name is Sam Stewart and I'm a student working with a research group > developing a Go AI. Recently, I have been utilizing CLOP (an optimization > system) to tune several parameters in our program. CLOP employs the > *twogtp*bridge, packaged with GoGui, along with the > *gogui-adapter*. CLOP managed to run about 1,000 games before the > *twogtp*bridge failed with the message: > "The Go program terminated unexpectedly" > After searching through the logs (attached) it appears that GnuGo failed to > generate a response to white. The *twogtp* bridge then forced white to quit > (our program, Orego) and calculated the final score. > > While the error is regrettably vague, I'm curious if anyone has had trouble > with the *twogtp* + GnuGo combination in the past? I welcome any > suggestions for further debugging/fixes. > > Note: I have also attached the complete *.sgf file of the game.
It's quite possible that gnugo is crashing due to a bug; in my experience it's rare but it does happen if you're running thousands of games. When it crashes it usually prints a detailed error report. If you pass the -debugtocomment option to twogtp, it should add any standard error output from gnugo to the game record, which would let you see the error text. -M- _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
