\textbf{2019/03/25 - this page will be updated during the beamtime}
\begin{itemize*}
-\item If one board is missing, do not panic! Do not risk many seconds of possible data taking for
-one missing board. Up to 2 (MDC endpoints missing or MBO w/o data) and up to 3 RICH
-front-ends is acceptable - don't restart the DAQ more than once per 30 minutes if only few boards
-are missing. But don’t run for too long with too many missing boards. The missing MDC endpoints
-should not be in the same chamber (same first 3 digits)
\item MDC 0x2057 is off and can’t be recovered by the operator
\end{itemize*}
+\clearpage
+
+
+\section{Main Tasks}
+\begin{itemize*}
+ \item Operate the data acquisition, mainly using the
+\hyperref[section:daqcontrolgui]{Control GUI}.
+ \item Monitor the status of the whole system, mainly using the
+\hyperref[sec:tacticaloverview]{Tactical Overview}.
+ \item Monitor some detailed performance data using the \hyperref[sec:hmon]{Hmon Plots}.
+ \item Run the \hyperref[sec:onlineqa]{Online QA} with analysis of the actual detector performance.
+ \item Make entries to the logbook about configuration changes and important issues.
+\end{itemize*}
\section{General Remarks}
\item Don’t hesitate to \textbf{call the expert} if there is a problem you can’t solve or you don't
fully understand!
-\item At least \textbf{once a day}, when there is a break >15 minutes, a full restart of the system
+\item At least once a day, when there is a break >15 minutes, a \textbf{full restart} of the system
should be performed. Talk to the DAQ expert to get this done!
-\item Almost \textbf{everything can be accessed} from the web page (\url{http://hades33/mon}, open
-in Firefox, preferably using an aptly named profile) and the Control GUI (icon on desktop)
+\item Almost \textbf{everything can be accessed} from the web page (\url{http://hades33/mon} and
+the Control GUI (icon on desktop)
\item Make sure you have access to everything well before your shift (e.g. set up tunnels for
remote work ->
[item:daqcontrol.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:eboperatorguide.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:ebstartup.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:expert_networkaddresses.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:expert_powersupplies.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:hadesoperator.kilepr]
archive=true
[item:hmon.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:main.aux]
archive=true
[item:main.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:main.toc]
archive=true
[item:powercycles.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:tacticaloverview.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
[item:tdccalibration.tex]
archive=true
-encoding=
-highlight=
-mode=
+encoding=UTF-8
+highlight=LaTeX
+mode=LaTeX
-
+\label{sec:tacticaloverview}
\begin{figure}[htp]
\centering
just a result. Some help texts tell you to ``look elsewhere''. Eventbuilder problems can't be fixed
while there is a DAQ problem.
- \item Errors are often listed with the networ address of the corresponding front-end board. Chec
+ \item Errors are often listed with the network address of the corresponding front-end board. Check
the table of addresses [\ref{sec:addresses}] to find out which subsystem it belongs to.
\item The error handling guides are usually written to be executed step by step. If the system is