2.3.3.3.96. NXdata_mpes¶
Status:
base class, extends NXdata
Description:
Symbols:
No symbol table
- Groups cited:
none
Structure:
energy: (optional) NX_NUMBER {units=NX_ENERGY} ⤆
Calibrated energy axis. ...
Calibrated energy axis.
Could be linked from the respective ‘@reference’ field.
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:
@reference: (optional) NX_CHAR ⤆
The energy can be dispersed according to different strategies. ``@reference` ...
The energy can be dispersed according to different strategies.
@referencepoints to the path of a field defining the calibrated axis which theenergyaxis refers.
- For example:
@reference: ‘entry/process/energy_calibration/calibrated_axis’ @reference: ‘entry/process/energy_referencing/calibrated_axis’
kN: (optional) NX_NUMBER {units=NX_WAVENUMBER} ⤆
One calibrated k-space coordinate. It is envisioned that the axes are named kx ...
One calibrated k-space coordinate. It is envisioned that the axes are named kx, ky, and kz, in accordance with the calibrations defined in NXprocess_mpes.
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 calibrated angular coordinate. It is envisioned that the axes are name ang ...
One calibrated angular coordinate. It is envisioned that the axes are name angular0, angular1, etc., in accordance with the calibrations defined in NXprocess_mpes.
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 calibrated spatial coordinate. It is envisioned that the axes are name spa ...
One calibrated spatial coordinate. It is envisioned that the axes are name spatial0, spatial1, etc., in accordance with the calibrations defined in NXprocess_mpes.
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.
delay: (optional) NX_NUMBER {units=NX_TIME} ⤆
Calibrated delay time.
polarization_angle: (optional) NX_FLOAT {units=NX_ANGLE}
Linear polarization angle of the incoming or outgoing beam. ...
Linear polarization angle of the incoming or outgoing beam.
In an application definition, this could be a link to /entry/instrument/beam/incident_polarization_angle or /entry/instrument/beam/final_polarization_angle if they exist.
ellipticity: (optional) NX_FLOAT {units=NX_ANGLE}
Ellipticity of the incoming or outgoing beam. ...
Ellipticity of the incoming or outgoing beam.
Can be any of linear polarization angle (degrees), ellipticity (arb. units). In an application definition, this could be a link to /entry/instrument/beam/incident_ellipticity or /entry/instrument/beam/final_ellipticity if they exist.
Hypertext Anchors¶
List of hypertext anchors for all groups, fields, attributes, and links defined in this class.
