2.3.3.3.94. NXdata_mpes_detector

Status:

base class, extends NXdata

Description:

Symbols:

No symbol table

Groups cited:

none

Structure:

raw: (optional) NX_NUMBER

Raw data before calibration.

pixel_x: (optional) NX_FLOAT {units=NX_ANY}

Detector pixel in x direction.

pixel_y: (optional) NX_FLOAT {units=NX_ANY}

Detector pixel in y direction.

energy: (optional) NX_NUMBER {units=NX_ENERGY}

(Un)calibrated energy axis.

@type: (optional) NX_CHAR

The energy can be either stored as kinetic or as binding energy. ...

The energy can be either stored as kinetic or as binding energy.

Any of these values:

  • kinetic: (Un)calibrated kinetic energy axis. This concept is related to term 3.35 of the ISO 18115-1:2023 standard.

  • binding: (Un)calibrated binding energy axis. This concept is related to term 12.16 of the ISO 18115-1:2023 standard.

kN: (optional) NX_NUMBER {units=NX_WAVENUMBER}

One (un)calibrated k-space coordinate. It is envisioned that the axes are name ...

One (un)calibrated k-space coordinate. It is envisioned that the axes are named kx, ky, and kz.

Typically, the vectors in momentum space are defined such that kx and ky comprise the parallel component, while kz is taken as the perpendicular component.

It is also possible to define k_parallel and k_perp for the parallel and perpendicular momenta, respectively. Units are 1/Angström.

angularN: (optional) NX_NUMBER {units=NX_ANGLE}

One (un)calibrated angular coordinate. It is envisioned that the axes are name ...

One (un)calibrated angular coordinate. It is envisioned that the axes are name angular0, angular1, etc.

The angular axes should be named in order of decreasing speed, i.e., angular0 should be the fastest scan axis and angular1 should be the slow-axis angular coordinate. However, angular0 may also be second slow axis if the measurement is angularly integrated and angular1 could also be the second fast axis in the case of simultaneous dispersion in two angular dimensions.

spatialN: (optional) NX_NUMBER {units=NX_ANGLE}

One (un)calibrated spatial coordinate. It is envisioned that the axes are name ...

One (un)calibrated spatial coordinate. It is envisioned that the axes are name spatial0, spatial1, etc.

The spatial axes should be named in order of decreasing speed, i.e., spatial0 should be the fastest scan axis and spatial1 should be the slow-axis spatial coordinate. However, spatial0 may also be second slow axis if the measurement is spatially integrated and spatial1 could also be the second fast axis in the case of simultaneous dispersion in two spatial dimensions.

time_of_flight: (optional) NX_FLOAT {units=NX_TIME_OF_FLIGHT}

Total time of flight.

time_of_flight_adc: (optional) NX_FLOAT {units=NX_ANY}

Time-of-flight values, analog-to-digital converted.

delay: (optional) NX_NUMBER {units=NX_TIME}

(Un)calibrated delay time.

polarization_angle: (optional) NX_FLOAT {units=NX_ANGLE}

Linear polarization angle of the incoming or outgoing beam.

ellipticity: (optional) NX_FLOAT {units=NX_ANGLE}

Ellipticity of the incoming or outgoing beam.

external_AXIS: (optional) NX_NUMBER {units=NX_ANY}

Describes an axis which is coming from outside the detectors scope. ...

Describes an axis which is coming from outside the detectors scope.

Think of a detector just being triggered for readout by the rest of the experimental setup - it would just know that it collected N images, which would flatten the external parameters to one axis, too. This can then be linked, e.g. with NXcalibration, to the appropriate fields in the instrument and write it to the top-level NXdata_mpes.

Hypertext Anchors

List of hypertext anchors for all groups, fields, attributes, and links defined in this class.

NXDL Source:

https://github.com/FAIRmat-NFDI/nexus_definitions/tree/fairmat/contributed_definitions/NXdata_mpes_detector.nxdl.xml