From 5a75b4aca1431663184222b610824b2c5fa9b0fd Mon Sep 17 00:00:00 2001 From: George O'Neill <133203284+ggoneiESS@users.noreply.github.com> Date: Tue, 13 May 2025 19:06:32 +0200 Subject: [PATCH] Update ev44_events.fbs going through ev44 today some parts were not very clear, so these have been clarified --- schemas/ev44_events.fbs | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/schemas/ev44_events.fbs b/schemas/ev44_events.fbs index 2a09fa3..c9ed81f 100644 --- a/schemas/ev44_events.fbs +++ b/schemas/ev44_events.fbs @@ -7,16 +7,15 @@ table Event44Message { message_id : long; // Consecutive numbers, to detect missing or unordered messages reference_time : [long] (required); // Nanoseconds since Unix epoch (1 Jan 1970) // If pulse times are available in the aquisition system, this field holds - // those timestamps. Holds wall time otherwise. + // those timestamps, otherwise it holds system clock time. reference_time_index : [int] (required); // Index into the time_of_flight array for the start of the neutron events linked // to the corresponding pulse/reference time. // reference_time_index and reference_time are the same length. - time_of_flight : [int]; // Nanoseconds - // Time of flight for each event if pulse time is available. If not, a - // (positive) offset from the wall time stored in the `reference_time`. - // Cannot be empty if events are being sent. - pixel_id : [int]; // Identifiers that represent the positions of the events in the detector(s). - // Can be empty even when events are sent if the pixel_id is implicit (e.g. single-pixel beam monitor). + time_of_flight : [int]; // Nanoseconds since reference_time + // An offset from the time stored in the `reference_time`. + // time_of_flight and pixel_id are the same (implied) length. + pixel_id : [int]; // Identifier that represents the voxel where an event has been detected. + // Can be empty even when events are sent if the pixel_id is implicit (e.g. single-pixel detector). } root_type Event44Message;