From: Jan Michel Date: Tue, 26 Feb 2019 16:21:16 +0000 (+0100) Subject: add hmon plots description X-Git-Url: https://jspc29.x-matter.uni-frankfurt.de/git/?a=commitdiff_plain;h=af87c88bb3818ce9163270a0667294e088960836;p=daqdocu.git add hmon plots description --- diff --git a/hadesoperator/figures/busy_times.png b/hadesoperator/figures/busy_times.png new file mode 100644 index 0000000..464dbbc Binary files /dev/null and b/hadesoperator/figures/busy_times.png differ diff --git a/hadesoperator/figures/eb_summary.png b/hadesoperator/figures/eb_summary.png new file mode 100644 index 0000000..b28e438 Binary files /dev/null and b/hadesoperator/figures/eb_summary.png differ diff --git a/hadesoperator/figures/last_hld.png b/hadesoperator/figures/last_hld.png new file mode 100644 index 0000000..436b4d1 Binary files /dev/null and b/hadesoperator/figures/last_hld.png differ diff --git a/hadesoperator/main.tex b/hadesoperator/main.tex index 0d1f70a..a13ed62 100644 --- a/hadesoperator/main.tex +++ b/hadesoperator/main.tex @@ -5,6 +5,8 @@ \input{../trb3/trb3qs_preamble} +\usepackage{siunitx} +\usepackage{float} \usepackage[utf8]{inputenc} \usepackage{amsfonts} \usepackage[american]{babel} @@ -118,6 +120,7 @@ \section{Hmon Plots} \input{hmon} +\input{monitors} \section{Eventbuilder} \input{ebmonitoring} diff --git a/hadesoperator/monitors.tex b/hadesoperator/monitors.tex new file mode 100644 index 0000000..fef7885 --- /dev/null +++ b/hadesoperator/monitors.tex @@ -0,0 +1,193 @@ +% remarks: tuning procedure +% insert pin header, to test mainboard and sensor individually +\section*{Busy times (bar plot)} +\begin{figure}[H] +\centering +\includegraphics[width=0.5\textwidth]{figures/busy_times.png} +\caption{} +\label{fig:busy_times} +%figure~\ref{fig:busy_times} +\end{figure} + +\begin{description} +\item[Y axis:] +Busy time/dead time in \% of the total time +\item[X axis:] +HADES detector subsystem (one set of bars per subsystem) +\item[Description:] +Busy time (dead time) is the time where a detector system is processing/transporting the recorded data and +cannot accept another data acquisition trigger. +Each HADES detector subsystem has one blue bar showing the total busy time of the entire subsystem. +The busy time is given in percent, i.e. the bar plot shows the "mean business" per unit time. +Accompanying the main blue bar, there are several grey bars which show the individual busy times of the +sub-subsystems (less important). +\end{description} + +\section*{Busy times (line graph)} +\begin{description} +\item[Y axis:] +Busy time/dead time in \% of the total time +\item[X axis:] +Time in seconds. +\item[Description:] +See \emph{Busy times (bar plot)}. Same observables graphed as a function of time. +\end{description} + +\section*{Data rates} +\begin{description} +\item[Y axis:] +Total data rate recorded by entire HADES experiment sent to eventbuilder in MB/s. +\item[X axis:] +Time in seconds. +\end{description} + +\section*{Start-X/Start-Y/Veto Rate} +\begin{description} +\item[Y axis:] +Particle hit rate on detector electrode in Hz. +\item[X axis:] +\# detector electrode +\item[Description:] +The Start detector consists of two layers of silicon strip detectors, located several centimeters upbeam of the target. +Each layer features 16 strips with a width of $\approx\SI{300}{\micro\meter}$. +One layer is oriented vertically (providing a beam intensity profile in X direction), while the second layer +is oriented horizontally (providing a beam intensity profile in Y direction). +During beam operation, the Start-X and the Start-Y plot should show a gaussian beam profile, which should be +centered and not move. + +Bar plots are either red or green. Green means \emph{used for trigger} (usually inner/center electrodes), +red means \emph{not used for trigger} (usually outer electrodes). + +The veto detector consists of four inner (channels 0-3) and four outer electrodes (channels 4-7). +It detects (beam) particles that did not interact with the target. +When the beam is perfectly centered, the only the inner four electrodes are hit equally. +% start-x/start-y/veto + +% start detektor hat 16 streifen in x und 16 streifen in y, circa 300 µm pitch +% in x und y hast du im Idealfall ein Gauß-Profil, was dir das Beam-Profil angibt. Sollte sich im Idealfall nicht bewegen. +% von den 16 streifen können wir nur auf 8 streifen gleichzeitig triggern. (Limitierung von CTS) +% zwei farben: grün bedeutet: benutzt für trigger, rot bedeutet nicht ausgewählt für Trigger. Möglichst viel Grün. +% in y-Plot genauso. + +% Veto detector: innere vier Elektroden vs äußere vier. innere vier sind grün, äußere vier sind rot. Wenn die ersten vier elektroden feuern, dann liegt der Strahl gerade. +\end{description} + + +\section*{Start X counts per spill (line graph)} +\begin{description} +\item[Y axis:] +Hits on start detector in Mega-Counts/spill +\item[X axis:] +Spill number. The last approx. 100 spills ($\sim$ time) +\item[Description:] +In normal beam operation this observable should stay mostly constant. If it fluctuates, the beam intensity/spill structure +is not stable. +\end{description} +% Start X counts. wieviele counts auf dem Startdetektor habe ich per spill. y-Achse start counts (in Mega-counts). x-Achse : die letzten 100 Spills. Das sollte konstant bleiben. Wenn stark fluktuiert, dann nix gut. + + +\section*{Recorded events per spill (line graph)} +\begin{description} +\item[Y axis:] +Events recorded by DAQ per spill (in kilo-Counts/spill) +\item[X axis:] +Spill number. The last approx. 100 spills ($\sim$ time) +\item[Description:] +Events which were actually recorded by the DAQ. +In normal beam operation this observable should stay mostly constant +and be proportional to \emph{Start X counts per spill}. +If the proportion changes, the micro spill structure has changed. +\end{description} +% recorded events per spill: Wieviel events sind wirklich aufgezeichnet worden? sollte mit dem vorigen zusammenhängen. wenn sich das Verhältnis zwischen beiden ändert, dann heißt das, etwas hat sich an der micro-spill-struktur geändert. + +\section*{Event rates (2x line graphs)} +\begin{description} +\item[Y axis:] +Event rate - Events accepted by DAQ per time unit (in kHz) +\item[X axis:] +Time in seconds. +\item[Description:] +There are two versions of this plot. One shows the event rate over 10-30 sec, the other shows the event rate +over 10 min. +The short-time plot shows the time structure of a single spill. +The long time plot shows the history over the last dozens of spills. +The ideal spill should have steep slopes, a constant plateau, no peaks/spikes and a short spill pause. +\end{description} +% event rate: akzeptierente rate pro sekunde, einmal über 10 min, einmal über 10-30 sekunden (damit man Struktur von einem Spill sieht (spill shape) ) Der ideale spill ist ein Plateau mit steilen Kanten, kurzer Totzeit. Keine Peaks. + +% Jeder plot hat eine Uhrzeit, um zu checken ob sich das System aktualisiert. + + +\section*{EB (Event Builder) Summary Window} +\begin{figure}[H] +\centering +\includegraphics[width=0.5\textwidth]{figures/eb_summary.png} +\caption{} +\label{fig:eb_summary} +%figure~\ref{fig:eb_summary} +\end{figure} + + +\begin{description} +\item[Description:] +Overview over Event Builder Servers. The event building servers (computers in the rear counting house) +serve two purposes:\\ +\textbf{1.} Receiving data streams from the read-out boards and (input node)\\ +\textbf{2.} Combining the received data belonging to the same event and writing it to disc (building node)\\\\ +The input nodes and the building nodes are software processes running on the same computer(s). +\item[What to check:] +The total data rate and the total event rate should be approximately the same in the input node and building +node table (there is a delay of several seconds). +If this is not the case, the total data/event rate field in the building notes table will turn red. +Every of the \emph{n} input nodes gets approximately 1/n of the total data rate produced by HADES. +If the load is not balanced, the respective field in the table turns red. +The \emph{dropped events} rate should be close to zero. +\item[Calib info:] +The top right box in this window shows the timestamp of the last TDC calibration and if it was successful or not. +\end{description} + +\section*{Lest *.hld files window} +\begin{figure}[H] +\centering +\includegraphics[width=0.5\textwidth]{figures/last_hld.png} +\caption{} +\label{fig:last_hld} +%figure~\ref{fig:last_hld} +\end{figure} + +\begin{description} +\item[Description:] +A list of the latest written data files. +\end{description} + +% übersicht über Eventbuilder server + +% oben Zusammenfassung + + +% Jeder der input-nodes kriegt ein 1/5 von jedem Event. +%für events pro sekunde ist das Average. Daten-Summe ist wirklich daten summe über die INput nodes. + +% die dropped events sollte nahe Null sein. + +% Events/s wird rot, wenn rate in einem input node zu sehr abweicht. + +% Wenn irgendwas nicht grün ist, sollte der Mouseover-Text erklären was schief läuft. + +% building nodes sum: Event rate sum wird rot, wenn die Zahl der empfangenen Events nicht der Anzahl der Gebauten events entpspricht. + +% Wir sind zufrieden wenn data rate und event rate von input and output ungefähr gleich ist. + +% es gibt für gewöhnlich einen Delay zw. input und build notes von ein paar Sekunden. + +% obere drei kästchen ist im wesentlichen Zusammenfassung. + +% rechts oben steht noch ob Kalibrierung in Ordnung ist. + +% rechte box dateinamen von geschriebenen Dateien. + + + + + +