Commit bd9dac1e authored by Paolo Baesso's avatar Paolo Baesso

Added print of event from EUDAQ

parent b8d73a28
......@@ -4,13 +4,13 @@
0
1
Main_TLU.tex
11
11
9
12
12
10
Main_TLU.tex
TeX
135278587 0 -1 4564 -1 1364 75 75 1448 573 0 1 49 340 -1 -1 0 0 43 -1 -1 43 1 0 1364 -1 0 -1 0
135278587 4 -1 4701 -1 4702 75 75 1448 573 0 1 249 561 -1 -1 0 0 43 -1 -1 43 1 0 4702 -1 0 -1 0
ch_TLU_Preparation.tex
TeX
1060859 0 -1 2411 -1 2429 150 150 1523 648 0 1 41 255 -1 -1 0 0 43 -1 -1 43 1 0 2429 -1 0 -1 0
......@@ -37,7 +37,10 @@ TeX
17838075 0 -1 7964 -1 8054 25 25 1411 497 0 1 289 306 -1 -1 0 0 45 -1 -1 45 1 0 8054 -1 0 -1 0
ch_EUDAQParameters.tex
TeX
269496315 0 -1 11640 -1 11739 175 175 1561 852 0 1 1081 935 -1 -1 0 0 45 -1 -1 45 1 0 11739 -1 0 -1 0
1060859 0 -1 11640 -1 11739 175 175 1561 852 0 1 1081 934 -1 -1 0 0 45 -1 -1 45 1 0 11739 -1 0 -1 0
ch_EUDAQProducer.tex
TeX
286273531 0 -1 1617 -1 2773 275 275 2188 952 0 1 521 884 -1 -1 0 0 -1 -1 -1 -1 1 0 2773 -1 0 -1 0
ch_TLU_Appendix.tex
TeX
1060859 0 -1 189 -1 194 175 175 1548 673 0 1 377 51 -1 -1 0 0 37 -1 -1 37 1 0 194 -1 0 -1 0
......@@ -54,5 +57,6 @@ TeX
*ch_TLU_Functions
*ch_TLU_IPBusRegs
*ch_EUDAQParameters
*ch_EUDAQProducer
*ch_TLU_Appendix
<
......@@ -184,6 +184,7 @@ Paolo Baesso - \monthname, \the\year\newline paolo.baesso@bristol.ac.uk
\include{ch_TLU_Functions}
\include{ch_TLU_IPBusRegs}
\include{ch_EUDAQParameters}
\include{ch_EUDAQProducer}
\include{ch_TLU_Appendix}
%\begin{figure}[h]
......
\chapter{EUDAQ Producer}\label{ch:eudaqprod}
Current structure of a fmctlu producer event:
\lstset{language=XML}
\scriptsize
\begin{lstlisting}
<Event>
<Type>2149999981</Type>
<Extendword>171577627</Extendword>
<Description>Ex0Tg</Description>
<Flag>0x00000018</Flag>
<RunN>0</RunN>
<StreamN>0</StreamN>
<EventN>0</EventN>
<TriggerN>88</TriggerN>
<Timestamp>0x0000000000000000 -> 0x0000000000000000</Timestamp>
<Timestamp>0 -> 0</Timestamp>
<Block_Size>0</Block_Size>
<SubEvents>
<Size>1</Size>
<Event>
<Type>2149999981</Type>
<Extendword>3634980144</Extendword>
<Description>TluRawDataEvent</Description>
<Flag>0x00000010</Flag>
<RunN>96</RunN>
<StreamN>4008428646</StreamN>
<EventN>88</EventN>
<TriggerN>88</TriggerN>
<Timestamp>0x0000000105b44f91 -> 0x0000000105b44faa</Timestamp>
<Timestamp>4390670225 -> 4390670250</Timestamp>
<Tags>
<Tag>PARTICLES=89</Tag>
<Tag>SCALER0=93</Tag>
<Tag>SCALER1=93</Tag>
<Tag>SCALER2=0</Tag>
<Tag>SCALER3=0</Tag>
<Tag>SCALER4=0</Tag>
<Tag>SCALER5=0</Tag>
<Tag>TEST=110011</Tag>
<Tag>trigger=</Tag>
</Tags>
<Block_Size>0</Block_Size>
</Event>
</SubEvents>
</Event>
\end{lstlisting}
\normalsize
\begin{description}
\item[Type] ??
\item[ExtendWord] ??
\item[Description]
\item[Flag] Independent from producer. See the \href{https://github.com/eudaq/eudaq/blob/master/main/lib/core/include/eudaq/Event.hh#L87}{EUDAQ documentation} for details.
\item[RunN]
\item[StreamN]
\item[EventN]
\item[TriggerN] Both in the event and subevent this is written byt the producer with \verb|ev->SetTriggerN(trigger_n);|
\item[Timestamp] The event timestamp is currently always 0. The subevent timestamps is written by the producer \verb|ev->SetTimestamp(ts_ns, ts_ns+25, false);|. The top line (0x0000000105b44f91, in the example) is coarse time stamp multiplied by 25, so it represents the time in nanoseconds. The bottom one (4390670225) is the same number but written in decimal format instead of hexadecimal.
\item[PARTICLES] Number of pre-veto triggers recorded by the \gls{tlu}: the trigger logic can detect a valid trigger condition even when the unit is vetoed. In this case no trigger is issued to the \gls{dut}s but the number of such triggers is stored as number of particles. \verb|ev->SetTag("PARTICLES", std::to_string(pt));|
\item[SCALER\#] Number of triggers edges seen by the specific discriminator. \verb|ev->SetTag("SCALER", std::to_string(sl));|
\item[???] Event type from \gls{tlu} is missing?
\item[???] Input trig, i.e. the actual firing inputs should be in TRIGGER but there seems to be nothing there
\end{description}
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