Commit 6847d55f authored by Simon Spannagel's avatar Simon Spannagel
Browse files

Docs: fix typos found by @jekroege

parent c2a90d75
Pipeline #1125342 failed with stages
in 12 minutes and 20 seconds
......@@ -89,7 +89,7 @@ If the device also provides a timestamp, the data can be directly assigned to ev
The situation becomes more problematic if the respective data only have the trigger ID or number assigned but should be combined with un-triggered devices which define their events based on timestamps only.
In order to process such data, a device which relates timestamps and trigger IDs such as a triller logic unit, is required.
In order to process such data, a device which relates timestamps and trigger IDs such as a trigger logic unit, is required.
This device should be placed before the detector in question in order to assign trigger IDs to the event using the \command{addTrigger(...)} function.
Then, the triggered device without timestamps can query the event for the position of its trigger ID with respect to the event:
......@@ -104,7 +104,7 @@ auto position = event->getTriggerPosition(my_trigger_id);
If the given trigger ID is smaller than the smallest trigger ID known to the event, the function places the data as \parameter{BEFORE}.
If the trigger ID is larger than the largest know ID, the function returns \parameter{AFTER}. returned. If the trigger ID is known to the event, the respective data is dated as being \parameter{DURING} the current event.
In cases where either no trigger ID has been previously added to the event or where the given ID lies between the smallest and larges known ID but is not part of the event, \parameter{UNKNOWN} is returned.
In cases where either no trigger ID has been previously added to the event or where the given ID lies between the smallest and largest known ID but is not part of the event, \parameter{UNKNOWN} is returned.
\section{The Metronome}
\label{sec:metronome}
......@@ -144,10 +144,10 @@ This example demonstrates the setup for event building based on a frame-based de
The event building strategy for this situation is sketched in Figure~\ref{fig:datadrivenandframebased}.
The configuration contains four different devices:
\begin{description}
\item[\parameter{CLICpix2}:] This prototype acts as device under test and is a detector designed for pperation at a linear collider, implementing a frame-based readout scheme. In this example, it will define the event.
\item[\parameter{CLICpix2}:] This prototype acts as device under test and is a detector designed for operation at a linear collider, implementing a frame-based readout scheme. In this example, it will define the event.
\item[\parameter{TLU}:] The trigger logic unit records scintillator coincidence signals with their respective timestamps, generates trigger signals and provides the reference clock for all other devices.
\item[\parameter{Timepix3}:] This detector is operated in its data-driven mode, where the external clock from the TLU is used to timestamp each individual pixel hit. The hits are directly read out and sent to the data acquisition system in a continuous data stream.
\item[\parameter{MIMOSA26}:] These detectors are devices with a continuous rolling shutter readout, which do not record any timing information in the individual frames. The data are tagged with the incoming triggers by its DAQ system.
\item[\parameter{MIMOSA26}:] These detectors are devices with a continuous rolling shutter readout, which do not record any timing information in the individual frames. The data are tagged with the incoming trigger IDs by its DAQ system.
\end{description}
It is assumed that all data have been recorded using the \emph{EUDAQ2} framework, and the \command{EventLoaderEUDAQ2} is used for all devices to read and decode their data.
......@@ -181,7 +181,7 @@ Then, the data from the \parameter{TLU} are added by comparing the trigger times
The matching trigger numbers are added to the event for later use.
Subsequently the \parameter{Timepix3} device adds its data to the event by comparing the individual pixel timestamps to the existing event definition.
Finally, the six \parameter{MIMOSA26} detectors are added one-by-one via the automatic \parameter{type}-instantiation of detector modules described in Section~\ref{sec:module_instantiation}.
Here, the trigger number from the detector data are compared to the ones stored in the event as described in Section~\ref{sec:triggered_devices}.
Here, the trigger numbers from the detector data are compared to the ones stored in the event as described in Section~\ref{sec:triggered_devices}.
It should be noted that in this example, the data from the \parameter{TLU} and the six \parameter{MIMOSA26} planes are read from the same file.
The event building algorithm is completely transparent to how the individual detector data are stored, and the very same building pattern could be used when storing the data in separate files.
......
Markdown is supported
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