raw_data_1/instrument/detector_<N>
This is a NXdetector.
Spectra are grouped into different detector_<N> groups based on the time-regime set they share. In other words,
detector_N contains data from all spectra configured to use time regime N.
raw_data_1/instrument/detector_<N>/counts
This is the histogram data for detector N, as int32 counts. It has dimensions periods,spectra,time_channels, where periods is the number
of DAQ periods (which may be different from the total number of periods).
This is written only if histograms were requested.
Attributes:
units:"counts"signal:1axes:On a muon instrument:
"period_index,spectrum_index,raw_time"On a neutron instrument:
"period_index,spectrum_index,time_of_flight"
long_name:"positron_counts"(written on Muon instruments only)
raw_data_1/instrument/detector_<N>/spectrum_index
Mapping of array position in the histogram array to spectrum IDs, as an int32.
Muon-specific datasets
Caution
TODO
raw_data_1/instrument/detector_<N>/period_index
This is a NeXus link to raw_data_1/instrument/dae/period_index.
raw_data_1/instrument/detector_<N>/time_of_flight
This is a NeXus link to raw_data_1/instrument/dae/time_channels_<N>/time_of_flight.
raw_data_1/instrument/detector_<N>/time_of_flight_raw
This is a NeXus link to raw_data_1/instrument/dae/time_channels_<N>/time_of_flight_raw.
It is only written on Neutron instruments.
raw_data_1/instrument/detector_<N>/source_detector_distance
This is user-settable float32 metadata. It is set in IBEX under Experiment Details -> Sample Parameters -> Sample Detector Distance
Caution
The parameter name in the NeXus file is the source-detector distance, whereas in IBEX it is called the sample-detector distance. This is only consistent it one interprets the “source” of the scattered radiation as being the sample.
raw_data_1/instrument/detector_<N>/polar_angle
This is the average polar angle (two-theta) of a spectrum, as a float32. It is an average because a spectrum may be made from multiple detector pixels.
Attributes:
units:"degree"
raw_data_1/instrument/detector_<N>/distance
This is the L2 flight path of a spectrum, as a float32. It is an average because a spectrum may be made from multiple detector pixels.
Attributes:
units:"metre"
raw_data_1/instrument/detector_<N>/delt
This is the “hold-off time” of a spectrum, as a float32. It is an average because a spectrum may be
made from multiple detector pixels. It is in us, but a units attribute is not written.
raw_data_1/instrument/detector_<N>/azimuthal_angle
This is the azimuthal angle of a spectrum, as a float32. It is an average because a spectrum may be made from multiple detector pixels.
Attributes:
units:"degree"
raw_data_1/instrument/detector_<N>/user_table<N>
These are arbitrary user-specified tables for each detector, as a float32. It is an average because a spectrum may be made from multiple detector pixels.
User tables start from user_table01.
user_table01 is always equivalent to raw_data_1/instrument/detector_<N>/azimuthal_angle.
raw_data_1/instrument/detector_<N>/event_id
This is the spectrum (not detector) that each event was detected on.
This is only written in event mode. See also NXevent_data.
raw_data_1/instrument/detector_<N>/event_index
The index into the event_time_offset, event_id pair for the pulse occurring at the matching entry in event_time_zero.
This is only written in event mode. See also NXevent_data.
raw_data_1/instrument/detector_<N>/event_time_zero
This is the time that each pulse started, as float32 microseconds, with respect to the offset which is the beginning of a run.
This is only written in event mode. See also NXevent_data.
Attributes:
offset: The start of run timestamp, for example"2025-03-27T13:38:28"units:"second"
raw_data_1/instrument/detector_<N>/event_time_offset
This is the timestamp of each event, as float32 microseconds, with respect to the offset in raw_data_1/instrument/detector_<N>/event_time_zero.
This is only written in event mode. See also NXevent_data.
Attributes:
units:"second"
raw_data_1/instrument/detector_<N>/event_time_offset_shift
This dataset contains the string "random" if event time offsets have been assigned a randomised position within the
time bin given by raw_data_1/detector_<N>_events/event_time_bins.
This randomisation is needed to avoid artefacts in downstream reduction software when using event-mode hardware with a low resolution clock (for example DAE2/3).
This is only written in event mode.
raw_data_1/instrument/detector_<N>/total_counts
This dataset contains the total number of event-mode events, as an int64. It is equal to the length of the event_time_offset or event_id datasets.
This is only written in event mode.