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.
+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 in the lowest row. 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.
-\subsection{TDC calibration in DABC software}
-The calibration of the trb3 TDC finetime counters is currently handled in the eventbuilder input nodes with the DABC software.
-The eventbuilder software has to aquire calibration information for each trb3 channel with special ''calibration runs''.
-In these runs the CTS will operate a pulser trigger of a few 100 Hz with a dedicated {\em calibration trigger} of type D.
-The trb3 boards will then produce special calibration data that is used to find out the channel-specific corrections.
-This calibration information is stored by DABC and will be used in all subsequent runs to mark the raw data from trb3 systems
-with correction factors for each hit message. The calibration meta information extracted from the calibration run is kept as file for
-each input subsystem on the eventbuilder server. It is also archived automatically to the tsm and /lustre storage
-into the subfolder {\em cal}
-
-\subsection{Operator calibration procedure}
-Since the TDC fine time calibration may change due to temperature changes or other long term drifts, it is necessary to repeat
-the calibration procedure frequently. The uppermost left field in the BNET control GUI tells the time since last successful
-calibration (see Fig. \ref{fig:evtbuild:bnetgui} where the time is shown as ''7h04m''). If this display turns red, usually a calibration
-run has to be performed.
-
-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 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''.
-
-
- \item Observe 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 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 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 Be sure that the beam or the desired trigger source is switched on before starting beam or cosmics files again!
-
-\end{enumerate}
-
+If the run takes longer than 5 minutes, there might be problems with noise or other data from the detectors. Try switching off beam and/or setting thresholds higher if nothing else helps.
jspc29 / daqdocu.git / commitdiff