3.3.2.13. NXsastofΒΆ
Status:
application definition, extends NXobject, version 1.0b
Description:
This is an application definition for small angle scattering using a 2D detector in TOF mode.
It strives to cover all the SAS techniques in the file again
Symbols:
No symbol table
- Groups cited:
- NXcollimator, NXdata, NXdetector, NXentry, NXgeometry, NXinstrument, NXmonitor, NXsample, NXshape, NXsource
Structure:
(entry): NXentry
@entry: NX_CHAR
NeXus convention is to use “entry1”, “entry2”, ... for analysis software to locate each entrytitle: NX_CHAR
start_time: NX_DATE_TIME
definition: NX_CHAR
Official NeXus NXDL schema to which this file conforms
Obligatory value:
NXsastof
instrument: NXinstrument
name: NX_CHAR
Name of the instrument actually used to perform the experimentsource: NXsource
collimator: NXcollimator
geometry: NXgeometry
detector: NXdetector
data[nXPixel, nYPixel, nTOF]: NX_NUMBER
This is area detector data, of number of x-pixel versus number of y-pixels. Since the beam center is to be determined as a step of data reduction, it is not necessary to document or assume the position of the beam center in acquired data.time_of_flight[nTOF]: NX_FLOAT {units=NX_TIME_OF_FLIGHT}
distance: NX_FLOAT {units=NX_LENGTH}
The distance between detector and samplex_pixel_size: NX_FLOAT {units=NX_LENGTH}
Physical size of a pixel in x-directiony_pixel_size: NX_FLOAT {units=NX_LENGTH}
Size of a pixel in y directionpolar_angle: NX_FLOAT {units=NX_ANGLE}
azimuthal_angle: NX_FLOAT {units=NX_ANGLE}
rotation_angle: NX_FLOAT {units=NX_ANGLE}
aequatorial_angle: NX_FLOAT {units=NX_ANGLE}
beam_center_x: NX_FLOAT {units=NX_LENGTH}
This is the x position where the direct beam would hit the detector. This is a length, not a pixel position, and can be outside of the actual detector.beam_center_y: NX_FLOAT {units=NX_LENGTH}
This is the y position where the direct beam would hit the detector. This is a length, not a pixel position, and can be outside of the actual detector.sample: NXsample
control: NXmonitor
mode: NX_CHAR
Count to a preset value based on either clock time (timer) or received monitor counts (monitor).
Any of these values:
monitor
|timer
preset: NX_FLOAT
preset value for time or monitordata[nTOF]: NX_INT
time_of_flight[nTOF]: NX_FLOAT {units=NX_TIME_OF_FLIGHT}
data: NXdata
data –> /NXentry/NXinstrument/NXdetector/data
time_of_flight –> /NXentry/NXinstrument/NXdetector/time_of_flight