[NeXus-tech] NeXus teleconference

[Mark Koennecke]

Hi,

On 12/04/2013 07:57 AM, yayahjb wrote:
> Dear Colleagues,
>
>   I have posted what I have done so far on the minimal mapping for the 
> PX monochromatic
> experiment in NeXus at:
>
> https://sites.google.com/site/nexuscbf/mapping-draft/px-monochromatic-nexus-mapping 
>
>
> I apologize for being so slow on this.  Things -- like last minute 
> cycling on a DOE proposal
> and a critical computer frying itself today keep coming up.  Your 
> comments on what I have
> done so far would be appreciated, especially your thoughts on things I 
> left out that need
> to be included and things I put in that are not really needed.
>
>   Regards,
>     Herbert
>
> _______________________________________________
> NeXus-tech mailing list
> NeXus-tech at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
Herbert, thanks for your effort. Unfortunately, it does not look like 
NeXus anymore.
Here is my quick shot, trying to convey the same information:



diffrn_id:NXentry
    definition:NX_CHAR
    diffrn_id:NX_CHAR
    diffrn_scan_id:NX_CHAR
    diffrn_crystal_id:NXsample
       diffrn_crystal_id:NX_CHAR
    instrument:NXinstrument
       source:NXsource
          name:NX_CHAR
          type:NX_CHAR
          current:NX_NUMBER
          probe:NX_CHAR
       monochromator:NXmonochromator
          type:NX_CHAR
       radiation_id:NXbeam
          radiation_id:NX_CHAR
          wavelength[] NX_NUMBER
          wavelength_weight[]:NX_NUMBER
          polarisation_source_ratio:NX_NUMBER
          polarisation_source_norm:NX_NUMBER
          beam_divergence[]:NX_NUMBER
          collimation:NX_CHAR
          azimuthal_angle:NX_AXIS
          distance:NX_AXIS
          height:NX_AXIS
          meridional_angle:NX_AXIS
          rotation_angle:NX_AXIS
          x_translation:NX_AXIS
          depends_on:NX_CHAR
        detector:NXdetector
          type:NX_CHAR
      frame_start_number:NX_NUMBER
          frame_end_number:NX_NUMBER
          description:NX_CHAR
          data[NP,XDIM,YDIM]
          x[XDIM]:NX_AXIS
          y[YDIM]:NX_AXIS
          azimuthal_angle:NX_AXIS
          distance:NX_AXIS
          height:NX_AXIS
          meridional_angle:NX_AXIS
          rotation_angle:NX_AXIS
          x_translation:NX_AXIS
          depends_on:NX_CHAR
        goniometer:NXgoniometer
          chi[NP]:NX_AXIS
          phi[NP]:NX_AXIS
          rotation_angle[NP]:NX_AXIS
          azimuthal_angle:NX_AXIS
          distance:NX_AXIS
          height:NX_AXIS
          meridional_angle:NX_AXIS
          rotation_angle:NX_AXIS
          x_translation:NX_AXIS
          depends_on:NX_CHAR
   data:NXdata
          link to instrument/detector/data
          link to instrument/goniomter/rotation_angle
          etc.


I took some liberties:
- I added some fields to NeXus base classes
- I use NX_AXIS which have not yet aggreed upon. Which means that the 
thing is
   a NeXus axis with the attributes: transfromation_type, vector, 
offset,depends_on etc.

Apparently, CBF tries to describe the characteristics of the beam rather 
then bother with
the individual components of the instrument. I tried to keep in this 
line. I put NXbeam
into NXinstrument but it can also be in NXsample.

I made NXbeam, NXsample and NXgoniometer implement the full of 
NXIFbeamline_component.
Becasue we need to know where these things are.........

In NXdata should be links to all the fields varied during the scan. 
Indicated by the etc.


Please note that todays Telco starts half an hour earlier then usual.

Hear you soon,

         Mark