On Fri, Jan 2, 2009 at 7:07 PM, Thomas Koch <[email protected]> wrote: > 1. Question: > > How can I save rollout results with python? I tried > > gnubg.command("hint") > gnubg.command("rollout =1 =2 =3") > gnubg.command("export position html...") > > But then the top moves of the hint are rolled out and the export sticks to > the simple analysis. Also if I type "rollout =1 =2 =3" as a command in the > GUI version it has no influence on the match record. I am on a 10.4 Mac so I > cannot switch to the most recent version of gnubg. >
Since nobody else answered this I fear the answer is as I expect: the rollout command is not linked to the analysis in the CL interface at present. That goes for the python interface as well. > 2. Question: > > Using python I am able to retrieve the position id with the command > "gnubg.positionid()", but I also need the match id. Is there an easy! way to > do that? > No, adding such a function is very easy, but that probably wont help you. dir(gnubg) under python, will tell you what commands are implemented: >>> dir(gnubg) ['__doc__', '__name__', 'board', 'cfevaluate', 'command', 'cubeinfo', 'eq2mwc', 'errorrating', 'evalcontext', 'evaluate', 'findbestmove', 'luckrating', 'match', 'matchchecksum', 'met', 'mwc2eq', 'navigate', 'nextturn', 'positionbearoff', 'positionfrombearoff', 'positionfromid', 'positionfromkey', 'positionid', 'positionkey'] >>> Christian. > Thanks in advance, > Thomas Koch > > > > -- > Backgammon in Berlin: http://berlinbg.wordpress.com > Der Backgammon Blog: http://graswurzelbackgammon.wordpress.com > > _______________________________________________ > Bug-gnubg mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-gnubg > > _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
