I think the nomenclature isn't so bad. Coordinate transformations often leave you with something that doesn't make sense if you think of it in the new frame or orientation, and if you walk up to them cold take a lot of time reading detailed specs to make sense of. They're tedious to read through and make sense of and easy to mess up when tracing through. I've had to work with stuff that had 7 C-sized sheets packed with notes (and some figures) to define the "base" coordinate system and the transformations to get to mine. You've got what looks like a relatively straightforward set of routines and a lot of detailed description, so I don't think I'd complain about your naming. Most of my experience with nomenclature for this is based on sitting next to someone saying "show me it sliced at the yz plane at x = 'about here' finger point looking from putting +x pointing this way another finger point." Where the finger points would refer to the global coordinates or vectors if I had to write code.

In reply to Re^8: Naming ordinals in the presence of 3D rotation? (A better explanation of the problem?)) by bitingduck
in thread Naming ordinals (directions/sides/faces) in the presence of 3D rotation? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.