Small changes by JoF

diff --git a/hadesoperator/daqcontrol.tex b/hadesoperator/daqcontrol.tex
index fc1750533d62194a979cf75aa8fbad3e4613038f..619804e4a06723ad0084855b2b45df59897ac962 100644 (file)
--- a/hadesoperator/daqcontrol.tex
+++ b/hadesoperator/daqcontrol.tex
@@ -55,8 +55,8 @@ eventbuilder monitor and are NOT accounted in the runtime database.
 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). It shall be followed by 
-clicking ''TEST file'' (or COSMICS or whatever) to start recording data again.
+ \item[Restart EB] Start eventbuilders again (with most recent settings). It needs to be followed by 
+clicking ''BEAM file'' (or ''TEST file'' or whatever) to start recording data again.
  \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.
@@ -83,7 +83,7 @@ trigger inputs and send special calibration events with a 500 Hz pulser.
   \item[Stop TDC CAL] Stop the calibration run for trb3 TDCs that was started with the above button. 
 This button has to be pressed when all DAQ input subsystems as shown 
   in the eventbuilder input nodes have turned from blue to green color. On pressing, the ''TC'' 
-files are stopped and the new calibration is used for the next data taking runs.
+files are stopped and the new calibration is used for the next data taking runs. For more info see sec.~\ref{sec:tdc_calibration_procedure}.
  \item[Stop EB] Stop eventbuilders. For expert and testing purpose only! 
  \item[MDC HighVoltageRamp]
  \item[Restart BNET Control] Restart the DABC master process that controls the building 
@@ -91,6 +91,9 @@ network (BNET). This process also delivers the eventbuilder monitoring at  \url{
  \item[Restart Hmon] use to activate changes in main monitoring
  \item[Restart Rawdata Mon] Restart the DABC analysis of the raw data contents. Use this button if \url{https://hades33/rawmon} is not working
  \item[Restart Sequencer] Restart automatic HV control procedures in EPICS
+ \item[Set RICH HV] Switches on all RICH HV lines and sets all HV modules to the correct supply voltage setting.
+If only one module is already switched on, this button will ramp down all HV modules instead.
+During ramp up keep an eye on \url{hades33/mon/monitor.cgi?6-RichRatev2} maximum rate should not exceed 1 MHz for longer times
  \item[Start Speech Output] Restart speech output of DAQ issues
  \item[Stop Speech Output] Silence the speech output of DAQ issues
 \end{description}
@@ -107,7 +110,7 @@ to reset the DAQ front-end boards.
 
  \item[Powercycle all] LV power cycle of everything. Requires ''Reprogram FPGA'', ''Reboot OEP'', and ''Reboot MDCHub''
  afterwards
- \item[RICH Powercycle] LV power cycle of RICH. Requires a ''Set RICH Thr'' afterwards.
+ \item[RICH Powercycle] LV power cycle of RICH.
  \item[RICH Fan Powercycle] LV power cycle of RICH Fans.  
  \item[ECAL RPC 48V Powercycle] LV powercycle for all DAQ boards mounted in the ECAL frame
  \item[ECAL Padiwa Powercycle] LV power cycle of ECAL frontends  

diff --git a/hadesoperator/daqtools.tex b/hadesoperator/daqtools.tex
index 4d73c1aa6bfa3fa4c8e42fe669d3ff2a7fc4685e..44d562d2a5f9c42f1c8715149e16d742ef0209d5 100644 (file)
--- a/hadesoperator/daqtools.tex
+++ b/hadesoperator/daqtools.tex
@@ -1,3 +1,4 @@
+\begin{center}\textbf{!Experts only!}\end{center}
 Detailed data and tables are available from using Daqtools (\url{http://hades33/daqtools}).
 These pages make direct accesses to the DAQ, so that a few access rules are necessary:
 \begin{itemize}

diff --git a/hadesoperator/hmonwindows.tex b/hadesoperator/hmonwindows.tex
index cd34d60fa42f4277b93f3d377358b6aba0eef4de..5a6a24127ca5e07d022178e03797e4add5258c19 100644 (file)
--- a/hadesoperator/hmonwindows.tex
+++ b/hadesoperator/hmonwindows.tex
@@ -47,14 +47,14 @@ fast and slow channels and their ratio
     \item[Muxhist]
     \item[Pt3AcceptRatio]
     \item[QA]
-    \item[RichGas]
+    \item[RichGas] Plots showing the gas sensors of the RICH
     \item[RichHV]
-    \item[RichInnerTemp]
-    \item[RichMagnet]
-    \item[RichRate]
-    \item[RichRatev2]
+    \item[RichInnerTemp] Display of the temperature sensors attached to the spokes inside the RICH detector 
+    \item[RichMagnet] Display of the magnetic field sensors attached to the spokes inside the RICH detector
+    \item[RichRate] RICH rate per channel (ordered by DiRICH-Nr.)
+    \item[RichRatev2] Two dimensional display of the RICH rate
     \item[RichTempHistoDiRICH]
-    \item[RichThresh]
+    \item[RichThresh] Two dimensional display of the DiRICH threshold settings
     \item[RpcRate]
     \item[RpcTofRate]
     \item[RpcTofSectorRate]

diff --git a/hadesoperator/powercycles.tex b/hadesoperator/powercycles.tex
index 536823919633a6a4e1375158143da063188f6079..3e1a1529b61b83aa8f6416f343156bc066b060f9 100644 (file)
--- a/hadesoperator/powercycles.tex
+++ b/hadesoperator/powercycles.tex
@@ -29,7 +29,7 @@ All boards of the RICH subsystem (addresses 7xxx and 82xx) are powered by the su
 Group". Use the button "RICH Powercycle" to switch them off and on again. When all power supplies 
 are active again (see the list in ``EPICS Power'' -> ``RICH LV''), do a DAQ restart.
 
-A power cycle will trigger the temperature interlock for RICH power supplies.
+In the case that the power cycle triggered the temperature interlock for RICH power supplies.
 The 3.3V supply might be blocked by the temperature interlock - restart DAQ, then try to reset it.
 
 \subsection*{Central Controls}

diff --git a/hadesoperator/tdccalibration.tex b/hadesoperator/tdccalibration.tex
index 6b17979d15e5348278a8041ca6ee875bd7467fc8..ba765450cc2dec973566b5b8d5d7c921e4e294ae 100644 (file)
--- a/hadesoperator/tdccalibration.tex
+++ b/hadesoperator/tdccalibration.tex
@@ -1,5 +1,7 @@
 
-\section{TDC Calibration procedure} The calibration needs to be done by an expert, because the 
+\section{TDC Calibration procedure} 
+\label{sec:tdc_calibration_procedure}
+The calibration needs to be done by an expert, because the 
 output of the Eventbuilders needs to be checked. This might take a while and therefore should only 
 be done during planned breaks, e.g. periods without beam.