[NeXus-tech] Summary of last Telco

[Herbert J. Bernstein]

Any name will have problems.  For example, for crystallographers,
goniometer is synonymous with the sample positioner, not with a general
nest of axis for an arbitrary beam line component.  The term "poise" came
into use for robot arm kinematics a few decades ago to provide a neutral,
but descriptive name for general orientation of a robot hand at the end of
a robot arm.  See for example to use of the term, "poise" in
http://doras.dcu.ie/18314/1/George_P._Anderson_20130306152250.pdf, the ME
thesis
of George P. Anderson, "Modelling and Simulation of a Puma 560 Manipulator
for
Control System Appraisal", Thesis submitted for the degree of Master of
Engineering, National Institute for Higher Education, Dublin, School of
Electronic Engineering, Control Technology Research Unit, September 1988.
At NYU in the 1980 we used "poise" consistently in our work on robotics.
Unfortunately "pose" crept into the literature as a typo for "poise"
subsequently, so you will find "pose" floating around, which explains
Jonathan's error.  I prefer to adhere to the "poise" spelling out of
respect for the original literature.

The use of poise as a term to describe how a head, hand or arm is carried
is in the OED and had even made it into trademarked terms for fancy lamps
that hold an adjusted position.


On Wed, Apr 16, 2014 at 8:19 AM, Pete Jemian <prjemian at gmail.com> wrote:

> Can a different name be chosen for this concept?
>
> Aside from the point noted below, the name requires much explanation to
> associate the name and the intent of this concept.  Something much more
> obvious should be chosen.
>
> If it is used anywhere to determine position and orientation of a
> component, perhaps NXcomponent_axes is more to the point.
>
>
> On 4/16/2014 6:50 AM, Mark Könnecke wrote:
>
>> NXpoise
>> =========
>>
>> NXpoise is a new group which has been suggested. It is a
>> generalisation of NXgoniometer. As NXGoniometer, it is supposed to
>> hold the axes needed to position the component and the depends_on
>> field. NXpoise can occurr anywhere where it is required to be able to
>> determine the position and orientation of a component precisely.
>> NXpoise is required for the PX application definition to work. The
>> consensus is that we use NXpoise for the time being and ratify it at
>> the next NIAC meeting. There was a little discussion about NXpose
>> versus NXpoise. Until the native speakers decided that NXpose is
>> actually a common  typo of NXpoise.
>>
> _______________________________________________
> NeXus-tech mailing list
> NeXus-tech at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nexusformat.org/mailman/private/nexus-tech/attachments/20140416/c98b5de4/attachment-0001.html>