\section{Eventbuilder Operator Guide}
\label{sec:eboperatorguide}
+\subsection{Regular beamtime control}
+During beamtime shift, data taking can be controlled by the main DAQ Operator GUI (Fig. \ref{fig:daqcontrol}).
+The GUI box {\bf Eventbuilder Tools} offers all relevant commands as shortcut buttons.
+These are described in operator manual section \ref{section:daqcontrolgui}.
-\subsection{DABC Webserver monitor }
-\label{sec:ebmonguide:dabc}
-In 2018 the HADES event building system was changed in topology. Before, all $n$ DAQ hubs sending their subevents to all $m$ eventbuilders
-each of which combines all subevents to full event packets. By switching the subevent destionation of the hubs in
-a ``barrel-shift'' manner, the eventbuilding load was distributed to all active eventbuilder entities.
-In the new scheme, each DAQ hub is configured to always send to a dedicated input node
-of the DABC builder network (BNET).
-
-Moreover, run number synchronisation between parallel event builder files is no longer done by the EPICS ''master'' ioc of EB1.
-Instead, all controls of the BNET is handled by a central {\em Master} process located on the server lxhadeb03. This master processes runs independent of the other BNET processes
-and will re-connect to their command channels whenever the eventbuilders are restarted.
-{\bf NOTE: The BNET master process itself can be re-started by button ''Restart BNET Master'' in the expert section of the DAQ control gui, see section \ref{sec:shortguide:daqcontrolwindow}.}
-Usually this is necessary only once before data taking, or after a DABC software upgrade of the master process.
-
-The BNET master offers a monitoring and control GUI on a webserver at the address {\tt http://lxhadeb07:8099/}. It is also available as part of the hmon webserver at \newline
-{\tt http://hades33/eb/}. When this address is opened in any web browser (e.g. firefox, chrome), the default GUI displays the state of the BNET as shown in figure \ref{fig:ebmonitorguide:dabc1}.
+\subsection{DABC Webserver controls}
+\label{sec:ebmonguide:dabc}
+The BNET master server of offers a monitoring and control GUI on a webserver at the address \url{http://lxhadeb07:8099/?browser=fix}.
+It is also available as part of the hmon webserver at
+\url{http://hades33/eb/}. When this address is opened in any web browser (e.g. firefox, chrome), the default GUI displays the state of the BNET as shown in figure \ref{fig:ebmonitorguide:dabc1}.
This screenshot explains the main graphical elements and the functionality of the most important buttons. Besides the control buttons,
Clicking on any active object gui elements (i.e. the text is underlined as a hyperlink), an appropriate plot or text information will
show up in the main display area. Just holding the mouse over a display element will after few scondes usually open a hover window showing additional information, or a tooltip help.
Note that the checkbox for ''Monitoring display'' has to be enabled to update the display frequently every 2 seconds.
-Figure \ref{fig:ebmonitorguide:dabc2} describes the GUI elements related to data taking and file writing. The respective buttons on top allow to select the next run type
-and to start and stop datataking at any time. Note that the BNET processes are not restarted when changing the run type as with the old eventbuilders, but continue even when
-writing to files is stopped. In this case, just the filename display will become empty and the builder node color turns yellow.
-Clicking on any of the rate and file size numbers allows to watch the trending graph of the assigned value in the display area.
-
-\newpage
-Figure \ref{fig:ebmonitorguide:dabc3} illustrates the details of the GbE hub input display.
For each BNET input node row, the UDP receiver ports are listed with the trbnet
address of the sending hub (if any data has yet been received!). The color of each hub shows the actual state of data receiving:
\begin{description}
\item [Green]: Data is received properly (TDC calibration runs: Calibration is sufficient)
- \item [Red]: No data is currently received (TDC calibration runs: Calibration is not ready, or calibration file not yet existing)
+ \item [Yellow/Red]: No data is currently received (TDC calibration runs: Calibration is not ready, or calibration file not yet existing)
\item [Blue]: TDC calibration runs only: Calibration is ongoing, but statistics not yet sufficient)
\end{description}
-If Calibration of trb3 inputs is not yet existing (red hub although full eventbuilding is running), a calibration procedure has to be
-done\footnote{Files of type ''Tc'' must be started. The hub inputs without calibration will turn blue until a sufficient TDC fine time
-calibration has been accumulated. Stopping the calibration runs with the button will store the new calibration as files for each tdc address into the {\em /home/hadaq/oper}
-directory on the eventbuilder server. The following runs will use thes calibration files and all hubs should show green color.}.
-Every single GbE hub input may be inspected by holding the mouse over it to see a hover info window. Clicking on it will display further information:
-The current receiver statistics is printed in a text field. For trb3 systems that are configured for online TDC calibration, the TDC sub-subevents
-with their addresses will be displayed. The color of each tdc will indicate if the statistics is sufficent for a TDC calibration
-(red: low statistics, blue: calibration ongoing, green: statistics is OK for doing new calibration).
-Clicking on the central hub box will display a comparison of count statistics for each TDC. If DABC is configured for debugging with additional histograms, clicking
-on each TDC box displays comparison of channel statistics. This mode is disabled for HADES production beamtime because of performance reasons!
-
-Figure \ref{fig:ebmonitorguide:dabc4} is an example of an input node that is not a trb3 hub with TDC calibration. In this case, clicking on the hub will offer buttons to display the
-trigger type statistics, or the subevent size histogram. {\bf Please note that the trigger type information are available only in the CTS hub 0x8800}.
-
-
-Clicking on the {\em hostname:port} title of a BNET node row will display the eventbuilder ''terminal''
-offering an ASCII monitor of the event building at the local inputs (see figure \ref{fig:ebmonitorguide:dabc5}).
-This is the DABC emulation of the old {\em hadaq} and {\em netmem} eventbuilder output, which is also known from standalone DABC datataking systems.
-Depending on the type of BNET node, parts of the generic terminal information is missing: For BNET input nodes, there is no final data file output.
-For builder nodes, there is no UDP receiver information, since the input rows reflect the DABC socket connections to the BNET input nodes.
-
-Figure \ref{fig:ebmonitorguide:dabc5} contains a kind of tutorial how the user can set up an individual display of monitored values.
-Chosing the webserver address {\tt http://lxhadeb03:8090/?browser=fix} displays the usually hidden hierarchy browser
-of the DABC master node. Here all known parameters, commands, and entities of the BNET are available in a hierarchic tree view.
-Clicking on any icon will display it in the currently active display area (usually the main display area of the default GUI).
-However, it is possible to change the default GUI and arrange the GUI elements in an arbitrary manner.
-Using the ''clear'' link in the DABC object browser will erase the default elements. The user may chose any of the given view partitionings and pad modes
-in the selection menu (e.g. a 4x4 grid of pads, different tabs, or flexible desktop-like subwindows). All newly clicked icons will then draw with respect to the selected style
-(the example in figure \ref{fig:ebmonitorguide:dabc5} shows the ''flex'' option).
-The right mouse button menu of the browser icons offers further draw options, e.g. a gauge instrument instead of trending graphs for rates.
-
-Note that frequent monitoring of the elements must be enabled explicitly in the marked checkbox on the top left.
-
-Once the monitoring entities of interest have been arranged in such way, the user can save it for later usage by means of the globe icon (''Global'')
-on top of the tree view. Right mouse button menu on such icon offers a ''Direct link'' option which will copy the current view to another browser window.
-The URL of this new browser window (or tab depending on browser set up) contains all required information, including the monitoring mode of the plots.
-It can be stored as bookmark (favourite address) in the browser, so it can be recalled later to show the user defined display.
-% \begin{figure}[htb]
-% \centering
-% \includegraphics[width=1\textwidth]{bnetgui_plain_cut.png}
-% \caption[Default BNET master control gui]{Default BNET master control gui}
-% \label{fig:ebmonitorguide:bnetguiplain}
-% \end{figure}
-%
+Figure \ref{fig:ebmonitorguide:dabc2} describes the GUI elements related to data taking and file writing. The respective buttons on top allow to select the next run type
+and to start and stop datataking at any time. Note that the BNET processes are not restarted when changing the run type as with the old eventbuilders, but continue even when
+writing to files is stopped. In this case, just the filename display will become empty and the builder node color turns yellow.
+Clicking on any of the rate and file size numbers allows to watch the trending graph of the assigned value in the display area.
+
+\newpage
+
+
\clearpage
\end{figure}
-\begin{figure}[htb]
- \centering
- \includegraphics[width=.9\textheight,page=3,angle=90]{figures/bnetmonitorguide.pdf}
- \caption[DABC BNET web GUI: input monitor]{BNET web GUI: hub and trb3 monitor}
- \label{fig:ebmonitorguide:dabc3}
-\end{figure}
-
-
-\begin{figure}[htb]
- \centering
- \includegraphics[width=.9\textheight,page=4,angle=90]{figures/bnetmonitorguide.pdf}
- \caption[DABC BNET web GUI: show triggertype]{BNET web GUI: how to show trigger type statistics}
- \label{fig:ebmonitorguide:dabc4}
-\end{figure}
-
-
-\begin{figure}[htb]
- \centering
- \includegraphics[width=.9\textheight,page=5,angle=90]{figures/bnetmonitorguide.pdf}
- \caption[DABC BNET web GUI: eventbuilder terminals for each node]{BNET web GUI: how to show eventbuilder terminals for each node}
- \label{fig:ebmonitorguide:dabc5}
-\end{figure}
-
-\begin{figure}[htb]
- \centering
- \includegraphics[width=.9\textheight,page=6,angle=90]{figures/bnetmonitorguide.pdf}
- \caption[DABC BNET web GUI: Expert browser and user defined GUI]{BNET web GUI: how to set up a user defined GUI display}
- \label{fig:ebmonitorguide:dabc6}
-\end{figure}
+% \begin{figure}[htb]
+% \centering
+% \includegraphics[width=.9\textheight,page=3,angle=90]{figures/bnetmonitorguide.pdf}
+% \caption[DABC BNET web GUI: input monitor]{BNET web GUI: hub and trb3 monitor}
+% \label{fig:ebmonitorguide:dabc3}
+% \end{figure}
+%
+%
+% \begin{figure}[htb]
+% \centering
+% \includegraphics[width=.9\textheight,page=4,angle=90]{figures/bnetmonitorguide.pdf}
+% \caption[DABC BNET web GUI: show triggertype]{BNET web GUI: how to show trigger type statistics}
+% \label{fig:ebmonitorguide:dabc4}
+% \end{figure}
+%
+%
+% \begin{figure}[htb]
+% \centering
+% \includegraphics[width=.9\textheight,page=5,angle=90]{figures/bnetmonitorguide.pdf}
+% \caption[DABC BNET web GUI: eventbuilder terminals for each node]{BNET web GUI: how to show eventbuilder terminals for each node}
+% \label{fig:ebmonitorguide:dabc5}
+% \end{figure}
+%
+% \begin{figure}[htb]
+% \centering
+% \includegraphics[width=.9\textheight,page=6,angle=90]{figures/bnetmonitorguide.pdf}
+% \caption[DABC BNET web GUI: Expert browser and user defined GUI]{BNET web GUI: how to set up a user defined GUI display}
+% \label{fig:ebmonitorguide:dabc6}
+% \end{figure}
\clearpage
%
\subsection{Eventbuilder monitoring in hmon}
-This is new and documentation still to do.
+This main hmon monitoring page offers a summary of most relevant eventbuilder status under the ''EBSummary'' section at the address
+\url{https://hades33/eb}http://hades33/mon/monitor.cgi?2-EBSummary}.
+Figure \ref{fig:evtbuild:ebsummary} shows the main components of it
+
jspc29 / daqdocu.git / commitdiff
