Re: [Bug-gnubg] Doing a rollout as a background job

[Michael Petch]

Hi Tim,

I do not believe the settings that define each level are documented anywhere
but there is an indirect way to  find out.

I would build a 2D variant of GnuBG on your Linux/Unix system (Enough to get
access to the menus). Run the gui from the command line so that you can
watch the console output. Then change the options in Gnubg for the level you
want. After you click OK on the rollout settings page the console should
show all the commands that were issued to change from one setting to
another. For example I went to Settings/Rollout then clicked on "First Play
Both" selected "World Class" and the console output showed:

(No game) set rollout player 0 chequer plies 2
(No game) set rollout player 1 cubedecision plies 2
(No game) set rollout player 1 chequer plies 2
(No game) set rollout truncation cube plies 2
(No game) set rollout truncation chequer plies 2

Example 2: If I changed the Rollout filter to Huge I would see this:
(No game) set rollout player 0 movefilter 2 0 0 20 0.440
(No game) set rollout player 0 movefilter 3 0 0 20 0.440
(No game) set rollout player 0 movefilter 3 2 0 6 0.110
(No game) set rollout player 0 movefilter 4 0 0 20 0.440
(No game) set rollout player 0 movefilter 4 2 0 6 0.110
(No game) set rollout player 1 movefilter 1 0 0 20 0.440
(No game) set rollout player 1 movefilter 2 0 0 20 0.440
(No game) set rollout player 1 movefilter 3 0 0 20 0.440
(No game) set rollout player 1 movefilter 3 2 0 6 0.110
(No game) set rollout player 1 movefilter 4 0 0 20 0.440
(No game) set rollout player 1 movefilter 4 2 0 6 0.110

You can then take these lines and then put them in a script for batch
rollouts.

One thing you may or may not know is that all Gnubg's settings get saved
into ~/.gnubg/gnubgautorc . This file contains all the commands that get pre
executed when you launch gnubg. When you "Save Settings" all the settings
get saved to that file.

One thing you can do is take a default gnubgautorc file (removing
gnubgautorc should force gnubg to recreate a default version) make all the
changes in the gui for the rollouts then "Save settings". Take the
gnubgautorc before and after the changes and run diff on them. You should
see all the commands that are different.

PS: This technique of watching the console doesn't work on the windows GUI
version (that I can tell) even when the "Messages" panel is enabled.

I hope this helps.

Michael


On 10/08/09 7:56 AM, "Timothy Y. Chow" <address@hidden> wrote:

> Michael Petch wrote:
>> Put this in a file rollout1
>> 
>> set player 0 name player1
>> set player 1 name player2
>> set gnubgid HN/ACAZiWzAMIw:sAFnAaAAEAAA
>> hint
>> cmark move set rollout 1 2
>> analyse rollout move
>> save position "rollout1.sgf"
>> 
>> And then did
>> 
>> nice -19 gnubg -t <rollout1 >rollout.log 2>&1
> 
> This worked; thanks very much.
> 
> What I am wondering now is how to set the parameters.  One of my main
> reasons for doing a rollout as a background job is to be able to do
> rollouts at higher than the expert level, which takes a long time.
> But how does one set the rollout parameters so that the rollout is
> done at the world-class/supremo/grandmaster level?
> 
> Tim
> 
> 
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>