describe calibration procedure

diff --git a/hadesoperator/calibration.tex b/hadesoperator/calibration.tex
new file mode 100644 (file)
index 0000000..150e455
--- /dev/null
+++ b/hadesoperator/calibration.tex
@@ -0,0 +1,16 @@
+A calibration of TDCs has to be done regularly. The affected sub-systems are ECAL, RICH and Start.
+The whole process takes a few minutes.
+It is needed if:
+\begin{itemize*}
+ \item The temperature of TDC boards changed by more than 5 degrees
+ \item The last calibration was done more than a day ago
+ \item There were boards added to the system for which there is no calibration data available
+\end{itemize*}
+
+It is suggested to run a calibration cycle about once a day (less is fine if temperatures are stable) and when there is a time window available (e.g. when the parasitic user takes over). As temperature is an important factor, the calibration should not be done immediately after power was switched on.
+
+There is an icon in the Tactical Overview checking the status of calibration near the lower left corner - it automatically checks the reasons for re-calibration as listed above.
+
+To do a calibration, use the "TDC Calibration" buttons in the DAQ control window. After clicking "Start TDC Cal", the Tactical Overview will show the (approximate) progress of the process. Once it is completed, use "Stop TDC Cal" to return to the normal data taking mode.
+
+Make sure that the Tactical Overview now shows the new time of the last calibration. If there was a DAQ failure (either restart or failing boards\footnote{Only from ECAL, RICH and Start. MDC is not affected by this run} while the calibration took place, the process has to be repeated.

diff --git a/hadesoperator/ebmonitoring.tex b/hadesoperator/ebmonitoring.tex
index a75bdb9d99e981f40e67a1d9615ba4b9141c8817..cc445e7439a5e5fb9cb757dd3b3c91476e11774d 100644 (file)
--- a/hadesoperator/ebmonitoring.tex
+++ b/hadesoperator/ebmonitoring.tex
@@ -1,7 +1,7 @@
 The BNET master node offers a monitoring and control GUI on a webserver at the address 
 {\tt http://hades33/eb/}. The default GUI displays the state of the BNET as shown in
-in figure \ref{fig:evtbuild:bnetgui}. All nodes of the BNET show up as separate rows with respective properties (hub inputs, file outputs) monitored. Clicking on
-an element will allow further inspection and trending plots. 
+in figure \ref{fig:evtbuild:bnetgui}. All nodes of the BNET show up as separate rows with respective properties (hub inputs, file outputs) monitored. Clicking on an element will allow further inspection and trending plots. 
+
 
 \begin{figure}[htb]
   \centering
@@ -9,3 +9,5 @@ an element will allow further inspection and trending plots.
   \caption[BNET master web control gui]{BNET master web control gui}
   \label{fig:evtbuild:bnetgui}
 \end{figure}
+
+This interface is usually not needed for the DAQ operator, but gives additional ways to debug error situations. The necessary information about event builder status can be found in the main monitoring page under "EBSummary".

diff --git a/hadesoperator/hmon.tex b/hadesoperator/hmon.tex
index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..97f1157c0ae4cdf63e8f7a5277978c2f9303946f 100644 (file)
--- a/hadesoperator/hmon.tex
+++ b/hadesoperator/hmon.tex
@@ -0,0 +1,4 @@
+Most monitoring can be accessed via the main web interface, available on \url{http://hades33/mon}.
+The most important windows to be open at all times are the "Tactical Overview" and the ones listed in the "Operator Monitor" box. They should be arranged on the upper left screens so that they can be seen from everywhere in the counting house.
+
+The description of the plots shown and the features to look out for are listed below.

diff --git a/hadesoperator/main.tex b/hadesoperator/main.tex
index fbe788c40ad370a4871e277aa49540485b575281..b1ea59ca0c748a3efd6e940aa9405567e324e996 100644 (file)
--- a/hadesoperator/main.tex
+++ b/hadesoperator/main.tex
@@ -122,7 +122,8 @@
 
 \clearpage
 \part{Handling Procedures}
-\section{TDC Cablibration Run}
+\section{TDC Calibration Run}
+\input{calibration}
 
 \section{Power Cycles}
 \input{powercycles}