mkohls-additions

diff --git a/hadesoperator/daqcontrol.tex b/hadesoperator/daqcontrol.tex
index 0902d4b02e0948ed351314909abcead5f805fdcc..d428a8a9d7204f52700e397d8a91b0517b7a6ef7 100644 (file)
--- a/hadesoperator/daqcontrol.tex
+++ b/hadesoperator/daqcontrol.tex
@@ -12,10 +12,10 @@ Most control tasks can be done using the DAQ Control GUI, only few things need a
 
 \subsection{DAQ-Operator}
 \begin{description}
- \item[Start DAQ] The main script to restart the DAQ 
+ \item[Start DAQ] The main script to restart the DAQ. Standard solution if some problems appear (red blinking). 
  \item[Start Stop Trigger] Interrupt sending triggers
  \item[Reprogram FPGA] Reload designs to old TRB2 based boards
- \item[Reboot OEP] Reload designs of MDC front-ends
+ \item[Reboot OEP] Reload designs of MDC front-ends (e.g. to be used if error "oeps too old" appears - let it follow a DAQ-restart!)
  \item[Reboot MDC Hub] Reload designs for MDC hub boards
  \item[ReSync Missing OEP] Tries to get a failed MDC front-end running again 
  \item[Reboot TRB3] The equivalent of 'Reprogram FPGA' for new subsystems.
@@ -47,7 +47,7 @@ Most control tasks can be done using the DAQ Control GUI, only few things need a
    \item[NO FILE] Stop recording any kind of file. This will close previous files. Note that eventbuilders are not stopped by this, but continue running without writing files.
    However, the QA and raw DAQ monitoring clients are still delivered with data in this state.
   
- \item[Restart EB] Start eventbuilders again (with most recent settings)
+ \item[Restart EB] Start eventbuilders again (with most recent settings). Has to be used, if the eight building nodes in the EBSummary-window disappear (at the moment this falsely gives no error in the tactical overview!). It shall be followed by clicking ''TEST file'' (or COSMICS or whatever) to start recording data again.
  \item[Stop EB] Stop eventbuilders. For expert and testing purpose only! 
  \item[Set N EB] Sets the number of running instances of eventbuilders and restart the building network with the new configuration. 
    Change only on request. E.g. 1 EB for cosmics, 8 or 12 EB for beam data.
@@ -95,7 +95,7 @@ clicking these buttons in the DAQ-Operator section!}
  \item[Wall Powercycle] LV power cycle of forward wall. Requires ''Reprogram FPGA''afterwards.
  \item[Start Powercycle] LV power cycle of Start detector
  \item[HUBS Powercycle] LV power cycle of trbnet hub nodes.  Requires ''Reprogram FPGA''afterwards.
- \item[MDC LV Powercycle] LV power cycle of MDC. Requires ''Reboot OEP'' afterwards.
+ \item[MDC LV Powercycle] LV power cycle of MDC. Requires ''Reboot OEP'' and ''Start DAQ'' afterwards. To be used, if DAQ- or MDCHub-restart did not work sufficiently.
 \item[RPC special PwrCyc] LV power cycle of RPC. Requires ''Reprogram FPGA''afterwards.
 
 

diff --git a/hadesoperator/main.tex b/hadesoperator/main.tex
index a13ed6228eddd315cfbe66b1575f20aad03768fa..1a5083f02e44963567513fb52e7b6ac94f929e81 100644 (file)
--- a/hadesoperator/main.tex
+++ b/hadesoperator/main.tex
@@ -108,6 +108,8 @@
 
 \part{General Advice}
 
+If one board is missing, do not panic! Do not risk many seconds of possible data taking for one missing board. Also take into account: if MDC is not running on HV, some chambers do not see any noise at all, so there will be some motherborads without data. In this case do not panic, if the ''MBO wo data'' button on the tactical overview shows some errors.
+
 \cleardoublepage
 \part{Control}
 \input{daqcontrol}
@@ -127,7 +129,7 @@
 
 \clearpage
 \part{Handling Procedures}
-\section{TDC Cablibration Run}
+\section{TDC Calibration Run}
 \input{calibration}
 
 \section{Power Cycles}

diff --git a/hadesoperator/monitors.tex b/hadesoperator/monitors.tex
index fef7885276d741d447733c3cab5ec8d4a54f92af..afb4b37e44def22b96ee686347046b415cd8b3e4 100644 (file)
--- a/hadesoperator/monitors.tex
+++ b/hadesoperator/monitors.tex
@@ -1,13 +1,7 @@
 % 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}
+Place an example plot!
 
 \begin{description}
 \item[Y axis:]
@@ -146,19 +140,7 @@ The \emph{dropped events} rate should be close to zero.
 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}
+Next to the EB status is a list of the latest written data files.
 
 % übersicht über Eventbuilder server