Commit 328a9028 authored by Simon Spannagel's avatar Simon Spannagel
Browse files

ELEUDAQ2: document behavior of TS assignment

parent 51c327e9
Pipeline #1129370 passed with stages
in 18 minutes and 48 seconds
......@@ -25,6 +25,9 @@ If yes, the corresponding pixels are added to the clipboard for this event.
If earlier, the next event is read until a matching event is found.
If later, the pointer to this event is kept and it continues with the next detector.
Data from detectors with triggered readout and without timestamps are matched against trigger IDs stored in the currently defined Corryvreckan event.
In case of a match, the timestamp of the respective trigger is assigned to all pixels of the device.
If no detector is capable of defining events, the `[Metronome]` model needs to be used.
Tags stores in the EUDAQ2 event header are read, a conversion to a double value is attempted and, if successful, a profile with the value over the number of events in the respective run is automatically allocated and filled. This feature can e.g. be used to log temperatures of the devices during data taking, simply storing the temperature as event tags.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment