--- /dev/null
++\subsection{General remarks}
+ 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.
++
++\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}
++
\subsection{Eventbuilder Tools}
\begin{description}
++<<<<<<< HEAD
+ \item[StartTDC CAL] Start calibration run for the trb3 TDCs. This will disable the regular CTS trigger inputs and send special calibration events with a 500 Hz pulser.
+ At the same time, the eventbuilders will record files of prefix ''TC''.
+ \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.
+ \item[BEAM files] Start recording files triggered with accelerator beam. These appear with prefix ''BE'' in eventbuilder monitor and are accounted in the runtime database (logbook).
+ \item[COSMICS files] Start recording files triggered without beam by cosmic radiation. These appear with prefix ''CO'' in eventbuilder monitor and are accounted in the runtime database
+ (logbook).
+ \item[Test file] Start recording any kind of test files. These appear with prefix ''TE'' in eventbuilder monitor and are NOT accounted in the runtime database.
+ Test files are not stored permanently!
+ \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[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.
+
+ \end{description}
++=======
+ \item[Start TDC CAL] Start process of TDC calibration
+ \item[Stop TDC CAL] Stops the TDC calibration, returns to normal data taking
+ \item[BEAM Files] Start to write "be" beam files
+ \item[COSMICS Files] Start to write "co" cosmics files
+ \item[TEST file] Start to write "te" test files without important data
+ \item[NO file] Leave eventbuilder running, but don't write data to disk
+ \item[Restart EB] Start eventbuilders again (with new settings or after stop / failure)
+ \item[Stop EB] Stop eventbuilders (not actually needed, select "NO file" instead)
+ \item[Set N EB] Sets the number of running instances of eventbuilders. Change only on request. E.g. 1 Builder for cosmics, 6/8 for beam data.
+ \end{description}
++>>>>>>> 3b2a03d2619e1b12a39f0716a97d1f584112e0af
\subsection{Expert Tools}
+{\it This section is visible only when the ''Show Expert Tools'' box on the upper left corner is checked.
+It contains actions which are not necessary for regular DAQ operation.}
+
\begin{description}
\item[MDC HighVoltageRamp]
\item[BLR Reinit FPGA]
\item[BLR Reload Settings]
\item[CTS Scope]
\item[MDC LV Turn On All Relais]
++<<<<<<< HEAD
+ \item[Reload RICH]
++=======
+ \item[Relaod RICH]
++>>>>>>> 3b2a03d2619e1b12a39f0716a97d1f584112e0af
\item[Reload RPC Thresholds]
- \item[Restart BNET Control]
+ \item[Restart BNET Control] Restart the DABC master process on lxhadeb07 that controls the building network (BNET).
+ This process also delivers the eventbuilder monitoring at \url{https://hades33/eb}
\item[Restart Hmon] use to activate changes in main monitoring
- \item[Restart Rawdata Mon] Use if \url{https://hades33/rawmon} is not working
+ \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]
\item[Set RICH HV] Switches RICH HV on if all channels are off, otherwise switches RICH HV off
\item[Set RICH Thr] Sets thresholds in RICH to default values from file
\item[Stop Speech Output]
\end{description}
- \end{description}
++<<<<<<< HEAD
+
+\subsection{Power Tools}
+This section offers buttons to cycle the low voltage supplies of several detector systems. These are convenience
+shortcuts to avoid operations on the full detector control system GUI.
+A power cycle may be necessary in some situations
+to reset the DAQ front-end boards. {\bf Note that after a power cycle it is mostly mandatory to perform
+a ''Reprogram FPGA'', ''Reboot OEP'' and ''Reboot MDCHub'' by
+clicking these buttons in the DAQ-Operator section!}
+
+\begin{description}
+ \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.
+ \item[RICH Fan Powercycle] LV power cycle of RICH Fans.
+ \item[ECAL LV5 Powercycle] LV power cycle of ECAL.
+ \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[RPC special PwrCyc] LV power cycle of RPC. Requires ''Reprogram FPGA''afterwards.
+
+
++\end{description}
++=======
+ \subsection{Power Tools}
+ \begin{description}
+ \item[Powercycle all]
+ \item[RICH Powercycle]
+ \item[RICH Fan Powercycle] Switches RICH fans on/off
+ \item[ECal 5V Entrance Powercycle]
+ \item[ECal LV5 Powercycle]
+ \item[Wall Powercycle]
+ \item[Start Powercycle]
+ \item[Hubs Powercycle]
+ \item[MDC LV Powercycle]
+ \item[RPC special PwrCyc]
+
+ \end{description}
++>>>>>>> 3b2a03d2619e1b12a39f0716a97d1f584112e0af
jspc29 / daqdocu.git / commitdiff