From 4701ed2ce77c36f325a62e8d0703718bf9b91ed6 Mon Sep 17 00:00:00 2001
From: Jan Michel <mail@janmichel.eu>
Date: Wed, 19 Jan 2022 20:46:20 +0100
Subject: [PATCH] update TDC calibration procedure
---
hadesoperator/generalremarks.tex | 7 +++--
hadesoperator/tdccalibration.tex | 48 +++++++++++++++++++++-----------
2 files changed, 36 insertions(+), 19 deletions(-)
diff --git a/hadesoperator/generalremarks.tex b/hadesoperator/generalremarks.tex
index ca8bf75..21b032e 100644
--- a/hadesoperator/generalremarks.tex
+++ b/hadesoperator/generalremarks.tex
@@ -26,6 +26,10 @@ day availability of experts is better, so you can get more help.
\item Before your first shift, please arrange with one of the other operators to spend a couple of
hours with them (preferably while having beam in the cave) to learn a bit about the operation of
the system.
+ \item If you do a remote shift, make sure you have access to the DAQ VNC (hades70:1) and the main
+web server (\url{http://hades33/mon}). Access from outside GSI needs an SSH tunnel made with your
+account. \href{https://jspc29.x-matter.uni-frankfurt.de/xmatterpad/p/HADES_GSI_Network_Access}{Some
+hints are listed here}.
\end{itemize*}
@@ -63,9 +67,6 @@ 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} 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 ->
-\href{https://jspc29.x-matter.uni-frankfurt.de/xmatterpad/p/HADES_GSI_Network_Access}{Manual})
\item Once per shift, make a summary entry to the logbook about DAQ issues. To take notes during
the shift, there is a \textbf{paper logbook} you can use to keep track about minor issues or error
diff --git a/hadesoperator/tdccalibration.tex b/hadesoperator/tdccalibration.tex
index ba76545..a4da9ca 100644
--- a/hadesoperator/tdccalibration.tex
+++ b/hadesoperator/tdccalibration.tex
@@ -10,39 +10,55 @@ The calibration procedure is as follows:
\begin{enumerate} \item Be sure that the beam is off and no other data source may interfere with the
calibration pulser!
- \item Remove old calibration files, as they will corrupt the new calibration is some larger changes
-happened. There is ~/bin/deletecalfiles.sh to help.
+ \item {\bf Remove old calibration} files, as they will corrupt the new calibration is some larger
+changes
+happened. There is ~/bin/deletecalfiles.sh to help. Use {\bf Restart EB} to disable the old
+calibration.
+
+ \item Do a reboot of the ECAL TDCs.
+ \item Make sure all boards (except MDC) are up, running and delivering data.
\item Click the Button {\bf Start TDC Cal} in the DAQ operator GUI. This will disable all inputs of
the CTS and put it into the special calibration mode (trigger type D, 500~Hz pulser). The
-eventbuilders will start writing files with prefix ''TC''.
+eventbuilders will start writing files with prefix ''TC''.
+
+\item {\bf Change pulser} to 1500~Hz in the CTS GUI to speed up data taking.
- \item Check the Tactical Overview for an increasing calibration status. For details, check the
+ \item Check the Tactical Overview for an increasing calibration status (orange field in the last
+row). \\
+ For details, check the
eventbuilder BNET GUI (Fig. \ref{fig:evtbuild:bnetgui}). The ''Input nodes'' box shows for each
eventbuilder server the subsystems (''HUBs'') which send data to them from the cave. These are
labeled with their trbnet hub address, e.g. ''0x83c1''. During calibration, the trb3 systems will
turn to a blue color. The ''Run control'' caption of the webpage will show the state
''Calibrating''.
- \item When all of the input hubs in the BNET GUI have turned to green color, the calibration
+ \item When the calibration status reached 100\%, calibration can be stopped by pressing the {\bf
+Stop TDC Cal} button in the DAQ control GUI (do not
+stop the run with the ''NO FILE'' button, and do not start immediately recording any other files
+types by the corresponding control GUI buttons). \\
+ In the BNET GUI all of the input hubs have turned to green color, the calibration
statistics is sufficient. In this state the ''Run control'' state will show ''Ready''. It can take
several minutes until this is reached, depending on the configured calibration precision in the
setup.
-
- \item If BNET GUI (or corresponding hmon display) shows that calibration is OK, stop the
-calibration procedure by pressing the {\bf Stop TDC Cal} button in the DAQ control GUI ({\bf do not
-stop the run with the ''NO FILE'' button, and do not start immediately recording any other files
-types by the corresponding control GUI buttons}). The eventbuilders will close the calibration run
+ \item The eventbuilders will close the calibration run
files and will archive the most recent calibration information. The trigger settings of the CTS will
be restored to the values just before the calibration procedure.
- \item If BNET GUI should show that calibration is not successful after 5 minutes, find out which
-subsystems have not turned to green and stay blue instead. Please check thresholds and detector
-setup of these systems, it might be that there are noise hits in addition to the calibration pulser
-hits. The calibration procedure can be stopped at any time anyway and will use the calibration infos
-although not complete. Repeat the calibration procedure after the reason for the missing statistics
-has been fixed as soon as possible.
+ \item Make a short (30 second) {\bf TDC Caltest} run to record an additional file used to analyze
+the calibration. Preferably, stop the run just before the first set of files reaches the 1.5 GB
+size limit (see EB monitor). Root analysis of the data starts automatically. Plots are published
+on \url{http://hades33/calib}
+
+ \item After this has finished (roughly 5-10 minutes), run hmon\_tdcchanerrors\_monitor.pl in the
+hmon directory (roughly 5 minutes), then check the resulting plots in hmon - TdcCalMon.
+
+ \item You can also run a manual analysis with any hld files as input: \\
+ Connect to hades63, screen 'tdccalib'. \\
+ Create a list of all files to analyse, e.g. 'ls /store/*/*/*/tc22018114* | tee list22018.hll \\
+ run dabc\_exe tdcmon.xml, and wait ~ 50 seconds per GB of data. Plots are published on
+\url{http://hades33/calibtest}.
\item Be sure that the beam or the desired trigger source is switched on before starting beam or
cosmics files again!
--
2.43.0