A representation of a "has a" relationship. Representation fo having a Value assigned. Representation of having a Unit assigned. NeXus concept 54df1c1 This is the base object of NeXus NeXus Base Class (Newer entries are found in Contributed Definitions) https://manual.nexusformat.org/classes/base_classes/index.html NeXus Application Class (Newer entries are found in Contributed Definitions) https://manual.nexusformat.org/classes/applications/index.html NeXus Attribute NeXus Field NeXus Group Unit categories in NXDL specifications describe the expected type of units for a NeXus field.They should describe valid units consistent withthe manual section on NeXus units (based on UDUNITS).Units are not validated by NeXus. NeXusUnitCategory any valid NeXus field or attribute type NeXusDataType ISO8601 ISO8601 date/time stamp. It is recommended to add an explicit time zone, otherwise the local time zone *is assumed* per ISO8601. The norm is that if there is no time zone, it is assumed local time, however, when a file moves from one country to another it is undefined. If the local time zone is written, the ambiguity is gone. https://manual.nexusformat.org/nxdl-types.html#iso8601 NX_BINARY any representation of binary data - if text, line terminator is [CR][LF] https://manual.nexusformat.org/nxdl-types.html#nx-binary NX_BOOLEAN true/false value ( true | 1 | false | 0 ) https://manual.nexusformat.org/nxdl-types.html#nx-boolean NX_CCOMPLEX Compound type cartesian representation of complex numbers (real and imaginary parts) in NeXus. https://manual.nexusformat.org/nxdl-types.html#nx-ccomplex NX_CHAR The preferred string representation is :index:`UTF-8`. Both fixed-length strings and variable-length strings are valid. String arrays cannot be used where only a string is expected (title, start_time, end_time, ``NX_class`` attribute,...). Fields or attributes requiring the use of string arrays will be clearly marked as such (like the ``NXdata`` attribute ``auxiliary_signals``). This is the default field type. https://manual.nexusformat.org/nxdl-types.html#nx-char NX_COMPLEX Compound type representation of complex numbers (either cartesian or polar form) in NeXus. https://manual.nexusformat.org/nxdl-types.html#nx-complex NX_DATE_TIME Alias for the ``ISO8601`` date/time stamp. It is recommended to add an explicit time zone, otherwise the local time zone is assumed per ISO8601. https://manual.nexusformat.org/nxdl-types.html#nx-date-time NX_FLOAT any representation of a floating point number https://manual.nexusformat.org/nxdl-types.html#nx-float NX_INT any representation of an integer number https://manual.nexusformat.org/nxdl-types.html#nx-int NX_NUMBER any valid NeXus number representation https://manual.nexusformat.org/nxdl-types.html#nx-number NX_PCOMPLEX Compound type polar representation of complex numbers (amplitude and phase *in radians*) in NeXus. https://manual.nexusformat.org/nxdl-types.html#nx-pcomplex NX_POSINT any representation of a positive integer number (greater than zero) https://manual.nexusformat.org/nxdl-types.html#nx-posint NX_QUATERNION Compound type representation of quaternion numbers (real,i,j,k) in NeXus. https://manual.nexusformat.org/nxdl-types.html#nx-quaternion NX_UINT any representation of an unsigned integer number (includes zero) https://manual.nexusformat.org/nxdl-types.html#nx-uint NX_CHAR_OR_NUMBER Any valid character string or NeXus number representation https://manual.nexusformat.org/nxdl-types.html#nx-char-or-number NX_ANGLE units of angle https://manual.nexusformat.org/nxdl-types.html#nx-angle NX_ANY units for things like logs that aren't picky on units https://manual.nexusformat.org/nxdl-types.html#nx-any NX_AREA units of area https://manual.nexusformat.org/nxdl-types.html#nx-area NX_CROSS_SECTION units of area (alias of NX_AREA) https://manual.nexusformat.org/nxdl-types.html#nx-cross-section NX_CHARGE units of electrical charge https://manual.nexusformat.org/nxdl-types.html#nx-charge NX_CURRENT units of electrical current https://manual.nexusformat.org/nxdl-types.html#nx-current NX_DIMENSIONLESS units for fields where the units cancel out (NOTE: not the same as NX_UNITLESS) https://manual.nexusformat.org/nxdl-types.html#nx-dimensionless NX_EMITTANCE units of emittance (``length * angle``) of a radiation source https://manual.nexusformat.org/nxdl-types.html#nx-emittance NX_ENERGY units of energy https://manual.nexusformat.org/nxdl-types.html#nx-energy NX_FLUX units of flux https://manual.nexusformat.org/nxdl-types.html#nx-flux NX_FREQUENCY units of frequency https://manual.nexusformat.org/nxdl-types.html#nx-frequency NX_LENGTH units of length https://manual.nexusformat.org/nxdl-types.html#nx-length NX_MASS units of mass https://manual.nexusformat.org/nxdl-types.html#nx-mass NX_MASS_DENSITY units of mass density https://manual.nexusformat.org/nxdl-types.html#nx-mass-density NX_MOLECULAR_WEIGHT units of molecular weight https://manual.nexusformat.org/nxdl-types.html#nx-molecular-weight NX_PER_AREA units of 1/length^2 https://manual.nexusformat.org/nxdl-types.html#nx-per-area NX_PER_LENGTH units of 1/length https://manual.nexusformat.org/nxdl-types.html#nx-per-length NX_PERIOD units of time, period of pulsed source (alias to `NX_TIME`) https://manual.nexusformat.org/nxdl-types.html#nx-period NX_POWER units of power https://manual.nexusformat.org/nxdl-types.html#nx-power NX_PRESSURE units of pressure https://manual.nexusformat.org/nxdl-types.html#nx-pressure NX_PULSES DEPRECATED: see NX_COUNT units of clock pulses (alias to `NX_NUMBER`) https://manual.nexusformat.org/nxdl-types.html#nx-pulses NX_COUNT units of quantity of item(s) such as number of photons, neutrons, pulses, or other counting events https://manual.nexusformat.org/nxdl-types.html#nx-count NX_SCATTERING_LENGTH_DENSITY units of scattering length density https://manual.nexusformat.org/nxdl-types.html#nx-scattering-length-density NX_SOLID_ANGLE units of solid angle https://manual.nexusformat.org/nxdl-types.html#nx-solid-angle NX_TEMPERATURE units of temperature https://manual.nexusformat.org/nxdl-types.html#nx-temperature NX_TIME units of time https://manual.nexusformat.org/nxdl-types.html#nx-time NX_TIME_OF_FLIGHT units of (neutron) time of flight (alias to `NX_TIME`) https://manual.nexusformat.org/nxdl-types.html#nx-time-of-flight NX_TRANSFORMATION units of the specified transformation could be any of these: ``NX_LENGTH``, ``NX_ANGLE``, or ``NX_UNITLESS`` There will be one or more transformations defined by one or more fields for each transformation. The units type ``NX_TRANSFORMATION`` designates the particular axis generating a transformation (e.g. a rotation axis or a translation axis or a general axis). ``NX_TRANSFORMATION`` designates the units will be appropriate to the type of transformation, indicated in the :ref:`NXtransformations` base class by the ``transformation_type`` value: * ``NX_LENGTH`` for ``translation`` * ``NX_ANGLE`` for ``rotation`` * ``NX_UNITLESS`` for axes for which no transformation type is specified. https://manual.nexusformat.org/nxdl-types.html#nx-transformation NX_UNITLESS for fields that don't have a unit (e.g. hkl) so that they don't inherit the wrong units (NOTE: not the same as NX_DIMENSIONLESS) https://manual.nexusformat.org/nxdl-types.html#nx-unitless NX_VOLTAGE units of voltage https://manual.nexusformat.org/nxdl-types.html#nx-voltage NX_VOLUME units of volume https://manual.nexusformat.org/nxdl-types.html#nx-volume NX_WAVELENGTH units of wavelength https://manual.nexusformat.org/nxdl-types.html#nx-wavelength NX_WAVENUMBER units of wavenumber or Q https://manual.nexusformat.org/nxdl-types.html#nx-wavenumber 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A crystal monochromator or analyzer. Permits double bent monochromator comprised of multiple segments with anisotropic Gaussian mosaic. If curvatures are set to zero or are absent, array is considered to be flat. Scattering vector is perpendicular to surface. Crystal is oriented parallel to beam incident on crystal before rotation, and lies in vertical plane. NXobject NXcrystal https://manual.nexusformat.org/classes/base_classes/NXcrystal.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A beamline collimator. NXobject NXcollimator https://manual.nexusformat.org/classes/base_classes/NXcollimator.html 0 0 0 0 0 0 0 0 Any additional freeform information not covered by the other base classes. This class can be used to store additional information in a NeXus file e.g. pictures, movies, audio, additional text logs NXobject NXnote https://manual.nexusformat.org/classes/base_classes/NXnote.html 0 0 0 0 A simple pinhole. For more complex geometries, :ref:`NXaperture` should be used. NXobject NXpinhole https://manual.nexusformat.org/classes/base_classes/NXpinhole.html 0 0 0 0 0 Logical grouping of detectors. When used, describes a group of detectors. Each detector is represented as an NXdetector with its own detector data array. Each detector data array may be further decomposed into array sections by use of NXdetector_module groups. Detectors can be grouped logically together using NXdetector_group. Groups can be further grouped hierarchically in a single NXdetector_group (for example, if there are multiple detectors at an endstation or multiple endstations at a facility). Alternatively, multiple NXdetector_groups can be provided. The groups are defined hierarchically, with names given in the group_names field, unique identifying indices given in the field group_index, and the level in the hierarchy given in the group_parent field. For example if an x-ray detector group, DET, consists of four detectors in a rectangular array:: DTL DTR DLL DLR We could have:: group_names: ["DET", "DTL", "DTR", "DLL", "DLR"] group_index: [1, 2, 3, 4, 5] group_parent: [-1, 1, 1, 1, 1] NXobject NXdetector_group https://manual.nexusformat.org/classes/base_classes/NXdetector_group.html An unvalidated set of terms, such as the description of a beam line. Use :ref:`NXcollection` to gather together any set of terms. The original suggestion is to use this as a container class for the description of a beamline. For NeXus validation, :ref:`NXcollection` will always generate a warning since it is always an optional group. Anything (groups, fields, or attributes) placed in an :ref:`NXcollection` group will not be validated. NXobject NXcollection https://manual.nexusformat.org/classes/base_classes/NXcollection.html 0 0 0 0 legacy class - (used by :ref:`NXgeometry`) - the shape and size of a component. This is the description of the general shape and size of a component, which may be made up of ``numobj`` separate elements - it is used by the :ref:`NXgeometry` class NXobject NXshape https://manual.nexusformat.org/classes/base_classes/NXshape.html 0 0 0 0 0 0 0 0 0 0 0 0 A device that blocks the beam completely, usually to protect a detector. Beamstops and their positions are important for SANS and SAXS experiments. NXobject NXbeam_stop https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html 0 0 0 0 0 0 0 0 0 0 0 A spin flipper. NXobject NXflipper https://manual.nexusformat.org/classes/base_classes/NXflipper.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Group of multiple application definitions for "multi-modal" (e.g. SAXS/WAXS) measurements. ``NXsubentry`` is a base class virtually identical to :ref:`NXentry` and is used as the (overlay) location for application definitions. Use a separate ``NXsubentry`` for each application definition. To use ``NXsubentry`` with a hypothetical application definition called ``NXmyappdef``: * Create a group with attribute ``NX_class="NXsubentry"`` * Within that group, create a field called ``definition="NXmyappdef"``. * There are two optional attributes of definition: ``version`` and ``URL`` The intended use is to define application definitions for a multi-modal (a.k.a. multi-technique) :ref:`NXentry`. Previously, an application definition replaced :ref:`NXentry` with its own definition. With the increasing popularity of instruments combining multiple techniques for data collection (such as SAXS/WAXS instruments), it was recognized the application definitions must be entered in the NeXus data file tree as children of :ref:`NXentry`. NXobject NXsubentry https://manual.nexusformat.org/classes/base_classes/NXsubentry.html 0 0 0 0 0 0 Document an event of data processing, reconstruction, or analysis for this data. NXobject NXprocess https://manual.nexusformat.org/classes/base_classes/NXprocess.html 0 0 Container for parameters, usually used in processing or analysis. NXobject NXparameters https://manual.nexusformat.org/classes/base_classes/NXparameters.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A Fermi chopper, possibly with curved slits. NXobject NXfermi_chopper https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html 0 0 0 0 0 0 0 0 0 0 0 A capillary lens to focus the X-ray beam. Based on information provided by Gerd Wellenreuther (DESY). NXobject NXcapillary https://manual.nexusformat.org/classes/base_classes/NXcapillary.html 0 0 0 0 0 A simple slit. For more complex geometries, :ref:`NXaperture` should be used. NXobject NXslit https://manual.nexusformat.org/classes/base_classes/NXslit.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 For band pass beam filters. If uncertain whether to use :ref:`NXfilter` (band-pass filter) or :ref:`NXattenuator` (reduces beam intensity), then use :ref:`NXattenuator`. NXobject NXfilter https://manual.nexusformat.org/classes/base_classes/NXfilter.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A detector, detector bank, or multidetector. NXobject NXdetector https://manual.nexusformat.org/classes/base_classes/NXdetector.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A device blocking the beam in a temporal periodic pattern. A disk which blocks the beam but has one or more slits to periodically let neutrons through as the disk rotates. Often used in pairs, one NXdisk_chopper should be defined for each disk. The rotation of the disk is commonly monitored by recording a timestamp for each full rotation of disk, by having a sensor in the stationary disk housing sensing when it is aligned with a feature (such as a magnet) on the disk. We refer to this below as the "top-dead-center signal". Angles and positive rotation speeds are measured in an anticlockwise direction when facing away from the source. NXobject NXdisk_chopper https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The neutron or x-ray storage ring/facility. NXobject NXsource https://manual.nexusformat.org/classes/base_classes/NXsource.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A bending magnet NXobject NXbending_magnet https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (**required**) :ref:`NXentry` describes the measurement. The top-level NeXus group which contains all the data and associated information that comprise a single measurement. It is mandatory that there is at least one group of this type in the NeXus file. NXobject NXentry https://manual.nexusformat.org/classes/base_classes/NXentry.html 0 0 0 0 0 0 0 Geometry and logical description of a detector module. When used, child group to NXdetector. Many detectors consist of multiple smaller modules. Sometimes it is important to know the exact position of such modules. This is the purpose of this group. It is a child group to NXdetector. Note, the pixel size is given as values in the array fast_pixel_direction and slow_pixel_direction. NXobject NXdetector_module https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A generic positioner such as a motor or piezo-electric transducer. NXobject NXpositioner https://manual.nexusformat.org/classes/base_classes/NXpositioner.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A fresnel zone plate NXobject NXfresnel_zone_plate https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The :ref:`NXdata` class is designed to encapsulate all the information required for a set of data to be plotted. NXdata groups contain plottable data (sometimes referred to as *signals* or *dependent variables*) and their associated axis coordinates (sometimes referred to as *axes* or *independent variables*). The actual names of the :ref:`DATA </NXdata/DATA-field>` and :ref:`AXISNAME </NXdata/AXISNAME-field>` fields can be chosen :ref:`freely <validItemName>`, as indicated by the upper case (this is a common convention in all NeXus classes). .. note:: ``NXdata`` provides data and coordinates to be plotted but does not describe how the data is to be plotted or even the dimensionality of the plot. https://www.nexusformat.org/NIAC2018Minutes.html#nxdata-plottype--attribute **Signals:** .. index:: plotting The :ref:`DATA </NXdata/DATA-field>` fields contain the signal values to be plotted. The name of the field to be used as the *default plot signal* is provided by the :ref:`signal </NXdata@signal-attribute>` attribute. The names of the fields to be used as *secondary plot signals* are provided by the :ref:`auxiliary_signals</NXdata@auxiliary_signals-attribute>` attribute. An example with three signals, one of which being the default .. code-block:: data:NXdata @signal = "data1" @auxiliary_signals = ["data2", "data3"] data1: float[10,20,30] --> the default signal data2: float[10,20,30] data3: float[10,20,30] **Axes:** .. index:: axes (attribute) .. index:: coordinates The :ref:`AXISNAME </NXdata/AXISNAME-field>` fields contain the axis coordinates associated with the data values. The names of all :ref:`AXISNAME </NXdata/AXISNAME-field>` fields are listed in the :ref:`axes </NXdata@axes-attribute>` attribute. `Rank` :ref:`AXISNAME </NXdata/AXISNAME-field>` fields are typically one-dimensional arrays, which annotate one of the dimensions. An example of this would be .. code-block:: data:NXdata @signal = "data" @axes = ["x", "y"] --> the order matters data: float[10,20] x: float[10] --> coordinates along the first dimension y: float[20] --> coordinates along the second dimension In this example each data point ``data[i,j]`` has axis coordinates ``[x[i], y[j]]``. However, the fields can also have a rank greater than 1, in which case the rank of each :ref:`AXISNAME </NXdata/AXISNAME-field>` must be equal to the number of data dimensions it spans. An example of this would be .. code-block:: data:NXdata @signal = "data" @axes = ["x", "y"] --> the order does NOT matter @x_indices = [0, 1] @y_indices = [0, 1] data: float[10,20] x: float[10,20] --> coordinates along both dimensions y: float[10,20] --> coordinates along both dimensions In this example each data point ``data[i,j]`` has axis coordinates ``[x[i,j], y[i,j]]``. `Dimensions` The data dimensions annotated by an :ref:`AXISNAME </NXdata/AXISNAME-field>` field are defined by the :ref:`AXISNAME_indices </NXdata@AXISNAME_indices-attribute>` attribute. When this attribute is missing, the position(s) of the :ref:`AXISNAME </NXdata/AXISNAME-field>` string in the :ref:`axes </NXdata@axes-attribute>` attribute are used. When all :ref:`AXISNAME </NXdata/AXISNAME-field>` fields are one-dimensional, and none of the data dimensions have more than one axis, the :ref:`AXISNAME_indices </NXdata@AXISNAME_indices-attribute>` attributes are often omitted. If one of the data dimensions has no :ref:`AXISNAME </NXdata/AXISNAME-field>` field, the string “.” can be used in the corresponding index of the axes list. An example of this would be .. code-block:: data:NXdata @signal = "data" @axes = ["x", ".", "z"] --> the order matters data: float[10,20,30] x: float[10] --> coordinates along the first dimension z: float[30] --> coordinates along the third dimension When using :ref:`AXISNAME_indices </NXdata@AXISNAME_indices-attribute>` this becomes .. code-block:: data:NXdata @signal = "data" @axes = ["x", "z"] --> the order does NOT matter data: float[10,20,30] @x_indices = 0 @z_indices = 2 x: float[10] --> coordinates along the first dimension z: float[30] --> coordinates along the third dimension When providing :ref:`AXISNAME_indices </NXdata@AXISNAME_indices-attribute>` attributes it is recommended to do it for all axes. `Non-trivial axes` What follows are two examples where :ref:`AXISNAME_indices </NXdata@AXISNAME_indices-attribute>` attributes cannot be omitted. The first is an example where data dimensions have alternative axis coordinates. The NXdata group represents a stack of images collected at different energies. The ``wavelength`` is an alternative axis of ``energy`` for the last dimension (or vice versa). .. code-block:: data:NXdata @signal = "data" @axes = ["x", "y", "energy", "wavelength"] --> the order does NOT matter @x_indices = 0 @y_indices = 1 @energy_indices = 2 @wavelength_indices = 2 data: float[10,20,30] x: float[10] --> coordinates along the first dimension y: float[20] --> coordinates along the second dimension energy: float[30] --> coordinates along the third dimension wavelength: float[30] --> coordinates along the third dimension The second is an example with coordinates that span more than one dimension. The NXdata group represents data from 2D mesh scans performed at multiple energies. Each data point ``data[i,j,k]`` has axis coordinates ``[x[i,j,k], y[i,j,k], energy[k]]``. .. code-block:: data:NXdata @signal = "data" @axes = ["x", "y", "energy"] --> the order does NOT matter @x_indices = [0, 1, 2] @y_indices = [0, 1, 2] @energy_indices = 2 data: float[10,20,30] x: float[10,20,30] --> coordinates along all dimensions y: float[10,20,30] --> coordinates along all dimensions energy: float[30] --> coordinates along the third dimension **Uncertainties:** Standard deviations on data values as well as coordinates can be provided by :ref:`FIELDNAME_errors </NXdata/FIELDNAME_errors-field>` fields where ``FIELDNAME`` is the name of a :ref:`DATA </NXdata/DATA-field>` field or an :ref:`AXISNAME </NXdata/AXISNAME-field>` field. An example of uncertainties on the signal, auxiliary signals and axis coordinates .. code-block:: data:NXdata @signal = "data1" @auxiliary_signals = ["data2", "data3"] @axes = ["x", "z"] @x_indices = 0 @z_indices = 2 data1: float[10,20,30] data2: float[10,20,30] data3: float[10,20,30] x: float[10] z: float[30] data1_errors: float[10,20,30] data2_errors: float[10,20,30] data3_errors: float[10,20,30] x_errors: float[10] z_errors: float[30] NXobject NXdata https://manual.nexusformat.org/classes/base_classes/NXdata.html 0 0 0 0 0 0 A literature reference Definition to include references for example for detectors, manuals, instruments, acquisition or analysis software used. The idea would be to include this in the relevant NeXus object: :ref:`NXdetector` for detectors, :ref:`NXinstrument` for instruments, etc. NXobject NXcite https://manual.nexusformat.org/classes/base_classes/NXcite.html 0 0 0 0 0 0 0 A spin polarizer. NXobject NXpolarizer https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 An X-ray lens, typically at a synchrotron X-ray beam line. Based on information provided by Gerd Wellenreuther (DESY). NXobject NXxraylens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html 1 0 0 0 0 0 0 0 0 0 0 0 0 Definition of the root NeXus group. NXobject NXroot https://manual.nexusformat.org/classes/base_classes/NXroot.html 0 0 0 0 Geometry description for cylindrical shapes. This class can be used in place of ``NXoff_geometry`` when an exact representation for cylinders is preferred. For example, for Helium-tube, neutron detectors. It can be used to describe the shape of any beamline component, including detectors. In the case of detectors it can be used to define the shape of a single pixel, or, if the pixel shapes are non-uniform, to describe the shape of the whole detector. NXobject NXcylindrical_geometry https://manual.nexusformat.org/classes/base_classes/NXcylindrical_geometry.html A NeXus transliteration of a PDB file, to be validated only as a PDB rather than in NeXus. Use :ref:`NXpdb` to incorporate the information in an arbitrary PDB into a NeXus file. The main suggestion is to use this as a container class for a PDB entry to describe a sample in NXsample, but it may be more appropriate to place this higher in the hierarchy, say in NXentry. The structure has to follow the structure of a PDB with each PDB data block mapped to a NeXus group of class NXpdb, using a lowercase version of the data block name as the name of the NeXus group, each PDB category in that data block mapped to a NeXus group of class NXpdb and with each PDB column mapped to a NeXus field. Each column in a looped PDB category should always be presented as a 1-dimensional array. The columns in an unlooped PDB category should be presented as scalar values. If a PDB category specifies particular units for columns, the same units should beused for the corresponding fields. A PDB entry is unambigous when all information is carried as text. All text data should be presented as quoted strings, with the quote marks except for the null values "." or "?" For clarity in NXpdb form, numeric data may be presented using the numeric types specified in the mmCIF dictionary. In that case, if a PDB null value, "." or "?", is contained in a numeric column, the IEEE nan should be used for "?" and the IEEE inf should be used for ".". An arbitrary DDL2 CIF file can be represented in NeXus using NXpdb. However, if save frames are required, an NXpdb_class attribute with the value "CBF_cbfsf" is required for each NeXus group representing a save frame. NXpdb attributes are not required for other CIF components, but may be used to provide internal documentation. The nesting of NXpdb groups and datasets that correspond to a CIF with two categories and one saveframe, including the NXpdb_class attribues is:: (datablock1):NXpdb @NXpdb_class:CBF_cbfdb (category1):NXpdb @NXpdb_class:CBF_cbfcat (column_name1):[...] (column_name2):[...] (column_name3):[...] ... (category2):NXpdb @NXpdb_class:CBF_cbfcat (column_name4):[...] (column_name5):[...] (column_name6):[...] ... (saveframe1):NXpdb @NXpdb_class:CBF_cbfsf (category3):NXpdb @NXpdb_class:CBF_cbfcat (column_name7):[...] (column_name8):[...] (column_name9):[...] ... ... ... For example, a PDB entry that begins:: data_1YVA # _entry.id 1YVA # _audit_conform.dict_name mmcif_pdbx.dic _audit_conform.dict_version 5.279 _audit_conform.dict_location http://mmcif.pdb.org/dictionaries/ascii/mmcif_pdbx.dic # loop_ _database_2.database_id _database_2.database_code PDB 1YVA RCSB RCSB031959 WWPDB D_1000031959 # would produce:: sample:NXsample 1yva:NXpdb entry:NXpdb id:"1YVA" audit_conform:NXpdb dict_name:"mmcif_pdbx.dic" dict_version:"5.279" dict_location:"http://mmcif.pdb.org/dictionaries/ascii/mmcif_pdbx.dic" database_2:NXpdb database_id:["PDB","RCSB","WWPDB"] database_code:["1YVA","RCSB031959","D_1000031959"] another example is the following excerpt from pdb entry 9ins, giving the sequences of the two chains:: loop_ _entity_poly.entity_id _entity_poly.nstd_linkage _entity_poly.nstd_monomer _entity_poly.pdbx_seq_one_letter_code _entity_poly.pdbx_seq_one_letter_code_can _entity_poly.type 1 no no GIVEQCCTSICSLYQLENYCN GIVEQCCTSICSLYQLENYCN polypeptide(L) 2 no no FVNQHLCGSHLVEALYLVCGERGFFYTPKA FVNQHLCGSHLVEALYLVCGERGFFYTPKA polypeptide(L) which converts to:: entity_poly:NXpdb @NXpdb_class:CBF_cbfcat entity_id:["1", "2"] nstd_linkage:["no", "no"] nstd_monomer:["no", "no"] pdbx_seq_one_letter_code:["GIVEQCCTSICSLYQLENYCN","FVNQHLCGSHLVEALYLVCGERGFFYTPKA"] pdbx_seq_one_letter_code_can:["GIVEQCCTSICSLYQLENYCN","FVNQHLCGSHLVEALYLVCGERGFFYTPKA"] type:["polypeptide(L)", "polypeptide(L)"] NXobject NXpdb https://manual.nexusformat.org/classes/base_classes/NXpdb.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 An insertion device, as used in a synchrotron light source. NXobject NXinsertion_device https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html 0 0 0 0 Collection of axis-based translations and rotations to describe a geometry. May also contain axes that do not move and therefore do not have a transformation type specified, but are useful in understanding coordinate frames within which transformations are done, or in documenting important directions, such as the direction of gravity. A nested sequence of transformations lists the translation and rotation steps needed to describe the position and orientation of any movable or fixed device. There will be one or more transformations (axes) defined by one or more fields for each transformation. Transformations can also be described by NXlog groups when the values change with time. The all-caps name ``AXISNAME`` designates the particular axis generating a transformation (e.g. a rotation axis or a translation axis or a general axis). The attribute ``units="NX_TRANSFORMATION"`` designates the units will be appropriate to the ``transformation_type`` attribute: * ``NX_LENGTH`` for ``translation`` * ``NX_ANGLE`` for ``rotation`` * ``NX_UNITLESS`` for axes for which no transformation type is specified This class will usually contain all axes of a sample stage or goniometer or a detector. The NeXus default McSTAS coordinate frame is assumed, but additional useful coordinate axes may be defined by using axes for which no transformation type has been specified. The entry point (``depends_on``) will be outside of this class and point to a field in here. Following the chain may also require following ``depends_on`` links to transformations outside, for example to a common base table. If a relative path is given, it is relative to the group enclosing the ``depends_on`` specification. For a chain of three transformations, where :math:`T_1` depends on :math:`T_2` and that in turn depends on :math:`T_3`, the final transformation :math:`T_f` is .. math:: T_f = T_3 T_2 T_1 In explicit terms, the transformations are a subset of affine transformations expressed as 4x4 matrices that act on homogeneous coordinates, :math:`w=(x,y,z,1)^T`. For rotation and translation, .. math:: T_r &= \begin{pmatrix} R & o \\ 0_3 & 1 \end{pmatrix} \\ T_t &= \begin{pmatrix} I_3 & t + o \\ 0_3 & 1 \end{pmatrix} where :math:`R` is the usual 3x3 rotation matrix, :math:`o` is an offset vector, :math:`0_3` is a row of 3 zeros, :math:`I_3` is the 3x3 identity matrix and :math:`t` is the translation vector. :math:`o` is given by the ``offset`` attribute, :math:`t` is given by the ``vector`` attribute multiplied by the field value, and :math:`R` is defined as a rotation about an axis in the direction of ``vector``, of angle of the field value. NOTE One possible use of ``NXtransformations`` is to define the motors and transformations for a diffractometer (goniometer). Such use is mentioned in the ``NXinstrument`` base class. Use one ``NXtransformations`` group for each diffractometer and name the group appropriate to the device. Collecting the motors of a sample table or xyz-stage in an NXtransformations group is equally possible. Following the section on the general dscription of axis in NXtransformations is a section which documents the fields commonly used within NeXus for positioning purposes and their meaning. Whenever there is a need for positioning a beam line component please use the existing names. Use as many fields as needed in order to position the component. Feel free to add more axis if required. In the description given below, only those atttributes which are defined through the name are spcified. Add the other attributes of the full set: * vector * offset * transformation_type * depends_on as needed. NXobject NXtransformations https://manual.nexusformat.org/classes/base_classes/NXtransformations.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 One group like this per component can be recorded For a sample consisting of multiple components. NXobject NXsample_component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A wavelength defining device. This is a base class for everything which selects a wavelength or energy, be it a monochromator crystal, a velocity selector, an undulator or whatever. The expected units are: * wavelength: angstrom * energy: eV NXobject NXmonochromator https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A sensor used to monitor an external condition The condition itself is described in :ref:`NXenvironment`. NXobject NXsensor https://manual.nexusformat.org/classes/base_classes/NXsensor.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A neutron velocity selector NXobject NXvelocity_selector https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Any information on the sample. This could include scanned variables that are associated with one of the data dimensions, e.g. the magnetic field, or logged data, e.g. monitored temperature vs elapsed time. NXobject NXsample https://manual.nexusformat.org/classes/base_classes/NXsample.html 0 0 0 0 0 0 0 0 0 0 0 A device that reduces the intensity of a beam by attenuation. If uncertain whether to use :ref:`NXfilter` (band-pass filter) or :ref:`NXattenuator` (reduces beam intensity), then choose :ref:`NXattenuator`. NXobject NXattenuator https://manual.nexusformat.org/classes/base_classes/NXattenuator.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A beamline mirror or supermirror. NXobject NXmirror https://manual.nexusformat.org/classes/base_classes/NXmirror.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Collection of the components of the instrument or beamline. Template of instrument descriptions comprising various beamline components. Each component will also be a NeXus group defined by its distance from the sample. Negative distances represent beamline components that are before the sample while positive distances represent components that are after the sample. This device allows the unique identification of beamline components in a way that is valid for both reactor and pulsed instrumentation. NXobject NXinstrument https://manual.nexusformat.org/classes/base_classes/NXinstrument.html 0 0 0 0 0 0 0 0 Description and metadata for a single channel from a multi-channel detector. Given an :ref:`NXdata` group linked as part of an NXdetector group that has an axis with named channels (see the example in :ref:`NXdata </NXdata@default_slice-attribute>`), the NXdetector will have a series of NXdetector_channel groups, one for each channel, named CHANNELNAME_channel. Example, given these axes in the NXdata group:: @axes = ["image_id", "channel", ".", "."] And this list of channels in the NXdata group:: channel = ["threshold_1", "threshold_2", "difference"] The NXdetector group would have three NXdetector_channel groups:: detector:NXdetector ... threshold_1_channel:NXdetector_channel threshold_energy = float flatfield = float[i, j] pixel_mask = uint[i, j] flatfield_applied = bool pixel_mask_applied = bool threshold_2_channel:NXdetector_channel threshold_energy = float flatfield = float[i, j] pixel_mask = uint[i, j] flatfield_applied = bool pixel_mask_applied = bool difference_channel:NXdetector_channel threshold_energy = float[2] NXobject NXdetector_channel https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A monitor of incident beam data. It is similar to the :ref:`NXdata` groups containing monitor data and its associated axis coordinates, e.g. time_of_flight or wavelength in pulsed neutron instruments. However, it may also include integrals, or scalar monitor counts, which are often used in both in both pulsed and steady-state instrumentation. NXobject NXmonitor https://manual.nexusformat.org/classes/base_classes/NXmonitor.html 0 0 0 0 0 0 0 0 0 0 0 0 0 Information recorded as a function of time. Description of information that is recorded against time. There are two common use cases for this: - When logging data such as temperature during a run - When data is taken in streaming mode data acquisition, i.e. just timestamp, value pairs are stored and correlated later in data reduction with other data, In both cases, NXlog contains the logged or streamed values and the times at which they were measured as elapsed time since a starting time recorded in ISO8601 format. The time units are specified in the units attribute. An optional scaling attribute can be used to accomodate non standard clocks. This method of storing logged data helps to distinguish instances in which a variable contains signal or axis coordinate values of plottable data, in which case it is stored in an :ref:`NXdata` group, and instances in which it is logged during the run, when it should be stored in an :ref:`NXlog` group. In order to make random access to timestamped data faster there is an optional array pair of ``cue_timestamp_zero`` and ``cue_index``. The ``cue_timestamp_zero`` will contain coarser timestamps than in the time array, say every five minutes. The ``cue_index`` will then contain the index into the time,value pair of arrays for that coarser ``cue_timestamp_zero``. NXobject NXlog https://manual.nexusformat.org/classes/base_classes/NXlog.html 0 0 0 0 0 0 0 0 0 0 Parameters for controlling external conditions NXobject NXenvironment https://manual.nexusformat.org/classes/base_classes/NXenvironment.html 0 0 0 legacy class - (used by :ref:`NXgeometry`) - general spatial location of a component. NXobject NXtranslation https://manual.nexusformat.org/classes/base_classes/NXtranslation.html 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 1 1 1 1 0 0 0 0 0 0 Reflection data from diffraction experiments NXobject NXreflections https://manual.nexusformat.org/classes/base_classes/NXreflections.html 0 0 0 0 0 0 legacy class - recommend to use :ref:`NXtransformations` now It is recommended that instances of :ref:`NXgeometry` be converted to use :ref:`NXtransformations`. This is the description for a general position of a component. It is recommended to name an instance of :ref:`NXgeometry` as "geometry" to aid in the use of the definition in simulation codes such as McStas. Also, in HDF, linked items must share the same name. However, it might not be possible or practical in all situations. NXobject NXgeometry https://manual.nexusformat.org/classes/base_classes/NXgeometry.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A diffraction grating, as could be used in a soft X-ray monochromator NXobject NXgrating https://manual.nexusformat.org/classes/base_classes/NXgrating.html 0 0 0 0 0 Geometry (shape) description. The format closely matches the Object File Format (OFF) which can be output by most CAD software. It can be used to describe the shape of any beamline component, including detectors. In the case of detectors it can be used to define the shape of a single pixel, or, if the pixel shapes are non-uniform, to describe the shape of the whole detector. NXobject NXoff_geometry https://manual.nexusformat.org/classes/base_classes/NXoff_geometry.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Properties of the neutron or X-ray beam at a given location. This group is intended to be referenced by beamline component groups within the :ref:`NXinstrument` group or by the :ref:`NXsample` group. This group is especially valuable in storing the results of instrument simulations in which it is useful to specify the beam profile, time distribution etc. at each beamline component. Otherwise, its most likely use is in the :ref:`NXsample` group in which it defines the results of the neutron scattering by the sample, e.g., energy transfer, polarizations. Finally, There are cases where the beam is considered as a beamline component and this group may be defined as a subgroup directly inside :ref:`NXinstrument`, in which case it is recommended that the position of the beam is specified by an :ref:`NXtransformations` group, unless the beam is at the origin (which is the sample). Note that incident_wavelength and related fields can be a scalar values or arrays, depending on the use case. To support these use cases, the explicit dimensionality of these fields is not specified, but it can be inferred by the presense of and shape of accompanying fields, such as incident_wavelength_weights for a polychromatic beam. NXobject NXbeam https://manual.nexusformat.org/classes/base_classes/NXbeam.html 0 0 0 0 0 0 0 0 0 A beamline aperture. Note, the group was incorrectly documented as deprecated, but it is not and it is in common use. NXobject NXaperture https://manual.nexusformat.org/classes/base_classes/NXaperture.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A neutron moderator NXobject NXmoderator https://manual.nexusformat.org/classes/base_classes/NXmoderator.html 0 0 0 0 0 0 0 0 NXevent_data is a special group for storing data from neutron detectors in event mode. In this mode, the detector electronics emits a stream of detectorID, timestamp pairs. With detectorID describing the detector element in which the neutron was detected and timestamp the timestamp at which the neutron event was detected. In NeXus detectorID maps to event_id, event_time_offset to the timestamp. As this kind of data is common at pulsed neutron sources, the timestamp is almost always relative to the start of a neutron pulse. Thus the pulse timestamp is recorded too together with an index in the event_id, event_time_offset pair at which data for that pulse starts. At reactor source the same pulsed data effect may be achieved through the use of choppers or in stroboscopic measurement setups. In order to make random access to timestamped data faster there is an optional array pair of cue_timestamp_zero and cue_index. The cue_timestamp_zero will contain courser timestamps then in the time array, say every five minutes. The cue_index will then contain the index into the event_id,event_time_offset pair of arrays for that courser cue_timestamp_zero. NXobject NXevent_data https://manual.nexusformat.org/classes/base_classes/NXevent_data.html 0 0 0 legacy class - recommend to use :ref:`NXtransformations` now Description for a general orientation of a component - used by :ref:`NXgeometry` NXobject NXorientation https://manual.nexusformat.org/classes/base_classes/NXorientation.html 0 0 0 0 0 0 0 0 0 0 Contact information for a user. The format allows more than one user with the same affiliation and contact information, but a second :ref:`NXuser` group should be used if they have different affiliations, etc. NXobject NXuser https://manual.nexusformat.org/classes/base_classes/NXuser.html 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 A neutron optical element to direct the path of the beam. :ref:`NXguide` is used by neutron instruments to describe a guide consists of several mirrors building a shape through which neutrons can be guided or directed. The simplest such form is box shaped although elliptical guides are gaining in popularity. The individual parts of a guide usually have common characteristics but there are cases where they are different. For example, a neutron guide might consist of 2 or 4 coated walls or a supermirror bender with multiple, coated vanes. To describe polarizing supermirrors such as used in neutron reflection, it may be necessary to revise this definition of :ref:`NXguide` to include :ref:`NXpolarizer` and/or :ref:`NXmirror`. When even greater complexity exists in the definition of what constitutes a *guide*, it has been suggested that :ref:`NXguide` be redefined as a :ref:`NXcollection` of :ref:`NXmirror` each having their own :ref:`NXgeometry` describing their location(s). For the more general case when describing mirrors, consider using :ref:`NXmirror`. NOTE: The NeXus International Advisory Committee welcomes comments for revision and improvement of this definition of :ref:`NXguide`. NXobject NXguide https://manual.nexusformat.org/classes/base_classes/NXguide.html 1 This is the application definition for x-ray or neutron tomography raw data with phase contrast variation at each point. In tomography first some dark field images are measured, some bright field images and, of course the sample. In order to properly sort the order of the images taken, a sequence number is stored with each image. NXobject NXtomophase https://manual.nexusformat.org/classes/applications/NXtomophase.html 1 Application definition for a STXM instrument. The interferometer position measurements, monochromator photon energy values and detector measurements are all treated as NXdetectors and stored within the NXinstrument group as lists of values stored in chronological order. The NXdata group then holds another version of the data in a regular 3D array (NumE by NumY by NumX, for a total of nP points in a sample image stack type scan). The former data values should be stored with a minimum loss of precision, while the latter values can be simplified and/or approximated in order to fit the constraints of a regular 3D array. 'Line scans' and 'point spectra' are just sample_image scan types with reduced dimensions in the same way as single images have reduced E dimensions compared to image 'stacks'. NXobject NXstxm https://manual.nexusformat.org/classes/applications/NXstxm.html 1 raw data from a kappa geometry (CAD4) single crystal diffractometer, extends :ref:`NXxbase` This is the application definition for raw data from a kappa geometry (CAD4) single crystal diffractometer. It extends :ref:`NXxbase`, so the full definition is the content of :ref:`NXxbase` plus the data defined here. NXxbase NXxkappa https://manual.nexusformat.org/classes/applications/NXxkappa.html 1 This is an application definition for raw data from an X-ray fluorescence experiment NXobject NXfluo https://manual.nexusformat.org/classes/applications/NXfluo.html 1 raw data from a single crystal laue camera, extends :ref:`NXxrot` This is the application definition for raw data from a single crystal laue camera. It extends :ref:`NXxrot`. NXxrot NXxlaue https://manual.nexusformat.org/classes/applications/NXxlaue.html 1 raw data from a single crystal diffractometer, extends :ref:`NXxbase` This is the application definition for raw data from a single crystal diffractometer measuring in normal beam mode. It extends :ref:`NXxbase`, so the full definition is the content of :ref:`NXxbase` plus the data defined here. All angles are logged in order to support arbitrary scans in reciprocal space. NXxbase NXxnb https://manual.nexusformat.org/classes/applications/NXxnb.html 1 This is a application definition for raw data from a TOF neutron powder diffractometer NXobject NXtofnpd https://manual.nexusformat.org/classes/applications/NXtofnpd.html 1 Implementation of the canSAS standard to store reduced small-angle scattering data of any dimension. .. index:: canSAS For more details, see: * http://www.cansas.org/ * http://www.cansas.org/formats/canSAS1d/1.1/doc/ * http://cansas-org.github.io/canSAS2012/ * https://github.com/canSAS-org/NXcanSAS_examples The minimum requirements for *reduced* small-angle scattering data as described by canSAS are summarized in the following figure: .. _canSAS_2012_minimum: .. figure:: canSAS/2012-minimum.png :width: 60% The minimum requirements for *reduced* small-angle scattering data. (:download:`full image <canSAS/2012-minimum.png>`) See :ref:`below <NXcanSAS_minimum>` for the minimum required information for a NeXus data file written to the NXcanSAS specification. .. rubric:: Implementation of canSAS standard in NeXus This application definition is an implementation of the canSAS standard for storing both one-dimensional and multi-dimensional *reduced* small-angle scattering data. * NXcanSAS is for reduced SAS data and metadata to be stored together in one file. * *Reduced* SAS data consists of :math:`I(\vec{Q})` or :math:`I(|\vec{Q}|)` * External file links are not to be used for the reduced data. * A good practice/practise is, at least, to include a reference to how the data was acquired and processed. Yet this is not a requirement. * There is no need for NXcanSAS to refer to any raw data. The canSAS data format has a structure similar to NeXus, not identical. To allow canSAS data to be expressed in NeXus, yet identifiable by the canSAS standard, an additional group attribute ``canSAS_class`` was introduced. Here is the mapping of some common groups. =============== ============ ========================== group (*) NX_class canSAS_class =============== ============ ========================== sasentry NXentry SASentry sasdata NXdata SASdata sasdetector NXdetector SASdetector sasinstrument NXinstrument SASinstrument sasnote NXnote SASnote sasprocess NXprocess SASprocess sasprocessnote NXcollection SASprocessnote sastransmission NXdata SAStransmission_spectrum sassample NXsample SASsample sassource NXsource SASsource =============== ============ ========================== (*) The name of each group is a suggestion, not a fixed requirement and is chosen as fits each data file. See the section on defining :ref:`NXDL group and field names <RegExpName>`. Refer to the NeXus Coordinate System drawing (:ref:`Design-CoordinateSystem`) for choice and direction of :math:`x`, :math:`y`, and :math:`z` axes. .. _NXcanSAS_minimum: .. rubric:: The minimum required information for a NeXus data file written to the NXcanSAS specification. .. literalinclude:: canSAS/minimum-required.txt :tab-width: 4 :linenos: :language: text NXobject NXcanSAS https://manual.nexusformat.org/classes/applications/NXcanSAS.html 1 This is the application definition for a TOF laue diffractometer NXobject NXlauetof https://manual.nexusformat.org/classes/applications/NXlauetof.html 1 This is a application definition for raw data from a direct geometry TOF spectrometer NXtofraw NXdirecttof https://manual.nexusformat.org/classes/applications/NXdirecttof.html 1 This is an application definition for raw data from an X-ray absorption spectroscopy experiment. This is essentially a scan on energy versus incoming/ absorbed beam. NXobject NXxas https://manual.nexusformat.org/classes/applications/NXxas.html 1 raw data from a :index:`four-circle diffractometer` with an :index:`eulerian cradle`, extends :ref:`NXxbase` It extends :ref:`NXxbase`, so the full definition is the content of :ref:`NXxbase` plus the data defined here. All four angles are logged in order to support arbitrary scans in reciprocal space. NXxbase NXxeuler https://manual.nexusformat.org/classes/applications/NXxeuler.html 1 functional application definition for macromolecular crystallography NXobject NXmx https://manual.nexusformat.org/classes/applications/NXmx.html 1 Application definition for a generic scan instrument. This definition is more an example then a stringent definition as the content of a given NeXus scan file needs to differ for different types of scans. This example definition shows a scan like done on a rotation camera: the sample is rotated and a detector image, the rotation angle and a monitor value is stored at each step in the scan. In the following, the symbol ``NP`` is used to represent the number of scan points. These are the rules for storing scan data in NeXus files which are implemented in this example: * Each value varied throughout a scan is stored as an array of length ``NP`` at its respective location within the NeXus hierarchy. * For area detectors, ``NP`` is the first dimension, example for a detector of 256x256: ``data[NP,256,256]`` * The NXdata group contains links to all variables varied in the scan and the data. This to give an equivalent to the more familiar classical tabular representation of scans. These rules exist for a reason: HDF allows the first dimension of a data set to be unlimited. This means the data can be appended too. Thus a NeXus file built according to the rules given above can be used in the following way: * At the start of a scan, write all the static information. * At each scan point, append new data from varied variables and the detector to the file. NXobject NXscan https://manual.nexusformat.org/classes/applications/NXscan.html 1 This is an application definition for the final result of a tomography experiment: a 3D construction of some volume of physical properties. NXobject NXtomoproc https://manual.nexusformat.org/classes/applications/NXtomoproc.html 1 This is the application definition for x-ray or neutron tomography raw data. In tomography a number of dark field images are measured, some bright field images and, of course the sample. In order to distinguish between them images carry a image_key. NXobject NXtomo https://manual.nexusformat.org/classes/applications/NXtomo.html 1 This is an application definition for a monochromatic scanning reflectometer. It does not have the information to calculate the resolution since it does not have any apertures. NXobject NXrefscan https://manual.nexusformat.org/classes/applications/NXrefscan.html 1 This is an application definition for angular resolved photo electron spectroscopy. It has been drawn up with hemispherical electron analysers in mind. NXobject NXarpes https://manual.nexusformat.org/classes/applications/NXarpes.html 1 Application definition for any :math:`I(Q)` data. NXobject NXiqproc https://manual.nexusformat.org/classes/applications/NXiqproc.html 1 Raw, monochromatic 2-D SAS data with an area detector. This is an application definition for raw data (not processed or reduced data) from a 2-D small angle scattering instrument collected with a monochromatic beam and an area detector. It is meant to be suitable both for neutron SANS and X-ray SAXS data. It covers all raw data from any monochromatic SAS techniques that use an area detector: SAS, WSAS, grazing incidence, GISAS It covers all raw data from any SAS techniques that use an area detector and a monochromatic beam. NXobject NXsas https://manual.nexusformat.org/classes/applications/NXsas.html 1 This is a application definition for raw data from a direct geometry TOF spectrometer NXtofraw NXindirecttof https://manual.nexusformat.org/classes/applications/NXindirecttof.html 1 NXSPE Inelastic Format. Application definition for NXSPE file format. NXobject NXspe https://manual.nexusformat.org/classes/applications/NXspe.html 1 This is an application definition for raw data from a TOF reflectometer. NXobject NXreftof https://manual.nexusformat.org/classes/applications/NXreftof.html 1 This is the application definition for S(Q,OM) processed data. As this kind of data is in general not on a rectangular grid after data reduction, it is stored as Q,E positions plus their intensity, table like. It is the task of a possible visualisation program to regrid this data in a sensible way. NXobject NXsqom https://manual.nexusformat.org/classes/applications/NXsqom.html 1 This is a definition for data to be archived by ICAT (http://www.icatproject.org/). .. text from the icatproject.org site the database (with supporting software) that provides an interface to all ISIS experimental data and will provide a mechanism to link all aspects of ISIS research from proposal through to publication. NXobject NXarchive https://manual.nexusformat.org/classes/applications/NXarchive.html 1 This is a application definition for raw data from a generic TOF instrument NXobject NXtofsingle https://manual.nexusformat.org/classes/applications/NXtofsingle.html 1 raw data from a single crystal Laue camera, extends :ref:`NXxlaue` This is the application definition for raw data from a single crystal Laue camera with an image plate as a detector. It extends :ref:`NXxlaue`. NXxlaue NXxlaueplate https://manual.nexusformat.org/classes/applications/NXxlaueplate.html 1 raw data from a rotation camera, extends :ref:`NXxbase` This is the application definition for raw data from a rotation camera. It extends :ref:`NXxbase`, so the full definition is the content of :ref:`NXxbase` plus the data defined here. NXxbase NXxrot https://manual.nexusformat.org/classes/applications/NXxrot.html 1 This definition covers the common parts of all monochromatic single crystal raw data application definitions. NXobject NXxbase https://manual.nexusformat.org/classes/applications/NXxbase.html 1 Processed data from XAS. This is energy versus I(incoming)/I(absorbed). NXobject NXxasproc https://manual.nexusformat.org/classes/applications/NXxasproc.html 1 This is an application definition for raw data from a generic TOF instrument NXobject NXtofraw https://manual.nexusformat.org/classes/applications/NXtofraw.html 1 This is an application definition for a triple axis spectrometer. It is for the trademark scan of the TAS, the Q-E scan. For your alignment scans use the rules in :ref:`NXscan`. NXobject NXtas https://manual.nexusformat.org/classes/applications/NXtas.html 1 raw, 2-D SAS data with an area detector with a time-of-flight source It covers all raw data from any SAS techniques that use an area detector at a time-of-flight source. NXobject NXsastof https://manual.nexusformat.org/classes/applications/NXsastof.html 1 Monochromatic Neutron and X-Ray Powder diffractometer Instrument definition for a powder diffractometer at a monochromatic neutron or X-ray beam. This is both suited for a powder diffractometer with a single detector or a powder diffractometer with a position sensitive detector. NXobject NXmonopd https://manual.nexusformat.org/classes/applications/NXmonopd.html NXcrystal/GEOMETRY Position of crystal https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-geometry-group true NXcrystal/temperature_log log file of crystal temperature https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-temperature-log-group NXcrystal/reflectivity crystal reflectivity versus wavelength https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-reflectivity-group NXcrystal/transmission crystal transmission versus wavelength https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-transmission-group NXcrystal/shape A NXshape group describing the shape of the crystal arrangement https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-shape-group true NXcrystal/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-off-geometry-group NXcrystal/TRANSFORMATIONS Transformations used by this component to define its position and orientation. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-transformations-group NXcollimator/GEOMETRY position, shape and size https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-geometry-group true NXcollimator/frequency_log Log of frequency https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-frequency-log-group NXcollimator/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-off-geometry-group NXcollimator/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-transformations-group NXpinhole/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXpinhole.html#nxpinhole-transformations-group NXbeam_stop/GEOMETRY engineering shape, orientation and position of the beam stop. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-geometry-group true NXbeam_stop/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-off-geometry-group NXbeam_stop/CYLINDRICAL_GEOMETRY This group is an alternative to NXoff_geometry for describing the shape of the beam stop. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-cylindrical-geometry-group NXbeam_stop/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-transformations-group NXflipper/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-transformations-group NXsubentry/experiment_documentation Description of the full experiment (document in pdf, latex, ...) https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-experiment-documentation-group NXsubentry/notes Notes describing entry https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-notes-group 0 NXsubentry/thumbnail A small image that is representative of the entry. An example of this is a 640x480 jpeg image automatically produced by a low resolution plot of the NXdata. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-thumbnail-group NXsubentry/USER https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-user-group NXsubentry/SAMPLE https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-sample-group NXsubentry/INSTRUMENT https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-instrument-group NXsubentry/COLLECTION https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-collection-group NXsubentry/MONITOR https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-monitor-group NXsubentry/DATA https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-data-group NXsubentry/PARAMETERS https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-parameters-group NXsubentry/PROCESS https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-process-group NXprocess/NOTE The note will contain information about how the data was processed or anything about the data provenance. The contents of the note can be anything that the processing code can understand, or simple text. The name will be numbered to allow for ordering of steps. https://manual.nexusformat.org/classes/base_classes/NXprocess.html#nxprocess-note-group NXfermi_chopper/GEOMETRY geometry of the fermi chopper https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-geometry-group true NXfermi_chopper/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-off-geometry-group NXfermi_chopper/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-transformations-group NXcapillary/gain The gain of the capillary as a function of energy https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-gain-group NXcapillary/transmission The transmission of the capillary as a function of energy https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-transmission-group NXcapillary/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-transformations-group NXslit/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXslit.html#nxslit-transformations-group NXfilter/GEOMETRY Geometry of the filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-geometry-group true NXfilter/transmission Wavelength transmission profile of filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-transmission-group NXfilter/temperature_log Linked temperature_log for the filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-temperature-log-group NXfilter/sensor_type Sensor(s)used to monitor the filter temperature https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-sensor-type-group NXfilter/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-off-geometry-group NXfilter/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-transformations-group NXdetector/GEOMETRY Position and orientation of detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-geometry-group true NXdetector/CHANNELNAME_channel Group containing the description and metadata for a single channel from a multi-channel detector. Given an :ref:`NXdata` group linked as part of an NXdetector group that has an axis with named channels (see the example in :ref:`NXdata </NXdata@default_slice-attribute>`), the NXdetector will have a series of NXdetector_channel groups, one for each channel, named CHANNELNAME_channel. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-channelname-channel-group 0 0 0 0 0 NXdetector/efficiency Spectral efficiency of detector with respect to e.g. wavelength https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-efficiency-group NXdetector/calibration_method summary of conversion of array data to pixels (e.g. polynomial approximations) and location of details of the calibrations https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-calibration-method-group NXdetector/data_file https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-data-file-group NXdetector/COLLECTION Use this group to provide other data related to this NXdetector group. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-collection-group NXdetector/DETECTOR_MODULE For use in special cases where the data in NXdetector is represented in several parts, each with a separate geometry. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-detector-module-group NXdetector/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-transformations-group NXdisk_chopper/GEOMETRY https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-geometry-group true NXdisk_chopper/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-off-geometry-group NXdisk_chopper/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-transformations-group NXsource/notes any source/facility related messages/events that occurred during the experiment https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-notes-group 0 NXsource/bunch_pattern For storage rings, description of the bunch pattern. This is useful to describe irregular bunch patterns. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-bunch-pattern-group NXsource/pulse_shape source pulse shape https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-pulse-shape-group NXsource/geometry "Engineering" location of source. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-geometry-group true NXsource/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-off-geometry-group NXsource/distribution The wavelength or energy distribution of the source https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-distribution-group NXsource/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-transformations-group NXbending_magnet/spectrum bending magnet spectrum https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-spectrum-group NXbending_magnet/GEOMETRY "Engineering" position of bending magnet https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-geometry-group true NXbending_magnet/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-off-geometry-group NXbending_magnet/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-transformations-group NXentry/DATA The data group .. note:: Before the NIAC2016 meeting [#]_, at least one :ref:`NXdata` group was required in each :ref:`NXentry` group. At the NIAC2016 meeting, it was decided to make :ref:`NXdata` an optional group in :ref:`NXentry` groups for data files that do not use an application definition. It is recommended strongly that all NeXus data files provide a NXdata group. It is permissable to omit the NXdata group only when defining the default plot is not practical or possible from the available data. For example, neutron event data may not have anything that makes a useful plot without extensive processing. Certain application definitions override this decision and require an :ref:`NXdata` group in the :ref:`NXentry` group. The ``minOccurs=0`` attribute in the application definition will indicate the :ref:`NXdata` group is optional, otherwise, it is required. .. [#] NIAC2016: https://www.nexusformat.org/NIAC2016.html, https://github.com/nexusformat/NIAC/issues/16 https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-data-group NXentry/experiment_documentation Description of the full experiment (document in pdf, latex, ...) https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-experiment-documentation-group NXentry/notes Notes describing entry https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-notes-group 0 NXentry/thumbnail A small image that is representative of the entry. An example of this is a 640x480 jpeg image automatically produced by a low resolution plot of the NXdata. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-thumbnail-group NXentry/USER https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-user-group NXentry/SAMPLE https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-sample-group NXentry/INSTRUMENT https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-instrument-group NXentry/COLLECTION https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-collection-group NXentry/MONITOR https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-monitor-group NXentry/PARAMETERS https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-parameters-group NXentry/PROCESS https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-process-group NXentry/SUBENTRY https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-subentry-group NXpositioner/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-transformations-group NXfresnel_zone_plate/TRANSFORMATIONS "Engineering" position of the fresnel zone plate This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-transformations-group NXpolarizer/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-transformations-group NXxraylens/cylinder_orientation Orientation of the cylinder axis. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-cylinder-orientation-group NXxraylens/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-off-geometry-group NXxraylens/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-transformations-group NXroot/ENTRY entries https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-entry-group NXinsertion_device/spectrum spectrum of insertion device https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-spectrum-group NXinsertion_device/GEOMETRY "Engineering" position of insertion device https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-geometry-group true NXinsertion_device/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-off-geometry-group NXinsertion_device/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-transformations-group NXsample_component/transmission As a function of Wavelength https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-transmission-group NXmonochromator/distribution https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-distribution-group NXmonochromator/geometry https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-geometry-group true NXmonochromator/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-off-geometry-group NXmonochromator/CRYSTAL Use as many crystals as necessary to describe https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-crystal-group NXmonochromator/VELOCITY_SELECTOR https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-velocity-selector-group NXmonochromator/GRATING For diffraction grating based monochromators https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-grating-group NXmonochromator/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-transformations-group NXsensor/geometry Defines the axes for logged vector quantities if they are not the global instrument axes. https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-geometry-group true NXsensor/value_log Time history of sensor readings https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-value-log-group NXsensor/value_deriv1_log Time history of first derivative of sensor readings https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-value-deriv1-log-group NXsensor/value_deriv2_log Time history of second derivative of sensor readings https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-value-deriv2-log-group NXsensor/external_field_full For complex external fields not satisfied by External_field_brief https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-external-field-full-group NXsensor/OFF_GEOMETRY This group describes the shape of the sensor when necessary. https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-off-geometry-group NXsensor/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-transformations-group NXvelocity_selector/geometry https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-geometry-group true NXvelocity_selector/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-off-geometry-group NXvelocity_selector/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-transformations-group NXsample/geometry The position and orientation of the center of mass of the sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-geometry-group true NXsample/BEAM Details of beam incident on sample - used to calculate sample/beam interaction point https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-beam-group NXsample/SAMPLE_COMPONENT One group per sample component This is the perferred way of recording per component information over the n_comp arrays https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-sample-component-group NXsample/transmission As a function of Wavelength https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-transmission-group NXsample/temperature_log temperature_log.value is a link to e.g. temperature_env.sensor1.value_log.value https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-temperature-log-group true NXsample/temperature_env Additional sample temperature environment information https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-temperature-env-group 0 NXsample/magnetic_field magnetic_field.value is a link to e.g. magnetic_field_env.sensor1.value https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-magnetic-field-group NXsample/magnetic_field_log magnetic_field_log.value is a link to e.g. magnetic_field_env.sensor1.value_log.value https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-magnetic-field-log-group true NXsample/magnetic_field_env Additional sample magnetic environment information https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-magnetic-field-env-group NXsample/external_ADC logged value (or logic state) read from user's setup https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-external-adc-group NXsample/POSITIONER Any positioner (motor, PZT, ...) used to locate the sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-positioner-group NXsample/OFF_GEOMETRY This group describes the shape of the sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-off-geometry-group NXsample/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-transformations-group NXattenuator/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-transformations-group NXattenuator/shape Shape of this component. Particulary useful to define the origin for position and orientation in non-standard cases. https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-shape-group NXmirror/GEOMETRY https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-geometry-group true NXmirror/reflectivity Reflectivity as function of wavelength https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-reflectivity-group NXmirror/shape A NXshape group describing the shape of the mirror https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-shape-group true NXmirror/figure_data Numerical description of the surface figure of the mirror. https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-figure-data-group NXmirror/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-off-geometry-group NXmirror/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-transformations-group NXinstrument/APERTURE https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-aperture-group NXinstrument/ATTENUATOR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-attenuator-group NXinstrument/BEAM https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-beam-group NXinstrument/BEAM_STOP https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-beam-stop-group NXinstrument/BENDING_MAGNET https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-bending-magnet-group NXinstrument/COLLIMATOR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-collimator-group NXinstrument/COLLECTION https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-collection-group NXinstrument/CAPILLARY https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-capillary-group NXinstrument/CRYSTAL https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-crystal-group NXinstrument/DETECTOR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-detector-group NXinstrument/DETECTOR_GROUP https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-detector-group-group NXinstrument/DISK_CHOPPER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-disk-chopper-group NXinstrument/EVENT_DATA https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-event-data-group NXinstrument/FERMI_CHOPPER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-fermi-chopper-group NXinstrument/FILTER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-filter-group NXinstrument/FLIPPER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-flipper-group NXinstrument/GUIDE https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-guide-group NXinstrument/INSERTION_DEVICE https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-insertion-device-group NXinstrument/MIRROR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-mirror-group NXinstrument/MODERATOR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-moderator-group NXinstrument/MONOCHROMATOR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-monochromator-group NXinstrument/POLARIZER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-polarizer-group NXinstrument/POSITIONER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-positioner-group NXinstrument/SOURCE https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-source-group NXinstrument/DIFFRACTOMETER https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-diffractometer-group NXinstrument/VELOCITY_SELECTOR https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-velocity-selector-group NXinstrument/XRAYLENS https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-xraylens-group NXmonitor/integral_log Time variation of monitor counts https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-integral-log-group NXmonitor/GEOMETRY Geometry of the monitor https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-geometry-group true NXmonitor/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-off-geometry-group NXmonitor/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-transformations-group NXenvironment/position The position and orientation of the apparatus. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-position-group NXenvironment/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-transformations-group NXenvironment/NOTE Additional information, LabView logs, digital photographs, etc https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-note-group NXenvironment/SENSOR https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-sensor-group NXtranslation/geometry Link to other object if we are relative, else absent https://manual.nexusformat.org/classes/base_classes/NXtranslation.html#nxtranslation-geometry-group NXgeometry/SHAPE shape/size information of component https://manual.nexusformat.org/classes/base_classes/NXgeometry.html#nxgeometry-shape-group NXgeometry/TRANSLATION translation of component https://manual.nexusformat.org/classes/base_classes/NXgeometry.html#nxgeometry-translation-group NXgeometry/ORIENTATION orientation of component https://manual.nexusformat.org/classes/base_classes/NXgeometry.html#nxgeometry-orientation-group NXgrating/shape A NXshape group describing the shape of the mirror https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-shape-group true NXgrating/figure_data Numerical description of the surface figure of the mirror. https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-figure-data-group NXgrating/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-off-geometry-group NXgrating/TRANSFORMATIONS "Engineering" position of the grating Transformations used by this component to define its position and orientation. https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-transformations-group NXbeam/DATA Distribution of beam with respect to relevant variable e.g. wavelength. This is mainly useful for simulations which need to store plottable information at each beamline component. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-data-group 0 0 NXbeam/TRANSFORMATIONS Direction (and location) for the beam. The location of the beam can be given by any point which it passes through as its offset attribute. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-group NXaperture/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-transformations-group NXaperture/OFF_GEOMETRY Use this group to describe the shape of the aperture https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-off-geometry-group NXaperture/GEOMETRY location and shape of aperture .. TODO: documentation needs improvement, contributions welcome * description of terms is poor and leaves much to interpretation * Describe what is meant by translation _here_ and ... * Similar throughout base classes * Some base classes do this much better * Such as where is the gap written? https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-geometry-group true NXaperture/BLADE_GEOMETRY location and shape of each blade https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-blade-geometry-group true NXaperture/NOTE describe any additional information in a note https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-note-group NXmoderator/GEOMETRY "Engineering" position of moderator https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-geometry-group true NXmoderator/temperature_log log file of moderator temperature https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-temperature-log-group NXmoderator/pulse_shape moderator pulse shape https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-pulse-shape-group NXmoderator/OFF_GEOMETRY This group describes the shape of the moderator https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-off-geometry-group NXmoderator/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-transformations-group NXorientation/GEOMETRY Link to another object if we are using relative positioning, else absent https://manual.nexusformat.org/classes/base_classes/NXorientation.html#nxorientation-geometry-group NXguide/GEOMETRY TODO: Explain what this NXgeometry group means. What is intended here? https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-geometry-group true 0 0 0 0 0 0 0 NXguide/reflectivity Reflectivity as function of reflecting surface and wavelength https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-group NXguide/OFF_GEOMETRY This group describes the shape of the beam line component https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-off-geometry-group NXguide/TRANSFORMATIONS This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups. https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-transformations-group 1 1 1 1 1 1 1 1 NXtomophase/entry https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-group 1 1 1 1 NXtomophase/entry/instrument https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-group 1 1 1 NXtomophase/entry/instrument/SOURCE https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-source-group 1 1 NXtomophase/entry/instrument/bright_field https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-bright-field-group 1 1 NXtomophase/entry/instrument/dark_field https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-dark-field-group 1 1 1 1 1 NXtomophase/entry/instrument/sample https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-sample-group 1 1 1 1 1 NXtomophase/entry/sample https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-sample-group 1 NXtomophase/entry/control https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-control-group NXtomophase/entry/data https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-data-group 1 1 1 1 0 1 1 1 1 1 1 NXstxm/ENTRY https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-group 1 1 1 1 1 0 1 0 1 0 1 NXstxm/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-group 1 1 1 1 1 1 NXstxm/ENTRY/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-source-group 1 1 NXstxm/ENTRY/INSTRUMENT/monochromator https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-monochromator-group 1 NXstxm/ENTRY/INSTRUMENT/DETECTOR https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-detector-group 1 NXstxm/ENTRY/INSTRUMENT/sample_x Measurements of the sample position from the x-axis interferometer. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-sample-x-group 1 NXstxm/ENTRY/INSTRUMENT/sample_y Measurements of the sample position from the y-axis interferometer. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-sample-y-group 1 NXstxm/ENTRY/INSTRUMENT/sample_z Measurements of the sample position from the z-axis interferometer. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-sample-z-group 1 NXstxm/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-sample-group 1 1 1 1 1 1 1 1 1 NXstxm/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-data-group 1 NXstxm/ENTRY/control https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-control-group 1 1 1 1 NXxkappa/entry https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-group 1 NXxkappa/entry/instrument https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-instrument-group 1 NXxkappa/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-instrument-detector-group 1 1 1 1 NXxkappa/entry/sample https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-sample-group NXxkappa/entry/name https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-name-group 1 1 1 1 1 1 1 NXfluo/entry https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-group 1 1 1 NXfluo/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-group 1 1 1 NXfluo/entry/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-source-group 1 NXfluo/entry/INSTRUMENT/monochromator https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-monochromator-group 1 1 NXfluo/entry/INSTRUMENT/fluorescence https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-fluorescence-group 1 NXfluo/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-sample-group 1 1 1 NXfluo/entry/MONITOR https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-monitor-group NXfluo/entry/data https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-data-group 1 1 NXxlaue/entry https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-group 1 NXxlaue/entry/instrument https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-instrument-group 1 NXxlaue/entry/instrument/source https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-instrument-source-group 1 1 NXxlaue/entry/instrument/source/distribution This is the wavelength distribution of the beam https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-instrument-source-distribution-group 1 1 1 1 NXxnb/entry https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-group 1 NXxnb/entry/instrument https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-instrument-group 1 1 NXxnb/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-instrument-detector-group 1 NXxnb/entry/sample https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-sample-group NXxnb/entry/name https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-name-group 1 1 1 1 1 1 1 1 1 NXtofnpd/entry https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-group 1 NXtofnpd/entry/user https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-user-group 1 NXtofnpd/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-group 1 1 1 1 1 1 NXtofnpd/entry/INSTRUMENT/detector https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-group 1 NXtofnpd/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-sample-group 1 1 1 1 1 NXtofnpd/entry/MONITOR https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-monitor-group NXtofnpd/entry/data https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-data-group 1 0 0 0 0 0 1 1 1 1 0 1 1 NXcanSAS/ENTRY .. index:: NXcanSAS (applications); SASentry Place the canSAS ``SASentry`` group as a child of a NeXus ``NXentry`` group (when data from multiple techniques are being stored) or as a replacement for the ``NXentry`` group. Note: It is required for all numerical objects to provide a *units* attribute that describes the engineering units. Use the Unidata UDunits [#]_ specification as this is compatible with various community standards. .. [#] The UDunits specification also includes instructions for derived units. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-group 1 1 0 0 0 0 0 0 1 1 1 1 1 0 0 NXcanSAS/ENTRY/DATA A *SASData* group contains a single reduced small-angle scattering data set that can be represented as :math:`I(\vec{Q})` or :math:`I(|\vec{Q}|)`. *Q* can be either a vector (:math:`\vec{Q}`) or a vector magnitude (:math:`|\vec{Q}|`) The name of each *SASdata* group must be unique within a SASentry group. Suggest using names such as ``sasdata01``. NOTE: For the first *SASdata* group, be sure to write the chosen name into the `SASentry/@default` attribute, as in:: SASentry/@default="sasdata01" A *SASdata* group has several attributes: * I_axes * Q_indices * Mask_indices To indicate the dependency relationships of other varied parameters, use attributes similar to ``@Mask_indices`` (such as ``@Temperature_indices`` or ``@Pressure_indices``). https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-group 0 0 0 0 1 NXcanSAS/ENTRY/INSTRUMENT Description of the small-angle scattering instrument. Consider, carefully, the relevance to the SAS data analysis process when adding subgroups in this **NXinstrument** group. Additional information can be added but will likely be ignored by standardized data anlysis processes. The NeXus :ref:`NXbeam` base class may be added as a subgroup of this **NXinstrument** group *or* as a subgroup of the **NXsample** group to describe properties of the beam at any point downstream from the source. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-group 1 0 1 0 1 1 NXcanSAS/ENTRY/INSTRUMENT/APERTURE :ref:`NXaperture` is generic and limits the variation in data files. Possible NeXus base class alternatives are: :ref:`NXpinhole` or :ref:`NXslit`. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-aperture-group 0 1 0 1 1 NXcanSAS/ENTRY/INSTRUMENT/COLLIMATOR Description of a collimating element (defines the divergence of the beam) in the instrument. To document a slit, pinhole, or the beam, refer to the documentation of the ``NXinstrument`` group above. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-collimator-group 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR Description of a detector in the instrument. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-group 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE Description of the radiation source. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-group 1 1 0 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0 1 1 NXcanSAS/ENTRY/SAMPLE Description of the sample. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-group 0 0 0 1 0 1 0 1 0 1 NXcanSAS/ENTRY/PROCESS Description of a processing or analysis step. Add additional fields as needed to describe value(s) of any variable, parameter, or term related to the *SASprocess* step. Be sure to include *units* attributes for all numerical fields. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-group NXcanSAS/ENTRY/PROCESS/NOTE Any additional notes or subprocessing steps will be documented here. An **NXnote** group can be added to any NeXus group at or below the **NXentry** group. It is shown here as a suggestion of a good place to *consider* its use. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-note-group 1 NXcanSAS/ENTRY/PROCESS/COLLECTION Describes anything about *SASprocess* that is not already described. Any content not defined in the canSAS standard can be placed at this point. Note: The name of this group is flexible, it could take any name, as long as it is unique within the **NXprocess** group. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-collection-group 1 NXcanSAS/ENTRY/COLLECTION Free form description of anything not covered by other elements. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-collection-group 1 1 1 1 1 1 1 0 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM The *SAStransmission_spectrum* element This describes certain data obtained from a variable-wavelength source such as pulsed-neutron source. The name of each *SAStransmission_spectrum* group must be unique within a SASentry group. Suggest using names such as ``sastransmission_spectrum01``. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-group 1 1 1 1 1 NXlauetof/entry https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-group 1 NXlauetof/entry/instrument https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-group 1 1 1 1 1 1 1 NXlauetof/entry/instrument/detector This assumes a planar 2D detector. All angles and distances refer to the center of the detector. https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-group 1 1 1 NXlauetof/entry/sample https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-sample-group 1 1 1 1 NXlauetof/entry/control https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-control-group NXlauetof/entry/name https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-name-group 1 1 1 1 NXdirecttof/entry https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-group 0 0 NXdirecttof/entry/INSTRUMENT We definitly want the rotation_speed and energy of the chopper. Thus either a fermi_chopper or a disk_chopper group is required. https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-group 1 1 NXdirecttof/entry/INSTRUMENT/fermi_chopper https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-fermi-chopper-group 1 1 NXdirecttof/entry/INSTRUMENT/disk_chopper https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-disk-chopper-group 1 1 1 1 1 1 1 1 NXxas/ENTRY https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-group 1 1 1 1 NXxas/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-group 1 1 1 NXxas/ENTRY/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-source-group 1 NXxas/ENTRY/INSTRUMENT/monochromator https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-monochromator-group 1 NXxas/ENTRY/INSTRUMENT/incoming_beam https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-incoming-beam-group 1 NXxas/ENTRY/INSTRUMENT/absorbed_beam https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-absorbed-beam-group 1 NXxas/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-sample-group 1 1 1 NXxas/ENTRY/MONITOR https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-monitor-group 1 NXxas/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-data-group 1 1 1 1 NXxeuler/entry https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-group 1 NXxeuler/entry/instrument https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-instrument-group 1 NXxeuler/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-instrument-detector-group 1 1 1 NXxeuler/entry/sample https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-sample-group NXxeuler/entry/name https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-name-group 1 1 1 1 0 1 0 1 1 0 NXmx/ENTRY Note, it is recommended that ``file_name`` and ``file_time`` are included as attributes at the root of a file that includes :ref:`NXmx`. See :ref:`NXroot`. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-group 0 NXmx/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-data-group 0 1 1 0 NXmx/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-sample-group NXmx/ENTRY/SAMPLE/TRANSFORMATIONS This is the recommended location for sample goniometer and other related axes. This is a requirement to describe for any scan experiment. The reason it is optional is mainly to accommodate XFEL single shot exposures. Use of the depends_on field and the NXtransformations group is strongly recommended. As noted above this should be an absolute requirement to have for any scan experiment. The reason it is optional is mainly to accommodate XFEL single shot exposures. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-sample-transformations-group 0 0 1 1 1 0 NXmx/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-group 0 NXmx/ENTRY/INSTRUMENT/ATTENUATOR https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-attenuator-group 1 1 1 NXmx/ENTRY/INSTRUMENT/DETECTOR_GROUP Optional logical grouping of detectors. Each detector is represented as an NXdetector with its own detector data array. Each detector data array may be further decomposed into array sections by use of NXdetector_module groups. Detectors can be grouped logically together using NXdetector_group. Groups can be further grouped hierarchically in a single NXdetector_group (for example, if there are multiple detectors at an endstation or multiple endstations at a facility). Alternatively, multiple NXdetector_groups can be provided. The groups are defined hierarchically, with names given in the group_names field, unique identifying indices given in the field group_index, and the level in the hierarchy given in the group_parent field. For example if an x-ray detector group, DET, consists of four detectors in a rectangular array:: DTL DTR DLL DLR We could have:: group_names: ["DET", "DTL", "DTR", "DLL", "DLR"] group_index: [1, 2, 3, 4, 5] group_parent: [-1, 1, 1, 1, 1] https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-group-group 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 NXmx/ENTRY/INSTRUMENT/DETECTOR Normally the detector group will have the name ``detector``. However, in the case of multiple detectors, each detector needs a uniquely named NXdetector. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-group NXmx/ENTRY/INSTRUMENT/DETECTOR/TRANSFORMATIONS Location for axes (transformations) to do with the detector. In the case of a single-module detector, the axes of the detector axis chain may be stored here. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-transformations-group NXmx/ENTRY/INSTRUMENT/DETECTOR/COLLECTION Suggested container for detailed non-standard detector information like corrections applied automatically or performance settings. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-collection-group 1 1 0 0 1 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-group NXmx/ENTRY/INSTRUMENT/DETECTOR/CHANNELNAME_channel Group containing the description and metadata for a single channel from a multi-channel detector. Given an :ref:`NXdata` group linked as part of an NXdetector group that has an axis with named channels (see the example in :ref:`NXdata </NXdata@default_slice-attribute>`), the NXdetector will have a series of NXdetector_channel groups, one for each channel, named CHANNELNAME_channel. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-channelname-channel-group 0 1 0 0 0 0 0 0 0 0 0 0 0 0 NXmx/ENTRY/INSTRUMENT/BEAM https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-group NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength_spectrum This group is intended for use cases that do not fit the :ref:`incident_wavelength </NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength-field>` and :ref:`incident_wavelength_weights </NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength_weights-field>` fields above, perhaps for example a 2D spectrometer. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-wavelength-spectrum-group 1 NXmx/ENTRY/SOURCE The neutron or x-ray storage ring/facility. Note, the NXsource base class has many more fields available, but at present we only require the name. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-source-group 1 1 1 1 1 1 1 1 NXscan/ENTRY https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-group 1 NXscan/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-instrument-group 1 NXscan/ENTRY/INSTRUMENT/DETECTOR https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-instrument-detector-group 1 NXscan/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-sample-group 1 NXscan/ENTRY/MONITOR https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-monitor-group NXscan/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-data-group 1 1 1 1 1 1 NXtomoproc/entry https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-group 1 NXtomoproc/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-instrument-group 1 1 1 NXtomoproc/entry/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-instrument-source-group 1 NXtomoproc/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-sample-group 1 1 1 1 NXtomoproc/entry/reconstruction https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-reconstruction-group 1 NXtomoproc/entry/reconstruction/parameters https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-reconstruction-parameters-group 1 1 1 1 NXtomoproc/entry/data https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-group 1 1 0 1 1 0 1 0 1 0 1 1 NXtomo/entry https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-group 0 1 1 NXtomo/entry/instrument https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-group 0 1 0 1 0 1 NXtomo/entry/instrument/SOURCE https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-source-group 1 1 0 1 0 1 0 1 0 1 0 1 NXtomo/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-group 1 1 0 1 0 1 0 1 NXtomo/entry/sample https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-sample-group 1 NXtomo/entry/control https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-control-group NXtomo/entry/data https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-data-group 1 1 1 1 1 1 1 1 NXrefscan/entry https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-group 1 1 1 NXrefscan/entry/instrument https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-group 1 1 1 NXrefscan/entry/instrument/SOURCE https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-source-group 1 NXrefscan/entry/instrument/monochromator https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-monochromator-group 1 1 NXrefscan/entry/instrument/DETECTOR https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-detector-group 1 1 NXrefscan/entry/sample https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-sample-group 1 1 1 NXrefscan/entry/control https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-control-group NXrefscan/entry/data https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-data-group 1 1 1 1 1 1 1 NXarpes/ENTRY https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-group 1 1 1 NXarpes/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-group 1 1 1 NXarpes/ENTRY/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-source-group 1 NXarpes/ENTRY/INSTRUMENT/monochromator https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-monochromator-group 1 1 1 1 1 1 1 1 1 1 1 1 1 NXarpes/ENTRY/INSTRUMENT/analyser https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-group 1 1 NXarpes/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-sample-group NXarpes/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-data-group 1 1 1 1 1 1 1 NXiqproc/ENTRY https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-group 1 1 NXiqproc/ENTRY/instrument https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-instrument-group 1 1 1 NXiqproc/ENTRY/instrument/SOURCE https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-instrument-source-group 1 NXiqproc/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-sample-group 1 1 1 1 NXiqproc/ENTRY/reduction https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-reduction-group 1 NXiqproc/ENTRY/reduction/input Input parameters for the reduction program used https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-reduction-input-group NXiqproc/ENTRY/reduction/output Eventual output parameters from the data reduction program used https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-reduction-output-group 1 1 1 1 NXiqproc/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-data-group 1 0 0 1 0 0 0 1 NXsas/ENTRY https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-group 1 1 0 1 1 NXsas/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-group 1 0 1 NXsas/ENTRY/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-source-group 1 0 NXsas/ENTRY/INSTRUMENT/MONOCHROMATOR https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-monochromator-group 1 NXsas/ENTRY/INSTRUMENT/COLLIMATOR https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-collimator-group 1 NXsas/ENTRY/INSTRUMENT/COLLIMATOR/GEOMETRY https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-collimator-geometry-group 1 1 NXsas/ENTRY/INSTRUMENT/COLLIMATOR/GEOMETRY/SHAPE https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-collimator-geometry-shape-group 1 1 1 1 0 0 0 0 0 0 NXsas/ENTRY/INSTRUMENT/DETECTOR https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-group 1 0 NXsas/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-sample-group 1 1 1 NXsas/ENTRY/MONITOR https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-monitor-group 0 NXsas/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-data-group 1 1 1 1 NXindirecttof/entry https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-group 1 NXindirecttof/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-instrument-group 1 1 1 NXindirecttof/entry/INSTRUMENT/analyser https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-instrument-analyser-group 1 1 1 1 1 1 NXspe/ENTRY https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-group 1 1 1 NXspe/ENTRY/NXSPE_info https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-nxspe-info-group 1 1 1 1 1 1 1 1 NXspe/ENTRY/data https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-group 1 1 NXspe/ENTRY/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-instrument-group 1 NXspe/ENTRY/INSTRUMENT/FERMI_CHOPPER https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-instrument-fermi-chopper-group 1 1 1 NXspe/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-sample-group 1 1 1 1 1 1 1 1 NXreftof/entry https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-group 1 1 1 NXreftof/entry/instrument https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-group 1 NXreftof/entry/instrument/chopper https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-chopper-group 1 1 1 1 1 1 NXreftof/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-group 1 1 NXreftof/entry/sample https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-sample-group 1 1 1 1 1 NXreftof/entry/control https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-control-group NXreftof/entry/data https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-data-group 1 1 1 1 1 1 1 NXsqom/ENTRY https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-group 1 1 NXsqom/ENTRY/instrument https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-instrument-group 1 1 1 NXsqom/ENTRY/instrument/SOURCE https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-instrument-source-group 1 NXsqom/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-sample-group 1 1 1 1 NXsqom/ENTRY/reduction https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-reduction-group 1 NXsqom/ENTRY/reduction/input Input parameters for the reduction program used https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-reduction-input-group NXsqom/ENTRY/reduction/output Eventual output parameters from the data reduction program used https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-reduction-output-group 1 1 1 1 1 NXsqom/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-data-group 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 NXarchive/entry https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-group 1 1 1 NXarchive/entry/user https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-user-group 1 1 1 NXarchive/entry/instrument https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-group 1 1 1 NXarchive/entry/instrument/SOURCE https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-source-group 1 1 1 1 1 1 1 1 1 1 1 1 NXarchive/entry/sample https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-group 1 1 1 1 1 1 1 1 1 1 NXtofsingle/entry https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-group 1 NXtofsingle/entry/user https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-user-group 1 NXtofsingle/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-group 1 1 1 1 1 NXtofsingle/entry/INSTRUMENT/detector https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-detector-group 1 1 NXtofsingle/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-sample-group 1 1 1 1 1 NXtofsingle/entry/MONITOR https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-monitor-group NXtofsingle/entry/data https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-data-group 1 1 NXxlaueplate/entry https://manual.nexusformat.org/classes/applications/NXxlaueplate.html#nxxlaueplate-entry-group 1 NXxlaueplate/entry/instrument https://manual.nexusformat.org/classes/applications/NXxlaueplate.html#nxxlaueplate-entry-instrument-group 1 NXxlaueplate/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXxlaueplate.html#nxxlaueplate-entry-instrument-detector-group 1 1 1 1 NXxrot/entry https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-group 1 1 NXxrot/entry/instrument https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-group 1 1 1 NXxrot/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-detector-group 1 NXxrot/entry/instrument/attenuator https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-attenuator-group 1 1 NXxrot/entry/sample https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-sample-group NXxrot/entry/name https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-name-group 1 1 1 1 1 1 1 NXxbase/entry https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-group 1 1 1 NXxbase/entry/instrument https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-group 1 1 1 NXxbase/entry/instrument/source https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-source-group 1 NXxbase/entry/instrument/monochromator https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-monochromator-group 1 1 1 1 1 NXxbase/entry/instrument/detector The name of the group is detector if there is only one detector, if there are several, names have to be detector1, detector2, ...detectorn. https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-group 1 1 1 1 1 1 1 NXxbase/entry/sample https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-group 1 1 1 NXxbase/entry/control https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-control-group NXxbase/entry/DATA The name of this group id data if there is only one detector; if there are several the names will be data1, data2, data3 and will point to the corresponding detector groups in the instrument hierarchy. https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-data-group 1 1 1 1 1 1 NXxasproc/ENTRY https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-group 1 NXxasproc/ENTRY/SAMPLE https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-sample-group 1 1 1 1 NXxasproc/ENTRY/XAS_data_reduction https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-xas-data-reduction-group 1 NXxasproc/ENTRY/XAS_data_reduction/parameters https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-xas-data-reduction-parameters-group 1 1 NXxasproc/ENTRY/DATA https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-data-group 1 1 1 1 1 1 1 1 1 1 1 NXtofraw/entry https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-group 1 NXtofraw/entry/user https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-user-group 1 NXtofraw/entry/instrument https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-group 1 1 1 1 1 1 NXtofraw/entry/instrument/detector https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-group 1 1 NXtofraw/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-sample-group 1 1 1 1 1 1 NXtofraw/entry/MONITOR https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-group NXtofraw/entry/data https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-data-group 1 1 1 1 1 1 1 NXtas/entry https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-group 1 1 1 1 NXtas/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-group 1 1 NXtas/entry/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-source-group 1 1 NXtas/entry/INSTRUMENT/monochromator https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-monochromator-group 1 1 1 NXtas/entry/INSTRUMENT/analyser https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-analyser-group 1 1 NXtas/entry/INSTRUMENT/DETECTOR https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-detector-group 1 1 1 1 1 1 1 1 1 1 1 NXtas/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-group 1 1 1 NXtas/entry/MONITOR https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-monitor-group NXtas/entry/DATA One of the ei,ef,qh,qk,ql,en should get a primary=1 attribute to denote the main scan axis https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-data-group 1 1 1 1 1 1 1 1 NXsastof/ENTRY https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-group 1 1 1 1 NXsastof/ENTRY/instrument https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-group 1 1 1 NXsastof/ENTRY/instrument/source https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-source-group 1 NXsastof/ENTRY/instrument/collimator https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-collimator-group 1 NXsastof/ENTRY/instrument/collimator/geometry https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-collimator-geometry-group 1 1 NXsastof/ENTRY/instrument/collimator/geometry/shape https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-collimator-geometry-shape-group 1 1 1 1 1 1 1 1 1 1 1 NXsastof/ENTRY/instrument/detector https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-group 1 1 NXsastof/ENTRY/sample https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-sample-group 1 1 1 1 NXsastof/ENTRY/control https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-control-group NXsastof/ENTRY/data https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-data-group 1 1 1 1 1 1 1 NXmonopd/entry https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-group 1 1 1 NXmonopd/entry/INSTRUMENT https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-group 1 1 1 NXmonopd/entry/INSTRUMENT/SOURCE https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-source-group 1 NXmonopd/entry/INSTRUMENT/CRYSTAL https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-crystal-group 1 1 NXmonopd/entry/INSTRUMENT/DETECTOR https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-detector-group 1 1 NXmonopd/entry/SAMPLE https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-sample-group 1 1 1 NXmonopd/entry/MONITOR https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-monitor-group NXmonopd/entry/DATA https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-data-group Bragg Laue NXcrystal/usage How this crystal is used. Choices are in the list. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-usage-field 0 1 NXcrystal/type Type or material of monochromating substance. Chemical formula can be specified separately. Use the "reflection" field to indicate the (hkl) orientation. Use the "d_spacing" field to record the lattice plane spacing. This field was changed (2010-11-17) from an enumeration to a string since common usage showed a wider variety of use than a simple list. These are the items in the list at the time of the change: PG (Highly Oriented Pyrolytic Graphite) | Ge | Si | Cu | Fe3Si | CoFe | Cu2MnAl (Heusler) | Multilayer | Diamond. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-type-field 0 1 NXcrystal/chemical_formula The chemical formula specified using CIF conventions. Abbreviated version of CIF standard: * Only recognized element symbols may be used. * Each element symbol is followed by a 'count' number. A count of '1' may be omitted. * A space or parenthesis must separate each cluster of (element symbol + count). * Where a group of elements is enclosed in parentheses, the multiplier for the group must follow the closing parentheses. That is, all element and group multipliers are assumed to be printed as subscripted numbers. * Unless the elements are ordered in a manner that corresponds to their chemical structure, the order of the elements within any group or moiety depends on whether or not carbon is present. * If carbon is present, the order should be: C, then H, then the other elements in alphabetical order of their symbol. If carbon is not present, the elements are listed purely in alphabetic order of their symbol. * This is the *Hill* system used by Chemical Abstracts. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-chemical-formula-field 0 1 NXcrystal/order_no A number which describes if this is the first, second,.. :math:`n^{th}` crystal in a multi crystal monochromator https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-order-no-field 0 1 NXcrystal/cut_angle Cut angle of reflecting Bragg plane and plane of crystal surface https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-cut-angle-field 0 1 NXcrystal/space_group Space group of crystal structure https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-space-group-field 0 1 NXcrystal/unit_cell Unit cell parameters (lengths and angles) https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-field 0 1 NXcrystal/unit_cell_a Unit cell lattice parameter: length of side a https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-a-field 0 1 NXcrystal/unit_cell_b Unit cell lattice parameter: length of side b https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-b-field 0 1 NXcrystal/unit_cell_c Unit cell lattice parameter: length of side c https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-c-field 0 1 NXcrystal/unit_cell_alpha Unit cell lattice parameter: angle alpha https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-alpha-field 0 1 NXcrystal/unit_cell_beta Unit cell lattice parameter: angle beta https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-beta-field 0 1 NXcrystal/unit_cell_gamma Unit cell lattice parameter: angle gamma https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-gamma-field 0 1 NXcrystal/unit_cell_volume Volume of the unit cell https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-unit-cell-volume-field 0 1 NXcrystal/orientation_matrix Orientation matrix of single crystal sample using Busing-Levy convention: W. R. Busing and H. A. Levy (1967). Acta Cryst. 22, 457-464 https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-orientation-matrix-field 0 1 NXcrystal/wavelength Optimum diffracted wavelength https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-wavelength-field 0 1 NXcrystal/d_spacing spacing between crystal planes of the reflection https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-d-spacing-field 0 1 NXcrystal/scattering_vector Scattering vector, Q, of nominal reflection https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-scattering-vector-field 0 1 NXcrystal/reflection Miller indices (hkl) values of nominal reflection https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-reflection-field 0 1 NXcrystal/thickness Thickness of the crystal. (Required for Laue orientations - see "usage" field) https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-thickness-field 0 1 NXcrystal/density mass density of the crystal https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-density-field 0 1 NXcrystal/segment_width Horizontal width of individual segment https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-segment-width-field 0 1 NXcrystal/segment_height Vertical height of individual segment https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-segment-height-field 0 1 NXcrystal/segment_thickness Thickness of individual segment https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-segment-thickness-field 0 1 NXcrystal/segment_gap Typical gap between adjacent segments https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-segment-gap-field 0 1 NXcrystal/segment_columns number of segment columns in horizontal direction https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-segment-columns-field 0 1 NXcrystal/segment_rows number of segment rows in vertical direction https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-segment-rows-field 0 1 NXcrystal/mosaic_horizontal horizontal mosaic Full Width Half Maximum https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-mosaic-horizontal-field 0 1 NXcrystal/mosaic_vertical vertical mosaic Full Width Half Maximum https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-mosaic-vertical-field 0 1 NXcrystal/curvature_horizontal Horizontal curvature of focusing crystal https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-curvature-horizontal-field 0 1 NXcrystal/curvature_vertical Vertical curvature of focusing crystal https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-curvature-vertical-field 0 1 NXcrystal/is_cylindrical Is this crystal bent cylindrically? https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-is-cylindrical-field 0 1 NXcrystal/cylindrical_orientation_angle If cylindrical: cylinder orientation angle https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-cylindrical-orientation-angle-field 0 1 NXcrystal/polar_angle Polar (scattering) angle at which crystal assembly is positioned. Note: some instrument geometries call this term 2theta. Note: it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-polar-angle-field 0 1 NXcrystal/azimuthal_angle Azimuthal angle at which crystal assembly is positioned. Note: it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-azimuthal-angle-field 0 1 NXcrystal/bragg_angle Bragg angle of nominal reflection https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-bragg-angle-field 0 1 NXcrystal/temperature average/nominal crystal temperature https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-temperature-field 0 1 NXcrystal/temperature_coefficient how lattice parameter changes with temperature https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-temperature-coefficient-field 0 1 NXcrystal/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a crystal. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-depends-on-field Soller radial oscillating honeycomb NXcollimator/type https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-type-field 0 1 NXcollimator/soller_angle Angular divergence of Soller collimator https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-soller-angle-field 0 1 NXcollimator/divergence_x divergence of collimator in local x direction https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-divergence-x-field 0 1 NXcollimator/divergence_y divergence of collimator in local y direction https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-divergence-y-field 0 1 NXcollimator/frequency Frequency of oscillating collimator https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-frequency-field 0 1 NXcollimator/blade_thickness blade thickness https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-blade-thickness-field 0 1 NXcollimator/blade_spacing blade spacing https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-blade-spacing-field 0 1 NXcollimator/absorbing_material name of absorbing material https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-absorbing-material-field 0 1 NXcollimator/transmitting_material name of transmitting material https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-transmitting-material-field 0 1 NXcollimator/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. Assuming a collimator with a "flat" entry surface, the reference plane is the plane which contains this surface. The reference point of the collimator in the x and y axis is the centre of the collimator entry surface on that plane. The reference plane is orthogonal to the z axis and the location of this plane is the reference point on the z axis. The collimator faces negative z values. .. image:: collimator/collimator.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-depends-on-field 0 1 NXnote/author Author or creator of note https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-author-field 0 1 NXnote/date Date note created/added https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-date-field 0 1 NXnote/type Mime content type of note data field e.g. image/jpeg, text/plain, text/html https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-type-field 0 1 NXnote/file_name Name of original file name if note was read from an external source https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-file-name-field 0 1 NXnote/description Title of an image or other details of the note https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-description-field 0 1 NXnote/sequence_index Sequence index of note, for placing a sequence of multiple **NXnote** groups in an order. Starts with 1. https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-sequence-index-field 0 1 NXnote/data Binary note data - if text, line terminator is [CR][LF]. https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-data-field 0 1 NXpinhole/depends_on Points to the path of the last element in the geometry chain that places this object in space. When followed through that chain is supposed to end at an element depending on "." i.e. the origin of the coordinate system. If desired the location of the slit can also be described relative to an NXbeam, which will allow a simple description of a non-centred pinhole. The reference direction of the pinhole is parallel with the z axis. The reference point of the pinhole is its center in the x and y axis. The reference point on the z axis is the plane which overlaps the side of the opening of the pin hole pointing towards the source (minus on the z axis). .. image:: pinhole/pinhole.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXpinhole.html#nxpinhole-depends-on-field 0 1 NXpinhole/diameter Size of the circular hole defining the transmitted beam size. https://manual.nexusformat.org/classes/base_classes/NXpinhole.html#nxpinhole-diameter-field 0 1 NXdetector_group/group_names An array of the names of the detectors given in NXdetector groups or the names of hierarchical groupings of detectors given as names of NXdetector_group groups or in NXdetector_group group_names and group_parent fields as having children. https://manual.nexusformat.org/classes/base_classes/NXdetector_group.html#nxdetector-group-group-names-field 0 1 NXdetector_group/group_index An array of unique identifiers for detectors or groupings of detectors. Each ID is a unique ID for the corresponding detector or group named in the field group_names. The IDs are positive integers starting with 1. https://manual.nexusformat.org/classes/base_classes/NXdetector_group.html#nxdetector-group-group-index-field 0 1 NXdetector_group/group_parent An array of the hierarchical levels of the parents of detectors or groupings of detectors. A top-level grouping has parent level -1. https://manual.nexusformat.org/classes/base_classes/NXdetector_group.html#nxdetector-group-group-parent-field 0 1 NXdetector_group/group_type Code number for group type, e.g. bank=1, tube=2 etc. https://manual.nexusformat.org/classes/base_classes/NXdetector_group.html#nxdetector-group-group-type-field nxflat nxcylinder nxbox nxsphere nxcone nxelliptical nxtoroidal nxparabolic nxpolynomial NXshape/shape general shape of a component https://manual.nexusformat.org/classes/base_classes/NXshape.html#nxshape-shape-field 0 1 NXshape/size physical extent of the object along its local axes (after NXorientation) with the center of mass at the local origin (after NXtranslation). The meaning and location of these axes will vary according to the value of the "shape" variable. ``nshapepar`` defines how many parameters: - For "nxcylinder" type the parameters are (diameter,height) and a three value orientation vector of the cylinder. - For the "nxbox" type the parameters are (length,width,height). - For the "nxsphere" type the parameters are (diameter). - For nxcone cone half aperture - For nxelliptical, semi-major axis, semi-minor-axis, angle of major axis and pole - For nxtoroidal, major radius, minor radius - For nxparabolic, parabolic parameter a - For nxpolynomial, an array of polynom coefficients, the dimension of the array encodes the degree of the polynom https://manual.nexusformat.org/classes/base_classes/NXshape.html#nxshape-size-field concave convex NXshape/direction https://manual.nexusformat.org/classes/base_classes/NXshape.html#nxshape-direction-field circular rectangular NXbeam_stop/description description of beamstop https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-description-field 0 1 NXbeam_stop/size Size of beamstop. If this is not sufficient to describe the beam stop use NXoff_geometry instead. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-size-field 0 1 NXbeam_stop/x x position of the beamstop in relation to the detector. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-x-field 0 1 NXbeam_stop/y y position of the beamstop in relation to the detector. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-y-field 0 1 NXbeam_stop/distance_to_detector distance of the beamstop to the detector. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-distance-to-detector-field in out NXbeam_stop/status https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-status-field 0 1 NXbeam_stop/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference point of the beam stop is its center in the x and y axis. The reference point on the z axis is the surface of the beam stop pointing towards the source. .. image:: beam_stop/beam_stop.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-depends-on-field coil current-sheet NXflipper/type https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-type-field 0 1 NXflipper/flip_turns Linear density of turns (such as number of turns/cm) in flipping field coils https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-flip-turns-field 0 1 NXflipper/comp_turns Linear density of turns (such as number of turns/cm) in compensating field coils https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-comp-turns-field 0 1 NXflipper/guide_turns Linear density of turns (such as number of turns/cm) in guide field coils https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-guide-turns-field 0 1 NXflipper/flip_current Flipping field coil current in "on" state" https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-flip-current-field 0 1 NXflipper/comp_current Compensating field coil current in "on" state" https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-comp-current-field 0 1 NXflipper/guide_current Guide field coil current in "on" state https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-guide-current-field 0 1 NXflipper/thickness thickness along path of neutron travel https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-thickness-field 0 1 NXflipper/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a spin flipper. https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-depends-on-field 0 1 NXsubentry/title Extended title for entry https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-title-field 0 1 NXsubentry/experiment_identifier Unique identifier for the experiment, defined by the facility, possibly linked to the proposals https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-experiment-identifier-field 0 1 NXsubentry/experiment_description Brief summary of the experiment, including key objectives. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-experiment-description-field 0 1 NXsubentry/collection_identifier User or Data Acquisition defined group of NeXus files or :ref:`NXentry` https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-collection-identifier-field 0 1 NXsubentry/collection_description Brief summary of the collection, including grouping criteria. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-collection-description-field 0 1 NXsubentry/entry_identifier unique identifier for the measurement, defined by the facility. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-entry-identifier-field 0 1 0 0 NXsubentry/definition Official NeXus NXDL schema to which this subentry conforms https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-definition-field 0 1 0 0 NXsubentry/definition_local Local NXDL schema extended from the subentry specified in the ``definition`` field. This contains any locally-defined, additional fields in the subentry. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-definition-local-field 0 1 NXsubentry/start_time Starting time of measurement https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-start-time-field 0 1 NXsubentry/end_time Ending time of measurement https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-end-time-field 0 1 NXsubentry/duration Duration of measurement https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-duration-field 0 1 NXsubentry/collection_time Time transpired actually collecting data i.e. taking out time when collection was suspended due to e.g. temperature out of range https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-collection-time-field 0 1 NXsubentry/run_cycle Such as "2007-3". Some user facilities organize their beam time into run cycles. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-run-cycle-field 0 1 0 0 NXsubentry/program_name Name of program used to generate this file https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-program-name-field 0 1 0 NXsubentry/revision Revision id of the file due to re-calibration, reprocessing, new analysis, new instrument definition format, ... https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-revision-field 0 1 NXsubentry/pre_sample_flightpath This is the flightpath before the sample position. This can be determined by a chopper, by the moderator or the source itself. In other words: it the distance to the component which gives the T0 signal to the detector electronics. If another component in the NXinstrument hierarchy provides this information, this should be a link. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-pre-sample-flightpath-field 0 1 NXprocess/program Name of the program used https://manual.nexusformat.org/classes/base_classes/NXprocess.html#nxprocess-program-field 0 1 NXprocess/sequence_index Sequence index of processing, for determining the order of multiple **NXprocess** steps. Starts with 1. https://manual.nexusformat.org/classes/base_classes/NXprocess.html#nxprocess-sequence-index-field 0 1 NXprocess/version Version of the program used https://manual.nexusformat.org/classes/base_classes/NXprocess.html#nxprocess-version-field 0 1 NXprocess/date Date and time of processing. https://manual.nexusformat.org/classes/base_classes/NXprocess.html#nxprocess-date-field 0 1 0 NXparameters/term A parameter (also known as a term) that is used in or results from processing. https://manual.nexusformat.org/classes/base_classes/NXparameters.html#nxparameters-term-field 0 1 NXfermi_chopper/type Fermi chopper type https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-type-field 0 1 NXfermi_chopper/rotation_speed chopper rotation speed https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-rotation-speed-field 0 1 NXfermi_chopper/radius radius of chopper https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-radius-field 0 1 NXfermi_chopper/slit width of an individual slit https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-slit-field 0 1 NXfermi_chopper/r_slit radius of curvature of slits https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-r-slit-field 0 1 NXfermi_chopper/number number of slits https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-number-field 0 1 NXfermi_chopper/height input beam height https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-height-field 0 1 NXfermi_chopper/width input beam width https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-width-field 0 1 NXfermi_chopper/distance distance. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-distance-field 0 1 NXfermi_chopper/wavelength Wavelength transmitted by chopper https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-wavelength-field 0 1 NXfermi_chopper/energy energy selected https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-energy-field 0 1 NXfermi_chopper/absorbing_material absorbing material https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-absorbing-material-field 0 1 NXfermi_chopper/transmitting_material transmitting material https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-transmitting-material-field 0 1 NXfermi_chopper/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a fermi chopper. https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-depends-on-field single_bounce polycapillary conical_capillary NXcapillary/type Type of the capillary https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-type-field 0 1 NXcapillary/manufacturer The manufacturer of the capillary. This is actually important as it may have an impact on performance. https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-manufacturer-field 0 1 NXcapillary/maximum_incident_angle https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-maximum-incident-angle-field 0 1 NXcapillary/accepting_aperture https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-accepting-aperture-field 0 1 NXcapillary/working_distance https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-working-distance-field 0 1 NXcapillary/focal_size The focal size in FWHM https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-focal-size-field 0 1 NXcapillary/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a capillary lens. https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-depends-on-field 0 1 NXslit/depends_on Points to the path of the last element in the geometry chain that places this object in space. When followed through that chain is supposed to end at an element depending on "." i.e. the origin of the coordinate system. If desired the location of the slit can also be described relative to an NXbeam, which will allow a simple description of a non-centred slit. The reference plane of the slit is orthogonal to the z axis and includes the surface that is the entry surface of the slit. The reference point of the slit is the centre of the slit opening in the x and y axis on the reference plane. The reference point on the z axis is the reference plane. .. image:: slit/slit.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXslit.html#nxslit-depends-on-field 0 1 NXslit/x_gap Size of the gap opening in the first dimension of the local coordinate system. https://manual.nexusformat.org/classes/base_classes/NXslit.html#nxslit-x-gap-field 0 1 NXslit/y_gap Size of the gap opening in the second dimension of the local coordinate system. https://manual.nexusformat.org/classes/base_classes/NXslit.html#nxslit-y-gap-field 0 1 NXfilter/description Composition of the filter. Chemical formula can be specified separately. This field was changed (2010-11-17) from an enumeration to a string since common usage showed a wider variety of use than a simple list. These are the items in the list at the time of the change: Beryllium | Pyrolytic Graphite | Graphite | Sapphire | Silicon | Supermirror. https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-description-field in out NXfilter/status position with respect to in or out of the beam (choice of only "in" or "out") https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-status-field 0 1 NXfilter/temperature average/nominal filter temperature https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-temperature-field 0 1 NXfilter/thickness Thickness of the filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-thickness-field 0 1 NXfilter/density mass density of the filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-density-field 0 1 NXfilter/chemical_formula The chemical formula specified using CIF conventions. Abbreviated version of CIF standard: * Only recognized element symbols may be used. * Each element symbol is followed by a 'count' number. A count of '1' may be omitted. * A space or parenthesis must separate each cluster of (element symbol + count). * Where a group of elements is enclosed in parentheses, the multiplier for the group must follow the closing parentheses. That is, all element and group multipliers are assumed to be printed as subscripted numbers. * Unless the elements are ordered in a manner that corresponds to their chemical structure, the order of the elements within any group or moiety depends on whether or not carbon is present. * If carbon is present, the order should be: * C, then H, then the other elements in alphabetical order of their symbol. * If carbon is not present, the elements are listed purely in alphabetic order of their symbol. * This is the *Hill* system used by Chemical Abstracts. https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-chemical-formula-field 0 1 NXfilter/unit_cell_a Unit cell lattice parameter: length of side a https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-a-field 0 1 NXfilter/unit_cell_b Unit cell lattice parameter: length of side b https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-b-field 0 1 NXfilter/unit_cell_c Unit cell lattice parameter: length of side c https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-c-field 0 1 NXfilter/unit_cell_alpha Unit cell lattice parameter: angle alpha https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-alpha-field 0 1 NXfilter/unit_cell_beta Unit cell lattice parameter: angle beta https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-beta-field 0 1 NXfilter/unit_cell_gamma Unit cell lattice parameter: angle gamma https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-gamma-field 0 1 NXfilter/unit_cell_volume Unit cell https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-unit-cell-volume-field 0 1 NXfilter/orientation_matrix Orientation matrix of single crystal filter using Busing-Levy convention: W. R. Busing and H. A. Levy (1967). Acta Cryst. 22, 457-464 https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-orientation-matrix-field 0 1 NXfilter/m_value m value of supermirror filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-m-value-field 0 1 NXfilter/substrate_material substrate material of supermirror filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-substrate-material-field 0 1 NXfilter/substrate_thickness substrate thickness of supermirror filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-substrate-thickness-field 0 1 NXfilter/coating_material coating material of supermirror filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-coating-material-field 0 1 NXfilter/substrate_roughness substrate roughness (RMS) of supermirror filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-substrate-roughness-field 0 1 NXfilter/coating_roughness coating roughness (RMS) of supermirror filter https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-coating-roughness-field 0 1 NXfilter/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a filter. https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-depends-on-field 0 1 0 0 0 NXdetector/time_of_flight Total time of flight https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-time-of-flight-field 0 1 0 NXdetector/raw_time_of_flight In DAQ clock pulses https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-raw-time-of-flight-field 0 1 NXdetector/detector_number Identifier for detector (pixels) Can be multidimensional, if needed https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-detector-number-field 0 1 0 0 NXdetector/data Data values from the detector. The rank and dimension ordering should follow a principle of slowest to fastest measurement axes and may be explicitly specified in application definitions. Mechanical scanning of objects (e.g. sample position/angle, incident beam energy, etc) tends to be the slowest part of an experiment and so any such scan axes should be allocated to the first dimensions of the array. Note that in some cases it may be useful to represent a 2D set of scan points as a single scan-axis in the data array, especially if the scan pattern doesn't fit a rectangular array nicely. Repetition of an experiment in a time series tends to be used similar to a slow scan axis and so will often be in the first dimension of the data array. The next fastest axes are typically the readout of the detector. A point detector will not add any dimensions (as it is just a single value per scan point) to the data array, a strip detector will add one dimension, an imaging detector will add two dimensions (e.g. X, Y axes) and detectors outputting higher dimensional data will add the corresponding number of dimensions. Note that the detector dimensions don't necessarily have to be written in order of the actual readout speeds - the slowest to fastest rule principle is only a guide. Finally, detectors that operate in a time-of-flight mode, such as a neutron spectrometer or a silicon drift detector (used for X-ray fluorescence) tend to have their dimension(s) added to the last dimensions in the data array. The type of each dimension should should follow the order of scan points, detector pixels, then time-of-flight (i.e. spectroscopy, spectrometry). The rank and dimension sizes (see symbol list) shown here are merely illustrative of coordination between related datasets. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-data-field 0 1 NXdetector/data_errors The best estimate of the uncertainty in the data value (array size should match the data field). Where possible, this should be the standard deviation, which has the same units as the data. The form data_error is deprecated. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-data-errors-field 0 1 0 0 0 NXdetector/x_pixel_offset Offset from the detector center in x-direction. Can be multidimensional when needed. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-x-pixel-offset-field 0 1 0 0 0 NXdetector/y_pixel_offset Offset from the detector center in the y-direction. Can be multidimensional when different values are required for each pixel. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-y-pixel-offset-field 0 1 0 0 0 NXdetector/z_pixel_offset Offset from the detector center in the z-direction. Can be multidimensional when different values are required for each pixel. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-z-pixel-offset-field 0 1 NXdetector/distance This is the distance to the previous component in the instrument; most often the sample. The usage depends on the nature of the detector: Most often it is the distance of the detector assembly. But there are irregular detectors. In this case the distance must be specified for each detector pixel. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-distance-field 0 1 NXdetector/polar_angle This is the polar angle of the detector towards the previous component in the instrument; most often the sample. The usage depends on the nature of the detector. Most often it is the polar_angle of the detector assembly. But there are irregular detectors. In this case, the polar_angle must be specified for each detector pixel. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-polar-angle-field 0 1 NXdetector/azimuthal_angle This is the azimuthal angle angle of the detector towards the previous component in the instrument; most often the sample. The usage depends on the nature of the detector. Most often it is the azimuthal_angle of the detector assembly. But there are irregular detectors. In this case, the azimuthal_angle must be specified for each detector pixel. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-azimuthal-angle-field 0 1 NXdetector/description name/manufacturer/model/etc. information https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-description-field 0 1 NXdetector/serial_number Serial number for the detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-serial-number-field 0 1 NXdetector/local_name Local name for the detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-local-name-field 0 1 NXdetector/solid_angle Solid angle subtended by the detector at the sample https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-solid-angle-field 0 1 NXdetector/x_pixel_size Size of each detector pixel. If it is scalar all pixels are the same size. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-x-pixel-size-field 0 1 NXdetector/y_pixel_size Size of each detector pixel. If it is scalar all pixels are the same size https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-y-pixel-size-field 0 1 NXdetector/dead_time Detector dead time https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-dead-time-field 0 1 NXdetector/gas_pressure Detector gas pressure https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-gas-pressure-field 0 1 NXdetector/detection_gas_path maximum drift space dimension https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-detection-gas-path-field 0 1 0 NXdetector/crate Crate number of detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-crate-field 0 1 0 NXdetector/slot Slot number of detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-slot-field 0 1 0 NXdetector/input Input number of detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-input-field 0 1 NXdetector/type Description of type such as He3 gas cylinder, He3 PSD, scintillator, fission chamber, proportion counter, ion chamber, ccd, pixel, image plate, CMOS, ... https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-type-field 0 1 NXdetector/efficiency/efficiency efficiency of the detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-efficiency-efficiency-field 0 1 NXdetector/efficiency/wavelength https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-efficiency-wavelength-field 0 1 NXdetector/real_time Real-time of the exposure (use this if exposure time varies for each array element, otherwise use ``count_time`` field). Most often there is a single real time value that is constant across an entire image frame. In such cases, only a 1-D array is needed. But there are detectors in which the real time changes per pixel. In that case, more than one dimension is needed. Therefore the rank of this field should be less than or equal to (detector rank + 1). https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-real-time-field 0 1 0 NXdetector/start_time start time for each frame, with the ``start`` attribute as absolute reference https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-start-time-field 0 1 0 NXdetector/stop_time stop time for each frame, with the ``start`` attribute as absolute reference https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-stop-time-field 0 1 NXdetector/calibration_date date of last calibration (geometry and/or efficiency) measurements https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-calibration-date-field point linear area NXdetector/layout How the detector is represented https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-layout-field 0 1 NXdetector/count_time Elapsed actual counting time https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-count-time-field 0 1 NXdetector/sequence_number In order to properly sort the order of the images taken in (for example) a tomography experiment, a sequence number is stored with each image. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-sequence-number-field 0 1 NXdetector/beam_center_x This is the x position where the direct beam would hit the detector. This is a length and can be outside of the actual detector. The length can be in physical units or pixels as documented by the units attribute. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-beam-center-x-field 0 1 NXdetector/beam_center_y This is the y position where the direct beam would hit the detector. This is a length and can be outside of the actual detector. The length can be in physical units or pixels as documented by the units attribute. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-beam-center-y-field 0 1 NXdetector/frame_start_number This is the start number of the first frame of a scan. In protein crystallography measurements one often scans a couple of frames on a give sample, then does something else, then returns to the same sample and scans some more frames. Each time with a new data file. This number helps concatenating such measurements. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-frame-start-number-field 0 1 NXdetector/diameter The diameter of a cylindrical detector https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-diameter-field gated triggered summed event histogrammed decimated NXdetector/acquisition_mode The acquisition mode of the detector. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-acquisition-mode-field 0 1 NXdetector/angular_calibration_applied True when the angular calibration has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-angular-calibration-applied-field 0 1 NXdetector/angular_calibration Angular calibration data. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-angular-calibration-field 0 1 NXdetector/flatfield_applied True when the flat field correction has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-flatfield-applied-field 0 1 NXdetector/flatfield Flat field correction data. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-flatfield-field 0 1 NXdetector/flatfield_errors Errors of the flat field correction data. The form flatfield_error is deprecated. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-flatfield-errors-field 0 1 NXdetector/pixel_mask_applied True when the pixel mask correction has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-pixel-mask-applied-field 0 1 NXdetector/pixel_mask The 32-bit pixel mask for the detector. Can be either one mask for the whole dataset (i.e. an array with indices i, j) or each frame can have its own mask (in which case it would be an array with indices np, i, j). Contains a bit field for each pixel to signal dead, blind or high or otherwise unwanted or undesirable pixels. They have the following meaning: .. can't make a table here, a bullet list will have to do for now * bit 0: gap (pixel with no sensor) * bit 1: dead * bit 2: under responding * bit 3: over responding * bit 4: noisy * bit 5: -undefined- * bit 6: pixel is part of a cluster of problematic pixels (bit set in addition to others) * bit 7: -undefined- * bit 8: user defined mask (e.g. around beamstop) * bits 9-30: -undefined- * bit 31: virtual pixel (corner pixel with interpolated value) Normal data analysis software would not take pixels into account when a bit in (mask & 0x0000FFFF) is set. Tag bit in the upper two bytes would indicate special pixel properties that normally would not be a sole reason to reject the intensity value (unless lower bits are set. If the full bit depths is not required, providing a mask with fewer bits is permissible. If needed, additional pixel masks can be specified by including additional entries named pixel_mask_N, where N is an integer. For example, a general bad pixel mask could be specified in pixel_mask that indicates noisy and dead pixels, and an additional pixel mask from experiment-specific shadowing could be specified in pixel_mask_2. The cumulative mask is the bitwise OR of pixel_mask and any pixel_mask_N entries. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-pixel-mask-field 0 1 NXdetector/image_key This field allow to distinguish different types of exposure to the same detector "data" field. Some techniques require frequent (re-)calibration inbetween measuremnts and this way of recording the different measurements preserves the chronological order with is important for correct processing. This is used for example in tomography (`:ref:`NXtomo`) sample projections, dark and flat images, a magic number is recorded per frame. The key is as follows: * projection (sample) = 0 * flat field = 1 * dark field = 2 * invalid = 3 * background (no sample, but buffer where applicable) = 4 In cases where the data is of type :ref:`NXlog` this can also be an NXlog. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-image-key-field 0 1 NXdetector/countrate_correction_applied Counting detectors usually are not able to measure all incoming particles, especially at higher count-rates. Count-rate correction is applied to account for these errors. True when count-rate correction has been applied, false otherwise. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-countrate-correction-applied-field 0 1 NXdetector/countrate_correction_lookup_table The countrate_correction_lookup_table defines the LUT used for count-rate correction. It maps a measured count :math:`c` to its corrected value :math:`countrate\_correction\_lookup\_table[c]`. :math:`m` denotes the length of the table. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-countrate-correction-lookup-table-field 0 1 NXdetector/virtual_pixel_interpolation_applied True when virtual pixel interpolation has been applied, false otherwise. When virtual pixel interpolation is applied, values of some pixels may contain interpolated values. For example, to account for space between readout chips on a module, physical pixels on edges and corners between chips may have larger sensor areas and counts may be distributed between their logical pixels. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-virtual-pixel-interpolation-applied-field 0 1 NXdetector/bit_depth_readout How many bits the electronics reads per pixel. With CCD's and single photon counting detectors, this must not align with traditional integer sizes. This can be 4, 8, 12, 14, 16, ... https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-bit-depth-readout-field 0 1 NXdetector/detector_readout_time Time it takes to read the detector (typically milliseconds). This is important to know for time resolved experiments. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-detector-readout-time-field 0 1 NXdetector/trigger_delay_time Time it takes to start exposure after a trigger signal has been received. This is the reaction time of the detector firmware after receiving the trigger signal to when the detector starts to acquire the exposure, including any user set delay.. This is important to know for time resolved experiments. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-trigger-delay-time-field 0 1 NXdetector/trigger_delay_time_set User-specified trigger delay. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-trigger-delay-time-set-field 0 1 NXdetector/trigger_internal_delay_time Time it takes to start exposure after a trigger signal has been received. This is the reaction time of the detector hardware after receiving the trigger signal to when the detector starts to acquire the exposure. It forms the lower boundary of the trigger_delay_time when the user does not request an additional delay. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-trigger-internal-delay-time-field 0 1 NXdetector/trigger_dead_time Time during which no new trigger signal can be accepted. Typically this is the trigger_delay_time + exposure_time + readout_time. This is important to know for time resolved experiments. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-trigger-dead-time-field 0 1 NXdetector/frame_time This is time for each frame. This is exposure_time + readout time. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-frame-time-field 0 1 NXdetector/gain_setting The gain setting of the detector. This is a detector-specific value meant to document the gain setting of the detector during data collection, for detectors with multiple available gain settings. Examples of gain settings include: * ``standard`` * ``fast`` * ``auto`` * ``high`` * ``medium`` * ``low`` * ``mixed high to medium`` * ``mixed medium to low`` Developers are encouraged to use one of these terms, or to submit additional terms to add to the list. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-gain-setting-field 0 1 NXdetector/saturation_value The value at which the detector goes into saturation. Especially common to CCD detectors, the data is known to be invalid above this value. For example, given a saturation_value and an underload_value, the valid pixels are those less than or equal to the saturation_value and greater than or equal to the underload_value. The precise type should match the type of the data. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-saturation-value-field 0 1 NXdetector/underload_value The lowest value at which pixels for this detector would be reasonably measured. The data is known to be invalid below this value. For example, given a saturation_value and an underload_value, the valid pixels are those less than or equal to the saturation_value and greater than or equal to the underload_value. The precise type should match the type of the data. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-underload-value-field 0 1 NXdetector/number_of_cycles CCD images are sometimes constructed by summing together multiple short exposures in the electronics. This reduces background etc. This is the number of short exposures used to sum images for an image. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-number-of-cycles-field 0 1 NXdetector/sensor_material At times, radiation is not directly sensed by the detector. Rather, the detector might sense the output from some converter like a scintillator. This is the name of this converter material. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-sensor-material-field 0 1 NXdetector/sensor_thickness At times, radiation is not directly sensed by the detector. Rather, the detector might sense the output from some converter like a scintillator. This is the thickness of this converter material. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-sensor-thickness-field 0 1 NXdetector/threshold_energy Single photon counter detectors can be adjusted for a certain energy range in which they work optimally. This is the energy setting for this. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-threshold-energy-field 0 1 NXdetector/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference point of the detector is the center of the first pixel. In complex geometries the NXoff_geometry groups can be used to provide an unambiguous reference. https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-depends-on-field Chopper type single contra_rotating_pair synchro_pair NXdisk_chopper/type Type of the disk-chopper: only one from the enumerated list (match text exactly) https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-type-field 0 1 NXdisk_chopper/rotation_speed Chopper rotation speed. Positive for anticlockwise rotation when facing away from the source, negative otherwise. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-rotation-speed-field 0 1 NXdisk_chopper/slits Number of slits https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-slits-field 0 1 NXdisk_chopper/slit_angle Angular opening https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-slit-angle-field 0 1 NXdisk_chopper/pair_separation Disk spacing in direction of beam https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-pair-separation-field 0 1 NXdisk_chopper/slit_edges Angle of each edge of every slit from the position of the top-dead-center timestamp sensor, anticlockwise when facing away from the source. The first edge must be the opening edge of a slit, thus the last edge may have an angle greater than 360 degrees. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-slit-edges-field 0 1 0 NXdisk_chopper/top_dead_center Timestamps of the top-dead-center signal. The times are relative to the "start" attribute and in the units specified in the "units" attribute. Please note that absolute timestamps under unix are relative to ``1970-01-01T00:00:00.0Z``. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-top-dead-center-field 0 1 NXdisk_chopper/beam_position Angular separation of the center of the beam and the top-dead-center timestamp sensor, anticlockwise when facing away from the source. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-beam-position-field 0 1 NXdisk_chopper/radius Radius of the disk https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-radius-field 0 1 NXdisk_chopper/slit_height Total slit height https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-slit-height-field 0 1 NXdisk_chopper/phase Chopper phase angle https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-phase-field 0 1 NXdisk_chopper/delay Time difference between timing system t0 and chopper driving clock signal https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-delay-field 0 1 NXdisk_chopper/ratio Pulse reduction factor of this chopper in relation to other choppers/fastest pulse in the instrument https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-ratio-field 0 1 NXdisk_chopper/distance Effective distance to the origin. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-distance-field 0 1 NXdisk_chopper/wavelength_range Low and high values of wavelength range transmitted https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-wavelength-range-field 0 1 NXdisk_chopper/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference plane of the disk chopper includes the surface of the spinning disk which faces the source. The reference point in the x and y axis is the point on this surface which is the centre of the axle which the disk is spinning around. The reference plane is orthogonal to the z axis and its position is the reference point on that axis. Note: This reference point in almost all practical cases is not where the beam passes though. .. image:: disk_chopper/disk_chopper.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-depends-on-field 0 1 NXsource/distance Effective distance from sample Distance as seen by radiation from sample. This number should be negative to signify that it is upstream of the sample. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-distance-field 0 1 0 NXsource/name Name of source https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-name-field Spallation Neutron Source Pulsed Reactor Neutron Source Reactor Neutron Source Synchrotron X-ray Source Pulsed Muon Source Rotating Anode X-ray Fixed Tube X-ray UV Laser Free-Electron Laser Optical Laser Ion Source UV Plasma Source Metal Jet X-ray NXsource/type type of radiation source (pick one from the enumerated list and spell exactly) https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-type-field neutron x-ray muon electron ultraviolet visible light positron proton NXsource/probe type of radiation probe (pick one from the enumerated list and spell exactly) https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-probe-field 0 1 NXsource/power Source power https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-power-field 0 1 NXsource/emittance_x Source emittance (nm-rad) in X (horizontal) direction. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-emittance-x-field 0 1 NXsource/emittance_y Source emittance (nm-rad) in Y (horizontal) direction. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-emittance-y-field 0 1 NXsource/sigma_x particle beam size in x https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-sigma-x-field 0 1 NXsource/sigma_y particle beam size in y https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-sigma-y-field 0 1 NXsource/flux Source intensity/area (example: s-1 cm-2) https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-flux-field 0 1 NXsource/energy Source energy. For storage rings, this would be the particle beam energy. For X-ray tubes, this would be the excitation voltage. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-energy-field 0 1 NXsource/current Accelerator, X-ray tube, or storage ring current https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-current-field 0 1 NXsource/voltage Accelerator voltage https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-voltage-field 0 1 NXsource/frequency Frequency of pulsed source https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-frequency-field 0 1 NXsource/period Period of pulsed source https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-period-field Ta W depleted_U enriched_U Hg Pb C NXsource/target_material Pulsed source target material https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-target-material-field 0 1 NXsource/bunch_pattern/title name of the bunch pattern https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-bunch-pattern-title-field 0 1 NXsource/number_of_bunches For storage rings, the number of bunches in use. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-number-of-bunches-field 0 1 NXsource/bunch_length For storage rings, temporal length of the bunch https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-bunch-length-field 0 1 NXsource/bunch_distance For storage rings, time between bunches https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-bunch-distance-field 0 1 NXsource/pulse_width temporal width of source pulse https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-pulse-width-field Single Bunch Multi Bunch NXsource/mode source operating mode https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-mode-field 0 1 NXsource/top_up Is the synchrotron operating in top_up mode? https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-top-up-field 0 1 0 NXsource/last_fill For storage rings, the current at the end of the most recent injection. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-last-fill-field 0 1 NXsource/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference point of the source plane is its center in the x and y axis. The source is considered infinitely thin in the z axis. .. image:: source/source.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-depends-on-field 0 1 NXbending_magnet/critical_energy https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-critical-energy-field 0 1 NXbending_magnet/bending_radius https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-bending-radius-field 0 1 NXbending_magnet/magnetic_field strength of magnetic field of dipole magnets https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-magnetic-field-field 0 1 NXbending_magnet/accepted_photon_beam_divergence An array of four numbers giving X+, X-, Y+ and Y- half divergence https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-accepted-photon-beam-divergence-field 0 1 NXbending_magnet/source_distance_x Distance of source point from particle beam waist in X (horizontal) direction. Note, it is recommended to use NXtransformations instead to place component. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-source-distance-x-field 0 1 NXbending_magnet/source_distance_y Distance of source point from particle beam waist in Y (vertical) direction. Note, it is recommended to use NXtransformations instead to place component. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-source-distance-y-field 0 1 NXbending_magnet/divergence_x_plus Accepted photon beam divergence in X+ (horizontal outboard) direction. Note that divergence_x_plus+divergence_x_minus is the total horizontal beam divergence. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-divergence-x-plus-field 0 1 NXbending_magnet/divergence_x_minus Accepted photon beam divergence in X- (horizontal inboard) direction. Note that divergence_x_plus+divergence_x_minus is the total horizontal beam divergence. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-divergence-x-minus-field 0 1 NXbending_magnet/divergence_y_plus Accepted photon beam divergence in Y+ (vertical upward) direction. Note that divergence_y_plus+divergence_y_minus is the total vertical beam divergence. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-divergence-y-plus-field 0 1 NXbending_magnet/divergence_y_minus Accepted photon beam divergence in Y- (vertical downward) direction. Note that divergence_y_plus+divergence_y_minus is the total vertical beam divergence. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-divergence-y-minus-field 0 1 NXbending_magnet/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a bending magnet. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-depends-on-field 0 1 NXentry/title Extended title for entry https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-title-field 0 1 NXentry/experiment_identifier Unique identifier for the experiment, defined by the facility, possibly linked to the proposals https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-experiment-identifier-field 0 1 NXentry/experiment_description Brief summary of the experiment, including key objectives. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-experiment-description-field 0 1 NXentry/collection_identifier User or Data Acquisition defined group of NeXus files or NXentry https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-collection-identifier-field 0 1 NXentry/collection_description Brief summary of the collection, including grouping criteria. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-collection-description-field 0 1 NXentry/entry_identifier unique identifier for the measurement, defined by the facility. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-entry-identifier-field 0 1 0 NXentry/entry_identifier_uuid UUID identifier for the measurement. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-entry-identifier-uuid-field 0 1 NXentry/features Reserved for future use by NIAC. See https://github.com/nexusformat/definitions/issues/382 https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-features-field 0 1 0 0 NXentry/definition (alternate use: see same field in :ref:`NXsubentry` for preferred) Official NeXus NXDL schema to which this entry conforms which must be the name of the NXDL file (case sensitive without the file extension) that the NXDL schema is defined in. For example the ``definition`` field for a file that conformed to the *NXarpes.nxdl.xml* definition must contain the string **NXarpes**. This field is provided so that :ref:`NXentry` can be the overlay position in a NeXus data file for an application definition and its set of groups, fields, and attributes. *It is advised* to use :ref:`NXsubentry`, instead, as the overlay position. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-definition-field 0 1 0 0 NXentry/definition_local Local NXDL schema extended from the entry specified in the ``definition`` field. This contains any locally-defined, additional fields in the entry. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-definition-local-field true 0 1 NXentry/start_time Starting time of measurement https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-start-time-field 0 1 NXentry/end_time Ending time of measurement https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-end-time-field 0 1 NXentry/duration Duration of measurement https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-duration-field 0 1 NXentry/collection_time Time transpired actually collecting data i.e. taking out time when collection was suspended due to e.g. temperature out of range https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-collection-time-field 0 1 NXentry/run_cycle Such as "2007-3". Some user facilities organize their beam time into run cycles. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-run-cycle-field 0 1 0 0 NXentry/program_name Name of program used to generate this file https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-program-name-field 0 1 0 NXentry/revision Revision id of the file due to re-calibration, reprocessing, new analysis, new instrument definition format, ... https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-revision-field 0 1 NXentry/pre_sample_flightpath This is the flightpath before the sample position. This can be determined by a chopper, by the moderator or the source itself. In other words: it the distance to the component which gives the T0 signal to the detector electronics. If another component in the NXinstrument hierarchy provides this information, this should be a link. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-pre-sample-flightpath-field 0 1 NXdetector_module/data_origin A dimension-2 or dimension-3 field which gives the indices of the origin of the hyperslab of data for this module in the main area detector image in the parent NXdetector module. The data_origin is 0-based. The frame number dimension (np) is omitted. Thus the data_origin field for a dimension-2 dataset with indices (np, i, j) will be an array with indices (i, j), and for a dimension-3 dataset with indices (np, i, j, k) will be an array with indices (i, j, k). The :ref:`order <Design-ArrayStorageOrder>` of indices (i, j or i, j, k) is slow to fast. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-data-origin-field 0 1 NXdetector_module/data_size Two or three values for the size of the module in pixels in each direction. Dimensionality and order of indices is the same as for data_origin. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-data-size-field 0 1 0 0 0 0 0 NXdetector_module/module_offset Offset of the module in regards to the origin of the detector in an arbitrary direction. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-module-offset-field 0 1 0 0 0 0 0 NXdetector_module/fast_pixel_direction Values along the direction of :ref:`fastest varying <Design-ArrayStorageOrder>` :index:`pixel direction<dimension; fastest varying>`. Each value in this array is the size of a pixel in the units specified. Alternatively, if only one value is given, all pixels in this direction have the same value. The direction itself is given through the vector attribute. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-fast-pixel-direction-field 0 1 0 0 0 0 0 NXdetector_module/slow_pixel_direction Values along the direction of :ref:`slowest varying<Design-ArrayStorageOrder>` :index:`pixel direction<dimension; slowest varying>`. Each value in this array is the size of a pixel in the units specified. Alternatively, if only one value is given, all pixels in this direction have the same value. The direction itself is given through the vector attribute. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-slow-pixel-direction-field 0 1 NXdetector_module/depends_on Points to the start of the dependency chain for this module. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-depends-on-field 0 1 NXpositioner/name symbolic or mnemonic name (one word) https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-name-field 0 1 NXpositioner/description description of positioner https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-description-field 0 1 NXpositioner/value best known value of positioner - need [n] as may be scanned https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-value-field 0 1 NXpositioner/raw_value raw value of positioner - need [n] as may be scanned https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-raw-value-field 0 1 NXpositioner/target_value targeted (commanded) value of positioner - need [n] as may be scanned https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-target-value-field 0 1 NXpositioner/tolerance maximum allowable difference between target_value and value https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-tolerance-field 0 1 NXpositioner/soft_limit_min minimum allowed limit to set value https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-soft-limit-min-field 0 1 NXpositioner/soft_limit_max maximum allowed limit to set value https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-soft-limit-max-field 0 1 NXpositioner/velocity velocity of the positioner (distance moved per unit time) https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-velocity-field 0 1 NXpositioner/acceleration_time time to ramp the velocity up to full speed https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-acceleration-time-field 0 1 NXpositioner/controller_record Hardware device record, e.g. EPICS process variable, taco/tango ... https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-controller-record-field 0 1 NXpositioner/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a positioner. https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-depends-on-field 0 1 NXfresnel_zone_plate/focus_parameters list of polynomial coefficients describing the focal length of the zone plate, in increasing powers of photon energy, that describes the focal length of the zone plate (in microns) at an X-ray photon energy (in electron volts). https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-focus-parameters-field 0 1 NXfresnel_zone_plate/outer_diameter https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-outer-diameter-field 0 1 NXfresnel_zone_plate/outermost_zone_width https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-outermost-zone-width-field 0 1 NXfresnel_zone_plate/central_stop_diameter https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-central-stop-diameter-field etched plated zone doubled other NXfresnel_zone_plate/fabrication how the zone plate was manufactured https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-fabrication-field 0 1 NXfresnel_zone_plate/zone_height https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-zone-height-field 0 1 NXfresnel_zone_plate/zone_material Material of the zones themselves https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-zone-material-field 0 1 NXfresnel_zone_plate/zone_support_material Material present between the zones. This is usually only present for the "zone doubled" fabrication process https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-zone-support-material-field 0 1 NXfresnel_zone_plate/central_stop_material https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-central-stop-material-field 0 1 NXfresnel_zone_plate/central_stop_thickness https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-central-stop-thickness-field 0 1 NXfresnel_zone_plate/mask_thickness https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-mask-thickness-field 0 1 NXfresnel_zone_plate/mask_material If no mask is present, set mask_thickness to 0 and omit the mask_material field https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-mask-material-field 0 1 NXfresnel_zone_plate/support_membrane_material https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-support-membrane-material-field 0 1 NXfresnel_zone_plate/support_membrane_thickness https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-support-membrane-thickness-field 0 1 NXfresnel_zone_plate/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a fresnel zone plate. https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-depends-on-field 0 1 0 0 0 0 0 0 NXdata/AXISNAME Coordinate values along one or more :ref:`data </NXdata/DATA-field>` dimensions. The rank must be equal to the number of dimensions it spans. As the upper case ``AXISNAME`` indicates, the names of the ``AXISNAME`` fields can be chosen :ref:`freely <validItemName>`. The :ref:`axes </NXdata@axes-attribute>` attribute can be used to find all datasets in the ``NXdata`` that contain coordinate values. Most AXISNAME fields will be sequences of numbers but if an axis is better represented using names, such as channel names, an array of NX_CHAR can be provided. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-field 0 1 0 0 0 NXdata/DATA .. index:: plotting Data values to be used as the NeXus *plottable data*. As the upper case ``DATA`` indicates, the names of the ``DATA`` fields can be chosen :ref:`freely <validItemName>`. The :ref:`signal attribute </NXdata@signal-attribute>` and :ref:`auxiliary_signals attribute</NXdata@auxiliary_signals-attribute>` can be used to find all datasets in the ``NXdata`` that contain data values. The maximum rank is ``32`` for compatibility with backend file formats. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-data-field 0 1 NXdata/FIELDNAME_errors "Errors" (meaning *uncertainties* or *standard deviations*) associated with any field named ``FIELDNAME`` in this ``NXdata`` group (e.g. an axis, signal or auxiliary signal). The dimensions of the ``FIELDNAME_errors`` field must match the dimensions of the ``FIELDNAME`` field. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-fieldname-errors-field 0 1 NXdata/errors Standard deviations of data values - the data array is identified by the group attribute ``signal``. The ``errors`` array must have the same dimensions as ``DATA``. Client is responsible for defining the dimensions of the data. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-errors-field true 0 1 NXdata/scaling_factor The elements in data are usually float values really. For efficiency reasons these are usually stored as integers after scaling with a scale factor. This value is the scale factor. It is required to get the actual physical value, when necessary. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-scaling-factor-field 0 1 NXdata/offset An optional offset to apply to the values in data. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-offset-field 0 1 NXdata/title Title for the plot. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-title-field 0 1 NXdata/x This is an array holding the values to use for the x-axis of data. The units must be appropriate for the measurement. This is a special case of a :ref:`AXISNAME field </NXdata/AXISNAME-field>` kept for backward compatiblity. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-x-field 0 1 NXdata/y This is an array holding the values to use for the y-axis of data. The units must be appropriate for the measurement. This is a special case of a :ref:`AXISNAME field </NXdata/AXISNAME-field>` kept for backward compatiblity. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-y-field 0 1 NXdata/z This is an array holding the values to use for the z-axis of data. The units must be appropriate for the measurement. This is a special case of a :ref:`AXISNAME field </NXdata/AXISNAME-field>` kept for backward compatiblity. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-z-field 0 1 NXcite/description This should describe the reason for including this reference. For example: The dataset in this group was normalised using the method which is described in detail in this reference. https://manual.nexusformat.org/classes/base_classes/NXcite.html#nxcite-description-field 0 1 NXcite/url URL referencing the document or data. https://manual.nexusformat.org/classes/base_classes/NXcite.html#nxcite-url-field 0 1 NXcite/doi DOI referencing the document or data. https://manual.nexusformat.org/classes/base_classes/NXcite.html#nxcite-doi-field 0 1 NXcite/endnote Bibliographic reference data in EndNote format. https://manual.nexusformat.org/classes/base_classes/NXcite.html#nxcite-endnote-field 0 1 NXcite/bibtex Bibliographic reference data in BibTeX format. https://manual.nexusformat.org/classes/base_classes/NXcite.html#nxcite-bibtex-field 0 1 NXpolarizer/type one of these values: "crystal", "supermirror", "3He" https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-type-field 0 1 NXpolarizer/composition description of the composition of the polarizing material https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-composition-field 0 1 NXpolarizer/reflection [hkl] values of nominal reflection https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-reflection-field 0 1 NXpolarizer/efficiency polarizing efficiency https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-efficiency-field 0 1 NXpolarizer/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a polarizer. https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-depends-on-field paraboloid spherical elliptical hyperbolical NXxraylens/lens_geometry Geometry of the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-lens-geometry-field 0 1 NXxraylens/symmetric Is the device symmetric? https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-symmetric-field 0 1 NXxraylens/cylindrical Is the device cylindrical? https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-cylindrical-field line point NXxraylens/focus_type The type of focus of the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-focus-type-field 0 1 NXxraylens/lens_thickness Thickness of the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-lens-thickness-field 0 1 NXxraylens/lens_length Length of the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-lens-length-field 0 1 NXxraylens/curvature Radius of the curvature as measured in the middle of the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-curvature-field 0 1 NXxraylens/aperture Diameter of the lens. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-aperture-field 0 1 NXxraylens/number_of_lenses Number of lenses that make up the compound lens. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-number-of-lenses-field 0 1 NXxraylens/lens_material Material used to make the lens. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-lens-material-field 0 1 NXxraylens/gas Gas used to fill the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-gas-field 0 1 NXxraylens/gas_pressure Gas pressure in the lens https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-gas-pressure-field 0 1 NXxraylens/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a x-ray lens. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-depends-on-field 0 1 NXcylindrical_geometry/vertices List of x,y,z coordinates for vertices. The origin of the coordinates is the position of the parent component, for example the NXdetector which the geometry describes. If the shape describes a single pixel for a detector with uniform pixel shape then the origin is the position of each pixel as described by the ``x/y/z_pixel_offset`` datasets in ``NXdetector``. https://manual.nexusformat.org/classes/base_classes/NXcylindrical_geometry.html#nxcylindrical-geometry-vertices-field 0 1 NXcylindrical_geometry/cylinders List of indices of vertices in the ``vertices`` dataset to form each cylinder. Each cylinder is described by three vertices A, B, C. First vertex A lies on the cylinder axis and circular face, second point B on edge of the same face as A, and third point C at the other face and on axis. https://manual.nexusformat.org/classes/base_classes/NXcylindrical_geometry.html#nxcylindrical-geometry-cylinders-field 0 1 NXcylindrical_geometry/detector_number Maps cylinders in ``cylinder``, by index, with a detector id. https://manual.nexusformat.org/classes/base_classes/NXcylindrical_geometry.html#nxcylindrical-geometry-detector-number-field undulator wiggler NXinsertion_device/type https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-type-field 0 1 NXinsertion_device/gap separation between opposing pairs of magnetic poles https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-gap-field 0 1 NXinsertion_device/taper angular of gap difference between upstream and downstream ends of the insertion device https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-taper-field 0 1 NXinsertion_device/phase https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-phase-field 0 1 NXinsertion_device/poles number of poles https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-poles-field 0 1 NXinsertion_device/magnetic_wavelength https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-magnetic-wavelength-field 0 1 NXinsertion_device/k beam displacement parameter https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-k-field 0 1 NXinsertion_device/length length of insertion device https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-length-field 0 1 NXinsertion_device/power total power delivered by insertion device https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-power-field 0 1 NXinsertion_device/energy energy of peak intensity in output spectrum https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-energy-field 0 1 NXinsertion_device/bandwidth bandwidth of peak energy https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-bandwidth-field 0 1 NXinsertion_device/harmonic harmonic number of peak https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-harmonic-field 0 1 NXinsertion_device/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a insertion device. https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-depends-on-field 0 1 0 1 0 0 0 0 NXtransformations/AXISNAME Units need to be appropriate for translation or rotation The name of this field is not forced. The user is free to use any name that does not cause confusion. When using more than one ``AXISNAME`` field, make sure that each field name is unique in the same group, as required by HDF5. The values given should be the start points of exposures for the corresponding frames. The end points should be given in ``AXISNAME_end``. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-field 0 1 NXtransformations/AXISNAME_end ``AXISNAME_end`` is a placeholder for a name constructed from the actual name of an axis to which ``_end`` has been appended. The values in this field are the end points of the motions that start at the corresponding positions given in the ``AXISNAME`` field. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-end-field 0 1 NXtransformations/AXISNAME_increment_set ``AXISNAME_increment_set`` is a placeholder for a name constructed from the actual name of an axis to which ``_increment_set`` has been appended. The value of this optional field is the intended average range through which the corresponding axis moves during the exposure of a frame. Ideally, the value of this field added to each value of ``AXISNAME`` would agree with the corresponding values of ``AXISNAME_end``, but there is a possibility of significant differences. Use of ``AXISNAME_end`` is recommended. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-increment-set-field 0 1 NXsample_component/name Descriptive name of sample component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-name-field 0 1 NXsample_component/chemical_formula The chemical formula specified using CIF conventions. Abbreviated version of CIF standard: * Only recognized element symbols may be used. * Each element symbol is followed by a 'count' number. A count of '1' may be omitted. * A space or parenthesis must separate each cluster of (element symbol + count). * Where a group of elements is enclosed in parentheses, the multiplier for the group must follow the closing parentheses. That is, all element and group multipliers are assumed to be printed as subscripted numbers. * Unless the elements are ordered in a manner that corresponds to their chemical structure, the order of the elements within any group or moiety depends on whether or not carbon is present. * If carbon is present, the order should be: - C, then H, then the other elements in alphabetical order of their symbol. - If carbon is not present, the elements are listed purely in alphabetic order of their symbol. * This is the *Hill* system used by Chemical Abstracts. https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-chemical-formula-field 0 1 NXsample_component/unit_cell_abc Crystallography unit cell parameters a, b, and c https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-unit-cell-abc-field 0 1 NXsample_component/unit_cell_alphabetagamma Crystallography unit cell parameters alpha, beta, and gamma https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-unit-cell-alphabetagamma-field 0 1 NXsample_component/unit_cell_volume Volume of the unit cell https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-unit-cell-volume-field 0 1 NXsample_component/sample_orientation This will follow the Busing and Levy convention from Acta.Crysta v22, p457 (1967) https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-sample-orientation-field 0 1 NXsample_component/orientation_matrix Orientation matrix of single crystal sample component. This will follow the Busing and Levy convention from Acta.Crysta v22, p457 (1967) https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-orientation-matrix-field 0 1 NXsample_component/mass Mass of sample component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-mass-field 0 1 NXsample_component/density Density of sample component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-density-field 0 1 NXsample_component/relative_molecular_mass Relative Molecular Mass of sample component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-relative-molecular-mass-field 0 1 NXsample_component/description Description of the sample component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-description-field 0 1 NXsample_component/volume_fraction Volume fraction of component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-volume-fraction-field 0 1 NXsample_component/scattering_length_density Scattering length density of component https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-scattering-length-density-field triclinic monoclinic orthorhombic tetragonal rhombohedral hexagonal cubic NXsample_component/unit_cell_class In case it is all we know and we want to record/document it https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-unit-cell-class-field 0 1 NXsample_component/space_group Crystallographic space group https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-space-group-field 0 1 NXsample_component/point_group Crystallographic point group, deprecated if space_group present https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-point-group-field 0 1 NXmonochromator/wavelength wavelength selected https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-wavelength-field 0 1 NXmonochromator/wavelength_error wavelength standard deviation https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-wavelength-error-field true 0 1 NXmonochromator/wavelength_errors wavelength standard deviation https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-wavelength-errors-field 0 1 NXmonochromator/energy energy selected https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-energy-field 0 1 NXmonochromator/energy_error energy standard deviation https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-energy-error-field true 0 1 NXmonochromator/energy_errors energy standard deviation https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-energy-errors-field 0 1 NXmonochromator/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a monochromator. https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-depends-on-field 0 1 NXsensor/model Sensor identification code/model number https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-model-field 0 1 NXsensor/name Name for the sensor https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-name-field 0 1 NXsensor/short_name Short name of sensor used e.g. on monitor display program https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-short-name-field 0 1 NXsensor/attached_to where sensor is attached to ("sample" | "can") https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-attached-to-field temperature pH magnetic_field electric_field conductivity resistance voltage pressure flow stress strain shear surface_pressure NXsensor/measurement name for measured signal https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-measurement-field 0 1 NXsensor/type The type of hardware used for the measurement. Examples (suggestions but not restrictions): :Temperature: J | K | T | E | R | S | Pt100 | Rh/Fe :pH: Hg/Hg2Cl2 | Ag/AgCl | ISFET :Ion selective electrode: specify species; e.g. Ca2+ :Magnetic field: Hall :Surface pressure: wilhelmy plate https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-type-field 0 1 NXsensor/run_control Is data collection controlled or synchronised to this quantity: 1=no, 0=to "value", 1=to "value_deriv1", etc. https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-run-control-field 0 1 NXsensor/high_trip_value Upper control bound of sensor reading if using run_control https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-high-trip-value-field 0 1 NXsensor/low_trip_value Lower control bound of sensor reading if using run_control https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-low-trip-value-field 0 1 NXsensor/value nominal setpoint or average value - need [n] as may be a vector https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-value-field 0 1 NXsensor/value_deriv1 Nominal/average first derivative of value e.g. strain rate - same dimensions as "value" (may be a vector) https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-value-deriv1-field 0 1 NXsensor/value_deriv2 Nominal/average second derivative of value - same dimensions as "value" (may be a vector) https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-value-deriv2-field along beam across beam transverse solenoidal flow shear gradient flow vorticity NXsensor/external_field_brief https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-external-field-brief-field 0 1 NXsensor/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a sensor. https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-depends-on-field 0 1 NXvelocity_selector/type velocity selector type https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-type-field 0 1 NXvelocity_selector/rotation_speed velocity selector rotation speed https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-rotation-speed-field 0 1 NXvelocity_selector/radius radius at beam centre https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-radius-field 0 1 NXvelocity_selector/spwidth spoke width at beam centre https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-spwidth-field 0 1 NXvelocity_selector/length rotor length https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-length-field 0 1 NXvelocity_selector/num number of spokes/lamella https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-num-field 0 1 NXvelocity_selector/twist twist angle along axis https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-twist-field 0 1 NXvelocity_selector/table offset vertical angle https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-table-field 0 1 NXvelocity_selector/height input beam height https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-height-field 0 1 NXvelocity_selector/width input beam width https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-width-field 0 1 NXvelocity_selector/wavelength wavelength https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-wavelength-field 0 1 NXvelocity_selector/wavelength_spread deviation FWHM /Wavelength https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-wavelength-spread-field 0 1 NXvelocity_selector/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a velocity selector. https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-depends-on-field 0 1 NXsample/name Descriptive name of sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-name-field 0 1 NXsample/chemical_formula The chemical formula specified using CIF conventions. Abbreviated version of CIF standard: * Only recognized element symbols may be used. * Each element symbol is followed by a 'count' number. A count of '1' may be omitted. * A space or parenthesis must separate each cluster of (element symbol + count). * Where a group of elements is enclosed in parentheses, the multiplier for the group must follow the closing parentheses. That is, all element and group multipliers are assumed to be printed as subscripted numbers. * Unless the elements are ordered in a manner that corresponds to their chemical structure, the order of the elements within any group or moiety depends on whether or not carbon is present. * If carbon is present, the order should be: - C, then H, then the other elements in alphabetical order of their symbol. - If carbon is not present, the elements are listed purely in alphabetic order of their symbol. * This is the *Hill* system used by Chemical Abstracts. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-chemical-formula-field 0 1 NXsample/temperature Sample temperature. This could be a scanned variable https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-temperature-field 0 1 0 NXsample/electric_field Applied electric field https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-electric-field-field 0 1 NXsample/magnetic_field Applied magnetic field https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-magnetic-field-field 0 1 0 NXsample/stress_field Applied external stress field https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-stress-field-field 0 1 NXsample/pressure Applied pressure https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-pressure-field 0 1 NXsample/changer_position Sample changer position https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-changer-position-field 0 1 NXsample/unit_cell_abc Crystallography unit cell parameters a, b, and c https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-unit-cell-abc-field 0 1 NXsample/unit_cell_alphabetagamma Crystallography unit cell parameters alpha, beta, and gamma https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-unit-cell-alphabetagamma-field 0 1 NXsample/unit_cell Unit cell parameters (lengths and angles) https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-unit-cell-field 0 1 NXsample/unit_cell_volume Volume of the unit cell https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-unit-cell-volume-field 0 1 NXsample/sample_orientation This will follow the Busing-Levy convention: W. R. Busing and H. A. Levy (1967). Acta Cryst. 22, 457-464 https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-sample-orientation-field 0 1 NXsample/orientation_matrix Orientation matrix of single crystal sample using Busing-Levy convention: W. R. Busing and H. A. Levy (1967). Acta Cryst. 22, 457-464 https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-orientation-matrix-field 0 1 NXsample/ub_matrix UB matrix of single crystal sample using Busing-Levy convention: W. R. Busing and H. A. Levy (1967). Acta Cryst. 22, 457-464. This is the multiplication of the orientation_matrix, given above, with the :math:`B` matrix which can be derived from the lattice constants. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-ub-matrix-field 0 1 NXsample/mass Mass of sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-mass-field 0 1 NXsample/density Density of sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-density-field 0 1 NXsample/relative_molecular_mass Relative Molecular Mass of sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-relative-molecular-mass-field sample sample+can can sample+buffer buffer calibration sample normalisation sample simulated data none sample environment NXsample/type https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-type-field air vacuum inert atmosphere oxidising atmosphere reducing atmosphere sealed can other NXsample/situation The atmosphere will be one of the components, which is where its details will be stored; the relevant components will be indicated by the entry in the sample_component member. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-situation-field 0 1 NXsample/description Description of the sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-description-field 0 1 NXsample/preparation_date Date of preparation of the sample https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-preparation-date-field 0 1 NXsample/component Details of the component of the sample and/or can https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-component-field sample can atmosphere kit NXsample/sample_component Type of component https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-sample-component-field 0 1 NXsample/concentration Concentration of each component https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-concentration-field 0 1 NXsample/volume_fraction Volume fraction of each component https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-volume-fraction-field 0 1 NXsample/scattering_length_density Scattering length density of each component https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-scattering-length-density-field triclinic monoclinic orthorhombic tetragonal rhombohedral hexagonal cubic NXsample/unit_cell_class In case it is all we know and we want to record/document it https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-unit-cell-class-field 0 1 NXsample/space_group Crystallographic space group https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-space-group-field 0 1 NXsample/point_group Crystallographic point group, deprecated if space_group present https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-point-group-field 0 1 NXsample/path_length Path length through sample/can for simple case when it does not vary with scattering direction https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-path-length-field 0 1 NXsample/path_length_window Thickness of a beam entry/exit window on the can (mm) - assumed same for entry and exit https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-path-length-window-field 0 1 NXsample/thickness sample thickness https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-thickness-field 0 1 NXsample/external_DAC value sent to user's sample setup https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-external-dac-field 0 1 NXsample/short_title 20 character fixed length sample description for legends https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-short-title-field 0 1 NXsample/rotation_angle Optional rotation angle for the case when the powder diagram has been obtained through an omega-2theta scan like from a traditional single detector powder diffractometer. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-rotation-angle-field 0 1 NXsample/x_translation Translation of the sample along the X-direction of the laboratory coordinate system Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-x-translation-field 0 1 NXsample/distance Translation of the sample along the Z-direction of the laboratory coordinate system. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-distance-field 0 1 NXsample/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-depends-on-field 0 1 NXattenuator/distance Distance from sample. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-distance-field 0 1 NXattenuator/type Type or composition of attenuator, e.g. polythene https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-type-field 0 1 NXattenuator/thickness Thickness of attenuator along beam direction https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-thickness-field 0 1 NXattenuator/scattering_cross_section Scattering cross section (coherent+incoherent) https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-scattering-cross-section-field 0 1 NXattenuator/absorption_cross_section Absorption cross section https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-absorption-cross-section-field 0 1 NXattenuator/attenuator_transmission The nominal amount of the beam that gets through (transmitted intensity)/(incident intensity) https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-attenuator-transmission-field in out moving 0 NXattenuator/status In or out or moving of the beam https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-status-field 0 1 NXattenuator/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference point of the attenuator is its center in the x and y axis. The reference point on the z axis is the surface of the attenuator pointing towards the source. In complex (asymmetic) geometries an NXoff_geometry group can be used to provide an unambiguous reference. .. image:: attenuator/attenuator.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-depends-on-field single multi NXmirror/type https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-type-field 0 1 NXmirror/description description of this mirror https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-description-field 0 1 NXmirror/incident_angle https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-incident-angle-field 0 1 NXmirror/bend_angle_x https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-bend-angle-x-field 0 1 NXmirror/bend_angle_y https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-bend-angle-y-field vacuum helium argon NXmirror/interior_atmosphere https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-interior-atmosphere-field 0 1 NXmirror/external_material external material outside substrate https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-external-material-field 0 1 NXmirror/m_value The m value for a supermirror, which defines the supermirror regime in multiples of the critical angle of Nickel. https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-m-value-field 0 1 NXmirror/substrate_material https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-substrate-material-field 0 1 NXmirror/substrate_density https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-substrate-density-field 0 1 NXmirror/substrate_thickness https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-substrate-thickness-field 0 1 NXmirror/coating_material https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-coating-material-field 0 1 NXmirror/substrate_roughness https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-substrate-roughness-field 0 1 NXmirror/coating_roughness https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-coating-roughness-field 0 1 NXmirror/even_layer_material https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-even-layer-material-field 0 1 NXmirror/even_layer_density https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-even-layer-density-field 0 1 NXmirror/odd_layer_material https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-odd-layer-material-field 0 1 NXmirror/odd_layer_density https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-odd-layer-density-field 0 1 NXmirror/layer_thickness An array describing the thickness of each layer https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-layer-thickness-field 0 1 NXmirror/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. Given a flat mirror, the reference plane is the plane which contains the "entry" surface of the mirror. The reference point of the mirror in the x and y axis is the centre of the mirror on that plane. The reference plane is orthogonal to the z axis and the location of this plane is the reference point on the z axis. The mirror faces negative z values. .. image:: mirror/mirror.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-depends-on-field 0 1 0 NXinstrument/name Name of instrument https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-name-field 0 1 NXdetector_channel/threshold_energy Energy at which a photon will be recorded https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-threshold-energy-field 0 1 NXdetector_channel/flatfield_applied True when the flat field correction has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-flatfield-applied-field 0 1 NXdetector_channel/flatfield Response of each pixel given a constant input https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-flatfield-field 0 1 NXdetector_channel/flatfield_errors Errors of the flat field correction data. The form flatfield_error is deprecated. https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-flatfield-errors-field 0 1 NXdetector_channel/pixel_mask_applied True when the pixel mask correction has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-pixel-mask-applied-field 0 1 NXdetector_channel/pixel_mask Custom pixel mask for this channel. May include nP as the first dimension for masks that vary for each scan point. https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-pixel-mask-field 0 1 NXdetector_channel/saturation_value The value at which the detector goes into saturation. Especially common to CCD detectors, the data is known to be invalid above this value. For example, given a saturation_value and an underload_value, the valid pixels are those less than or equal to the saturation_value and greater than or equal to the underload_value. The precise type should match the type of the data. https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-saturation-value-field 0 1 NXdetector_channel/underload_value The lowest value at which pixels for this detector would be reasonably measured. The data is known to be invalid below this value. For example, given a saturation_value and an underload_value, the valid pixels are those less than or equal to the saturation_value and greater than or equal to the underload_value. The precise type should match the type of the data. https://manual.nexusformat.org/classes/base_classes/NXdetector_channel.html#nxdetector-channel-underload-value-field monitor timer NXmonitor/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-mode-field 0 1 NXmonitor/start_time Starting time of measurement https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-start-time-field 0 1 NXmonitor/end_time Ending time of measurement https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-end-time-field 0 1 NXmonitor/preset preset value for time or monitor https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-preset-field 0 1 NXmonitor/distance Distance of monitor from sample https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-distance-field true 0 1 NXmonitor/range Range (X-axis, Time-of-flight, etc.) over which the integral was calculated https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-range-field 0 1 NXmonitor/nominal Nominal reading to be used for normalisation purposes. https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-nominal-field 0 1 NXmonitor/integral Total integral monitor counts https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-integral-field Fission Chamber Scintillator NXmonitor/type https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-type-field 0 1 NXmonitor/time_of_flight Time-of-flight https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-time-of-flight-field 0 1 NXmonitor/efficiency Monitor efficiency https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-efficiency-field 0 1 NXmonitor/data Monitor data https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-data-field 0 1 NXmonitor/sampled_fraction Proportion of incident beam sampled by the monitor (0<x<1) https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-sampled-fraction-field 0 1 NXmonitor/count_time Elapsed actual counting time, can be an array of size ``np`` when scanning. This is not the difference of the calendar time but the time the instrument was really counting, without pauses or times lost due beam unavailability https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-count-time-field 0 1 NXmonitor/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference plane of the monitor contains the surface of the detector that faces the source and is the entry point of the beam. The reference point of the monitor in the x and y axis is its centre on this surface. The reference plane is orthogonal to the the z axis and the reference point on this z axis is where they intersect. .. image:: monitor/monitor.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-depends-on-field 0 1 0 0 NXlog/time Time of logged entry. The times are relative to the "start" attribute and in the units specified in the "units" attribute. Please note that absolute timestamps under unix are relative to ``1970-01-01T00:00:00.0Z``. The scaling_factor, when present, has to be applied to the time values in order to arrive at the units specified in the units attribute. The scaling_factor allows for arbitrary time units such as ticks of some hardware clock. https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-time-field 0 1 NXlog/value Array of logged value, such as temperature. If this is a single value the dimensionality is nEntries. However, NXlog can also be used to store multi dimensional time stamped data such as images. In this example the dimensionality of values would be value[nEntries,xdim,ydim]. https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-value-field 0 1 NXlog/raw_value Array of raw information, such as thermocouple voltage https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-raw-value-field 0 1 NXlog/description Description of logged value https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-description-field 0 1 NXlog/average_value https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-average-value-field 0 1 NXlog/average_value_error estimated uncertainty (often used: standard deviation) of average_value https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-average-value-error-field true 0 1 NXlog/average_value_errors estimated uncertainty (often used: standard deviation) of average_value https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-average-value-errors-field 0 1 NXlog/minimum_value https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-minimum-value-field 0 1 NXlog/maximum_value https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-maximum-value-field 0 1 NXlog/duration Total time log was taken https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-duration-field 0 1 0 0 NXlog/cue_timestamp_zero Timestamps matching the corresponding cue_index into the time, value pair. https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-cue-timestamp-zero-field 0 1 NXlog/cue_index Index into the time, value pair matching the corresponding cue_timestamp_zero. https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-cue-index-field 0 1 NXenvironment/name Apparatus identification code/model number; e.g. OC100 011 https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-name-field 0 1 NXenvironment/short_name Alternative short name, perhaps for dashboard display like a present Seblock name https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-short-name-field 0 1 NXenvironment/type Type of apparatus. This could be the SE codes in scheduling database; e.g. OC/100 https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-type-field 0 1 NXenvironment/description Description of the apparatus; e.g. 100mm bore orange cryostat with Roots pump https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-description-field 0 1 NXenvironment/program Program controlling the apparatus; e.g. LabView VI name https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-program-field 0 1 NXenvironment/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. https://manual.nexusformat.org/classes/base_classes/NXenvironment.html#nxenvironment-depends-on-field 0 1 NXtranslation/distances (x,y,z) This field describes the lateral movement of a component. The pair of groups NXtranslation and NXorientation together describe the position of a component. For absolute position, the origin is the scattering center (where a perfectly aligned sample would be) with the z-axis pointing downstream and the y-axis pointing gravitationally up. For a relative position the NXtranslation is taken into account before the NXorientation. The axes are right-handed and orthonormal. https://manual.nexusformat.org/classes/base_classes/NXtranslation.html#nxtranslation-distances-field 0 1 NXreflections/experiments The experiments from which the reflection data derives https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-experiments-field 0 1 0 NXreflections/h The h component of the miller index https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-h-field 0 1 0 NXreflections/k The k component of the miller index https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-k-field 0 1 0 NXreflections/l The l component of the miller index https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-l-field 0 1 0 NXreflections/id The id of the experiment which resulted in the reflection. If the value is greater than 0, the experiments must link to a multi-experiment NXmx group https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-id-field 0 1 0 NXreflections/reflection_id The id of the reflection. Multiple partials from the same reflection should all have the same id https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-reflection-id-field 0 1 0 NXreflections/entering Is the reflection entering or exiting the Ewald sphere https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-entering-field 0 1 0 NXreflections/det_module The detector module on which the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-det-module-field 0 1 0 NXreflections/flags Status flags describing the reflection. This is a bit mask. The bits in the mask follow the convention used by DIALS, and have the following names: === ========================================== bit name === ========================================== 0 ``predicted`` 1 ``observed`` 2 ``indexed`` 3 ``used_in_refinement`` 4 ``strong`` 5 ``reference_spot`` 6 ``dont_integrate`` 7 ``integrated_sum`` 8 ``integrated_prf`` 9 ``integrated`` 10 ``overloaded`` 11 ``overlapped`` 12 ``overlapped_fg`` 13 ``in_powder_ring`` 14 ``foreground_includes_bad_pixels`` 15 ``background_includes_bad_pixels`` 16 ``includes_bad_pixels`` 17 ``bad_shoebox`` 18 ``bad_spot`` 19 ``used_in_modelling`` 20 ``centroid_outlier`` 21 ``failed_during_background_modelling`` 22 ``failed_during_summation`` 23 ``failed_during_profile_fitting`` 24 ``bad_reference`` === ========================================== https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-flags-field 0 1 0 NXreflections/d The resolution of the reflection https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-d-field 0 1 0 NXreflections/partiality The partiality of the reflection. Dividing by this number will inflate the measured intensity to the full reflection equivalent. https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-partiality-field 0 1 0 NXreflections/predicted_frame The frame on which the bragg peak of the reflection is predicted https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-frame-field 0 1 0 NXreflections/predicted_x The x position at which the bragg peak of the reflection is predicted https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-x-field 0 1 0 NXreflections/predicted_y The y position at which the bragg peak of the reflection is predicted https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-y-field 0 1 0 NXreflections/predicted_phi The phi angle at which the bragg peak of the reflection is predicted https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-phi-field 0 1 0 NXreflections/predicted_px_x The x pixel position at which the bragg peak of the reflection is predicted https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-px-x-field 0 1 0 NXreflections/predicted_px_y The y pixel position at which the bragg peak of the reflection is predicted https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-px-y-field 0 1 0 NXreflections/observed_frame The estimate of the frame at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-frame-field 0 1 0 NXreflections/observed_frame_var The variance on the estimate of the frame at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-frame-var-field 0 1 0 NXreflections/observed_frame_errors The standard deviation of the estimate of the frame at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-frame-errors-field 0 1 0 NXreflections/observed_px_x The estimate of the pixel x position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-x-field 0 1 0 NXreflections/observed_px_x_var The variance on the estimate of the pixel x position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-x-var-field 0 1 0 NXreflections/observed_px_x_errors The standard deviation of the estimate of the pixel x position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-x-errors-field 0 1 0 NXreflections/observed_px_y The estimate of the pixel y position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-y-field 0 1 0 NXreflections/observed_px_y_var The variance on the estimate of the pixel y position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-y-var-field 0 1 0 NXreflections/observed_px_y_errors The standard deviation of the estimate of the pixel y position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-y-errors-field 0 1 0 NXreflections/observed_phi The estimate of the phi angle at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-phi-field 0 1 0 NXreflections/observed_phi_var The variance on the estimate of the phi angle at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-phi-var-field 0 1 0 NXreflections/observed_phi_errors The standard deviation of the estimate of the phi angle at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-phi-errors-field 0 1 0 NXreflections/observed_x The estimate of the x position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-x-field 0 1 0 NXreflections/observed_x_var The variance on the estimate of the x position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-x-var-field 0 1 0 NXreflections/observed_x_errors The standard deviation of the estimate of the x position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-x-errors-field 0 1 0 NXreflections/observed_y The estimate of the y position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-y-field 0 1 0 NXreflections/observed_y_var The variance on the estimate of the y position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-y-var-field 0 1 0 NXreflections/observed_y_errors The standard deviation of the estimate of the y position at which the central impact of the reflection was recorded https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-y-errors-field 0 1 0 NXreflections/bounding_box The bounding box around the recorded recorded reflection. Should be an integer array of length 6, where the 6 values are pixel positions or frame numbers, as follows: ===== =========================== index meaning ===== =========================== 0 The lower pixel x position 1 The upper pixel x position 2 The lower pixel y position 3 The upper pixel y position 4 The lower frame number 5 The upper frame number ===== =========================== https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-bounding-box-field 0 1 0 NXreflections/background_mean The mean background under the reflection peak https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-background-mean-field 0 1 0 NXreflections/int_prf The estimate of the reflection intensity by profile fitting https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-prf-field 0 1 0 NXreflections/int_prf_var https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-prf-var-field 0 1 0 NXreflections/int_prf_errors The standard deviation of the estimate of the reflection intensity by profile fitting https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-prf-errors-field 0 1 0 NXreflections/int_sum The estimate of the reflection intensity by summation https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-sum-field 0 1 0 NXreflections/int_sum_var The variance on the estimate of the reflection intensity by summation https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-sum-var-field 0 1 0 NXreflections/int_sum_errors The standard deviation of the estimate of the reflection intensity by summation https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-sum-errors-field 0 1 0 NXreflections/lp The LP correction factor to be applied to the reflection intensities https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-lp-field 0 1 0 NXreflections/prf_cc The correlation of the reflection profile with the reference profile used in profile fitting https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-prf-cc-field 0 1 0 NXreflections/overlaps An adjacency list specifying the spatial overlaps of reflections. The adjacency list is specified using an array data type where the elements of the array are the indices of the adjacent overlapped reflection https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-overlaps-field 0 1 0 NXreflections/polar_angle Polar angle of reflection centroid, following the NeXus simple (spherical polar) coordinate system https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-polar-angle-field 0 1 NXreflections/azimuthal_angle Azimuthal angle of reflection centroid, following the NeXus simple (spherical polar) coordinate system https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-azimuthal-angle-field 0 1 NXgeometry/description Optional description/label. Probably only present if we are an additional reference point for components rather than the location of a real component. https://manual.nexusformat.org/classes/base_classes/NXgeometry.html#nxgeometry-description-field 0 1 NXgeometry/component_index Position of the component along the beam path. The sample is at 0, components upstream have negative component_index, components downstream have positive component_index. https://manual.nexusformat.org/classes/base_classes/NXgeometry.html#nxgeometry-component-index-field 0 1 NXgrating/angles Blaze or trapezoidal angles, with the angle of the upstream facing edge listed first. Blazed gratings can be identified by the low value of the first-listed angle. https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-angles-field 0 1 NXgrating/period List of polynomial coefficients describing the spatial separation of lines/grooves as a function of position along the grating, in increasing powers of position. Gratings which do not have variable line spacing will only have a single coefficient (constant). https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-period-field 0 1 NXgrating/duty_cycle https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-duty-cycle-field 0 1 NXgrating/depth https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-depth-field 0 1 NXgrating/diffraction_order https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-diffraction-order-field 0 1 NXgrating/deflection_angle Angle between the incident beam and the utilised outgoing beam. https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-deflection-angle-field vacuum helium argon NXgrating/interior_atmosphere https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-interior-atmosphere-field 0 1 NXgrating/substrate_material https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-substrate-material-field 0 1 NXgrating/substrate_density https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-substrate-density-field 0 1 NXgrating/substrate_thickness https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-substrate-thickness-field 0 1 NXgrating/coating_material https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-coating-material-field 0 1 NXgrating/substrate_roughness https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-substrate-roughness-field 0 1 NXgrating/coating_roughness https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-coating-roughness-field 0 1 NXgrating/layer_thickness An array describing the thickness of each layer https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-layer-thickness-field 0 1 NXgrating/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. .. todo:: Add a definition for the reference point of a bending grating. https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-depends-on-field 0 1 NXoff_geometry/vertices List of x,y,z coordinates for vertices. The origin of the coordinates is the position of the parent component, for example the NXdetector which the geometry describes. If the shape describes a single pixel for a detector with uniform pixel shape then the origin is the position of each pixel as described by the ``x/y/z_pixel_offset`` datasets in ``NXdetector``. https://manual.nexusformat.org/classes/base_classes/NXoff_geometry.html#nxoff-geometry-vertices-field 0 1 NXoff_geometry/winding_order List of indices of vertices in the ``vertices`` dataset to form each face, right-hand rule for face normal. https://manual.nexusformat.org/classes/base_classes/NXoff_geometry.html#nxoff-geometry-winding-order-field 0 1 NXoff_geometry/faces The start index in ``winding_order`` for each face. https://manual.nexusformat.org/classes/base_classes/NXoff_geometry.html#nxoff-geometry-faces-field 0 1 NXoff_geometry/detector_faces List of pairs of index in the "faces" dataset and detector id. Face IDs in the first column, and corresponding detector IDs in the second column. This dataset should only be used only if the ``NXoff_geometry`` group is describing a detector. Note, the face indices must be in ascending order but need not be consecutive as not every face in faces need be a detecting surface or boundary of detecting volume. Can use multiple entries with the same detector id to define detector volumes. https://manual.nexusformat.org/classes/base_classes/NXoff_geometry.html#nxoff-geometry-detector-faces-field 0 1 NXbeam/distance Distance from sample. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-distance-field 0 1 NXbeam/incident_energy Energy carried by each particle of the beam on entering the beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-energy-field 0 1 NXbeam/final_energy Energy carried by each particle of the beam on leaving the beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-final-energy-field 0 1 NXbeam/energy_transfer Change in particle energy caused by the beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-energy-transfer-field 0 1 NXbeam/incident_wavelength In the case of a monochromatic beam this is the scalar wavelength. Several other use cases are permitted, depending on the presence or absence of other incident_wavelength_X fields. In the case of a polychromatic beam this is an array of length **m** of wavelengths, with the relative weights in ``incident_wavelength_weights``. In the case of a monochromatic beam that varies shot- to-shot, this is an array of wavelengths, one for each recorded shot. Here, ``incident_wavelength_weights`` and incident_wavelength_spread are not set. In the case of a polychromatic beam that varies shot-to- shot, this is an array of length **m** with the relative weights in ``incident_wavelength_weights`` as a 2D array. In the case of a polychromatic beam that varies shot-to- shot and where the channels also vary, this is a 2D array of dimensions **nP** by **m** (slow to fast) with the relative weights in ``incident_wavelength_weights`` as a 2D array. Note, :ref:`variants <Design-Variants>` are a good way to represent several of these use cases in a single dataset, e.g. if a calibrated, single-value wavelength value is available along with the original spectrum from which it was calibrated. Wavelength on entering beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-wavelength-field 0 1 NXbeam/incident_wavelength_weights In the case of a polychromatic beam this is an array of length **m** of the relative weights of the corresponding wavelengths in ``incident_wavelength``. In the case of a polychromatic beam that varies shot-to- shot, this is a 2D array of dimensions **nP** by **m** (slow to fast) of the relative weights of the corresponding wavelengths in ``incident_wavelength``. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-wavelength-weights-field 0 1 NXbeam/incident_wavelength_spread The wavelength spread FWHM for the corresponding wavelength(s) in incident_wavelength. In the case of shot-to-shot variation in the wavelength spread, this is a 2D array of dimension **nP** by **m** (slow to fast) of the spreads of the corresponding wavelengths in incident_wavelength. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-wavelength-spread-field 0 1 NXbeam/incident_beam_divergence Beam crossfire in degrees parallel to the laboratory X axis The dimension **c** is a series of moments of that represent the standard uncertainty (e.s.d.) of the directions of of the beam. The first and second moments are in the XZ and YZ planes around the mean source beam direction, respectively. Further moments in **c** characterize co-variance terms, so the next moment is the product of the first two, and so on. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-beam-divergence-field 0 1 NXbeam/extent Size of the beam entering this component. Note this represents a rectangular beam aperture, and values represent FWHM https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-extent-field 0 1 NXbeam/final_wavelength Wavelength on leaving beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-final-wavelength-field 0 1 NXbeam/incident_polarization Polarization vector on entering beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-polarization-field 0 1 NXbeam/final_polarization Polarization vector on leaving beamline component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-final-polarization-field 0 1 NXbeam/incident_polarization_stokes Polarization vector on entering beamline component using Stokes notation The Stokes parameters are four components labelled I,Q,U,V or S_0,S_1,S_2,S_3. These are defined with the standard Nexus coordinate frame unless it is overridden by an NXtransformations field pointed to by a depends_on attribute. The last component, describing the circular polarization state, is positive for a right-hand circular state - that is the electric field vector rotates clockwise at the sample and over time when observed from the source. I (S_0) is the beam intensity (often normalized to 1). Q, U, and V scale linearly with the total degree of polarization, and indicate the relative magnitudes of the pure linear and circular orientation contributions. Q (S_1) is linearly polarized along the x axis (Q > 0) or y axis (Q < 0). U (S_2) is linearly polarized along the x==y axis (U > 0) or the -x==y axis (U < 0). V (S_3) is circularly polarized. V > 0 when the electric field vector rotates clockwise at the sample with respect to time when observed from the source; V < 0 indicates the opposite rotation. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-incident-polarization-stokes-field 0 1 NXbeam/final_polarization_stokes Polarization vector on leaving beamline component using Stokes notation (see incident_polarization_stokes). https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-final-polarization-stokes-field 0 1 NXbeam/final_wavelength_spread Wavelength spread FWHM of beam leaving this component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-final-wavelength-spread-field 0 1 NXbeam/final_beam_divergence Divergence FWHM of beam leaving this component https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-final-beam-divergence-field 0 1 NXbeam/flux flux incident on beam plane area https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-flux-field 0 1 NXbeam/depends_on The NeXus coordinate system defines the Z axis to be along the nominal beam direction. This is the same as the McStas coordinate system (see :ref:`Design-CoordinateSystem`). However, the additional transformations needed to represent an altered beam direction can be provided using this depends_on field that contains the path to a NXtransformations group. This could represent redirection of the beam, or a refined beam direction. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-depends-on-field 0 1 0 0 0 0 NXbeam/TRANSFORMATIONS/DIRECTION Direction of beam vector, its value is ignored. If missing, then the beam direction is defined as [0,0,1] and passes through the origin https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-direction-field 0 1 0 0 0 0 NXbeam/TRANSFORMATIONS/reference_plane Direction of normal to reference plane used to measure azimuth relative to the beam, its value is ignored. This also defines the parallel and perpendicular components of the beam's polarization. If missing, then the reference plane normal is defined as [0,1,0] and passes through the origin https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-reference-plane-field 0 1 NXaperture/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference point of the aperture is its center in the x and y axis. The reference point on the z axis is the surface of the aperture pointing towards the source. In complex (asymmetic) geometries an NXoff_geometry group can be used to provide an unambiguous reference. .. image:: aperture/aperture.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-depends-on-field 0 1 NXaperture/material Absorbing material of the aperture https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-material-field 0 1 NXaperture/description Description of aperture https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-description-field 0 1 NXmoderator/distance Effective distance as seen by measuring radiation. Note, it is recommended to use NXtransformations instead. https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-distance-field H20 D20 Liquid H2 Liquid CH4 Liquid D2 Solid D2 C Solid CH4 Solid H2 NXmoderator/type https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-type-field 0 1 NXmoderator/poison_depth https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-poison-depth-field 0 1 NXmoderator/coupled whether the moderator is coupled https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-coupled-field 0 1 NXmoderator/coupling_material The material used for coupling. Usually Cd. https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-coupling-material-field Gd Cd NXmoderator/poison_material https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-poison-material-field 0 1 NXmoderator/temperature average/nominal moderator temperature https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-temperature-field 0 1 NXmoderator/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The reference point of the moderator is its center in the x and y axis. The reference point on the z axis is the surface of the moderator pointing towards the source (the negative part of the z axis). .. image:: moderator/moderator.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-depends-on-field 0 1 NXevent_data/event_time_offset A list of timestamps for each event as it comes in. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-event-time-offset-field 0 1 NXevent_data/event_id There will be extra information in the NXdetector to convert event_id to detector_number. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-event-id-field 0 1 0 NXevent_data/event_time_zero The time that each pulse started with respect to the offset https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-event-time-zero-field 0 1 NXevent_data/event_index The index into the event_time_offset, event_id pair for the pulse occurring at the matching entry in event_time_zero. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-event-index-field 0 1 NXevent_data/pulse_height If voltages from the ends of the detector are read out this is where they go. This list is for all events with information to attach to a particular pulse height. The information to attach to a particular pulse is located in events_per_pulse. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-pulse-height-field 0 1 0 NXevent_data/cue_timestamp_zero Timestamps matching the corresponding cue_index into the event_id, event_time_offset pair. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-cue-timestamp-zero-field 0 1 NXevent_data/cue_index Index into the event_id, event_time_offset pair matching the corresponding cue_timestamp. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-cue-index-field 0 1 NXorientation/value The orientation information is stored as direction cosines. The direction cosines will be between the local coordinate directions and the reference directions (to origin or relative NXgeometry). Calling the local unit vectors (x',y',z') and the reference unit vectors (x,y,z) the six numbers will be [x' dot x, x' dot y, x' dot z, y' dot x, y' dot y, y' dot z] where "dot" is the scalar dot product (cosine of the angle between the unit vectors). The unit vectors in both the local and reference coordinates are right-handed and orthonormal. The pair of groups NXtranslation and NXorientation together describe the position of a component. https://manual.nexusformat.org/classes/base_classes/NXorientation.html#nxorientation-value-field 0 1 NXuser/name Name of user responsible for this entry https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-name-field 0 1 NXuser/role Role of user responsible for this entry. Suggested roles are "local_contact", "principal_investigator", and "proposer" https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-role-field 0 1 NXuser/affiliation Affiliation of user https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-affiliation-field 0 1 NXuser/address Address of user https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-address-field 0 1 NXuser/telephone_number Telephone number of user https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-telephone-number-field 0 1 NXuser/fax_number Fax number of user https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-fax-number-field 0 1 NXuser/email Email of user https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-email-field 0 1 NXuser/facility_user_id facility based unique identifier for this person e.g. their identification code on the facility address/contact database https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-facility-user-id-field 0 1 NXuser/ORCID an author code, Open Researcher and Contributor ID, defined by https://orcid.org and expressed as a URI https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-orcid-field 0 1 NXguide/description A description of this particular instance of ``NXguide``. https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-description-field 0 1 NXguide/incident_angle TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-incident-angle-field 0 1 NXguide/reflectivity/data reflectivity of each surface as a function of wavelength https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-data-field 0 1 NXguide/reflectivity/surface List of surfaces. Probably best to use index numbers but the specification is very loose. https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-surface-field 0 1 NXguide/reflectivity/wavelength wavelengths at which reflectivity was measured https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-wavelength-field 0 1 NXguide/bend_angle_x TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-bend-angle-x-field 0 1 NXguide/bend_angle_y TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-bend-angle-y-field vacuum helium argon NXguide/interior_atmosphere https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-interior-atmosphere-field 0 1 NXguide/external_material external material outside substrate https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-external-material-field 0 1 NXguide/m_value The ``m`` value for a supermirror, which defines the supermirror regime in multiples of the critical angle of Nickel. https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-m-value-field 0 1 NXguide/substrate_material TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-substrate-material-field 0 1 NXguide/substrate_thickness TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-substrate-thickness-field 0 1 NXguide/coating_material TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-coating-material-field 0 1 NXguide/substrate_roughness TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-substrate-roughness-field 0 1 NXguide/coating_roughness TODO: documentation needed https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-coating-roughness-field 0 1 NXguide/number_sections number of substrate sections (also called ``nsurf`` as an index in the ``NXguide`` specification) https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-number-sections-field 0 1 NXguide/depends_on NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string "." if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere. The entry opening of the guide lies on the reference plane. The center of the opening on that plane is the reference point on the x and y axis. The reference plane is orthogonal to the z axis and is the reference point along the z axis. Given no bend in the guide, it is parallel with z axis and extends in the positive direction of the z axis. .. image:: guide/guide.png :width: 40% https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-depends-on-field 0 1 NXtomophase/entry/title https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-title-field 0 1 NXtomophase/entry/start_time https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-start-time-field 0 1 NXtomophase/entry/end_time https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-end-time-field NXtomophase NXtomophase/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-definition-field 0 1 NXtomophase/entry/instrument/SOURCE/type https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-source-type-field 0 1 NXtomophase/entry/instrument/SOURCE/name https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-source-name-field neutron x-ray electron NXtomophase/entry/instrument/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-source-probe-field 0 1 NXtomophase/entry/instrument/bright_field/data https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-bright-field-data-field 0 1 NXtomophase/entry/instrument/bright_field/sequence_number https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-bright-field-sequence-number-field 0 1 NXtomophase/entry/instrument/dark_field/data https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-dark-field-data-field 0 1 NXtomophase/entry/instrument/dark_field/sequence_number https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-dark-field-sequence-number-field 0 1 NXtomophase/entry/instrument/sample/data https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-sample-data-field 0 1 NXtomophase/entry/instrument/sample/sequence_number https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-sample-sequence-number-field 0 1 NXtomophase/entry/instrument/sample/x_pixel_size https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-sample-x-pixel-size-field 0 1 NXtomophase/entry/instrument/sample/y_pixel_size https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-sample-y-pixel-size-field 0 1 NXtomophase/entry/instrument/sample/distance Distance between detector and sample https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-instrument-sample-distance-field 0 1 NXtomophase/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-sample-name-field 0 1 NXtomophase/entry/sample/rotation_angle https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-sample-rotation-angle-field 0 1 NXtomophase/entry/sample/x_translation https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-sample-x-translation-field 0 1 NXtomophase/entry/sample/y_translation https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-sample-y-translation-field 0 1 NXtomophase/entry/sample/z_translation https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-sample-z-translation-field 0 1 NXtomophase/entry/control/integral Total integral monitor counts for each measured frame. Allows a correction for fluctuations in the beam between frames. https://manual.nexusformat.org/classes/applications/NXtomophase.html#nxtomophase-entry-control-integral-field 0 1 NXstxm/ENTRY/title https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-title-field 0 1 NXstxm/ENTRY/start_time https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-start-time-field 0 1 NXstxm/ENTRY/end_time https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-end-time-field NXstxm NXstxm/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-definition-field 0 1 NXstxm/ENTRY/INSTRUMENT/SOURCE/type https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-source-type-field 0 1 NXstxm/ENTRY/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-source-name-field 0 1 NXstxm/ENTRY/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-source-probe-field 0 1 NXstxm/ENTRY/INSTRUMENT/monochromator/energy https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-monochromator-energy-field 0 1 NXstxm/ENTRY/INSTRUMENT/DETECTOR/data https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-detector-data-field 0 1 NXstxm/ENTRY/INSTRUMENT/sample_x/data https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-sample-x-data-field 0 1 NXstxm/ENTRY/INSTRUMENT/sample_y/data https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-sample-y-data-field 0 1 NXstxm/ENTRY/INSTRUMENT/sample_z/data https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-instrument-sample-z-data-field 0 1 NXstxm/ENTRY/SAMPLE/rotation_angle https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-sample-rotation-angle-field sample point spectrum sample line spectrum sample image sample image stack sample focus osa image osa focus detector image generic scan NXstxm/ENTRY/DATA/stxm_scan_type Label for typical scan types as a convenience for humans. Each label corresponds to a specific set of axes being scanned to produce a data array of shape: * sample point spectrum: (photon_energy,) * sample line spectrum: (photon_energy, sample_y/sample_x) * sample image: (sample_y, sample_x) * sample image stack: (photon_energy, sample_y, sample_x) * sample focus: (zoneplate_z, sample_y/sample_x) * osa image: (osa_y, osa_x) * osa focus: (zoneplate_z, osa_y/osa_x) * detector image: (detector_y, detector_x) The "generic scan" string is to be used when none of the other choices are appropriate. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-data-stxm-scan-type-field 0 1 NXstxm/ENTRY/DATA/data Detectors that provide more than one value per scan point should be summarised to a single value per scan point for this array in order to simplify plotting. Note that 'Line scans' and focus type scans measure along one spatial dimension but are not restricted to being parallel to the X or Y axes. Such scans should therefore use a single dimension for the positions along the spatial line. The 'sample_x' and 'sample_y' fields should then contain lists of the x- and y-positions and should both have the 'axis' attribute pointing to the same dimension. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-data-data-field 0 1 NXstxm/ENTRY/DATA/energy List of photon energies of the X-ray beam. If scanned through multiple values, then an 'axis' attribute will be required to link the field to the appropriate data array dimension. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-data-energy-field 0 1 NXstxm/ENTRY/DATA/sample_y List of Y positions on the sample. If scanned through multiple values, then an 'axis' attribute will be required to link the field to the appropriate data array dimension. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-data-sample-y-field 0 1 NXstxm/ENTRY/DATA/sample_x List of X positions on the sample. If scanned through multiple values, then an 'axis' attribute will be required to link the field to the appropriate data array dimension. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-data-sample-x-field 0 1 NXstxm/ENTRY/control/data Values to use to normalise for time-variations in photon flux. Typically, the synchrotron storage ring electron beam current is used as a proxy for the X-ray beam intensity. Array must have same shape as the NXdata groups. https://manual.nexusformat.org/classes/applications/NXstxm.html#nxstxm-entry-control-data-field NXxkappa NXxkappa/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-definition-field 0 1 NXxkappa/entry/instrument/detector/polar_angle The polar_angle (two theta) at each scan point https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-instrument-detector-polar-angle-field 0 1 NXxkappa/entry/sample/rotation_angle This is an array holding the sample rotation angle at each scan point https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-sample-rotation-angle-field 0 1 NXxkappa/entry/sample/kappa This is an array holding the kappa angle at each scan point https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-sample-kappa-field 0 1 NXxkappa/entry/sample/phi This is an array holding the phi angle at each scan point https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-sample-phi-field 0 1 NXxkappa/entry/sample/alpha This holds the inclination angle of the kappa arm. https://manual.nexusformat.org/classes/applications/NXxkappa.html#nxxkappa-entry-sample-alpha-field 0 1 NXfluo/entry/title https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-title-field 0 1 NXfluo/entry/start_time https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-start-time-field NXfluo NXfluo/entry/definition Official NeXus NXDL schema to which this file conforms. https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-definition-field 0 1 NXfluo/entry/INSTRUMENT/SOURCE/type https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-source-type-field 0 1 NXfluo/entry/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-source-name-field x-ray NXfluo/entry/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-source-probe-field 0 1 NXfluo/entry/INSTRUMENT/monochromator/wavelength https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-monochromator-wavelength-field 0 1 NXfluo/entry/INSTRUMENT/fluorescence/data https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-fluorescence-data-field 0 1 NXfluo/entry/INSTRUMENT/fluorescence/energy https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-instrument-fluorescence-energy-field 0 1 NXfluo/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-sample-name-field monitor timer NXfluo/entry/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-monitor-mode-field 0 1 NXfluo/entry/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-monitor-preset-field 0 1 NXfluo/entry/MONITOR/data https://manual.nexusformat.org/classes/applications/NXfluo.html#nxfluo-entry-monitor-data-field NXxlaue NXxlaue/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-definition-field 0 1 NXxlaue/entry/instrument/source/distribution/data expect ``signal=1 axes="energy"`` https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-instrument-source-distribution-data-field 0 1 NXxlaue/entry/instrument/source/distribution/wavelength https://manual.nexusformat.org/classes/applications/NXxlaue.html#nxxlaue-entry-instrument-source-distribution-wavelength-field NXxnb NXxnb/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-definition-field 0 1 NXxnb/entry/instrument/detector/polar_angle The polar_angle (gamma) of the detector for each scan point. https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-instrument-detector-polar-angle-field 0 1 NXxnb/entry/instrument/detector/tilt_angle The angle by which the detector has been tilted out of the scattering plane. https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-instrument-detector-tilt-angle-field 0 1 NXxnb/entry/sample/rotation_angle This is an array holding the sample rotation angle at each scan point https://manual.nexusformat.org/classes/applications/NXxnb.html#nxxnb-entry-sample-rotation-angle-field 0 1 NXtofnpd/entry/title https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-title-field 0 1 NXtofnpd/entry/start_time https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-start-time-field NXtofnpd NXtofnpd/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-definition-field 0 1 NXtofnpd/entry/pre_sample_flightpath This is the flight path before the sample position. This can be determined by a chopper, by the moderator or the source itself. In other words: it the distance to the component which gives the T0 signal to the detector electronics. If another component in the NXinstrument hierarchy provides this information, this should be a link. https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-pre-sample-flightpath-field 0 1 NXtofnpd/entry/user/name https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-user-name-field 0 1 NXtofnpd/entry/INSTRUMENT/detector/data https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-data-field 0 1 NXtofnpd/entry/INSTRUMENT/detector/detector_number https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-detector-number-field 0 1 NXtofnpd/entry/INSTRUMENT/detector/distance distance to sample for each detector https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-distance-field 0 1 NXtofnpd/entry/INSTRUMENT/detector/time_of_flight https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-time-of-flight-field 0 1 NXtofnpd/entry/INSTRUMENT/detector/polar_angle polar angle for each detector element https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-polar-angle-field 0 1 NXtofnpd/entry/INSTRUMENT/detector/azimuthal_angle azimuthal angle for each detector element https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-instrument-detector-azimuthal-angle-field 0 1 NXtofnpd/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-sample-name-field monitor timer NXtofnpd/entry/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-monitor-mode-field 0 1 NXtofnpd/entry/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-monitor-preset-field 0 1 NXtofnpd/entry/MONITOR/distance https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-monitor-distance-field 0 1 NXtofnpd/entry/MONITOR/data https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-monitor-data-field 0 1 NXtofnpd/entry/MONITOR/time_of_flight https://manual.nexusformat.org/classes/applications/NXtofnpd.html#nxtofnpd-entry-monitor-time-of-flight-field NXcanSAS NXcanSAS/ENTRY/definition Official NeXus NXDL schema to which this subentry conforms. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-definition-field 0 1 1 0 0 0 NXcanSAS/ENTRY/DATA/Q .. index:: NXcanSAS (applications); Q Array of :math:`Q` data to accompany :math:`I`. .. figure:: canSAS/Q-geometry.jpg :width: 60% The :math:`\vec{Q}` geometry. (:download:`full image <canSAS/Q-geometry.jpg>`) :math:`Q` may be represented as either the three-dimensional scattering vector :math:`\vec{Q}` or the magnitude of the scattering vector, :math:`|\vec{Q}|`. .. math:: |\vec{Q}| = (4\pi/\lambda) sin(\theta) When we write :math:`Q`, we may refer to either or both of :math:`|\vec{Q}|` or :math:`\vec{Q}`, depending on the context. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-q-field 0 1 1 0 0 NXcanSAS/ENTRY/DATA/I .. index:: NXcanSAS (applications); I Array of intensity (:math:`I`) data. The intensity may be represented in one of these forms: **absolute units**: :math:`d\Sigma/d\Omega(Q)` differential cross-section per unit volume per unit solid angle (such as: 1/cm/sr or 1/m/sr) **absolute units**: :math:`d\sigma/d\Omega(Q)` differential cross-section per unit atom per unit solid angle (such as: cm^2 or m^2) **arbitrary units**: :math:`I(Q)` usually a ratio of two detectors but units are meaningless (such as: a.u. or counts) This presents a few problems for analysis software to sort out when reading the data. Fortunately, it is possible to analyze the *units* to determine which type of intensity is being reported and make choices at the time the file is read. But this is an area for consideration and possible improvement. One problem arises with software that automatically converts data into some canonical units used by that software. The software should not convert units between these different types of intensity indiscriminately. A second problem is that when arbitrary units are used, then the set of possible analytical results is restricted. With such units, no meaningful volume fraction or number density can be determined directly from :math:`I(Q)`. In some cases, it is possible to apply a factor to convert the arbitrary units to an absolute scale. This should be considered as a possibility of the analysis process. Where this documentation says *typical units*, it is possible that small-angle data may be presented in other units and still be consistent with NeXus. See the :ref:`design-units` section. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-i-field 0 1 1 NXcanSAS/ENTRY/DATA/Idev .. index:: NXcanSAS (applications); Idev Estimated **uncertainty** (usually standard deviation) in :math:`I`. Must have the same units as :math:`I`. When present, the name of this field is also recorded in the *uncertainties* attribute of *I*, as in:: I/@uncertainties="Idev" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-idev-field 0 1 1 NXcanSAS/ENTRY/DATA/Qdev .. index:: NXcanSAS (applications); Qdev Estimated :math:`Q` **resolution** (usually standard deviation). Must have the same units as :math:`Q`. When present, the name of this field is also recorded in the *resolutions* attribute of *Q*, as in:: Q/@resolutions="Qdev" or:: Q/@resolutions="dQw", "dQl" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-qdev-field 0 1 1 NXcanSAS/ENTRY/DATA/dQw .. index:: NXcanSAS (applications); dQw :math:`Q` **resolution** along the axis of scanning (the high-resolution *slit width* direction). Useful for defining resolution data from slit-smearing instruments such as Bonse-Hart geometry. Must have the same units as :math:`Q`. When present, the name of this field is also recorded in the *resolutions* attribute of *Q*, as in:: Q/@resolutions="dQw", "dQl" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-dqw-field 0 1 1 NXcanSAS/ENTRY/DATA/dQl .. index:: NXcanSAS (applications); dQl :math:`Q` **resolution** perpendicular to the axis of scanning (the low-resolution *slit length* direction). Useful for defining resolution data from slit-smearing instruments such as Bonse-Hart geometry. Must have the same units as :math:`Q`. When present, the name of this field is also recorded in the *resolutions* attribute of *Q*, as in:: Q/@resolutions="dQw", "dQl" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-dql-field 0 1 1 NXcanSAS/ENTRY/DATA/Qmean Mean value of :math:`Q` for this data point. Useful when describing data that has been binned from higher-resolution data. It is expected that ``Q`` is provided and that both ``Q`` and ``Qmean`` will have the same units. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-qmean-field 0 1 NXcanSAS/ENTRY/DATA/ShadowFactor A numerical factor applied to pixels affected by the beam stop penumbra. Used in data files from NIST/NCNR instruments. See: J.G. Barker and J.S. Pedersen (1995) *J. Appl. Cryst.* **28**, 105-114. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-shadowfactor-field 0 1 NXcanSAS/ENTRY/title Title of this *SASentry*. Make it so that you can recognize the data by its title. Could be the name of the sample, the name for the measured data, or something else representative. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-title-field 0 1 0 NXcanSAS/ENTRY/run Run identification for this *SASentry*. For many facilities, this is an integer, such as en experiment number. Use multiple instances of ``run`` as needed, keeping in mind that HDF5 requires unique names for all entities in a group. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-run-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/APERTURE/shape describe the type of aperture (pinhole, 4-blade slit, Soller slit, ...) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-aperture-shape-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/APERTURE/x_gap opening along the :math:`x` axis https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-aperture-x-gap-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/APERTURE/y_gap opening along the :math:`y` axis https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-aperture-y-gap-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/COLLIMATOR/length Amount/length of collimation inserted (as on a SANS instrument) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-collimator-length-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/COLLIMATOR/distance Distance from this collimation element to the sample https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-collimator-distance-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/name Identifies the name of this detector https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-name-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/SDD Distance between sample and detector. Note: In NXdetector, the ``distance`` field records the distance to the previous component ... most often the sample. This use is the same as ``SDD`` for most SAS instruments but not all. For example, Bonse-Hart cameras have one or more crystals between the sample and detector. We define here the field ``SDD`` to document without ambiguity the distance between sample and detector. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-sdd-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/slit_length Slit length of the instrument for this detector, expressed in the same units as :math:`Q`. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-slit-length-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/x_position Location of the detector in :math:`x` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-x-position-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/y_position Location of the detector in :math:`y` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-y-position-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/roll Rotation of the detector about the :math:`z` axis (roll) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-roll-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/pitch Rotation of the detector about the :math:`x` axis (roll) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-pitch-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/yaw Rotation of the detector about the :math:`y` axis (yaw) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-yaw-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/beam_center_x Position of the beam center on the detector. This is the x position where the direct beam would hit the detector plane. This is a length and can be outside of the actual detector. The length can be in physical units or pixels as documented by the units attribute. The value can be any real number (positive, zero, or negative). https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-beam-center-x-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/beam_center_y Position of the beam center on the detector. This is the y position where the direct beam would hit the detector plane. This is a length and can be outside of the actual detector. The length can be in physical units or pixels as documented by the units attribute. The value can be any real number (positive, zero, or negative). https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-beam-center-y-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/x_pixel_size Size of each detector pixel. If it is scalar all pixels are the same size https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-x-pixel-size-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/y_pixel_size Size of each detector pixel. If it is scalar all pixels are the same size https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-y-pixel-size-field Spallation Neutron Source Pulsed Reactor Neutron Source Reactor Neutron Source Synchrotron X-ray Source Pulsed Muon Source Rotating Anode X-ray Fixed Tube X-ray UV Laser Free-Electron Laser Optical Laser Ion Source UV Plasma Source neutron x-ray muon electron ultraviolet visible light positron proton NXcanSAS/ENTRY/INSTRUMENT/SOURCE/radiation Name of the radiation used. Note that this is **not** the name of the facility! This field contains a value from either the ``probe`` or ``type`` fields in :ref:`NXsource`. Thus, it is redundant with existing NeXus structure. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-radiation-field true 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/beam_shape Text description of the shape of the beam (incident on the sample). https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-beam-shape-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/incident_wavelength wavelength (:math:`\lambda`) of radiation incident on the sample https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-incident-wavelength-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/wavelength_min Some facilities specify wavelength using a range. This is the lowest wavelength in such a range. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-wavelength-min-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/wavelength_max Some facilities specify wavelength using a range. This is the highest wavelength in such a range. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-wavelength-max-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/incident_wavelength_spread Some facilities specify wavelength using a range. This is the width (FWHM) of such a range. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-incident-wavelength-spread-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/beam_size_x Size of the incident beam along the x axis. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-beam-size-x-field 0 1 NXcanSAS/ENTRY/INSTRUMENT/SOURCE/beam_size_y Size of the incident beam along the y axis. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-beam-size-y-field 0 1 NXcanSAS/ENTRY/SAMPLE/name **ID**: Text string that identifies this sample. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-name-field 0 1 NXcanSAS/ENTRY/SAMPLE/thickness Thickness of this sample https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-thickness-field 0 1 NXcanSAS/ENTRY/SAMPLE/transmission Transmission (:math:`I/I_0`) of this sample. There is no *units* attribute as this number is dimensionless. Note: the ability to store a transmission *spectrum*, instead of a single value, is provided elsewhere in the structure, in the *SAStransmission_spectrum* element. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-transmission-field 0 1 NXcanSAS/ENTRY/SAMPLE/temperature Temperature of this sample. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-temperature-field 0 1 NXcanSAS/ENTRY/SAMPLE/details Any additional sample details. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-details-field 0 1 NXcanSAS/ENTRY/SAMPLE/x_position Location of the sample in :math:`x` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-x-position-field 0 1 NXcanSAS/ENTRY/SAMPLE/y_position Location of the sample in :math:`y` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-y-position-field 0 1 NXcanSAS/ENTRY/SAMPLE/roll Rotation of the sample about the :math:`z` axis (roll) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-roll-field 0 1 NXcanSAS/ENTRY/SAMPLE/pitch Rotation of the sample about the :math:`x` axis (roll) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-pitch-field 0 1 NXcanSAS/ENTRY/SAMPLE/yaw Rotation of the sample about the :math:`y` axis (yaw) https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-yaw-field 0 1 NXcanSAS/ENTRY/PROCESS/name Optional name for this data processing or analysis step https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-name-field 0 1 NXcanSAS/ENTRY/PROCESS/date Optional date for this data processing or analysis step. [#iso8601]_ .. [#iso8601] ISO-8601 standard time representation. NeXus dates and times are reported in ISO-8601 (e.g., ``yyyy-mm-ddThh:mm:ss``) or modified ISO-8601 (e.g., ``yyyy-mm-dd hh:mm:ss``). See: http://www.w3.org/TR/NOTE-datetime or http://en.wikipedia.org/wiki/ISO_8601 for more details. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-date-field 0 1 NXcanSAS/ENTRY/PROCESS/description Optional description for this data processing or analysis step https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-description-field 0 1 NXcanSAS/ENTRY/PROCESS/term Specifies the value of a single variable, parameter, or term (while defined here as a string, it could be a number) related to the *SASprocess* step. Note: The name *term* is not required, it could take any name, as long as the name is unique within this group. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-term-field 0 1 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/lambda Wavelength of the radiation. This array is of the same shape as ``T`` and ``Tdev``. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-lambda-field 0 1 1 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/T Transmission values (:math:`I/I_0`) as a function of wavelength. This array is of the same shape as ``lambda`` and ``Tdev``. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-t-field 0 1 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/Tdev .. index:: NXcanSAS (applications); Tdev Estimated uncertainty (usually standard deviation) in :math:`T`. Must have the same units as :math:`T`. This is the field is named in the *uncertainties* attribute of *T*, as in:: T/@uncertainties="Tdev" This array is of the same shape as ``lambda`` and ``T``. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-tdev-field NXlauetof NXlauetof/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-definition-field 0 1 NXlauetof/entry/instrument/detector/polar_angle The polar_angle (two theta) where the detector is placed. https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-polar-angle-field 0 1 NXlauetof/entry/instrument/detector/azimuthal_angle The azimuthal angle where the detector is placed. https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-azimuthal-angle-field 0 1 1 NXlauetof/entry/instrument/detector/data https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-data-field 0 1 NXlauetof/entry/instrument/detector/x_pixel_size https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-x-pixel-size-field 0 1 NXlauetof/entry/instrument/detector/y_pixel_size https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-y-pixel-size-field 0 1 NXlauetof/entry/instrument/detector/distance https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-distance-field 0 1 NXlauetof/entry/instrument/detector/time_of_flight https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-time-of-flight-field 0 1 NXlauetof/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-sample-name-field 0 1 NXlauetof/entry/sample/orientation_matrix The orientation matrix according to Busing and Levy conventions. This is not strictly necessary as the UB can always be derived from the data. But let us bow to common usage which includes thie UB nearly always. https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-sample-orientation-matrix-field 0 1 NXlauetof/entry/sample/unit_cell The unit cell, a, b, c, alpha, beta, gamma. Again, not strictly necessary, but normally written. https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-sample-unit-cell-field monitor timer NXlauetof/entry/control/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-control-mode-field 0 1 NXlauetof/entry/control/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-control-preset-field 0 1 NXlauetof/entry/control/data use these attributes ``primary=1 signal=1`` https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-control-data-field 0 1 NXlauetof/entry/control/time_of_flight https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-control-time-of-flight-field 0 1 NXdirecttof/entry/title https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-title-field 0 1 NXdirecttof/entry/start_time https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-start-time-field NXdirecttof NXdirecttof/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-definition-field 0 1 NXdirecttof/entry/INSTRUMENT/fermi_chopper/rotation_speed chopper rotation speed https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-fermi-chopper-rotation-speed-field 0 1 NXdirecttof/entry/INSTRUMENT/fermi_chopper/energy energy selected https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-fermi-chopper-energy-field 0 1 NXdirecttof/entry/INSTRUMENT/disk_chopper/rotation_speed chopper rotation speed https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-disk-chopper-rotation-speed-field 0 1 NXdirecttof/entry/INSTRUMENT/disk_chopper/energy energy selected https://manual.nexusformat.org/classes/applications/NXdirecttof.html#nxdirecttof-entry-instrument-disk-chopper-energy-field 0 1 NXxas/ENTRY/title https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-title-field 0 1 NXxas/ENTRY/start_time https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-start-time-field NXxas NXxas/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-definition-field 0 1 NXxas/ENTRY/INSTRUMENT/SOURCE/type https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-source-type-field 0 1 NXxas/ENTRY/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-source-name-field x-ray NXxas/ENTRY/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-source-probe-field 0 1 NXxas/ENTRY/INSTRUMENT/monochromator/energy https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-monochromator-energy-field 0 1 NXxas/ENTRY/INSTRUMENT/incoming_beam/data https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-incoming-beam-data-field 0 1 NXxas/ENTRY/INSTRUMENT/absorbed_beam/data This data corresponds to the sample signal. https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-instrument-absorbed-beam-data-field 0 1 NXxas/ENTRY/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-sample-name-field monitor timer NXxas/ENTRY/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-monitor-mode-field 0 1 NXxas/ENTRY/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-monitor-preset-field 0 1 NXxas/ENTRY/MONITOR/data This field could be a link to ``/NXentry/NXinstrument/incoming_beam:NXdetector/data`` https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-monitor-data-field Total Electron Yield Partial Electron Yield Auger Electron Yield Fluorescence Yield Transmission NXxas/ENTRY/DATA/mode Detection method used for observing the sample absorption (pick one from the enumerated list and spell exactly) https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-data-mode-field NXxeuler NXxeuler/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-definition-field 0 1 NXxeuler/entry/instrument/detector/polar_angle The polar_angle (two theta) where the detector is placed at each scan point. https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-instrument-detector-polar-angle-field 0 1 NXxeuler/entry/sample/rotation_angle This is an array holding the sample rotation angle at each scan point https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-sample-rotation-angle-field 0 1 NXxeuler/entry/sample/chi This is an array holding the chi angle of the eulerian cradle at each scan point https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-sample-chi-field 0 1 NXxeuler/entry/sample/phi This is an array holding the phi rotation of the eulerian cradle at each scan point https://manual.nexusformat.org/classes/applications/NXxeuler.html#nxxeuler-entry-sample-phi-field 0 1 NXmx/ENTRY/title https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-title-field 0 1 NXmx/ENTRY/start_time ISO 8601 time/date of the first data point collected in UTC, using the Z suffix to avoid confusion with local time. Note that the time zone of the beamline should be provided in NXentry/NXinstrument/time_zone. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-start-time-field 0 1 NXmx/ENTRY/end_time ISO 8601 time/date of the last data point collected in UTC, using the Z suffix to avoid confusion with local time. Note that the time zone of the beamline should be provided in NXentry/NXinstrument/time_zone. This field should only be filled when the value is accurately observed. If the data collection aborts or otherwise prevents accurate recording of the end_time, this field should be omitted. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-end-time-field 0 1 NXmx/ENTRY/end_time_estimated ISO 8601 time/date of the last data point collected in UTC, using the Z suffix to avoid confusion with local time. Note that the time zone of the beamline should be provided in NXentry/NXinstrument/time_zone. This field may be filled with a value estimated before an observed value is available. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-end-time-estimated-field NXmx NXmx/ENTRY/definition NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-definition-field 0 1 NXmx/ENTRY/DATA/data For a dimension-2 detector, the rank of the data array will be 3. For a dimension-3 detector, the rank of the data array will be 4. This allows for the introduction of the frame number as the first index. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-data-data-field 0 1 NXmx/ENTRY/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-sample-name-field 0 1 NXmx/ENTRY/SAMPLE/depends_on This is a requirement to describe for any scan experiment. The axis on which the sample position depends may be stored anywhere, but is normally stored in the NXtransformations group within the NXsample group. If there is no goniometer, e.g. with a jet, depends_on should be set to "." https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-sample-depends-on-field 0 1 NXmx/ENTRY/SAMPLE/temperature https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-sample-temperature-field 0 1 0 NXmx/ENTRY/INSTRUMENT/name Name of instrument. Consistency with the controlled vocabulary beamline naming in https://mmcif.wwpdb.org/dictionaries/mmcif_pdbx_v50.dic/Items/_diffrn_source.pdbx_synchrotron_beamline.html and https://mmcif.wwpdb.org/dictionaries/mmcif_pdbx_v50.dic/Items/_diffrn_source.type.html is highly recommended. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-name-field 0 1 NXmx/ENTRY/INSTRUMENT/time_zone ISO 8601 time_zone offset from UTC. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-time-zone-field 0 1 NXmx/ENTRY/INSTRUMENT/ATTENUATOR/attenuator_transmission https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-attenuator-attenuator-transmission-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR_GROUP/group_names An array of the names of the detectors or the names of hierarchical groupings of detectors. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-group-group-names-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR_GROUP/group_index An array of unique identifiers for detectors or groupings of detectors. Each ID is a unique ID for the corresponding detector or group named in the field group_names. The IDs are positive integers starting with 1. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-group-group-index-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR_GROUP/group_parent An array of the hierarchical levels of the parents of detectors or groupings of detectors. A top-level grouping has parent level -1. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-group-group-parent-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/depends_on NeXus path to the detector positioner axis that most directly supports the detector. In the case of a single-module detector, the detector axis chain may start here. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-depends-on-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/data For a dimension-2 detector, the rank of the data array will be 3. For a dimension-3 detector, the rank of the data array will be 4. This allows for the introduction of the frame number as the first index. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-data-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/description name/manufacturer/model/etc. information. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-description-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/time_per_channel For a time-of-flight detector this is the scaling factor to convert from the numeric value reported to the flight time for a given measurement. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-time-per-channel-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/data_origin A dimension-2 or dimension-3 field which gives the indices of the origin of the hyperslab of data for this module in the main area detector image in the parent NXdetector module. The data_origin is 0-based. The frame number dimension (nP) is omitted. Thus the data_origin field for a dimension-2 dataset with indices (nP, i, j) will be an array with indices (i, j), and for a dimension-3 dataset with indices (nP, i, j, k) will be an array with indices (i, j, k). The :ref:`order <Design-ArrayStorageOrder>` of indices (i, j or i, j, k) is slow to fast. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-data-origin-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/data_size Two or three values for the size of the module in pixels in each direction. Dimensionality and order of indices is the same as for data_origin. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-data-size-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/data_stride Two or three values for the stride of the module in pixels in each direction. By default the stride is [1,1] or [1,1,1], and this is the most likely case. This optional field is included for completeness. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-data-stride-field 0 1 1 1 1 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/module_offset Offset of the module in regards to the origin of the detector in an arbitrary direction. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-module-offset-field 0 1 1 1 1 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/fast_pixel_direction Values along the direction of :ref:`fastest varying <Design-ArrayStorageOrder>` pixel direction. The direction itself is given through the vector attribute. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-fast-pixel-direction-field 0 1 1 1 1 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/slow_pixel_direction Values along the direction of :ref:`slowest varying <Design-ArrayStorageOrder>` pixel direction. The direction itself is given through the vector attribute. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-slow-pixel-direction-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/distance Distance from the sample to the beam center. Normally this value is for guidance only, the proper geometry can be found following the depends_on axis chain, But in appropriate cases where the dectector distance to the sample is observable independent of the axis chain, that may take precedence over the axis chain calculation. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-distance-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/distance_derived Boolean to indicate if the distance is a derived, rather than a primary observation. If distance_derived true or is not specified, the distance is assumed to be derived from detector axis specifications. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-distance-derived-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/dead_time Detector dead time. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-dead-time-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/count_time Elapsed actual counting time. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-count-time-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/beam_center_derived Boolean to indicate if the distance is a derived, rather than a primary observation. If true or not provided, that value of beam_center_derived is assumed to be true. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-beam-center-derived-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/beam_center_x This is the x position where the direct beam would hit the detector. This is a length and can be outside of the actual detector. The length can be in physical units or pixels as documented by the units attribute. Normally, this should be derived from the axis chain, but the direct specification may take precedence if it is not a derived quantity. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-beam-center-x-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/beam_center_y This is the y position where the direct beam would hit the detector. This is a length and can be outside of the actual detector. The length can be in physical units or pixels as documented by the units attribute. Normally, this should be derived from the axis chain, but the direct specification may take precedence if it is not a derived quantity. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-beam-center-y-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/angular_calibration_applied True when the angular calibration has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-angular-calibration-applied-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/angular_calibration Angular calibration data. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-angular-calibration-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/flatfield_applied True when the flat field correction has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-flatfield-applied-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/flatfield Flat field correction data. If provided, it is recommended that it be compressed. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-flatfield-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/flatfield_error *** Deprecated form. Use plural form *** Errors of the flat field correction data. If provided, it is recommended that it be compressed. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-flatfield-error-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/flatfield_errors Errors of the flat field correction data. If provided, it is recommended that it be compressed. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-flatfield-errors-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/pixel_mask_applied True when the pixel mask correction has been applied in the electronics, false otherwise. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-pixel-mask-applied-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/pixel_mask The 32-bit pixel mask for the detector. Can be either one mask for the whole dataset (i.e. an array with indices i, j) or each frame can have its own mask (in which case it would be an array with indices nP, i, j). Contains a bit field for each pixel to signal dead, blind, high or otherwise unwanted or undesirable pixels. They have the following meaning: * bit 0: gap (pixel with no sensor) * bit 1: dead * bit 2: under-responding * bit 3: over-responding * bit 4: noisy * bit 5: -undefined- * bit 6: pixel is part of a cluster of problematic pixels (bit set in addition to others) * bit 7: -undefined- * bit 8: user defined mask (e.g. around beamstop) * bits 9-30: -undefined- * bit 31: virtual pixel (corner pixel with interpolated value) Normal data analysis software would not take pixels into account when a bit in (mask & 0x0000FFFF) is set. Tag bit in the upper two bytes would indicate special pixel properties that normally would not be a sole reason to reject the intensity value (unless lower bits are set. If the full bit depths is not required, providing a mask with fewer bits is permissible. If needed, additional pixel masks can be specified by including additional entries named pixel_mask_N, where N is an integer. For example, a general bad pixel mask could be specified in pixel_mask that indicates noisy and dead pixels, and an additional pixel mask from experiment-specific shadowing could be specified in pixel_mask_2. The cumulative mask is the bitwise OR of pixel_mask and any pixel_mask_N entries. If provided, it is recommended that it be compressed. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-pixel-mask-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/countrate_correction_applied Counting detectors usually are not able to measure all incoming particles, especially at higher count-rates. Count-rate correction is applied to account for these errors. True when count-rate correction has been applied, false otherwise. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-countrate-correction-applied-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/countrate_correction_lookup_table The countrate_correction_lookup_table defines the LUT used for count-rate correction. It maps a measured count :math:`c` to its corrected value :math:`countrate\_correction\_lookup\_table[c]`. :math:`m` denotes the length of the table. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-countrate-correction-lookup-table-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/virtual_pixel_interpolation_applied True when virtual pixel interpolation has been applied, false otherwise. When virtual pixel interpolation is applied, values of some pixels may contain interpolated values. For example, to account for space between readout chips on a module, physical pixels on edges and corners between chips may have larger sensor areas and counts may be distributed between their logical pixels. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-virtual-pixel-interpolation-applied-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/bit_depth_readout How many bits the electronics record per pixel. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-bit-depth-readout-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/detector_readout_time Time it takes to read the detector (typically milliseconds). This is important to know for time resolved experiments. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-readout-time-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/frame_time This is time for each frame. This is exposure_time + readout time. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-frame-time-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/gain_setting The gain setting of the detector. This influences background. This is a detector-specific value meant to document the gain setting of the detector during data collection, for detectors with multiple available gain settings. Examples of gain settings include: * ``standard`` * ``fast`` * ``auto`` * ``high`` * ``medium`` * ``low`` * ``mixed high to medium`` * ``mixed medium to low`` Developers are encouraged to use one of these terms, or to submit additional terms to add to the list. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-gain-setting-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/saturation_value The value at which the detector goes into saturation. Data above this value is known to be invalid. For example, given a saturation_value and an underload_value, the valid pixels are those less than or equal to the saturation_value and greater than or equal to the underload_value. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-saturation-value-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/underload_value The lowest value at which pixels for this detector would be reasonably be measured. For example, given a saturation_value and an underload_value, the valid pixels are those less than or equal to the saturation_value and greater than or equal to the underload_value. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-underload-value-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/sensor_material At times, radiation is not directly sensed by the detector. Rather, the detector might sense the output from some converter like a scintillator. This is the name of this converter material. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-sensor-material-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/sensor_thickness At times, radiation is not directly sensed by the detector. Rather, the detector might sense the output from some converter like a scintillator. This is the thickness of this converter material. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-sensor-thickness-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/threshold_energy Single photon counter detectors can be adjusted for a certain energy range in which they work optimally. This is the energy setting for this. If the detector supports multiple thresholds, this is an array. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-threshold-energy-field 0 1 NXmx/ENTRY/INSTRUMENT/DETECTOR/type Description of type such as scintillator, ccd, pixel, image plate, CMOS, ... https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-type-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength In the case of a monchromatic beam this is the scalar wavelength. Several other use cases are permitted, depending on the presence or absence of other incident_wavelength_X fields. In the case of a polychromatic beam this is an array of length **m** of wavelengths, with the relative weights in ``incident_wavelength_weights``. In the case of a monochromatic beam that varies shot- to-shot, this is an array of wavelengths, one for each recorded shot. Here, ``incident_wavelength_weights`` and incident_wavelength_spread are not set. In the case of a polychromatic beam that varies shot-to- shot, this is an array of length **m** with the relative weights in ``incident_wavelength_weights`` as a 2D array. In the case of a polychromatic beam that varies shot-to- shot and where the channels also vary, this is a 2D array of dimensions **nP** by **m** (slow to fast) with the relative weights in ``incident_wavelength_weights`` as a 2D array. Note, :ref:`variants <Design-Variants>` are a good way to represent several of these use cases in a single dataset, e.g. if a calibrated, single-value wavelength value is available along with the original spectrum from which it was calibrated. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-wavelength-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength_weight In the case of a polychromatic beam this is an array of length **m** of the relative weights of the corresponding wavelengths in incident_wavelength. In the case of a polychromatic beam that varies shot-to- shot, this is a 2D array of dimensions **nP** by **m** (slow to fast) of the relative weights of the corresponding wavelengths in incident_wavelength. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-wavelength-weight-field true 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength_weights In the case of a polychromatic beam this is an array of length **m** of the relative weights of the corresponding wavelengths in ``incident_wavelength``. In the case of a polychromatic beam that varies shot-to- shot, this is a 2D array of dimensions **np** by **m** (slow to fast) of the relative weights of the corresponding wavelengths in ``incident_wavelength``. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-wavelength-weights-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_wavelength_spread The wavelength spread FWHM for the corresponding wavelength(s) in incident_wavelength. In the case of shot-to-shot variation in the wavelength spread, this is a 2D array of dimension **nP** by **m** (slow to fast) of the spreads of the corresponding wavelengths in incident_wavelength. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-wavelength-spread-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/flux Flux density incident on beam plane area in photons per second per unit area. In the case of a beam that varies in flux shot-to-shot, this is an array of values, one for each recorded shot. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-flux-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/total_flux Flux incident on beam plane in photons per second. In other words this is the :ref:`flux </NXmx/ENTRY/INSTRUMENT/BEAM/flux-field>` integrated over area. Useful where spatial beam profiles are not known. In the case of a beam that varies in total flux shot-to-shot, this is an array of values, one for each recorded shot. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-total-flux-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/flux_integrated Flux density incident on beam plane area in photons per unit area. In other words this is the :ref:`flux </NXmx/ENTRY/INSTRUMENT/BEAM/flux-field>` integrated over time. Useful where temporal beam profiles of flux are not known. In the case of a beam that varies in flux shot-to-shot, this is an array of values, one for each recorded shot. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-flux-integrated-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/total_flux_integrated Flux incident on beam plane in photons. In other words this is the :ref:`flux </NXmx/ENTRY/INSTRUMENT/BEAM/flux-field>` integrated over time and area. Useful where temporal beam profiles of flux are not known. In the case of a beam that varies in total flux shot-to-shot, this is an array of values, one for each recorded shot. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-total-flux-integrated-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_beam_size Two-element array of FWHM (if Gaussian or Airy function) or diameters (if top hat) or widths (if rectangular) of the beam in the order x, y https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-beam-size-field Gaussian Airy top-hat rectangular NXmx/ENTRY/INSTRUMENT/BEAM/profile The beam profile, Gaussian, Airy function, top-hat or rectangular. The profile is given in the plane of incidence of the beam on the sample. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-profile-field 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_polarisation_stokes https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-polarisation-stokes-field true 0 1 NXmx/ENTRY/INSTRUMENT/BEAM/incident_polarization_stokes Polarization vector on entering beamline component using Stokes notation. See incident_polarization_stokes in :ref:`NXbeam` https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-incident-polarization-stokes-field 0 1 0 NXmx/ENTRY/SOURCE/name Name of source. Consistency with the naming in https://mmcif.wwpdb.org/dictionaries/mmcif_pdbx_v50.dic/Items/_diffrn_source.pdbx_synchrotron_site.html controlled vocabulary is highly recommended. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-source-name-field 0 1 NXscan/ENTRY/title https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-title-field 0 1 NXscan/ENTRY/start_time https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-start-time-field 0 1 NXscan/ENTRY/end_time https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-end-time-field NXscan NXscan/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-definition-field 0 1 NXscan/ENTRY/INSTRUMENT/DETECTOR/data https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-instrument-detector-data-field 0 1 NXscan/ENTRY/SAMPLE/rotation_angle https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-sample-rotation-angle-field 0 1 NXscan/ENTRY/MONITOR/data https://manual.nexusformat.org/classes/applications/NXscan.html#nxscan-entry-monitor-data-field 0 1 NXtomoproc/entry/title https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-title-field NXtomoproc NXtomoproc/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-definition-field 0 1 NXtomoproc/entry/INSTRUMENT/SOURCE/type https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-instrument-source-type-field 0 1 NXtomoproc/entry/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-instrument-source-name-field neutron x-ray electron NXtomoproc/entry/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-instrument-source-probe-field 0 1 NXtomoproc/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-sample-name-field 0 1 NXtomoproc/entry/reconstruction/program Name of the program used for reconstruction https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-reconstruction-program-field 0 1 NXtomoproc/entry/reconstruction/version Version of the program used https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-reconstruction-version-field 0 1 NXtomoproc/entry/reconstruction/date Date and time of reconstruction processing. https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-reconstruction-date-field 0 1 NXtomoproc/entry/reconstruction/parameters/raw_file Original raw data file this data was derived from https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-reconstruction-parameters-raw-file-field 0 1 1 1 1 NXtomoproc/entry/data/data This is the reconstructed volume. This can be different things. Please indicate in the unit attribute what physical quantity this really is. https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-data-field 0 1 NXtomoproc/entry/data/x This is an array holding the values to use for the x-axis of data. The units must be appropriate for the measurement. https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-x-field 0 1 NXtomoproc/entry/data/y This is an array holding the values to use for the y-axis of data. The units must be appropriate for the measurement. https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-y-field 0 1 NXtomoproc/entry/data/z This is an array holding the values to use for the z-axis of data. The units must be appropriate for the measurement. https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-z-field 0 1 NXtomo/entry/title https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-title-field 0 1 NXtomo/entry/start_time https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-start-time-field 0 1 NXtomo/entry/end_time https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-end-time-field NXtomo NXtomo/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-definition-field 0 1 NXtomo/entry/instrument/SOURCE/type https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-source-type-field 0 1 NXtomo/entry/instrument/SOURCE/name https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-source-name-field neutron x-ray electron NXtomo/entry/instrument/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-source-probe-field 0 1 NXtomo/entry/instrument/detector/data https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-data-field 0 1 NXtomo/entry/instrument/detector/image_key In order to distinguish between sample projections, dark and flat images, a magic number is recorded per frame. The key is as follows: * projection = 0 * flat field = 1 * dark field = 2 * invalid = 3 https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-image-key-field 0 1 NXtomo/entry/instrument/detector/x_pixel_size https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-x-pixel-size-field 0 1 NXtomo/entry/instrument/detector/y_pixel_size https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-y-pixel-size-field 0 1 NXtomo/entry/instrument/detector/distance Distance between detector and sample https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-distance-field 0 1 NXtomo/entry/instrument/detector/x_rotation_axis_pixel_position https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-x-rotation-axis-pixel-position-field 0 1 NXtomo/entry/instrument/detector/y_rotation_axis_pixel_position https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-instrument-detector-y-rotation-axis-pixel-position-field 0 1 NXtomo/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-sample-name-field 0 1 NXtomo/entry/sample/rotation_angle In practice this axis is always aligned along one pixel direction on the detector and usually vertical. There are experiments with horizontal rotation axes, so this would need to be indicated somehow. For now the best way for that is an open question. https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-sample-rotation-angle-field 0 1 NXtomo/entry/sample/x_translation https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-sample-x-translation-field 0 1 NXtomo/entry/sample/y_translation https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-sample-y-translation-field 0 1 NXtomo/entry/sample/z_translation https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-sample-z-translation-field 0 1 NXtomo/entry/control/data Total integral monitor counts for each measured frame. Allows a to correction for fluctuations in the beam between frames. https://manual.nexusformat.org/classes/applications/NXtomo.html#nxtomo-entry-control-data-field 0 1 NXrefscan/entry/title https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-title-field 0 1 NXrefscan/entry/start_time https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-start-time-field 0 1 NXrefscan/entry/end_time https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-end-time-field NXrefscan NXrefscan/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-definition-field 0 1 NXrefscan/entry/instrument/SOURCE/type https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-source-type-field 0 1 NXrefscan/entry/instrument/SOURCE/name https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-source-name-field neutron x-ray electron NXrefscan/entry/instrument/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-source-probe-field 0 1 NXrefscan/entry/instrument/monochromator/wavelength https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-monochromator-wavelength-field 0 1 NXrefscan/entry/instrument/DETECTOR/data https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-detector-data-field 0 1 NXrefscan/entry/instrument/DETECTOR/polar_angle https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-instrument-detector-polar-angle-field 0 1 NXrefscan/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-sample-name-field 0 1 NXrefscan/entry/sample/rotation_angle https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-sample-rotation-angle-field monitor timer NXrefscan/entry/control/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-control-mode-field 0 1 NXrefscan/entry/control/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-control-preset-field 0 1 NXrefscan/entry/control/data Monitor counts for each step https://manual.nexusformat.org/classes/applications/NXrefscan.html#nxrefscan-entry-control-data-field 0 1 NXarpes/ENTRY/title https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-title-field 0 1 NXarpes/ENTRY/start_time https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-start-time-field NXarpes NXarpes/ENTRY/definition Official NeXus NXDL schema to which this file conforms. https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-definition-field 0 1 NXarpes/ENTRY/INSTRUMENT/SOURCE/type https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-source-type-field 0 1 NXarpes/ENTRY/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-source-name-field x-ray NXarpes/ENTRY/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-source-probe-field 0 1 NXarpes/ENTRY/INSTRUMENT/monochromator/energy https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-monochromator-energy-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/data https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-data-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/lens_mode setting for the electron analyser lens https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-lens-mode-field swept fixed NXarpes/ENTRY/INSTRUMENT/analyser/acquisition_mode https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-acquisition-mode-field curved straight NXarpes/ENTRY/INSTRUMENT/analyser/entrance_slit_shape https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-entrance-slit-shape-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/entrance_slit_setting dial setting of the entrance slit https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-entrance-slit-setting-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/entrance_slit_size size of the entrance slit https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-entrance-slit-size-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/pass_energy energy of the electrons on the mean path of the analyser https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-pass-energy-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/time_per_channel todo: define more clearly https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-time-per-channel-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/angles Angular axis of the analyser data which dimension the axis applies to is defined using the normal NXdata methods. https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-angles-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/energies Energy axis of the analyser data which dimension the axis applies to is defined using the normal NXdata methods. https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-energies-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/sensor_size number of raw active elements in each dimension https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-sensor-size-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/region_origin origin of rectangular region selected for readout https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-region-origin-field 0 1 NXarpes/ENTRY/INSTRUMENT/analyser/region_size size of rectangular region selected for readout https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-instrument-analyser-region-size-field 0 1 NXarpes/ENTRY/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-sample-name-field 0 1 NXarpes/ENTRY/SAMPLE/temperature https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-sample-temperature-field 0 1 NXiqproc/ENTRY/title https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-title-field NXiqproc NXiqproc/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-definition-field 0 1 NXiqproc/ENTRY/instrument/SOURCE/type https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-instrument-source-type-field 0 1 NXiqproc/ENTRY/instrument/SOURCE/name https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-instrument-source-name-field neutron x-ray electron NXiqproc/ENTRY/instrument/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-instrument-source-probe-field 0 1 NXiqproc/ENTRY/instrument/name Name of the instrument from which this data was reduced. https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-instrument-name-field 0 1 NXiqproc/ENTRY/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-sample-name-field 0 1 NXiqproc/ENTRY/reduction/program https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-reduction-program-field 0 1 NXiqproc/ENTRY/reduction/version https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-reduction-version-field 0 1 NXiqproc/ENTRY/reduction/input/filenames Raw data files used to generate this I(Q) https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-reduction-input-filenames-field 0 1 NXiqproc/ENTRY/DATA/data This is I(Q). The client has to analyse the dimensions of I(Q). Often, multiple I(Q) for various environment conditions are measured; that would be the first dimension. Q can be multidimensional, this accounts for the further dimensions in the data https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-data-data-field 0 1 1 NXiqproc/ENTRY/DATA/variable https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-data-variable-field 0 1 NXiqproc/ENTRY/DATA/qx Values for the first dimension of Q https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-data-qx-field 0 1 NXiqproc/ENTRY/DATA/qy Values for the second dimension of Q https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-data-qy-field 0 1 NXsas/ENTRY/title https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-title-field 0 1 NXsas/ENTRY/start_time https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-start-time-field 0 1 NXsas/ENTRY/end_time https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-end-time-field NXsas NXsas/ENTRY/definition Official NeXus NXDL schema to which this file conforms. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-definition-field 0 1 NXsas/ENTRY/INSTRUMENT/SOURCE/type Type of radiation source. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-source-type-field 0 1 NXsas/ENTRY/INSTRUMENT/SOURCE/name Name of the radiation source. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-source-name-field neutron x-ray NXsas/ENTRY/INSTRUMENT/SOURCE/probe Name of radiation probe, necessary to compute the sample contrast. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-source-probe-field 0 1 NXsas/ENTRY/INSTRUMENT/MONOCHROMATOR/wavelength The wavelength (:math:`\lambda`) of the radiation. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-monochromator-wavelength-field 0 1 NXsas/ENTRY/INSTRUMENT/MONOCHROMATOR/wavelength_spread delta_lambda/lambda (:math:`\Delta\lambda/\lambda`): Important for resolution calculations. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-monochromator-wavelength-spread-field nxcylinder nxbox NXsas/ENTRY/INSTRUMENT/COLLIMATOR/GEOMETRY/SHAPE/shape https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-collimator-geometry-shape-shape-field 0 1 NXsas/ENTRY/INSTRUMENT/COLLIMATOR/GEOMETRY/SHAPE/size The collimation length. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-collimator-geometry-shape-size-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/data This is area detector data, 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. It is necessary to define which are the x and y directions, to coordinate with the pixel size and compute Q. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-data-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/distance The distance between detector and sample. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-distance-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/x_pixel_size Physical size of a pixel in x-direction. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-x-pixel-size-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/y_pixel_size Physical size of a pixel in y-direction. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-y-pixel-size-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/polar_angle https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-polar-angle-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/azimuthal_angle https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-azimuthal-angle-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/rotation_angle https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-rotation-angle-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/aequatorial_angle https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-aequatorial-angle-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/beam_center_x 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. It is expected that data reduction will determine beam center from the raw data, thus it is not required here. The instrument can provide an initial or nominal value to advise data reduction. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-beam-center-x-field 0 1 NXsas/ENTRY/INSTRUMENT/DETECTOR/beam_center_y 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. It is expected that data reduction will determine beam center from the raw data, thus it is not required here. The instrument can provide an initial or nominal value to advise data reduction. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-detector-beam-center-y-field 0 1 NXsas/ENTRY/INSTRUMENT/name Name of the instrument actually used to perform the experiment. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-instrument-name-field 0 1 NXsas/ENTRY/SAMPLE/name Descriptive name of sample. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-sample-name-field 0 1 NXsas/ENTRY/SAMPLE/aequatorial_angle https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-sample-aequatorial-angle-field monitor timer NXsas/ENTRY/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-monitor-mode-field 0 1 NXsas/ENTRY/MONITOR/preset Preset value for time or monitor. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-monitor-preset-field 0 1 NXsas/ENTRY/MONITOR/integral Total integral monitor counts. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-monitor-integral-field 0 1 NXindirecttof/entry/title https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-title-field 0 1 NXindirecttof/entry/start_time https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-start-time-field NXindirecttof NXindirecttof/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-definition-field 0 1 NXindirecttof/entry/INSTRUMENT/analyser/energy analyzed energy https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-instrument-analyser-energy-field 0 1 NXindirecttof/entry/INSTRUMENT/analyser/polar_angle polar angle towards sample https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-instrument-analyser-polar-angle-field 0 1 NXindirecttof/entry/INSTRUMENT/analyser/distance distance from sample https://manual.nexusformat.org/classes/applications/NXindirecttof.html#nxindirecttof-entry-instrument-analyser-distance-field 0 1 NXspe/ENTRY/program_name https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-program-name-field NXspe 1 NXspe/ENTRY/definition Official NeXus NXDL schema to which this file conforms. https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-definition-field 0 1 NXspe/ENTRY/NXSPE_info/fixed_energy The fixed energy used for this file. https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-nxspe-info-fixed-energy-field 0 1 NXspe/ENTRY/NXSPE_info/ki_over_kf_scaling Indicates whether ki/kf scaling has been applied or not. https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-nxspe-info-ki-over-kf-scaling-field 0 1 NXspe/ENTRY/NXSPE_info/psi Orientation angle as expected in DCS-MSlice https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-nxspe-info-psi-field 0 1 NXspe/ENTRY/data/azimuthal https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-azimuthal-field 0 1 NXspe/ENTRY/data/azimuthal_width https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-azimuthal-width-field 0 1 NXspe/ENTRY/data/polar https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-polar-field 0 1 NXspe/ENTRY/data/polar_width https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-polar-width-field 0 1 NXspe/ENTRY/data/distance https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-distance-field 0 1 NXspe/ENTRY/data/data https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-data-field 0 1 NXspe/ENTRY/data/error https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-error-field 0 1 NXspe/ENTRY/data/energy https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-data-energy-field 0 1 NXspe/ENTRY/INSTRUMENT/name https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-instrument-name-field 0 1 NXspe/ENTRY/INSTRUMENT/FERMI_CHOPPER/energy https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-instrument-fermi-chopper-energy-field 0 1 NXspe/ENTRY/SAMPLE/rotation_angle https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-sample-rotation-angle-field 0 1 NXspe/ENTRY/SAMPLE/seblock https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-sample-seblock-field 0 1 NXspe/ENTRY/SAMPLE/temperature https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-sample-temperature-field 0 1 NXreftof/entry/title https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-title-field 0 1 NXreftof/entry/start_time https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-start-time-field 0 1 NXreftof/entry/end_time https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-end-time-field NXreftof NXreftof/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-definition-field 0 1 NXreftof/entry/instrument/name https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-name-field 0 1 NXreftof/entry/instrument/chopper/distance Distance between chopper and sample https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-chopper-distance-field 0 1 NXreftof/entry/instrument/detector/data https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-data-field 0 1 NXreftof/entry/instrument/detector/time_of_flight Array of time values for each bin in a time-of-flight measurement https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-time-of-flight-field 0 1 NXreftof/entry/instrument/detector/distance https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-distance-field 0 1 NXreftof/entry/instrument/detector/polar_angle https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-polar-angle-field 0 1 NXreftof/entry/instrument/detector/x_pixel_size https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-x-pixel-size-field 0 1 NXreftof/entry/instrument/detector/y_pixel_size https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-instrument-detector-y-pixel-size-field 0 1 NXreftof/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-sample-name-field 0 1 NXreftof/entry/sample/rotation_angle https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-sample-rotation-angle-field monitor timer NXreftof/entry/control/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-control-mode-field 0 1 NXreftof/entry/control/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-control-preset-field 0 1 NXreftof/entry/control/integral Total integral monitor counts https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-control-integral-field 0 1 NXreftof/entry/control/time_of_flight Time channels https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-control-time-of-flight-field 0 1 NXreftof/entry/control/data Monitor counts in each time channel https://manual.nexusformat.org/classes/applications/NXreftof.html#nxreftof-entry-control-data-field 0 1 NXsqom/ENTRY/title https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-title-field NXsqom NXsqom/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-definition-field 0 1 NXsqom/ENTRY/instrument/SOURCE/type https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-instrument-source-type-field 0 1 NXsqom/ENTRY/instrument/SOURCE/name https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-instrument-source-name-field neutron x-ray electron NXsqom/ENTRY/instrument/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-instrument-source-probe-field 0 1 NXsqom/ENTRY/instrument/name Name of the instrument from which this data was reduced. https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-instrument-name-field 0 1 NXsqom/ENTRY/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-sample-name-field 0 1 NXsqom/ENTRY/reduction/program https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-reduction-program-field 0 1 NXsqom/ENTRY/reduction/version https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-reduction-version-field 0 1 NXsqom/ENTRY/reduction/input/filenames Raw data files used to generate this I(Q) https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-reduction-input-filenames-field 0 1 NXsqom/ENTRY/DATA/data This is the intensity for each point in QE https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-data-data-field 0 1 NXsqom/ENTRY/DATA/qx Positions for the first dimension of Q https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-data-qx-field 0 1 NXsqom/ENTRY/DATA/qy Positions for the the second dimension of Q https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-data-qy-field 0 1 NXsqom/ENTRY/DATA/qz Positions for the the third dimension of Q https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-data-qz-field 0 1 NXsqom/ENTRY/DATA/en Values for the energy transfer for each point https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-data-en-field 0 1 NXarchive/entry/title https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-title-field 0 1 NXarchive/entry/experiment_identifier unique identifier for the experiment https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-experiment-identifier-field 0 1 NXarchive/entry/experiment_description Brief description of the experiment and its objectives https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-experiment-description-field 0 1 NXarchive/entry/collection_identifier ID of user or DAQ define group of data files https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-collection-identifier-field 0 1 NXarchive/entry/collection_description Brief summary of the collection, including grouping criteria https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-collection-description-field 0 1 NXarchive/entry/entry_identifier unique identifier for this measurement as provided by the facility https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-entry-identifier-field 0 1 NXarchive/entry/start_time https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-start-time-field 0 1 NXarchive/entry/end_time https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-end-time-field 0 1 NXarchive/entry/duration TODO: needs documentation https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-duration-field 0 1 NXarchive/entry/collection_time TODO: needs documentation https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-collection-time-field 0 1 NXarchive/entry/run_cycle TODO: needs documentation https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-run-cycle-field 0 1 NXarchive/entry/revision revision ID of this file, may be after recalibration, reprocessing etc. https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-revision-field NXarchive NXarchive/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-definition-field 0 1 1 NXarchive/entry/program The program and version used for generating this file https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-program-field 0 1 NXarchive/entry/release_date when this file is to be released into PD https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-release-date-field 0 1 NXarchive/entry/user/name https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-user-name-field 0 1 NXarchive/entry/user/role role of the user https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-user-role-field 0 1 NXarchive/entry/user/facility_user_id ID of the user in the facility burocracy database https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-user-facility-user-id-field Spallation Neutron Source Pulsed Reactor Neutron Source Reactor Neutron Source Synchrotron X-Ray Source Pulsed Muon Source Rotating Anode X-Ray Fixed Tube X-Ray NXarchive/entry/instrument/SOURCE/type https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-source-type-field 0 1 NXarchive/entry/instrument/SOURCE/name https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-source-name-field neutron x-ray electron NXarchive/entry/instrument/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-source-probe-field 0 1 NXarchive/entry/instrument/name https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-name-field 0 1 NXarchive/entry/instrument/description Brief description of the instrument https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-instrument-description-field 0 1 NXarchive/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-name-field 0 1 NXarchive/entry/sample/sample_id Unique database id of the sample https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-sample-id-field 0 1 NXarchive/entry/sample/description https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-description-field sample sample+can calibration sample normalisation sample simulated data none sample_environment NXarchive/entry/sample/type https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-type-field 0 1 NXarchive/entry/sample/chemical_formula Chemical formula formatted according to CIF conventions https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-chemical-formula-field 0 1 NXarchive/entry/sample/preparation_date https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-preparation-date-field 0 1 NXarchive/entry/sample/situation Description of the environment the sample is in: air, vacuum, oxidizing atmosphere, dehydrated, etc. https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-situation-field 0 1 NXarchive/entry/sample/temperature https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-temperature-field 0 1 NXarchive/entry/sample/magnetic_field https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-magnetic-field-field 0 1 NXarchive/entry/sample/electric_field https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-electric-field-field 0 1 NXarchive/entry/sample/stress_field https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-stress-field-field 0 1 NXarchive/entry/sample/pressure https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-sample-pressure-field 0 1 NXtofsingle/entry/title https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-title-field 0 1 NXtofsingle/entry/start_time https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-start-time-field NXtofsingle NXtofsingle/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-definition-field 0 1 NXtofsingle/entry/duration https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-duration-field 0 1 NXtofsingle/entry/pre_sample_flightpath This is the flight path before the sample position. This can be determined by a chopper, by the moderator or the source itself. In other words: it the distance to the component which gives the T0 signal to the detector electronics. If another component in the NXinstrument hierarchy provides this information, this should be a link. https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-pre-sample-flightpath-field 0 1 NXtofsingle/entry/user/name https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-user-name-field 0 1 NXtofsingle/entry/INSTRUMENT/detector/data https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-detector-data-field 0 1 NXtofsingle/entry/INSTRUMENT/detector/distance Distance to sample for the center of the detector https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-detector-distance-field 0 1 NXtofsingle/entry/INSTRUMENT/detector/time_of_flight https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-detector-time-of-flight-field 0 1 NXtofsingle/entry/INSTRUMENT/detector/polar_angle polar angle for each detector element https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-detector-polar-angle-field 0 1 NXtofsingle/entry/INSTRUMENT/detector/azimuthal_angle azimuthal angle for each detector element https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-instrument-detector-azimuthal-angle-field 0 1 NXtofsingle/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-sample-name-field powder liquid single crystal NXtofsingle/entry/SAMPLE/nature https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-sample-nature-field monitor timer NXtofsingle/entry/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-monitor-mode-field 0 1 NXtofsingle/entry/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-monitor-preset-field 0 1 NXtofsingle/entry/MONITOR/distance https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-monitor-distance-field 0 1 NXtofsingle/entry/MONITOR/data https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-monitor-data-field 0 1 NXtofsingle/entry/MONITOR/time_of_flight https://manual.nexusformat.org/classes/applications/NXtofsingle.html#nxtofsingle-entry-monitor-time-of-flight-field NXxlaueplate NXxlaueplate/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxlaueplate.html#nxxlaueplate-entry-definition-field 0 1 NXxlaueplate/entry/instrument/detector/diameter The diameter of a cylindrical detector https://manual.nexusformat.org/classes/applications/NXxlaueplate.html#nxxlaueplate-entry-instrument-detector-diameter-field NXxrot NXxrot/entry/definition Official NeXus NXDL schema to which this file conforms. https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-definition-field 0 1 NXxrot/entry/instrument/detector/polar_angle The polar_angle (two theta) where the detector is placed. https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-detector-polar-angle-field 0 1 NXxrot/entry/instrument/detector/beam_center_x 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. https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-detector-beam-center-x-field 0 1 NXxrot/entry/instrument/detector/beam_center_y 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. https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-detector-beam-center-y-field 0 1 NXxrot/entry/instrument/attenuator/attenuator_transmission https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-instrument-attenuator-attenuator-transmission-field 0 1 NXxrot/entry/sample/rotation_angle This is an array holding the sample rotation start angle at each scan point https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-sample-rotation-angle-field 0 1 NXxrot/entry/sample/rotation_angle_step This is an array holding the step made for sample rotation angle at each scan point https://manual.nexusformat.org/classes/applications/NXxrot.html#nxxrot-entry-sample-rotation-angle-step-field 0 1 NXxbase/entry/title https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-title-field 0 1 NXxbase/entry/start_time https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-start-time-field NXxbase NXxbase/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-definition-field 0 1 NXxbase/entry/instrument/source/type https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-source-type-field 0 1 NXxbase/entry/instrument/source/name https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-source-name-field neutron x-ray electron NXxbase/entry/instrument/source/probe https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-source-probe-field 0 1 NXxbase/entry/instrument/monochromator/wavelength https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-monochromator-wavelength-field 0 1 1 NXxbase/entry/instrument/detector/data The area detector data, the first dimension is always the number of scan points, the second and third are the number of pixels in x and y. The origin is always assumed to be in the center of the detector. maxOccurs is limited to the the number of detectors on your instrument. https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-data-field 0 1 NXxbase/entry/instrument/detector/x_pixel_size https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-x-pixel-size-field 0 1 NXxbase/entry/instrument/detector/y_pixel_size https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-y-pixel-size-field 0 1 NXxbase/entry/instrument/detector/distance https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-distance-field 0 1 NXxbase/entry/instrument/detector/frame_start_number This is the start number of the first frame of a scan. In PX one often scans a couple of frames on a give sample, then does something else, then returns to the same sample and scans some more frames. Each time with a new data file. This number helps concatenating such measurements. https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-frame-start-number-field 0 1 NXxbase/entry/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-name-field 0 1 NXxbase/entry/sample/orientation_matrix The orientation matrix according to Busing and Levy conventions. This is not strictly necessary as the UB can always be derived from the data. But let us bow to common usage which includes the UB nearly always. https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-orientation-matrix-field 0 1 NXxbase/entry/sample/unit_cell The unit cell, a, b, c, alpha, beta, gamma. Again, not strictly necessary, but normally written. https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-unit-cell-field 0 1 NXxbase/entry/sample/temperature The sample temperature or whatever sensor represents this value best https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-temperature-field 0 1 NXxbase/entry/sample/x_translation Translation of the sample along the X-direction of the laboratory coordinate system https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-x-translation-field 0 1 NXxbase/entry/sample/y_translation Translation of the sample along the Y-direction of the laboratory coordinate system https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-y-translation-field 0 1 NXxbase/entry/sample/distance Translation of the sample along the Z-direction of the laboratory coordinate system https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-sample-distance-field monitor timer NXxbase/entry/control/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-control-mode-field 0 1 NXxbase/entry/control/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-control-preset-field 0 1 NXxbase/entry/control/integral Total integral monitor counts https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-control-integral-field 0 1 NXxasproc/ENTRY/title https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-title-field NXxasproc NXxasproc/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-definition-field 0 1 NXxasproc/ENTRY/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-sample-name-field 0 1 NXxasproc/ENTRY/XAS_data_reduction/program Name of the program used for reconstruction https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-xas-data-reduction-program-field 0 1 NXxasproc/ENTRY/XAS_data_reduction/version Version of the program used https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-xas-data-reduction-version-field 0 1 NXxasproc/ENTRY/XAS_data_reduction/date Date and time of reconstruction processing. https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-xas-data-reduction-date-field 0 1 NXxasproc/ENTRY/XAS_data_reduction/parameters/raw_file Original raw data file this data was derived from https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-xas-data-reduction-parameters-raw-file-field 0 1 NXxasproc/ENTRY/DATA/energy https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-data-energy-field 0 1 NXxasproc/ENTRY/DATA/data This is corrected and calibrated I(incoming)/I(absorbed). So it is the absorption. Expect attribute ``signal=1`` https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-data-data-field 0 1 NXtofraw/entry/title https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-title-field 0 1 NXtofraw/entry/start_time https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-start-time-field NXtofraw NXtofraw/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-definition-field 0 1 NXtofraw/entry/duration https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-duration-field 0 1 NXtofraw/entry/run_number https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-run-number-field 0 1 NXtofraw/entry/pre_sample_flightpath This is the flight path before the sample position. This can be determined by a chopper, by the moderator, or the source itself. In other words: it is the distance to the component which gives the T0 signal to the detector electronics. If another component in the NXinstrument hierarchy provides this information, this should be a link. https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-pre-sample-flightpath-field 0 1 NXtofraw/entry/user/name https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-user-name-field 0 1 NXtofraw/entry/instrument/detector/data https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-data-field 0 1 NXtofraw/entry/instrument/detector/detector_number https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-detector-number-field 0 1 NXtofraw/entry/instrument/detector/distance distance to sample for each detector https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-distance-field 0 1 NXtofraw/entry/instrument/detector/time_of_flight https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-time-of-flight-field 0 1 NXtofraw/entry/instrument/detector/polar_angle polar angle for each detector element https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-polar-angle-field 0 1 NXtofraw/entry/instrument/detector/azimuthal_angle azimuthal angle for each detector element https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-instrument-detector-azimuthal-angle-field 0 1 NXtofraw/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-sample-name-field powder liquid single crystal NXtofraw/entry/SAMPLE/nature https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-sample-nature-field monitor timer NXtofraw/entry/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-mode-field 0 1 NXtofraw/entry/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-preset-field 0 1 NXtofraw/entry/MONITOR/distance https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-distance-field 0 1 NXtofraw/entry/MONITOR/data https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-data-field 0 1 NXtofraw/entry/MONITOR/time_of_flight https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-time-of-flight-field 0 1 NXtofraw/entry/MONITOR/integral_counts https://manual.nexusformat.org/classes/applications/NXtofraw.html#nxtofraw-entry-monitor-integral-counts-field 0 1 NXtas/entry/title https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-title-field 0 1 NXtas/entry/start_time https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-start-time-field NXtas NXtas/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-definition-field 0 1 NXtas/entry/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-source-name-field neutron x-ray NXtas/entry/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-source-probe-field 0 1 NXtas/entry/INSTRUMENT/monochromator/ei https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-monochromator-ei-field 0 1 NXtas/entry/INSTRUMENT/monochromator/rotation_angle https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-monochromator-rotation-angle-field 0 1 NXtas/entry/INSTRUMENT/analyser/ef https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-analyser-ef-field 0 1 NXtas/entry/INSTRUMENT/analyser/rotation_angle https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-analyser-rotation-angle-field 0 1 NXtas/entry/INSTRUMENT/analyser/polar_angle https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-analyser-polar-angle-field 0 1 NXtas/entry/INSTRUMENT/DETECTOR/data https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-detector-data-field 0 1 NXtas/entry/INSTRUMENT/DETECTOR/polar_angle https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-instrument-detector-polar-angle-field 0 1 NXtas/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-name-field 0 1 NXtas/entry/SAMPLE/qh https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-qh-field 0 1 NXtas/entry/SAMPLE/qk https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-qk-field 0 1 NXtas/entry/SAMPLE/ql https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-ql-field 0 1 NXtas/entry/SAMPLE/en https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-en-field 0 1 NXtas/entry/SAMPLE/rotation_angle https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-rotation-angle-field 0 1 NXtas/entry/SAMPLE/polar_angle https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-polar-angle-field 0 1 NXtas/entry/SAMPLE/sgu https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-sgu-field 0 1 NXtas/entry/SAMPLE/sgl https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-sgl-field 0 1 NXtas/entry/SAMPLE/unit_cell https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-unit-cell-field 0 1 NXtas/entry/SAMPLE/orientation_matrix https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-sample-orientation-matrix-field monitor timer NXtas/entry/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-monitor-mode-field 0 1 NXtas/entry/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-monitor-preset-field 0 1 NXtas/entry/MONITOR/data Total integral monitor counts https://manual.nexusformat.org/classes/applications/NXtas.html#nxtas-entry-monitor-data-field 0 1 NXsastof/ENTRY/title https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-title-field 0 1 NXsastof/ENTRY/start_time https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-start-time-field NXsastof NXsastof/ENTRY/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-definition-field 0 1 NXsastof/ENTRY/instrument/source/type type of radiation source https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-source-type-field 0 1 NXsastof/ENTRY/instrument/source/name Name of the radiation source https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-source-name-field neutron x-ray NXsastof/ENTRY/instrument/source/probe https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-source-probe-field nxcylinder nxbox NXsastof/ENTRY/instrument/collimator/geometry/shape/shape https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-collimator-geometry-shape-shape-field 0 1 NXsastof/ENTRY/instrument/collimator/geometry/shape/size The collimation length https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-collimator-geometry-shape-size-field 0 1 NXsastof/ENTRY/instrument/detector/data 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. https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-data-field 0 1 NXsastof/ENTRY/instrument/detector/time_of_flight https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-time-of-flight-field 0 1 NXsastof/ENTRY/instrument/detector/distance The distance between detector and sample https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-distance-field 0 1 NXsastof/ENTRY/instrument/detector/x_pixel_size Physical size of a pixel in x-direction https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-x-pixel-size-field 0 1 NXsastof/ENTRY/instrument/detector/y_pixel_size Size of a pixel in y direction https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-y-pixel-size-field 0 1 NXsastof/ENTRY/instrument/detector/polar_angle https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-polar-angle-field 0 1 NXsastof/ENTRY/instrument/detector/azimuthal_angle https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-azimuthal-angle-field 0 1 NXsastof/ENTRY/instrument/detector/rotation_angle https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-rotation-angle-field 0 1 NXsastof/ENTRY/instrument/detector/aequatorial_angle https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-aequatorial-angle-field 0 1 NXsastof/ENTRY/instrument/detector/beam_center_x 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. https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-beam-center-x-field 0 1 NXsastof/ENTRY/instrument/detector/beam_center_y 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. https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-detector-beam-center-y-field 0 1 NXsastof/ENTRY/instrument/name Name of the instrument actually used to perform the experiment https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-instrument-name-field 0 1 NXsastof/ENTRY/sample/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-sample-name-field 0 1 NXsastof/ENTRY/sample/aequatorial_angle https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-sample-aequatorial-angle-field monitor timer NXsastof/ENTRY/control/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-control-mode-field 0 1 NXsastof/ENTRY/control/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-control-preset-field 0 1 NXsastof/ENTRY/control/data https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-control-data-field 0 1 NXsastof/ENTRY/control/time_of_flight https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-control-time-of-flight-field 0 1 NXmonopd/entry/title https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-title-field 0 1 NXmonopd/entry/start_time https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-start-time-field NXmonopd NXmonopd/entry/definition Official NeXus NXDL schema to which this file conforms https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-definition-field 0 1 NXmonopd/entry/INSTRUMENT/SOURCE/type https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-source-type-field 0 1 NXmonopd/entry/INSTRUMENT/SOURCE/name https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-source-name-field neutron x-ray electron NXmonopd/entry/INSTRUMENT/SOURCE/probe https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-source-probe-field 0 1 NXmonopd/entry/INSTRUMENT/CRYSTAL/wavelength Optimum diffracted wavelength https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-crystal-wavelength-field 0 1 NXmonopd/entry/INSTRUMENT/DETECTOR/polar_angle https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-detector-polar-angle-field 0 1 NXmonopd/entry/INSTRUMENT/DETECTOR/data detector signal (usually counts) are already corrected for detector efficiency https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-instrument-detector-data-field 0 1 NXmonopd/entry/SAMPLE/name Descriptive name of sample https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-sample-name-field 0 1 NXmonopd/entry/SAMPLE/rotation_angle Optional rotation angle for the case when the powder diagram has been obtained through an omega-2theta scan like from a traditional single detector powder diffractometer https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-sample-rotation-angle-field monitor timer NXmonopd/entry/MONITOR/mode Count to a preset value based on either clock time (timer) or received monitor counts (monitor). https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-monitor-mode-field 0 1 NXmonopd/entry/MONITOR/preset preset value for time or monitor https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-monitor-preset-field 0 1 NXmonopd/entry/MONITOR/integral Total integral monitor counts https://manual.nexusformat.org/classes/applications/NXmonopd.html#nxmonopd-entry-monitor-integral-field 0 NXcrystal/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXcrystal.html#nxcrystal-default-attribute 0 NXcollimator/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXcollimator.html#nxcollimator-default-attribute 0 NXnote/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXnote.html#nxnote-default-attribute 0 NXpinhole/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXpinhole.html#nxpinhole-default-attribute 0 NXdetector_group/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXdetector_group.html#nxdetector-group-default-attribute 0 NXshape/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXshape.html#nxshape-default-attribute 0 NXbeam_stop/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXbeam_stop.html#nxbeam-stop-default-attribute 0 NXflipper/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXflipper.html#nxflipper-default-attribute 0 NXsubentry/default .. index:: find the default plottable data .. index:: plotting .. index:: default attribute value Declares which :ref:`NXdata` group contains the data to be shown by default. It is used to resolve ambiguity when one :ref:`NXdata` group exists. The value :ref:`names <validItemName>` the default :ref:`NXentry` group. The value must be the name of a child of the current group. The child must be a NeXus group or a link to a NeXus group. For more information about how NeXus identifies the default plottable data, see the :ref:`Find Plottable Data, v3 <Find-Plottable-Data-v3>` section. https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-default-attribute 0 NXsubentry/IDF_Version ISIS Muon IDF_Version https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-idf-version-attribute 0 NXsubentry/definition/version NXDL version number https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-definition-version-attribute 0 NXsubentry/definition/URL URL of NXDL file https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-definition-url-attribute 0 NXsubentry/definition_local/version NXDL version number https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-definition-local-version-attribute 0 NXsubentry/definition_local/URL URL of NXDL file https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-definition-local-url-attribute 0 NXsubentry/program_name/version Program version number https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-program-name-version-attribute 0 NXsubentry/program_name/configuration configuration of the program https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-program-name-configuration-attribute 0 NXsubentry/revision/comment https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-revision-comment-attribute image/* NXsubentry/thumbnail/mime_type The value should be an ``image/*`` https://manual.nexusformat.org/classes/base_classes/NXsubentry.html#nxsubentry-thumbnail-mime-type-attribute 0 NXprocess/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXprocess.html#nxprocess-default-attribute 0 NXparameters/term/units https://manual.nexusformat.org/classes/base_classes/NXparameters.html#nxparameters-term-units-attribute 0 NXparameters/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXparameters.html#nxparameters-default-attribute 0 NXfermi_chopper/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXfermi_chopper.html#nxfermi-chopper-default-attribute 0 NXcapillary/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXcapillary.html#nxcapillary-default-attribute 0 NXslit/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXslit.html#nxslit-default-attribute 0 NXfilter/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXfilter.html#nxfilter-default-attribute 3 NXdetector/time_of_flight/axis https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-time-of-flight-axis-attribute true 1 NXdetector/time_of_flight/primary https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-time-of-flight-primary-attribute true 0 NXdetector/time_of_flight/long_name Total time of flight https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-time-of-flight-long-name-attribute 0 NXdetector/raw_time_of_flight/frequency Clock frequency in Hz https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-raw-time-of-flight-frequency-attribute 0 NXdetector/data/long_name Title of measurement https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-data-long-name-attribute 0 NXdetector/data/check_sum Integral of data as check of data integrity https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-data-check-sum-attribute 1 NXdetector/x_pixel_offset/axis https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-x-pixel-offset-axis-attribute true 1 NXdetector/x_pixel_offset/primary https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-x-pixel-offset-primary-attribute true 0 NXdetector/x_pixel_offset/long_name x-axis offset from detector center https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-x-pixel-offset-long-name-attribute 2 NXdetector/y_pixel_offset/axis https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-y-pixel-offset-axis-attribute true 1 NXdetector/y_pixel_offset/primary https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-y-pixel-offset-primary-attribute true 0 NXdetector/y_pixel_offset/long_name y-axis offset from detector center https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-y-pixel-offset-long-name-attribute 3 NXdetector/z_pixel_offset/axis https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-z-pixel-offset-axis-attribute true 1 NXdetector/z_pixel_offset/primary https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-z-pixel-offset-primary-attribute true 0 NXdetector/z_pixel_offset/long_name y-axis offset from detector center https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-z-pixel-offset-long-name-attribute 0 NXdetector/crate/local_name Equivalent local term https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-crate-local-name-attribute 0 NXdetector/slot/local_name Equivalent local term https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-slot-local-name-attribute 0 NXdetector/input/local_name Equivalent local term https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-input-local-name-attribute efficiency NXdetector/efficiency/signal https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-efficiency-signal-attribute . . . . . . . . . . wavelength NXdetector/efficiency/axes https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-efficiency-axes-attribute 0 NXdetector/efficiency/wavelength_indices https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-efficiency-wavelength-indices-attribute 0 NXdetector/start_time/start https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-start-time-start-attribute 0 NXdetector/stop_time/start https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-stop-time-start-attribute 0 NXdetector/default https://manual.nexusformat.org/classes/base_classes/NXdetector.html#nxdetector-default-attribute 0 NXdisk_chopper/top_dead_center/start https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-top-dead-center-start-attribute 0 NXdisk_chopper/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXdisk_chopper.html#nxdisk-chopper-default-attribute 0 NXsource/name/short_name short name for source, perhaps the acronym https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-name-short-name-attribute 0 NXsource/last_fill/time date and time of the most recent injection. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-last-fill-time-attribute 0 NXsource/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXsource.html#nxsource-default-attribute 0 NXbending_magnet/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXbending_magnet.html#nxbending-magnet-default-attribute 0 NXentry/default .. index:: find the default plottable data .. index:: plotting .. index:: default attribute value Declares which :ref:`NXdata` group contains the data to be shown by default. It is used to resolve ambiguity when one :ref:`NXdata` group exists. The value :ref:`names <validItemName>` a child group. If that group itself has a ``default`` attribute, continue this chain until an :ref:`NXdata` group is reached. For more information about how NeXus identifies the default plottable data, see the :ref:`Find Plottable Data, v3 <Find-Plottable-Data-v3>` section. https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-default-attribute 0 NXentry/IDF_Version ISIS Muon IDF_Version https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-idf-version-attribute 0 NXentry/entry_identifier_uuid/version Version of UUID used https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-entry-identifier-uuid-version-attribute 0 NXentry/definition/version NXDL version number https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-definition-version-attribute 0 NXentry/definition/URL URL of NXDL file https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-definition-url-attribute 0 NXentry/definition_local/version NXDL version number https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-definition-local-version-attribute 0 NXentry/definition_local/URL URL of NXDL file https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-definition-local-url-attribute 0 NXentry/program_name/version Program version number https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-program-name-version-attribute 0 NXentry/program_name/configuration configuration of the program https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-program-name-configuration-attribute 0 NXentry/revision/comment https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-revision-comment-attribute image/* NXentry/thumbnail/type The mime type should be an ``image/*`` https://manual.nexusformat.org/classes/base_classes/NXentry.html#nxentry-thumbnail-type-attribute translation NXdetector_module/module_offset/transformation_type https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-module-offset-transformation-type-attribute 0 NXdetector_module/module_offset/vector Three values that define the axis for this transformation https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-module-offset-vector-attribute 0 NXdetector_module/module_offset/offset A fixed offset applied before the transformation (three vector components). https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-module-offset-offset-attribute 0 NXdetector_module/module_offset/offset_units Units of the offset. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-module-offset-offset-units-attribute 0 NXdetector_module/module_offset/depends_on Points to the path of the next element in the geometry chain. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-module-offset-depends-on-attribute translation NXdetector_module/fast_pixel_direction/transformation_type https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-fast-pixel-direction-transformation-type-attribute 0 NXdetector_module/fast_pixel_direction/vector Three values that define the axis for this transformation https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-fast-pixel-direction-vector-attribute 0 NXdetector_module/fast_pixel_direction/offset A fixed offset applied before the transformation (three vector components). https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-fast-pixel-direction-offset-attribute 0 NXdetector_module/fast_pixel_direction/offset_units Units of the offset. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-fast-pixel-direction-offset-units-attribute 0 NXdetector_module/fast_pixel_direction/depends_on Points to the path of the next element in the geometry chain. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-fast-pixel-direction-depends-on-attribute translation NXdetector_module/slow_pixel_direction/transformation_type https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-slow-pixel-direction-transformation-type-attribute 0 NXdetector_module/slow_pixel_direction/vector Three values that define the axis for this transformation https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-slow-pixel-direction-vector-attribute 0 NXdetector_module/slow_pixel_direction/offset A fixed offset applied before the transformation (three vector components). https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-slow-pixel-direction-offset-attribute 0 NXdetector_module/slow_pixel_direction/offset_units Units of the offset. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-slow-pixel-direction-offset-units-attribute 0 NXdetector_module/slow_pixel_direction/depends_on Points to the path of the next element in the geometry chain. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-slow-pixel-direction-depends-on-attribute 0 NXdetector_module/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXdetector_module.html#nxdetector-module-default-attribute 0 NXpositioner/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXpositioner.html#nxpositioner-default-attribute 0 NXfresnel_zone_plate/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXfresnel_zone_plate.html#nxfresnel-zone-plate-default-attribute 0 NXdata/signal .. index:: find the default plottable data .. index:: plotting .. index:: signal attribute value The value is the :ref:`name <validItemName>` of the signal that contains the default plottable data. This field or link *must* exist and be a direct child of this NXdata group. It is recommended (as of NIAC2014) to use this attribute rather than adding a signal attribute to the field. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-signal-attribute 0 NXdata/auxiliary_signals .. index:: plotting Array of strings holding the :ref:`names <validItemName>` of additional signals to be plotted with the :ref:`default signal </NXdata@signal-attribute>`. These fields or links *must* exist and be direct children of this NXdata group. Each auxiliary signal needs to be of the same shape as the default signal. .. NIAC2018: https://www.nexusformat.org/NIAC2018Minutes.html https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-auxiliary-signals-attribute 0 NXdata/default_slice Which slice of data to show in a plot by default. This is useful especially for datasets with more than 2 dimensions. Should be an array of length equal to the number of dimensions in the data, with the following possible values: * ".": All the data in this dimension should be included * Integer: Only this slice should be used. * String: Only this slice should be used. Use if ``AXISNAME`` is a string array. Example:: data:NXdata @signal = "data" @axes = ["image_id", "channel", ".", "."] @image_id_indices = 0 @channel_indices = 1 @default_slice = [".", "difference", ".", "."] image_id = [1, ..., nP] channel = ["threshold_1", "threshold_2", "difference"] data = uint[nP, nC, i, j] Here, a data array with four dimensions, including the number of images (nP) and number of channels (nC), specifies more dimensions than can be visualized with a 2D image viewer for a given image. Therefore the default_slice attribute specifies that the "difference" channel should be shown by default. Alternate version using an integer would look like this (note 2 is a string):: data:NXdata @signal = "data" @axes = ["image_id", "channel", ".", "."] @image_id_indices = 0 @channel_indices = 1 @default_slice = [".", "2", ".", "."] image_id = [1, ..., nP] channel = ["threshold_1", "threshold_2", "difference"] data = uint[nP, nC, i, j] https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-default-slice-attribute 0 NXdata/AXISNAME_indices The ``AXISNAME_indices`` attribute is a single integer or an array of integers that defines which :ref:`data </NXdata/DATA-field>` dimension(s) are spanned by the corresponding axis. The first dimension index is ``0`` (zero). When the ``AXISNAME_indices`` attribute is missing for an :ref:`AXISNAME </NXdata/AXISNAME-field>` field, its value becomes the index (or indices) of the :ref:`AXISNAME </NXdata/AXISNAME-field>` name in the :ref:`axes </NXdata@axes-attribute>` attribute. .. note:: When ``AXISNAME_indices`` contains multiple integers, it must be saved as an actual array of integers and not a comma separated string. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-indices-attribute 0 NXdata/axes .. index:: plotting The ``axes`` attribute is a list of strings which are the names of the :ref:`AXISNAME </NXdata/AXISNAME-field>` fields that contain the values of the coordinates along the :ref:`data </NXdata/DATA-field>` dimensions. .. note:: When ``axes`` contains multiple strings, it must be saved as an actual array of strings and not a single comma separated string. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axes-attribute 0 NXdata/AXISNAME/long_name Axis label https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-long-name-attribute 0 NXdata/AXISNAME/units Unit in which the coordinate values are expressed. See the section :ref:`Design-Units` for more information. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-units-attribute 0 NXdata/AXISNAME/distribution ``0|false``: single value, ``1|true``: multiple values https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-distribution-attribute 0 NXdata/AXISNAME/first_good Index of first good value https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-first-good-attribute 0 NXdata/AXISNAME/last_good Index of last good value https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-last-good-attribute 0 NXdata/AXISNAME/axis Index (positive integer) identifying this specific set of numbers. N.B. The ``axis`` attribute is the old way of designating a link. Do not use the :ref:`axes </NXdata@axes-attribute>` attribute with the ``axis`` attribute. The :ref:`axes </NXdata@axes-attribute>` attribute is now preferred. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-axisname-axis-attribute true 0 NXdata/DATA/signal .. index:: plotting Plottable (independent) axis, indicate index number. Only one field in a :ref:`NXdata` group may have the ``signal=1`` attribute. Do not use the ``signal`` attribute with the ``axis`` attribute. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-data-signal-attribute true 0 NXdata/DATA/axes Defines the names of the coordinates (independent axes) for this data set as a colon-delimited array. NOTE: The :ref:`axes </NXdata@axes-attribute>` attribute is the preferred method of designating a link. Do not use the :ref:`axes </NXdata@axes-attribute>` attribute with the ``axis`` attribute. https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-data-axes-attribute true 0 NXdata/DATA/long_name data label https://manual.nexusformat.org/classes/base_classes/NXdata.html#nxdata-data-long-name-attribute 0 NXcite/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXcite.html#nxcite-default-attribute 0 NXpolarizer/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXpolarizer.html#nxpolarizer-default-attribute 0 NXxraylens/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXxraylens.html#nxxraylens-default-attribute NXroot NXroot/NX_class The root of any NeXus data file is an ``NXroot`` class (no other choice is allowed for a valid NeXus data file). This attribute cements that definition. https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-nx-class-attribute 0 NXroot/file_time Date and time file was originally created https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-file-time-attribute 0 NXroot/file_name File name of original NeXus file https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-file-name-attribute 0 NXroot/file_update_time Date and time of last file change at close https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-file-update-time-attribute 0 NXroot/NeXus_version Version of NeXus API used in writing the file. Only used when the NAPI has written the file. Note that this is different from the version of the base class or application definition version number. https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-nexus-version-attribute 0 NXroot/HDF_version Version of HDF (version 4) library used in writing the file https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-hdf-version-attribute 0 NXroot/HDF5_Version Version of HDF5 library used in writing the file. Note this attribute is spelled with uppercase "V", different than other version attributes. https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-hdf5-version-attribute 0 NXroot/XML_version Version of XML support library used in writing the XML file https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-xml-version-attribute 0 NXroot/h5py_version Version of h5py Python package used in writing the file https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-h5py-version-attribute 0 NXroot/creator facility or program where file originated https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-creator-attribute 0 NXroot/creator_version Version of facility or program used in writing the file https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-creator-version-attribute 0 NXroot/default .. index:: find the default plottable data .. index:: plotting .. index:: default attribute value Declares which :ref:`NXentry` group contains the data to be shown by default. It is used to resolve ambiguity when more than one :ref:`NXentry` group exists. The value :ref:`names <validItemName>` the default :ref:`NXentry` group. The value must be the name of a child of the current group. The child must be a NeXus group or a link to a NeXus group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXroot.html#nxroot-default-attribute 0 NXcylindrical_geometry/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXcylindrical_geometry.html#nxcylindrical-geometry-default-attribute 0 NXinsertion_device/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXinsertion_device.html#nxinsertion-device-default-attribute translation rotation NXtransformations/AXISNAME/transformation_type The transformation_type may be ``translation``, in which case the values are linear displacements along the axis, ``rotation``, in which case the values are angular rotations around the axis. If this attribute is omitted, this is an axis for which there is no motion to be specifies, such as the direction of gravity, or the direction to the source, or a basis vector of a coordinate frame. In this case the value of the ``AXISNAME`` field is not used and can be set to the number ``NaN``. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-transformation-type-attribute 0 NXtransformations/AXISNAME/vector Three values that define the axis for this transformation. The axis should be normalized to unit length, making it dimensionless. For ``rotation`` axes, the direction should be chosen for a right-handed rotation with increasing angle. For ``translation`` axes the direction should be chosen for increasing displacement. For general axes, an appropriate direction should be chosen. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-vector-attribute 0 NXtransformations/AXISNAME/offset A fixed offset applied before the transformation (three vector components). This is not intended to be a substitute for a fixed ``translation`` axis but, for example, as the mechanical offset from mounting the axis to its dependency. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-offset-attribute 0 NXtransformations/AXISNAME/offset_units Units of the offset. Values should be consistent with NX_LENGTH. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-offset-units-attribute 0 NXtransformations/AXISNAME/depends_on Points to the path to a field defining the axis on which this depends or the string ".". https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-depends-on-attribute 0 NXtransformations/AXISNAME/equipment_component An arbitrary identifier of a component of the equipment to which the transformation belongs, such as 'detector_arm' or 'detector_module'. NXtransformations with the same equipment_component label form a logical grouping which can be combined together into a single change-of-basis operation. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-axisname-equipment-component-attribute 0 NXtransformations/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXtransformations.html#nxtransformations-default-attribute 0 NXsample_component/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXsample_component.html#nxsample-component-default-attribute 0 NXmonochromator/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXmonochromator.html#nxmonochromator-default-attribute 0 NXsensor/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXsensor.html#nxsensor-default-attribute 0 NXvelocity_selector/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXvelocity_selector.html#nxvelocity-selector-default-attribute x y z NXsample/electric_field/direction https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-electric-field-direction-attribute x y z NXsample/magnetic_field/direction https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-magnetic-field-direction-attribute x y z NXsample/stress_field/direction https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-stress-field-direction-attribute 0 NXsample/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXsample.html#nxsample-default-attribute 0 NXattenuator/status/time time stamp for this observation https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-status-time-attribute 0 NXattenuator/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXattenuator.html#nxattenuator-default-attribute 0 NXmirror/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXmirror.html#nxmirror-default-attribute 0 NXinstrument/name/short_name short name for instrument, perhaps the acronym https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-name-short-name-attribute 0 NXinstrument/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXinstrument.html#nxinstrument-default-attribute 0 NXmonitor/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXmonitor.html#nxmonitor-default-attribute 0 NXlog/time/start https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-time-start-attribute 0 NXlog/time/scaling_factor https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-time-scaling-factor-attribute 0 NXlog/cue_timestamp_zero/start If missing start is assumed to be the same as for "time". https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-cue-timestamp-zero-start-attribute 0 NXlog/cue_timestamp_zero/scaling_factor If missing start is assumed to be the same as for "time". https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-cue-timestamp-zero-scaling-factor-attribute 0 NXlog/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXlog.html#nxlog-default-attribute 0 NXtranslation/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXtranslation.html#nxtranslation-default-attribute 0 NXreflections/h/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-h-description-attribute 0 NXreflections/k/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-k-description-attribute 0 NXreflections/l/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-l-description-attribute 0 NXreflections/id/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-id-description-attribute 0 NXreflections/reflection_id/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-reflection-id-description-attribute 0 NXreflections/entering/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-entering-description-attribute 0 NXreflections/det_module/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-det-module-description-attribute 0 NXreflections/flags/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-flags-description-attribute 0 NXreflections/d/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-d-description-attribute 0 NXreflections/partiality/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-partiality-description-attribute 0 NXreflections/predicted_frame/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-frame-description-attribute 0 NXreflections/predicted_x/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-x-description-attribute 0 NXreflections/predicted_y/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-y-description-attribute 0 NXreflections/predicted_phi/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-phi-description-attribute 0 NXreflections/predicted_px_x/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-px-x-description-attribute 0 NXreflections/predicted_px_y/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-predicted-px-y-description-attribute 0 NXreflections/observed_frame/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-frame-description-attribute 0 NXreflections/observed_frame_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-frame-var-description-attribute 0 NXreflections/observed_frame_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-frame-errors-description-attribute 0 NXreflections/observed_px_x/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-x-description-attribute 0 NXreflections/observed_px_x_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-x-var-description-attribute 0 NXreflections/observed_px_x_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-x-errors-description-attribute 0 NXreflections/observed_px_y/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-y-description-attribute 0 NXreflections/observed_px_y_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-y-var-description-attribute 0 NXreflections/observed_px_y_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-px-y-errors-description-attribute 0 NXreflections/observed_phi/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-phi-description-attribute 0 NXreflections/observed_phi_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-phi-var-description-attribute 0 NXreflections/observed_phi_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-phi-errors-description-attribute 0 NXreflections/observed_x/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-x-description-attribute 0 NXreflections/observed_x_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-x-var-description-attribute 0 NXreflections/observed_x_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-x-errors-description-attribute 0 NXreflections/observed_y/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-y-description-attribute 0 NXreflections/observed_y_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-y-var-description-attribute 0 NXreflections/observed_y_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-observed-y-errors-description-attribute 0 NXreflections/bounding_box/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-bounding-box-description-attribute 0 NXreflections/background_mean/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-background-mean-description-attribute 0 NXreflections/int_prf/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-prf-description-attribute 0 NXreflections/int_prf_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-prf-var-description-attribute 0 NXreflections/int_prf_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-prf-errors-description-attribute 0 NXreflections/int_sum/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-sum-description-attribute 0 NXreflections/int_sum_var/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-sum-var-description-attribute 0 NXreflections/int_sum_errors/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-int-sum-errors-description-attribute 0 NXreflections/lp/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-lp-description-attribute 0 NXreflections/prf_cc/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-prf-cc-description-attribute 0 NXreflections/overlaps/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-overlaps-description-attribute 0 NXreflections/polar_angle/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-polar-angle-description-attribute 0 NXreflections/description Describes the dataset https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-description-attribute 0 NXreflections/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXreflections.html#nxreflections-default-attribute 0 NXgeometry/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXgeometry.html#nxgeometry-default-attribute 0 NXgrating/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXgrating.html#nxgrating-default-attribute 0 NXoff_geometry/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXoff_geometry.html#nxoff-geometry-default-attribute 0 NXbeam/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-default-attribute translation NXbeam/TRANSFORMATIONS/DIRECTION/transformation_type https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-direction-transformation-type-attribute 0 NXbeam/TRANSFORMATIONS/DIRECTION/vector Three values that define the direction of beam vector https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-direction-vector-attribute 0 NXbeam/TRANSFORMATIONS/DIRECTION/offset Three values that define the location of a point through which the beam passes https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-direction-offset-attribute 0 NXbeam/TRANSFORMATIONS/DIRECTION/depends_on Points to the path to a field defining the location on which this depends or the string "." for origin. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-direction-depends-on-attribute translation NXbeam/TRANSFORMATIONS/reference_plane/transformation_type https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-reference-plane-transformation-type-attribute 0 NXbeam/TRANSFORMATIONS/reference_plane/vector Three values that define the direction of reference plane normal https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-reference-plane-vector-attribute 0 NXbeam/TRANSFORMATIONS/reference_plane/offset Not required as beam direction offset locates the plane https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-reference-plane-offset-attribute 0 NXbeam/TRANSFORMATIONS/reference_plane/depends_on Points to the path to a field defining the location on which this depends or the string "." for origin. https://manual.nexusformat.org/classes/base_classes/NXbeam.html#nxbeam-transformations-reference-plane-depends-on-attribute 0 NXaperture/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXaperture.html#nxaperture-default-attribute 0 NXmoderator/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXmoderator.html#nxmoderator-default-attribute 0 NXevent_data/event_time_zero/offset ISO8601 https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-event-time-zero-offset-attribute 0 NXevent_data/cue_timestamp_zero/start https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-cue-timestamp-zero-start-attribute 0 NXevent_data/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXevent_data.html#nxevent-data-default-attribute 0 NXorientation/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXorientation.html#nxorientation-default-attribute 0 NXuser/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXuser.html#nxuser-default-attribute data NXguide/reflectivity/signal https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-signal-attribute surface wavelength NXguide/reflectivity/axes https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-axes-attribute 0 NXguide/reflectivity/surface_indices https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-surface-indices-attribute 1 NXguide/reflectivity/wavelength_indices https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-reflectivity-wavelength-indices-attribute 0 NXguide/default .. index:: plotting Declares which child group contains a path leading to a :ref:`NXdata` group. It is recommended (as of NIAC2014) to use this attribute to help define the path to the default dataset to be plotted. See https://www.nexusformat.org/2014_How_to_find_default_data.html for a summary of the discussion. https://manual.nexusformat.org/classes/base_classes/NXguide.html#nxguide-default-attribute 0 NXcanSAS/ENTRY/default .. index:: plotting Declares which :ref:`NXdata` group contains the data to be shown by default. It is needed to resolve ambiguity when more than one :ref:`NXdata` group exists. The value is the name of the default :ref:`NXdata` group. Usually, this will be the name of the first *SASdata* group. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-default-attribute SASentry NXcanSAS/ENTRY/canSAS_class Official canSAS group: **SASentry** https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-cansas-class-attribute 1.1 NXcanSAS/ENTRY/version Describes the version of the canSAS standard used to write this data. This must be a text (not numerical) representation. Such as:: @version="1.1" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-version-attribute SASdata NXcanSAS/ENTRY/DATA/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASdata` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-cansas-class-attribute I NXcanSAS/ENTRY/DATA/signal Name of the default data field. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-signal-attribute 0 NXcanSAS/ENTRY/DATA/I_axes String array that defines the independent data fields used in the default plot for all of the dimensions of the *signal* field (the *signal* field is the field in this group that is named by the ``signal`` attribute of this group). One entry is provided for every dimension of the ``I`` data object. Such as:: @I_axes="Temperature", "Time", "Pressure", "Q", "Q" Since there are five items in the list, the intensity field of this example ``I`` must be a five-dimensional array (rank=5). https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-i-axes-attribute 0 NXcanSAS/ENTRY/DATA/Q_indices Integer or integer array that describes which indices (of the :math:`I` data object) are used to reference the ``Q`` data object. The items in this array use zero-based indexing. Such as:: @Q_indices=1,3,4 which indicates that ``Q`` requires three indices from the :math:`I` data object: one for time and two for Q position. Thus, in this example, the ``Q`` data is time-dependent: :math:`\vec{Q}(t)`. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-q-indices-attribute 0 NXcanSAS/ENTRY/DATA/mask Name of the data mask field. .. see: https://github.com/nexusformat/definitions/issues/533 The data *mask* must have the same shape as the *data* field. Positions in the mask correspond to positions in the *data* field. The value of the mask field may be either a boolean array where ``false`` means *no mask* and ``true`` means *mask* or a more descriptive array as as defined in :ref:`NXdetector`. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-mask-attribute 0 NXcanSAS/ENTRY/DATA/Mask_indices Integer or integer array that describes which indices (of the :math:`I` data object) are used to reference the ``Mask`` data object. The items in this array use zero-based indexing. Such as:: @Mask_indices=3,4 which indicates that Q requires two indices from the :math:`I` data object for Q position. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-mask-indices-attribute 0 NXcanSAS/ENTRY/DATA/timestamp ISO-8601 time [#iso8601]_ https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-timestamp-attribute 1/m 1/nm 1/angstrom NXcanSAS/ENTRY/DATA/Q/units Engineering units to use when expressing :math:`Q` and related terms. Data expressed in other units will generate a warning from validation software and may not be processed by some analysis software packages. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-q-units-attribute 0 NXcanSAS/ENTRY/DATA/Q/uncertainties (optional: for numerical arrays) Names the dataset (in this SASdata group) that provides the uncertainty to be used for data analysis. The name of the dataset containing the :math:`Q` uncertainty is flexible. The name must be unique in the *SASdata* group. .. comment see: https://github.com/canSAS-org/canSAS2012/issues/7 Such as:: @uncertainties="Q_uncertainties" The *uncertainties* field will have the same *shape* (dimensions) as the Q field. These values are the estimates of uncertainty of each Q. By default, this will be interpreted to be the estimated standard deviation. In special cases, when a standard deviation cannot possibly be used, its value can specify another measure of distribution width. There may also be a subdirectory (optional) with constituent components. .. note:: To report distribution in reported :math:`Q` values, use the ``@resolutions`` attribute. It is possible for both ``@resolutions`` and ``uncertainties`` to be reported. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-q-uncertainties-attribute 0 NXcanSAS/ENTRY/DATA/Q/resolutions .. index:: NXcanSAS (applications); resolutions (optional: for numerical arrays) Names the dataset (in this SASdata group) containing the :math:`Q` resolution. The name of the dataset containing the :math:`Q` resolution is flexible. The name must be unique in the *SASdata* group. .. comment see: https://github.com/canSAS-org/canSAS2012/issues/7 The *resolutions* field will have the same *shape* (dimensions) as the Q field. Generally, this is the principal resolution of each :math:`Q`. Names the data object (in this SASdata group) that provides the :math:`Q` resolution to be used for data analysis. Such as:: @resolutions="Qdev" To specify two-dimensional resolution for slit-smearing geometry, such as (*dQw*, *dQl*), use a string array, such as:: @resolutions="dQw", "dQl" There may also be a subdirectory (optional) with constituent components. This pattern will demonstrate how to introduce further as-yet unanticipated terms related to the data. .. comment see: https://github.com/nexusformat/definitions/issues/492#issuecomment-262813907 By default, the values of the resolutions data object are assumed to be one standard deviation of any function used to approximate the resolution function. This equates to the width of the gaussian distribution if a Gaussian is chosen. See the ``@resolutions_description`` attribute. .. note:: To report uncertainty in reported :math:`Q` values, use the ``@uncertainties`` attribute. It is possible for both ``@resolutions`` and ``uncertainties`` to be reported. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-q-resolutions-attribute 0 NXcanSAS/ENTRY/DATA/Q/resolutions_description (optional) Generally, this describes the :math:`Q` ``@resolutions`` data object. By default, the value is assumed to be "Gaussian". These are suggestions: * Gaussian * Lorentzian * Square : note that the full width of the square would be ~2.9 times the standard deviation specified in the vector * Triangular * Sawtooth-outward : vertical edge pointing to larger Q * Sawtooth-inward vertical edge pointing to smaller Q * Bin : range of values contributing (for example, when 2-D detector data have been reduced to a 1-D :math:`I(|Q|)` dataset) For other meanings, it may be necessary to provide further details such as the function used to assess the resolution. In such cases, use additional datasets or a :ref:`NXnote` subgroup to include that detail. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-q-resolutions-description-attribute 1/m 1/cm m2/g cm2/g arbitrary NXcanSAS/ENTRY/DATA/I/units Engineering units to use when expressing :math:`I` and intensity-related terms. Data expressed in other units (or missing a ``@units`` attribute) will be treated as ``arbitrary`` by some software packages. For software using the UDUNITS-2 library, ``arbitrary`` will be changed to ``unknown`` for handling with that library. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-i-units-attribute 0 NXcanSAS/ENTRY/DATA/I/uncertainties (optional: for numerical arrays) Names the dataset (in this SASdata group) that provides the uncertainty of :math:`I` to be used for data analysis. The name of the dataset containing the :math:`I` uncertainty is flexible. The name must be unique in the *SASdata* group. .. comment see: https://github.com/canSAS-org/canSAS2012/issues/7 Generally, this is the estimate of the uncertainty of each :math:`I`. Typically the estimated standard deviation. *Idev* is the canonical name from the 1D standard. The NXcanSAS standard allows for the name to be described using this attribute. Such as:: @uncertainties="Idev" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-i-uncertainties-attribute 0 NXcanSAS/ENTRY/DATA/I/scaling_factor (optional) Names the field (a.k.a. dataset) that contains a factor to multiply ``I``. By default, this value is unity. Should an uncertainty be associated with the scaling factor field, the field containing that uncertainty would be designated via the ``uncertainties`` attribute. Such as:: I : NX_NUMBER @uncertainties="Idev" : NX_CHAR @scaling_factor="I_scaling" : NX_CHAR Idev : NX_NUMBER I_scaling : NX_NUMBER @uncertainties="I_scaling_dev" : NX_CHAR I_scaling_dev : NX_NUMBER The exact names for ``I_scaling`` and ``I_scaling_dev`` are not defined by NXcanSAS. The user has the flexibility to use names different than those shown in this example. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-i-scaling-factor-attribute 1/m 1/cm m2/g cm2/g arbitrary NXcanSAS/ENTRY/DATA/Idev/units Engineering units to use when expressing :math:`I` and intensity-related terms. Data expressed in other units (or missing a ``@units`` attribute) will generate a warning from any validation process and will be treated as ``arbitrary`` by some analysis software packages. For software using the UDUNITS-2 library, ``arbitrary`` will be changed to ``unknown`` for handling with that library. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-idev-units-attribute 1/m 1/nm 1/angstrom NXcanSAS/ENTRY/DATA/Qdev/units Engineering units to use when expressing :math:`Q` and related terms. Data expressed in other units may not be processed by some software packages. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-qdev-units-attribute 1/m 1/nm 1/angstrom NXcanSAS/ENTRY/DATA/dQw/units Engineering units to use when expressing :math:`Q` and related terms. Data expressed in other units may not be processed by some software packages. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-dqw-units-attribute 1/m 1/nm 1/angstrom NXcanSAS/ENTRY/DATA/dQl/units Engineering units to use when expressing :math:`Q` and related terms. Data expressed in other units may not be processed by some software packages. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-dql-units-attribute 1/m 1/nm 1/angstrom NXcanSAS/ENTRY/DATA/Qmean/units Engineering units to use when expressing :math:`Q` and related terms. Data expressed in other units may not be processed by some software packages. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-data-qmean-units-attribute 0 NXcanSAS/ENTRY/run/name Optional string attribute to identify this particular *run*. Could use this to associate (correlate) multiple *SASdata* elements with *run* elements. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-run-name-attribute SASinstrument NXcanSAS/ENTRY/INSTRUMENT/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASinstrument` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-cansas-class-attribute SASaperture NXcanSAS/ENTRY/INSTRUMENT/APERTURE/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASaperture` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-aperture-cansas-class-attribute SAScollimation NXcanSAS/ENTRY/INSTRUMENT/COLLIMATOR/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SAScollimation` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-collimator-cansas-class-attribute SASdetector NXcanSAS/ENTRY/INSTRUMENT/DETECTOR/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASdetector` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-detector-cansas-class-attribute SASsource NXcanSAS/ENTRY/INSTRUMENT/SOURCE/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASsource` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-instrument-source-cansas-class-attribute SASsample NXcanSAS/ENTRY/SAMPLE/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASsample` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-sample-cansas-class-attribute SASprocess NXcanSAS/ENTRY/PROCESS/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASprocess` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-cansas-class-attribute SASprocessnote NXcanSAS/ENTRY/PROCESS/COLLECTION/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASprocessnote` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-process-collection-cansas-class-attribute SASnote NXcanSAS/ENTRY/COLLECTION/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SASnote` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-collection-cansas-class-attribute SAStransmission_spectrum NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/canSAS_class Official canSAS group: :index:`NXcanSAS (applications); SAStransmission_spectrum` https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-cansas-class-attribute T NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/signal Name of the default data field. https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-signal-attribute T NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/T_axes https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-t-axes-attribute 0 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/name Identify what type of spectrum is being described. It is expected that this value will take either of these two values: ====== ============================================== value meaning ====== ============================================== sample measurement with the sample and container can measurement with just the container ====== ============================================== https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-name-attribute 0 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/timestamp https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-timestamp-attribute 0 NXcanSAS/ENTRY/TRANSMISSION_SPECTRUM/T/uncertainties Names the dataset (in this SASdata group) that provides the uncertainty of each transmission :math:`T` to be used for data analysis. The name of the dataset containing the :math:`T` uncertainty is expected to be ``Tdev``. .. comment see: https://github.com/canSAS-org/canSAS2012/issues/7 Typically: @uncertainties="Tdev" https://manual.nexusformat.org/classes/applications/NXcanSAS.html#nxcansas-entry-transmission-spectrum-t-uncertainties-attribute 1 NXlauetof/entry/instrument/detector/data/signal https://manual.nexusformat.org/classes/applications/NXlauetof.html#nxlauetof-entry-instrument-detector-data-signal-attribute 0 NXxas/ENTRY/entry NeXus convention is to use "entry1", "entry2", ... for analysis software to locate each entry. https://manual.nexusformat.org/classes/applications/NXxas.html#nxxas-entry-entry-attribute 1.0 NXmx/ENTRY/version Describes the version of the NXmx definition used to write this data. This must be a text (not numerical) representation. Such as:: @version="1.0" https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-version-attribute 0 NXmx/ENTRY/INSTRUMENT/name/short_name Short name for instrument, perhaps the acronym. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-name-short-name-attribute translation NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/module_offset/transformation_type https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-module-offset-transformation-type-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/module_offset/vector https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-module-offset-vector-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/module_offset/offset https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-module-offset-offset-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/module_offset/depends_on https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-module-offset-depends-on-attribute translation NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/fast_pixel_direction/transformation_type https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-fast-pixel-direction-transformation-type-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/fast_pixel_direction/vector https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-fast-pixel-direction-vector-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/fast_pixel_direction/offset https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-fast-pixel-direction-offset-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/fast_pixel_direction/depends_on https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-fast-pixel-direction-depends-on-attribute translation NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/slow_pixel_direction/transformation_type https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-slow-pixel-direction-transformation-type-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/slow_pixel_direction/vector https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-slow-pixel-direction-vector-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/slow_pixel_direction/offset https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-slow-pixel-direction-offset-attribute 0 NXmx/ENTRY/INSTRUMENT/DETECTOR/DETECTOR_MODULE/slow_pixel_direction/depends_on https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-detector-detector-module-slow-pixel-direction-depends-on-attribute 0 NXmx/ENTRY/INSTRUMENT/BEAM/flux Which field contains the measured flux. One of ``flux``, ``total_flux``, ``flux_integrated``, or ``total_flux_integrated``. Alternatively, the name being indicated could be a link to a dataset in an NXmonitor group that records per shot beam data. https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-instrument-beam-flux-attribute 0 NXmx/ENTRY/SOURCE/name/short_name short name for source, perhaps the acronym https://manual.nexusformat.org/classes/applications/NXmx.html#nxmx-entry-source-name-short-name-attribute 0 NXtomoproc/entry/data/data/transform https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-data-transform-attribute 0 NXtomoproc/entry/data/data/offset https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-data-offset-attribute 0 NXtomoproc/entry/data/data/scaling https://manual.nexusformat.org/classes/applications/NXtomoproc.html#nxtomoproc-entry-data-data-scaling-attribute 0 NXarpes/ENTRY/entry NeXus convention is to use "entry1", "entry2", ... for analysis software to locate each entry. https://manual.nexusformat.org/classes/applications/NXarpes.html#nxarpes-entry-entry-attribute 0 NXiqproc/ENTRY/entry https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-entry-attribute 0 NXiqproc/ENTRY/DATA/variable/varied_variable The real name of the varied variable in the first dim of data, temperature, P, MF etc... https://manual.nexusformat.org/classes/applications/NXiqproc.html#nxiqproc-entry-data-variable-varied-variable-attribute data NXsas/ENTRY/DATA/signal Name the *plottable* field. The link here defines this name as ``data``. https://manual.nexusformat.org/classes/applications/NXsas.html#nxsas-entry-data-signal-attribute 0 NXspe/ENTRY/definition/version https://manual.nexusformat.org/classes/applications/NXspe.html#nxspe-entry-definition-version-attribute 0 NXsqom/ENTRY/entry https://manual.nexusformat.org/classes/applications/NXsqom.html#nxsqom-entry-entry-attribute 0 NXarchive/entry/index https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-index-attribute 0 NXarchive/entry/program/version https://manual.nexusformat.org/classes/applications/NXarchive.html#nxarchive-entry-program-version-attribute 1 NXxbase/entry/instrument/detector/data/signal https://manual.nexusformat.org/classes/applications/NXxbase.html#nxxbase-entry-instrument-detector-data-signal-attribute 0 NXxasproc/ENTRY/entry NeXus convention is to use "entry1", "entry2", ... for analysis software to locate each entry. https://manual.nexusformat.org/classes/applications/NXxasproc.html#nxxasproc-entry-entry-attribute 0 NXsastof/ENTRY/entry NeXus convention is to use "entry1", "entry2", ... for analysis software to locate each entry https://manual.nexusformat.org/classes/applications/NXsastof.html#nxsastof-entry-entry-attribute