Hi Ian, I'm with you on making the rollout reports easier to read. For those who prefer the old reporting, there could be an option for users to turn on if they wanted, with the default being the new easier-reading variety. What would you think of also converting the profiles to percents instead of fractions, too? It would get rid of those first zeroes. You could still leave one there in the cases where the value is under one percent, as is often true with the backgammon numbers. Spaces could be inserted in the line as needed to make all results line up when they are printed or cut-and-pasted elsewhere. Your first line in the example:
0.3462 0.0792 0.0030 - 0.6538 0.2416 0.0096 would become: 34.62 7.92 0.30 - 65.38 24.16 0.96 Do you think that would be an improvement? Mary Hickey > From: [email protected] > To: [email protected]; [email protected] > Date: Tue, 31 May 2011 12:32:51 +0000 > CC: [email protected] > Subject: Re: [Bug-gnubg] Fwd: Listing JSDs in rollouts > > Since no-one else has commented I'll chime in here: > > Adding the JSDs is a great idea, if it can be done tidily. > > Now I'm going to hijack this post somewhat, and develop the topic furhter: > > Gnubg has a larger problem in it's rollout reporting. Anyone who has seen XG > rollouts knows thay are much more succinct and readable than gnubg's. > > TO some extent, this is because XG has fewer options than gnubg (JSD-halting > is a good example), so gnubg rollouts are always going to have to contain > more data. > > However, XG does a great job of displaying the data so that it's easy to > compare the rollout results between plays without the rollout context > interfering. It does this by > (a) using a small font for the rollout context > (b) relegating the rollout context to below the results and marking them with > a superscript 1,2 etc. > > Gnubg would benefit from something similar. > A smaller font would be quite easy. Other improvements would be trickier. > Because gnubg can stop early, there might be a different number of trials for > each play. > However, a lot of information gets repeated, e.g. rng, seed, plies, etc. This > could be condensed somehow. > > Long before XG existed, I suggested a differential report of rollout context. > That is, gnubg exports only display context information which differs from > the play below it. This would cut out a lot of redundant rng, seed, ply > information. > > An alternative solution would be to print the number of trials and jsd for > each play, then reference the rest of the context with a superscript to a > footnote, XG-style. > > Here is a link to a rollout I performed recently. Four plays were rolled out > at 2-ply, and five more at 0-ply. https://sites.google.com/site/gnubgexport/ > > The original is on the left. Look how messy it is. > > On the right I have tweaked it to reduce redundant information, and include > the suggested JSD information. I think the primary data - the rollout results > - are a lot more legible. > > What do people think of this? > > There is scope for a lot more improvement, such as: > Labels for cubeless and cubeful equity > Labels for wins, gammons, backgammons > Making the confidence intervals less intrusive > Any others? > > > -- Ian > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > [email protected] > Sent: 25 May 2011 19:10 > To: [email protected] > Cc: [email protected] > Subject: [Bug-gnubg] Fwd: Listing JSDs in rollouts > > > Wondering whether y'all have decided on the suggestion that the rollout > results indicate the plays' JSDs. Note that because we can manually stop > rolling out specific plays it is not clear in the outoput listing whether a > rollout was stopped manually or whether the JSD limit was reached. In other > words, by looking at the output, you cannot tell whether the JSD limit was > reached. > > Thanks. > > > _______________________________________________ > Bug-gnubg mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/bug-gnubg
_______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
