>> [Aside: The only suggestion I would make would be to add a more
>> detailed rollout context to the analysis records. The current rollout
>> context shows number of trials, but not the full context including
>> truncation points, plies, etc.]
>That's incorrect - there's enough data held to allow resuming a rollout to
extend the number of trials.
It may be that the data is inside gnubg, but I am not finding it in the
dictionary returned by the python match() function. I'll take another look
as I am trying the suggestion below...
>> So:
>>
>> Is there some sequence of set commands I can issue so that I can see
>> what I want in the dictionary returned by gnubg.match()?
>>
>> Or must I continue to redirect stdout to a file and (ugh) parse the
>> output of 'hint'?
>The problem is that you need a move record to attach the analysis or
rollout results to.
>Then you could use the gnubg.command("analyse move") to get the results
back in the match dictionary.
<example omitted>
I'll give this a try. Much thanks!
David
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg
