[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnubg] Can I fully avoid gnubg.command output?

From: Aslak Grinsted
Subject: [Bug-gnubg] Can I fully avoid gnubg.command output?
Date: Thu, 23 Mar 2006 15:16:53 +0200

Hello Everybody

I am attempting to write a python script that uses .findbestmove to play
against itself (money game). I am then saving the position and the
cfevaluate results after each move. I am afterwards looking at the empirical
cdf of various indicators (such as (pipO-pipX)/(pipO+pipX)) to find unusual
positions that I want to look closer at. 

My problem is that I don't want gnubg to keep past played games in memory
and I would like to start a new money session after each game. But if I
execute gnubg.command('new session') and I already have a session started
then gnubg will ask me if I am sure I want to end the current session. Is
there any way I can avoid that?

I would also like to avoid the drawing of the board whenever I execute
gnubg.command('move xxx') or gnubg.command('roll'). Essentially turning
verbose off. 

Suggestion: Perhaps console-output from gnubg.command could be returned in a

Aslak Grinsted
Music page: http://www.phunck.com

reply via email to

[Prev in Thread] Current Thread [Next in Thread]