|
BGonline.org Forums
A Procedural Definition of Hit/Most/Six
Posted By: Taper_Mike In Response To: A Procedural Definition of Hit/Most/Six (Nack Ballard)
Date: Tuesday, 22 November 2011, at 12:18 a.m.
Although I still remain committed to the notion of a procedural description of the Hit/Most/Six Rule, there is no doubt that I've erred on the side of extra verbage. In the first draft, simply getting my understanding of the rule explained in an unambiguous way was the top priority. In the next draft, perhaps I'll do better.
Nack wrote: ...the concept of "tie goes to the lower point" doesn't seem like it should require several lines of text to be computer-worthy.
I like your idea, but I think that, "tie goes to the lower point," while accurate, somewhat obscures the point (n.p.i.). I would like to see a reference to the distinction between inner and outer boards. What about something like this?
At a given distance from the 6pt, holding a point in the inner board outranks holding a point in the outer board.
As far as computer code is concerned, the entire rule is unnecessary. A program will simply check the inner board point at a given distance from the 6pt before it checks the corresponding point in the outer board. Here is my description of that:
Begin at the 6pt, and search outwards in both directions one point at a time, at each step checking first in the inner board, and then in the outer board, until you find a point that is made in one position and not in the other. The position in which the point is made ranks higher in the family.
Although readers may think this tends toward the inscrutable, I would still argue that it is an improvement, computer-wise, over my original prose. The fact that I'm not using it is evidence of an interest beyond programming. That, and a sincere concern that readers can detect that I am writing in English.
Nack: Are you constructing your explanations/descriptions for a computer program or so that bgonline folks can understand? Both?
My primary purpose remains only to master Nactation. Writing out my procedural description has caused me to discover, and forced me to address, many areas of misunderstanding. It is a tribute to the simplicity of the system that readers may have forgotten that I am a rank beginner! (This pun intended!) Any expertise I may have is newfound. A month ago, I could only nactate what was described in the first edition of the Nactation Guide. Now I am contemplating writing a program.
My second priority is to provide some utility to the readers at BGO who are following these threads. In this regard, my job is to pose perspicacious inquiries. Nack's is to provide the utility!
A final (still quite distant) interest is to code a program that can automate parts of the Nactation process.
At the end of the day, the next edition of the Nactation Guide should obviate my procedural definition. Indeed, the long-term value of my definition may be only as a starting point for would-be programmers of Nactation. The Nactation Guide, written in Nack's minimalist style, and buttressed by myriad examples, will be a welcome replacement.
As an aside, let me state that Nack is truly the Philip Glass of backgammon authors. He achives a simple elegance that is unique in the world of backgammon writing. His minimalist approach is front and center in the masterwork Backgammon Openings, Book A, coauthered with Paul Weaver. If you don't own a copy, you are missing something special. Its descriptions are succinct, uncluttered and complete.
Until the Nactation Guide is updated, however, all we have is the minimalist part. The examples are out there, but to find them, one must be adroit in searching out the dozens of posts wherein they reside. The minimalist prose is still fine, but without the examples, a certain, small percentage of readers (plus a few donkeys like me) will misconstrue what is being said.
My hope is that my procedural definition can fill in the gap. It may not be the best writing around, but it is meant to be complete and exact. In one location, if gives a full and precise description of Hit/Most/Six. Ulimately, my writing style is informed by my background in programming. Hopefully, that will not prevent BGO readers from finding some value in it.
Mike
|
BGonline.org Forums is maintained by Stick with WebBBS 5.12.