[Nexus] NXgeometry lacking documentation and others....

[Mark Koennecke]

Hi,

On 11/19/2012 10:45 PM, Pete Jemian wrote:
> Very likely the case then, that NXgeometry is overused.
> Anyone want to take on the task of reviewing and offering revisions?
>
well, my suggestion would be a different one:
- mark NXgeometry as deprecated in favour of the CIF scheme
- Revise NXaperture to better cover the common usage case of a 
rectangular slit with fields:

     * bottom, top, left, right being the actual motors driven
     * width and height as derived values commonly asked for
     * distance, x_ and y_translation to position  the whole beast
- Consider an NXcylindrical_aperture with fields diameter and length to 
cover photographic aperture
   like round slits. Rather then  another class we could also have a 
type filed in NXaperture which indicates the
   type of slits.

I am aware that his needs proper discussion and may not be sortable 
before a next meeting of the NIAC.
Lets try the Telco next.

Regards,

           Mark


> On 11/19/2012 10:17 AM, Ray Osborn wrote:
>> This is now old history, but my vote would have been that we store 
>> certain parameters in common use, according to their common usage 
>> (with documentation), and keep NXgeometry only for cases where we are 
>> physically describing the object as it would appear in a CAD drawing. 
>> I am guessing that is not how it is used in a lot of the NXDL files.
> _______________________________________________
> NeXus mailing list
> NeXus at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus