On Sun, 20 Mar 2011, Michael Petch wrote:
I had never thoroughly dived into the contents of a GNUBGID but I was a
bit surprised when I didn't see either beaver information or Jacoby. I
was wondering if there is a reason this information is not included? If
there is a reason would someone be kind enough to let me know what they are.
If they should become part of the MatchID portion of a GNUBGID, what are
the ramifications for backwards compatibility by adding more bits to the
end. Will more bits break much older releases if you attempt to paste
new ID's into older versions? I did some test and that didn't seem to be
the case.
I'd be willing make such changes if this was something people felt was a
good idea.
I think it would be useful to have a flag for the Jacoby rule but that's
it. You could use the same bit as for Crafword (probably with Jacoby on if
value is zero to be backward compatible with common usage). The matchid
format would then remain unchanged.
I suppose the idea is that when you have an gnubgid blah:blah and its
evaluation you want to know exactly what you're talking about. But beavers
essentially don't happen beyond ply 0 when a bot is playing hence their
use don't change the evaluation, and at ply 0 the numbers are easy to
interpret.
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg
