Re: [Bug-gnubg] feature request: Automatic rollouts on pos-files

[crawling . weasel]

> > I've now tried this script and it doesn't work. The rollouts are not
> > saved in the sgf file. Can anyone make it work?
> 
> This is the usual quirk; the work-around is to perform a move and go
> back... but I imagine this is a bit difficult inside the python script.

Thanks! As I know which files contain moves, which double-decisions 
and which contain take-decisions I can handle this ... partly:

If it is a take-decision:

     gnubg.command("set turn GNUBG")
# no idea why I have set the turn ...
     gnubg.command("play")
     gnubg.command("hint")
     gnubg.command("rollout =cube")
     gnubg.command("take")
     gnubg.command("save match " + filename + ".sgf")

if it is a double-decision:

     gnubg.command("hint")
     gnubg.command("rollout =cube")
     gnubg.command("double")
     gnubg.command("save match " + filename + ".sgf")


But what do I do if it is a move?

     gnubg.command("hint")
     gnubg.command("rollout =1 =2 =3 =4 =5")

And then? How to move without knowing which move is legal? My first 
idea would be to tell gnubg to play my move but I have no idea how to do 
this. Any ideas?

And another question: Where can I find a documentation of the sgf-file-
format? How do I extract the analysis from sgf?

Thanks a lot in advance

Hans