These symbols will be used below to coordinate datasets with the same shape. number of scan points (only present in scanning measurements) number of detector pixels in the first (X, slowest) direction number of detector pixels in the second (Y, faster) direction number of detector pixels in the third (Z, if necessary, fastest) direction number of bins in the time-of-flight histogram A detector, detector bank, or multidetector. Total time of flight Total time of flight In DAQ clock pulses Clock frequency in Hz Identifier for detector (pixels) Can be multidimensional, if needed Data values from the detector. Title of measurement Integral of data as check of data integrity The best estimate of the uncertainty in the data value. Where possible, this should be the standard deviation, which has the same units as the data. Offset from the detector center in x-direction. Can be multidimensional when needed. x-axis offset from detector center Offset from the detector center in the y-direction. Can be multidimensional when different values are required for each pixel. y-axis offset from detector center Offset from the detector center in the z-direction. Can be multidimensional when different values are required for each pixel. y-axis offset from detector center 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. 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. 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. name/manufacturer/model/etc. information Serial number for the detector Local name for the detector Position and orientation of detector Solid angle subtended by the detector at the sample Size of each detector pixel. If it is scalar all pixels are the same size. Size of each detector pixel. If it is scalar all pixels are the same size Detector dead time Detector gas pressure maximum drift space dimension Crate number of detector Equivalent local term Slot number of detector Equivalent local term Input number of detector Equivalent local term Description of type such as He3 gas cylinder, He3 PSD, scintillator, fission chamber, proportion counter, ion chamber, ccd, pixel, image plate, CMOS, ... Spectral efficiency of detector with respect to e.g. wavelength efficiency of the detector This field can be two things: #. For a pixel detector it provides the nominal wavelength for which the detector has been calibrated. #. For other detectors this field has to be seen together with the efficiency field above. For some detectors, the efficiency is wavelength dependent. Thus this field provides the wavelength axis for the efficiency field. In this use case, the efficiency and wavelength arrays must have the same dimensionality. start time for each frame, with the ``start`` attribute as absolute reference stop time for each frame, with the ``start`` attribute as absolute reference real-time of the exposure (use this if exposure time varies for each array element, otherwise use ``count_time`` field) date of last calibration (geometry and/or efficiency) measurements summary of conversion of array data to pixels (e.g. polynomial approximations) and location of details of the calibrations How the detector is represented Elapsed actual counting time Use this group to provide other data related to this NXdetector group. 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. 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. 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. 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. The diameter of a cylindrical detector The acquisition mode of the detector. True when the angular calibration has been applied in the electronics, false otherwise. Angular calibration data. True when the flat field correction has been applied in the electronics, false otherwise. Flat field correction data. Errors of the flat field correction data. True when the pixel mask correction has been applied in the electronics, false otherwise. 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. True when a count-rate correction has already been applied in the electronics, false otherwise. 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, ... Time it takes to read the detector (typically milliseconds). This is important to know for time resolved experiments. 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. User-specified trigger delay. 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. 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. This is time for each frame. This is exposure_time + readout time. The gain setting of the detector. This influences background etc. 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 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. 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. 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. 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. Single photon counter detectors can be adjusted for a certain energy range in which they work optimally. This is the energy setting for this. For use in special cases where the data in NXdetector is represented in several parts, each with a separate geometry. Use one or more instances of the NXdetector_module group to declare regions of interest or some other subdivision of a detector. Shape description of each pixel. Use only if all pixels in the detector are of uniform shape. Shape description of each pixel. Use only if all pixels in the detector are of uniform shape and require being described by cylinders. Shape description of the whole detector. Use only if pixels in the detector are not of uniform shape. Shape description of the whole detector. Use only if pixels in the detector are not of uniform shape and require being described by cylinders.