[NeXus-definitions-tickets] [NeXusDefinitions] #112: Merge CIF coordinates into NeXus

[NeXus Base Classes and Instrument Definitions]

#112: Merge CIF coordinates into NeXus
-------------------------+-----------------------------
 Reporter:  Pete Jemian  |       Owner:  Tobias Richter
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:  later
Component:  general      |  Resolution:
 Keywords:               |
-------------------------+-----------------------------

Comment (by Tobias Richter):

 An example would be:

 {{{
          DATASET "tilt" {
             DATATYPE  H5T_IEEE_F32LE
             DATASPACE  SIMPLE { ( 1 ) / ( 1 ) }
             DATA {
             (0): 0.05
             }
             ATTRIBUTE "depends_on" {
                DATATYPE  H5T_STRING {
                      STRSIZE 47;
                      STRPAD H5T_STR_NULLPAD;
                      CSET H5T_CSET_ASCII;
                      CTYPE H5T_C_S1;
                   }
                DATASPACE  SCALAR
                DATA {
                (0): "/entry1/instrument/manipulator/azimuthal_angle"
                }
             }
             ATTRIBUTE "transformation_type" {
                DATATYPE  H5T_STRING {
                      STRSIZE 8;
                      STRPAD H5T_STR_NULLPAD;
                      CSET H5T_CSET_ASCII;
                      CTYPE H5T_C_S1;
                   }
                DATASPACE  SCALAR
                DATA {
                (0): "rotation"
                }
             }
             ATTRIBUTE "units" {
                DATATYPE  H5T_STRING {
                      STRSIZE 6;
                      STRPAD H5T_STR_NULLPAD;
                      CSET H5T_CSET_ASCII;
                      CTYPE H5T_C_S1;
                   }
                DATASPACE  SCALAR
                DATA {
                (0): "degree"
                }
             }
             ATTRIBUTE "vector" {
                DATATYPE  H5T_IEEE_F32LE
                DATASPACE  SIMPLE { ( 3 ) / ( 3 ) }
                DATA {
                (0): 1, 0, 0
                }
             }
          }

 }}}

 The `depends_on` is new, the rest should be in there already (but isn't)
 since it was agreed in Oak Ridge.

 The idea is that a missing `depends_on` would signal that this
 transformation starts in the origin of the coordinate system. You could
 say that explicitly with `depends_on=.`

 To fix e.g. an NXdetector in space a `depends_on` '''field''' would point
 to the last translation or rotation in the chain required to reach the
 location.

-- 
Ticket URL: <http://trac.nexusformat.org/definitions/ticket/112#comment:9>
NeXus Base Classes and Instrument Definitions <http://www.nexusformat.org/>
NeXus Base Classes and Instrument Definitions