def_graphic_ext=
img_extIsRegExp=false
img_extensions=.eps .jpg .jpeg .png .pdf .ps .fig .gif
-kileprversion=2
-kileversion=2.1.2
-lastDocument=networkaddresses.tex
+kileprversion=3
+kileversion=2.9.92
masterDocument=main.tex
name=daqnet
pkg_extIsRegExp=false
MakeIndex=
QuickBuild=PDFLaTeX+ViewPDF
-[document-settings,item:/local/trb/cvs/daq_docu/cts.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:/local/trb/cvs/daq_docu/tof.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:blrconfig.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:commonfeatures.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:cts.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:daqcontrol.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:daqmonitorguide.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:daqstartup.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:ebinstructions.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:ebmonitorguide.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:ebsetup.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:endpoint.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:epics.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:evtbuild.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:gbe.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:generaldaq.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:hubs.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:installation_ethernet_table.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:installation_trbnet.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=normal
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:ipudataformat.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:loggermessages.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:lvl1trigger.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:main.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:mdc.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:mdcinstructions.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:mediainterface.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:networkaddresses.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:rich.tex]
-Bookmarks=
-Encoding=ISO-8859-15
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:richinstructions.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:shortguide.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:showerdata.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:showerinstructions.tex]
-Bookmarks=
-Encoding=UTF-8
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:slowcontrol.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
-[document-settings,item:software.tex]
-Bookmarks=
-Encoding=UTF-8
-FoldedColumns=
-FoldedLines=
-Highlighting=LaTeX
-Indentation Mode=
-Mode=LaTeX
-ReadWrite=true
-
[item:/local/trb/cvs/daq_docu/cts.tex]
archive=true
-column=0
encoding=ISO-8859-15
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=14
[item:/local/trb/cvs/daq_docu/tof.tex]
archive=true
-column=0
encoding=ISO-8859-15
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=13
[item:biblio.bib]
archive=true
-column=0
encoding=ISO 8859-15
highlight=BibTeX
-line=0
mode=
-open=false
-order=-1
[item:blrconfig.tex]
archive=true
-column=14
encoding=UTF-8
highlight=LaTeX
-line=55
mode=LaTeX
-open=true
-order=19
[item:commonfeatures.tex]
archive=true
-column=0
encoding=ISO-8859-15
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=15
[item:cts.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=322
mode=LaTeX
-open=false
-order=20
[item:daqcontrol.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=63
mode=LaTeX
-open=true
-order=8
[item:daqmonitorguide.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=23
[item:daqnet.kilepr]
archive=true
-column=1769099307
encoding=
highlight=
-line=0
mode=
-open=false
-order=-1
[item:daqstartup.tex]
archive=true
-column=73
encoding=UTF-8
highlight=LaTeX
-line=177
mode=LaTeX
-open=true
-order=12
[item:ebinstructions.tex]
archive=true
-column=38
encoding=UTF-8
highlight=LaTeX
-line=2
mode=LaTeX
-open=true
-order=17
[item:ebmonitorguide.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=19
[item:ebsetup.tex]
archive=true
-column=56
encoding=UTF-8
highlight=LaTeX
-line=32
mode=LaTeX
-open=false
-order=19
[item:endpoint.tex]
archive=true
-column=98
encoding=ISO-8859-15
highlight=LaTeX
-line=117
mode=LaTeX
-open=true
-order=4
[item:epics.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=true
-order=15
[item:evtbuild.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=155
mode=LaTeX
-open=false
-order=16
[item:gbe.tex]
archive=true
-column=0
encoding=ISO-8859-15
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=12
[item:generaldaq.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=true
-order=9
[item:hubs.tex]
archive=true
-column=157
encoding=UTF-8
highlight=LaTeX
-line=59
mode=LaTeX
-open=true
-order=2
[item:installation_ethernet_table.tex]
archive=true
-column=6
encoding=UTF-8
highlight=LaTeX
-line=122
mode=LaTeX
-open=true
-order=11
[item:installation_trbnet.tex]
archive=true
-column=23
encoding=UTF-8
highlight=LaTeX
-line=81
mode=LaTeX
-open=true
-order=20
[item:ipudataformat.tex]
archive=true
-column=58
encoding=UTF-8
highlight=LaTeX
-line=240
mode=LaTeX
-open=true
-order=3
[item:loggermessages.tex]
archive=true
-column=57
encoding=UTF-8
highlight=LaTeX
-line=49
mode=LaTeX
-open=true
-order=10
[item:lvl1trigger.tex]
archive=true
-column=54
encoding=UTF-8
highlight=LaTeX
-line=40
mode=LaTeX
-open=true
-order=5
[item:main.tex]
archive=true
-column=10
encoding=UTF-8
highlight=LaTeX
-line=178
mode=LaTeX
-open=true
-order=0
[item:mdc.tex]
archive=true
-column=72
encoding=ISO-8859-15
highlight=LaTeX
-line=62
mode=LaTeX
-open=true
-order=1
[item:mdcinstructions.tex]
archive=true
-column=132
encoding=UTF-8
highlight=LaTeX
-line=35
mode=LaTeX
-open=true
-order=18
[item:mediainterface.tex]
archive=true
-column=45
encoding=UTF-8
highlight=LaTeX
-line=110
mode=LaTeX
-open=true
-order=7
[item:networkaddresses.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=21
mode=LaTeX
-open=true
-order=21
[item:rich.tex]
archive=true
-column=21
encoding=ISO-8859-15
highlight=LaTeX
-line=269
mode=LaTeX
-open=true
-order=6
[item:richinstructions.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=true
-order=16
[item:shortguide.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=21
[item:showerdata.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=7
[item:showerinstructions.tex]
archive=true
-column=0
encoding=UTF-8
highlight=LaTeX
-line=0
mode=LaTeX
-open=false
-order=22
[item:slowcontrol.tex]
archive=true
-column=18
encoding=UTF-8
highlight=LaTeX
-line=334
mode=LaTeX
-open=true
-order=14
[item:software.tex]
archive=true
-column=21
encoding=UTF-8
highlight=LaTeX
-line=356
-mode=LaTeX
-open=true
-order=13
-
-[view-settings,view=0,item:/local/trb/cvs/daq_docu/cts.tex]
-CursorColumn=0
-CursorLine=0
-
-[view-settings,view=0,item:/local/trb/cvs/daq_docu/tof.tex]
-CursorColumn=0
-CursorLine=0
-
-[view-settings,view=0,item:blrconfig.tex]
-CursorColumn=14
-CursorLine=55
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:commonfeatures.tex]
-CursorColumn=0
-CursorLine=0
-
-[view-settings,view=0,item:cts.tex]
-CursorColumn=0
-CursorLine=322
-
-[view-settings,view=0,item:daqcontrol.tex]
-CursorColumn=0
-CursorLine=63
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:daqmonitorguide.tex]
-CursorColumn=0
-CursorLine=3
-
-[view-settings,view=0,item:daqstartup.tex]
-CursorColumn=73
-CursorLine=177
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:ebinstructions.tex]
-CursorColumn=38
-CursorLine=2
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:ebmonitorguide.tex]
-CursorColumn=0
-CursorLine=2
-
-[view-settings,view=0,item:ebsetup.tex]
-CursorColumn=56
-CursorLine=32
-
-[view-settings,view=0,item:endpoint.tex]
-CursorColumn=98
-CursorLine=117
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:epics.tex]
-CursorColumn=0
-CursorLine=0
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:evtbuild.tex]
-CursorColumn=0
-CursorLine=155
-
-[view-settings,view=0,item:gbe.tex]
-CursorColumn=0
-CursorLine=0
-
-[view-settings,view=0,item:generaldaq.tex]
-CursorColumn=0
-CursorLine=0
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:hubs.tex]
-CursorColumn=157
-CursorLine=59
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:installation_ethernet_table.tex]
-CursorColumn=6
-CursorLine=122
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:installation_trbnet.tex]
-CursorColumn=23
-CursorLine=81
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:ipudataformat.tex]
-CursorColumn=58
-CursorLine=240
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:loggermessages.tex]
-CursorColumn=57
-CursorLine=49
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:lvl1trigger.tex]
-CursorColumn=54
-CursorLine=40
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:main.tex]
-CursorColumn=10
-CursorLine=178
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:mdc.tex]
-CursorColumn=72
-CursorLine=62
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:mdcinstructions.tex]
-CursorColumn=132
-CursorLine=35
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:mediainterface.tex]
-CursorColumn=45
-CursorLine=110
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:networkaddresses.tex]
-CursorColumn=0
-CursorLine=21
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:rich.tex]
-CursorColumn=21
-CursorLine=269
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:richinstructions.tex]
-CursorColumn=0
-CursorLine=0
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:shortguide.tex]
-CursorColumn=0
-CursorLine=29
-
-[view-settings,view=0,item:showerdata.tex]
-CursorColumn=0
-CursorLine=0
-
-[view-settings,view=0,item:showerinstructions.tex]
-CursorColumn=0
-CursorLine=0
-
-[view-settings,view=0,item:slowcontrol.tex]
-CursorColumn=18
-CursorLine=334
-JumpList=
-ViMarks=
-
-[view-settings,view=0,item:software.tex]
-CursorColumn=21
-CursorLine=356
-JumpList=
-ViMarks=
+mode=LaTeX
+++ /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. before we take beam back from the parasitic user). 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. First, make sure that all boards are running and no front-ends (especially from RICH, ECAL, Start) are missing. If some are missing, follow the usual procedures to recover them.
-
-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. Be patient now, the EB need some time to actually finish the process.
-
-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.
-
-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. The EB monitor can give some hints on where the problem is located.
\subsection{DAQ-Operator}
\begin{description}
\item[Start DAQ] The main script to restart the DAQ. Standard solution if some problems appear (red blinking).
- \item[Start Stop Trigger] Interrupt sending triggers
- \item[Reprogram FPGA] Reload designs to old TRB2 based boards (RPC, TOF, FW, CTS only)
- \item[Reboot OEP] Reload designs of MDC front-ends (e.g. to be used if error "oeps too old" appears - let it follow a DAQ-restart!)
+ \item[Start Stop Trigger] Interrupt sending triggers to stop data taking for a while
+ \item[Reprogram FPGA] Reload designs to old TRB2 based boards (CTS only)
+ \item[Reboot OEP] Reload designs of MDC front-ends (e.g. to be used if error "oeps too old"
+appears)
\item[Reboot MDC Hub] Reload designs for MDC hub boards
\item[ReSync Missing OEP] Tries to get a failed MDC front-end running again
- \item[Resync DiRich] Tries to recover failing RICH front-ends. Might need a DAQ restart afterwards
+ \item[Resync DiRich] Tries to recover failing RICH front-ends
\item[Reboot CentralHubs] Reloads the firmware for all central hub boards (1)
\item[Reboot DiRich] Reloads the firmware for RICH front-ends (1)
\item[Reboot Ecal] Reloads the firmware for all ECal boards (1)
\item[Reboot RICH Combiner] Reloads the firmware for the first layer of RICH network hubs (1)
- \item[Reboot RICH hubs] Reloads the firmware for the second layer of RICH network hubs (1)
+ \item[Reboot RICH Hubs] Reloads the firmware for the second layer of RICH network hubs (1)
\end{description}
The tools marked with (1) can only be used succesfully, if all boards are responding and are not reported as missing. If there are missing boards, first try a DAQ restart and then the reboot.
\begin{description}
\item[CTS Mon] The monitor for CTS settings and scalers. One instance should be open for experts, but usually not needed by the operator
\item[Hmon] Opens a browser pointed at \url{https://hades33/mon}
- \item[Epics old] Opens the old "blue" EPICS. Only needed to open the power supply window ("crate LV"), the rest are detector expert tools
- \item[BNET] Opens a browser pointed at \url{https://hades33/eb} to monitor eventbuilders
- \item[DAQ Rawmon] Opens a browser pointed at \url{https://hades33/rawmon} for low level data analysis. Expert tool
- \item[Daq VNC] This VNC is typically used by experts to remotely control the system. Not used for operating the system from the control room
+ \item[Epics Power] Opens a VNC with the EPICS control for power supplies
+ \item[Eventbuilder] Opens a browser pointed at \url{https://hades33/eb} to monitor eventbuilders -
+mainly for experts
+ \item[Daq VNC] This VNC is typically used by experts to remotely control the system. Not used for
+operating the system from the control room
\item[Chat] A terminal based chat window, not used during beam time
\item[Hmon Snapshot] Creates a copy of all plots and windows in Hmon for documentation
- \item[mumble] Conferencing tool, an instance should always be running on the left DAQ computer
\end{description}
-
+
\subsection{Eventbuilder Tools}
\begin{description}
- \item[Start TDC 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
+ \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.
+ \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 on Lustre!
+ \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). Has to be used, if the eight building nodes in the EBSummary-window disappear (at the moment this falsely gives no error in the tactical overview!). It shall be followed by clicking ''TEST file'' (or COSMICS or whatever) to start recording data again.
- \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.
+ \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[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}
+ \subsection{Settings}
+ \begin{description}
+
+ \item[BLR Reinit FPGA] Reconfigures the analog trigger collection board from TOF / RPC. Use when
+rates from TOF/RPC or M2 are wrong.
+ \item[Thresholds XXX] Reload thresholds for the named detector. Use if something seems to be wrong
+with frontend settings
+ \end{description}
+
+
\subsection{Expert Tools}
{\it This section is visible only when the ''Show Expert Tools'' box on the upper left corner is checked.}
\begin{description}
+ \item[Start TDC 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[Stop EB] Stop eventbuilders. For expert and testing purpose only!
\item[MDC HighVoltageRamp]
- \item[BLR Reinit FPGA]
- \item[BLR Reload Settings]
- \item[CTS Scope]
- \item[MDC LV Turn On All Relais] Switches on power to all MDC front-ends. Use if a larger amount of boards is missing after a power cycle
- \item[Reload RICH]
- \item[Reload RPC Thresholds]
- \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 BNET Control] Restart the DABC master process 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] 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 ECAL Thr] Sets thresholds for all ECAl front-ends
- \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 (can be done while DAQ is running)
- \item[Start Speech Output]
- \item[Stop Speech Output]
+ \item[Start Speech Output] Restart speech output of DAQ issues
+ \item[Stop Speech Output] Silence the speech output of DAQ issues
\end{description}
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/or ''Reboot MDCHub'' by
-clicking these buttons in the DAQ-Operator section!}
-
+to reset the DAQ front-end boards.
+{\it These scripts might or might no be up to date. Needs some work.}
\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. Requires a ''Set RICH Thr'' afterwards.
\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.
+ \item[ECAL Padiwa Powercycle] LV power cycle of ECAL frontends
\item[ECAL Rack Powercycle] LV power cycle for some auxilliary boards in the ECAL frame
- \item[Wall Powercycle] LV power cycle of forward wall. Requires ''Reprogram FPGA'' afterwards.
+ \item[Wall Powercycle] LV power cycle of forward wall.
\item[Start Powercycle] LV power cycle of Start detector
\item[MdcTofCentral Powercycle] LV power cycle of some central boards (MDCHub, TOF, CTS...). Requires ''Reprogram FPGA'' afterwards
\item[HUBS Powercycle] LV power cycle of trbnet hub nodes.
- \item[MDC LV Powercycle] LV power cycle of MDC. Requires ''Reboot OEP'' and ''Start DAQ'' afterwards. To be used, if DAQ- or MDCHub-restart did not work sufficiently.
+ \item[MDC LV Powercycle] LV power cycle of MDC. Requires ''Reboot OEP'' and ''Start DAQ''
+afterwards. To be used, if DAQ- or MDCHub-restart did not work sufficiently.
+ \item[MDC LV Turn On All Relais] Switches on power to all MDC front-ends. Use if a larger amount
+of
+boards is missing after a power cycle
+
\item[RPC special PwrCyc] Don't use.
-% \section{Eventbuilder Operator Guide}
+\section{Eventbuilder}
\label{sec:eboperatorguide}
-\subsection{Regular beamtime control}
-During beamtime shift, data taking can be controlled by the main DAQ Operator GUI (Fig. \ref{fig:daqcontrol}).
-The GUI box {\bf Eventbuilder Tools} offers all relevant commands as shortcut buttons.
-These are described in operator manual section \ref{section:daqcontrolgui}.
\subsection{DABC Webserver controls}
-\subsection{Restart with different number of builder nodes}
-Depending on the data rate delivered from the DAQ, it may be necessary to adjust the number of builder nodes, i.e. parallel files written.
+\subsection{Regular beamtime control}
+During beamtime shift, data taking can be controlled by the main DAQ Operator GUI (Fig.
+\ref{fig:daqcontrol}).
+The GUI box {\bf Eventbuilder Tools} offers all relevant commands as shortcut buttons.
+
+\subsubsection{Restart with different number of builder nodes}
+Depending on the data rate delivered from the DAQ, it may be necessary to adjust the number of
+builder nodes, i.e. parallel files written.
For cosmics usually only 1 builder is enough, for full beam operation it may be 12 builders.
-To restart the builder network with different number of parallel files, use the buttons {\bf Set N EB}
+To restart the builder network with different number of parallel files, use the buttons {\bf Set N
+EB}
in the ''Eventbuilder Tools'' box of the DAQ operator GUI (section \ref{section:daqcontrolgui}).
If the DAQ control GUI should not be available, one can use the corresponding scripts
-\subsection{Restart of BNET master controll process}
+\subsubsection{Restart of BNET master control process}
The master control process handles the run synchronization and overall monitoring of all
nodes of the event buiding network (BNET).
-{\bf It is necessary to restart the BNET master whenever the setup of the server processes have been edited, or the DABC installation
+{\bf It is necessary to restart the BNET master whenever the setup of the server processes have
+been
+edited, or the DABC installation
has been updated!}
-To restart it, press the button {\bf Restart BNET Control} in the expert section of the DAQ operator GUI (see section
+To restart it, press the button {\bf Restart BNET Control} in the expert section of the DAQ
+operator
+GUI (see section
\ref{section:daqcontrolgui})
-If the DAQ control GUI should not be available, one can call this script directly {\bf as user hadaq on node lxhadeb07}:
-{\tt /home/hadaq/bin/restart\_bnetmaster.sh}
-
+\subsection{TDC calibration}
+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}
+
+Since the TDC fine time calibration may change due to temperature changes or other long term
+drifts, it is necessary to repeat the calibration sometimes. The Tactical Overview shows
+information about the last calibration. If this display turns red, usually a calibration run has to
+be performed. Don't do a calibration without an expert present.
--- /dev/null
+
+\section{Addressing scheme}
+
+\begin{table}[hb]
+\begin{center}
+\begin{tabularx}{\textwidth}{l|l|X}
+\textbf{Address(es)} & \textbf{Board(s)} & \textbf{Description} \\
+0000 - 01FF & Trigger & CTS: 0002, 0003; Triggerbox 0010; 2nd Triggerbox 0100, Beam Abort 0130,
+RICH Control 0110, ECal pulser 0120\\
+1000 - 17FF & MDC Concentrator & 2nd digit: inner(0) / outer(1) MDC; 3rd digit: sector (0-5), 4th
+digit FPGA (0-4) \\
+2000 - 2FFF & MDC OEP & 2nd digit: MDC layer (0-3); 3rd digit: sector (0-5); 4th digit MBO (0-F) \\
+5000 - 50FF & Start & Start/Veto. 3rd digit: 0: Start, 1: Veto, 4th digit: FPGA (0-7)\\
+
+5800 - 58FF & RPC & 3rd digit sector (0..5), 4th digit TDC (0..8) \\
+5C00 - 5CFF & TOF & 3rd digit sector (0..6), 4th digit TDC (0..3) \\
+5D00 - 5D0F & iTOF & 4th digit TDC (0..5) \\
+6000 - 60FF & Ecal & Ecal read-out. 3rd digit: Sector, 4th digit: Readout Board (0-6)\\
+6400 - 64FF & STT & 3rd digit detector part (0-7), 4th digit FPGA (0-6) \\
+6700 - 67FF & Wall & 3rd digit board (0..2), 4th digit TDC (0..3) \\
+6800 - 68FF & f-RPC & 3rd digit board number (0-1), 4th digit FPGA (0-3)\\
+7000 - 7FFF & RICH & DiRich modules. 2nd/3rd digit backplane number, 4th digit: DiRich (0-11)\\
+8000 - 80FF & Central Hub & central hub\\
+8100 - 81FF & MDC Hub & Hub for inner MDC (3rd digit 0) or outer MDC (1), 4th digit (0-5)\\
+83C0 - 83DF & RICH Hubs & Hubs for old RICH, 4th digit: hub number (0..13)\\
+84C0 - 84CF & RPC Hubs & Hubs for RPC, 4th digit: sector (0..5) \\
+86C0 - 86CF & TOF Hub & Hubs (central FPGA TRB3), 4th digit: sector(0..6)\\
+8700 - 870F & Wall Hub & 4th digit: board(0..2)\\
+8800 - 88FF & Central Hub & Central Hubs with GbE \\
+8880 - 88BF & Start Hub & Hubs for timing detectors, 8880: Start, 8890 Veto\\
+8900 - 89FF & Pion Tracker Hub & 3rd digit: station\\
+8A00 - 8AFF & Ecal Hubs& 4th digit: pseudo-sector\\
+8B00 - 8BFF & STT Hubs & 3rd digit board number (0-9)\\
+8C00 - 8CFF & f-RPC Hubs & 3rd digit board number (0-1)\\
+8D00 - 8D00 & iTOF Hub & \\
+F000 - FDFF & Test Setups & \\
+FE00 - FFFF & Broadcasts & Broadcast addresses
+\end{tabularx}
+\caption{Network Addresses}
+\label{networkaddresses}
+\end{center}
+\end{table}
+
+
+\begin{table}[hb]
+\begin{center}
+\begin{tabularx}{\textwidth}{l|X}
+\textbf{Address} & \textbf{Description} \\
+ff7f & all boards with GbE \\
+fffe & all boards with Hubs \\
+fe40 & Hubs: Trb3 central FPGA \\
+fe61 & Hubs: Trb3sc crate master \\
+fe65 & Hubs: in central crate \\
+fe66 & Hubs: RICH \\
+fe11 & MDC: Hubs, peripheral FPGA \\
+fe15 & MDC: Hubs, central FPGA \\
+fffd & MDC: OEP \\
+fe51 & RICH: DiRich \\
+fe52 & RICH: Combiner \\
+fe4c & TDC: Veto, STS \\
+fe47 & TDC: TOF, fRPC, FW \\
+fe71 & TDC: ECal \\
+fe73 & TDC: RPC \\
+fe74 & TDC: iTOF \\
+fe76 & TDC: Start
+\end{tabularx}
+\caption{Broadcast Addresses}
+\label{broadcastaddresses}
+\end{center}
+\end{table}
--- /dev/null
+
+
+\section{Power Switches and Supply control}
+\label{powersupplies}
+There are several interfaces for control, depending on the supply.
+\begin{itemize}
+
+\item EPICS Power from the control GUI
+\begin{description}
+ \item[MDC/TOF/Trigger] MDC Hubs, TOF Trb \& Fee, iTOF Trb
+ \item[ECAL/RPC] ECal Trb, RPC Trb, ECal pulser, Trigger distribution in ECAL
+ \item[Central] RICH Hubs, Central Hubs
+ \item[STS] STS Trb
+ \item[fRPC] fRPC Trb
+ \item[RPC LV] Group of 2 supplies: RPC Fee
+ \item[RICH LV] Group of 9 supplies: RICH Fee
+ \item[MDC LV] Group of 6 supplies: MDC Fee
+\end{description}
+\item Webbrowser \url{http://hades33:2222}
+\begin{description}
+ \item[RichFans] Coolings fans on RICH
+ \item[ECal 1/2/3] ECal Fee
+ \item[CentralControls] iTOF Fee, Trigger fanout at CTS, CTS Trb, BLR
+ \item[STS 1/2] STS Fee
+ \item[Start] Start Trb, Start Fee
+ \item[Veto] Hodo Trb, Hodo Fee
+ \item[iTofHV] iTOF
+ \end{description}
+
+\item Power Switches\newline
+ Web interface and/or a button in the control GUI
+ \begin{description}
+ \item[ForwardWall] \url{http://haepcp06}
+ \item[ECal Laser] \url{http://haepcp15}
+ \item[White Rabbit PC] \url{http://haepcp10}
+ \item[Pexor PC] \url{http://haepcp02}
+ \end{description}
+
+\end{itemize}
+
+Some reference values can be found at
+\url{https://hessenbox-a10.rz.uni-frankfurt.de/getlink/fiPKXwN7sRuy82d9Bbf9Md2m/PowerSupply.xlsx}
+
+
+
+
+
+++ /dev/null
-
-
-\section{Power Switches and Supply control}
-\label{powersupplies}
-\begin{description}
-\item[Start Detector TRB3] ~\\odroid1, \verb!/dev/HAMEG_HAMEG_HO720_020546031!, \url{http://odroid1:1234} \\
-Linear power supply for start detector.
-\item[RICH fans] ~\\odroid1, \verb!/dev/HAMEG_HAMEG_HO720_100030280929!, \url{http://odroid1:1234} \\
-Only cooling fans. Don't change.
-\item[RICH LV] See EPICS (PS devices 17 - 26). Powers all boards installed inside the RICH. The 3.3V supply might be blocked by the temperature interlock - restart DAQ, then try to reset it via EPICS.
-\item[ECAL 5V central] ~\\odroid6, \verb!/dev/FTDI_USB_Serial_Converter_FTGZLM92!, \url{http://odroid6:1234} \\
- Powers the trigger distribution and pulse generator in ECAL frame. Don't switch off unless absolutely necessary. Use with care, this might trigger some problems with trigger distribution.
-\item[ECAL 5V front-ends] ~\\odroid4, \verb!/dev/HAMEG_HAMEG_HO720_100030271763!, \url{http://odroid4:1234} \\
- odroid5, \verb!/dev/HAMEG_HAMEG_HO720_100030505473!, \url{http://odroid5:1234} \\
- odroid6, \verb!/dev/HAMEG_HAMEG_HO720_100030805647!, \url{http://odroid6:1234} \\
- Powers all Padiwa boards in ECAL.
-\item[ECAL, RPC 48V] See EPICS (PS device 11). Powers TRBs from RPC and ECAL and their hubs. FPGA reprogram needed.
-\item[MDC] See EPICS group. Powers MDC OEP/MBO. OEP reload needed.
-\item[CTS/TOF/MDC] See EPICS (PS device 3). Powers the CTS, TOF and MDC hubs. FPGA reprogram needed. Check multiplicity trigger settings afterwards ("BLR" icons in DAQ control). Will trigger MDC relais to be off (use "MDC Turn On All LV")
-\item[central Hubs] See EPICS (PS device 16). Powers the central hub and RICH hub. Only TRB3-based boards. A power cycle will trigger the temperature interlock for RICH power supplies.
-\item[Forward Wall] haepcp06 \\ Powers the TRB2 and Hub of Forward Wall. FPGA reprogram needed.
-\item[Pexor PC] haepcp02 \\ Hard Reset for PC.
-\item[White Rabbit PC] haepcp10 \\ Hard Reset for PC.
-\item[RPC something] haepcp15 - unknown purpose
-
-\end{description}
-
-
-\section{Reload all FPGA}
-Easiest way:
-\begin{enumerate}
- \item 'trbcmd reload 0xffff' while the DAQ is running and all boards are reachable
- \item "Reprogram FPGA"
-\end{enumerate}
-
-\section{Full Power Cycle}
-To do a full power-cycle (by experts only!): Follow the ``Daily DAQ reboot'' guide.
-
--- /dev/null
+[General]
+bib_extensions=.bib
+bibliographyBackendAutoDetected=
+bibliographyBackendUserOverride=
+def_graphic_ext=eps
+img_extIsRegExp=false
+img_extensions=.eps .jpg .jpeg .png .pdf .ps .fig .gif
+kileprversion=3
+kileversion=2.9.93
+masterDocument=
+name=hadesoperator
+pkg_extIsRegExp=false
+pkg_extensions=.cls .sty .bbx .cbx .lbx
+src_extIsRegExp=false
+src_extensions=.tex .ltx .latex .dtx .ins
+
+[Tools]
+MakeIndex=
+QuickBuild=
+
+[item:hadesoperator.kilepr]
+archive=true
+encoding=
+highlight=
+mode=
\newcolumntype{C}{>{\centering\arraybackslash}X}
-\usepackage{scrpage2}
+\usepackage{scrlayer-scrpage}
\usepackage[toc,title]{appendix}
\newenvironment{itemize*}%
\begin{itemize*}
\item \textbf{Please read the additional page with notes for the DAQ Operator.}
-\item If one board is missing, do not panic! Do not risk many seconds of possible data taking for one missing board. As a rough guide 1 MDC and/or 2 RICH boards missing is acceptable. If a board goes missing after an hour of data taking, you can restart the DAQ, but don't do it too often in case of frequent failures.
+\item The DAQ operator should always be present in the Mumble channel ``Operators Corner'' - DAQi
+will provide some audible (sometimes even recognizable) hints if something is wrong.
-\item If the high voltage on some detectors is not at nominal values, it's perfectly normal to get some warnings for this subsystem, like boards that don't deliver any data. Always check with the detector responsible to see whether this is expected behavior or an error in the DAQ.
+\item If one board is missing, do not panic! Do not risk many seconds of possible data taking for
+one missing board. As a rough guide 1 MDC and/or 2 RICH boards missing is acceptable. If a board
+goes missing after an hour of data taking, you can restart the DAQ, but don't do it too often in
+case of frequent failures.
+
+\item If the high voltage on some detectors is not at nominal values, it's perfectly normal to get
+some warnings for this subsystem, like boards that don't deliver any data. Always check with the
+detector responsible to see whether this is expected behavior or an error in the DAQ.
\item Don't forget to monitor the QA windows to see whether data quality is ok.
+
+\item If you notice something noteworthy in the Hmon monitoring, use the ``Hmon Snapshot'' button
+to store the current plots for later analysis.
+
\end{itemize*}
\part{Monitoring}
\section{Tactical Overview}
\input{tacticaloverview}
-
+\clearpage
\section{Hmon Plots}
\input{hmon}
\input{monitors}
-
+\clearpage
\section{Eventbuilder}
\input{ebmonitoring}
\clearpage
\part{Handling Procedures}
-\section{TDC Calibration Run}
-\input{calibration}
+\clearpage
\section{Power Cycles}
\input{powercycles}
-\section{Eventbuilder restart}
+\clearpage
+\section{Eventbuilder Control}
\input{ebstartup}
-\clearpage
-\part{QA}
-\section{QA Control}
-\clearpage
+% \clearpage
+% \part{QA}
+% \section{QA Control}
+\clearpage
\part{Expert Section}
-\input{expertknowledge}
+\clearpage
+\input{expert_networkaddresses}
+\clearpage
+\input{expert_powersupplies}
+
+\clearpage
+\input{tdccalibration}
\clearpage
-\section{Eventbuilder}
\input{eboperatorguide}
The main power supplies can be controlled. A full list for the experts can be found in section \ref{powersupplies}.
-Before doing a power cycle, please stop trigger using ``Start Stop Trigger'' in the control window.
+Before doing a power cycle, please stop the trigger using ``Start Stop Trigger'' in the control
+window.
-\begin{figure}[htp]
- \centering
- \includegraphics[width=\textwidth]{figures/EpicsLvSupplies.png}
- \caption{Controls for main Power Supplies}
- \label{fig:powersupplycontrol}
-\end{figure}
+% \begin{figure}[htp]
+% \centering
+% \includegraphics[width=\textwidth]{figures/EpicsLvSupplies.png}
+% \caption{Controls for main Power Supplies}
+% \label{fig:powersupplycontrol}
+% \end{figure}
\subsection{MDC Chamber}
-If a few MDC boards fail (with a "FEE error" or "MBO w/o data") and a DAQ restart doesn't help (or is needed frequently), a power cycle of one MDC chamber can be performed: Read the address of the failing board (e.g. 2045) from the Tactical Overview. Use the Icon "MDC LV Powercycle" and select the corresponding button (here 204x).
-Afterwards, the correct FPGA design needs to be loaded to the OEP. Click the ``RebootOEP'' button. After 10 seconds all OEP are rebooted and DAQ can be started again. If rebooting of the OEP fails, first run a DAQ start-up until the script complains ``OEP design too old''. Close the window and try ``Reboot OEP'' again.
+If a few MDC boards fail (with a "FEE error" or "MBO w/o data") and a DAQ restart doesn't help (or
+is needed frequently), a power cycle of one MDC chamber can be performed: Read the address of the
+failing board (e.g. 2045) from the Tactical Overview. Use the Icon "MDC LV Powercycle" and select
+the corresponding button (here 204x).
+Afterwards, the correct FPGA design needs to be loaded to the OEP. Click the ``RebootOEP''
+button. After 10 seconds all OEP are rebooted and DAQ can be started again. If rebooting of the OEP
+fails, first run a DAQ start-up until the script complains ``OEP design too old''. Close the window
+and try ``Reboot OEP'' again.
\subsection{Full MDC}
-If it's unclear which part of MDC causes an error, or if there is a larger number of boards failing, you can do a complete MDC power cycle using "EPICS old" and "MDC Group" instead of using the "MDC LV Powercycle".
+If it's unclear which part of MDC causes an error, or if there is a larger number of boards
+failing, you can do a complete MDC power cycle using "EPICS Power" and "MDC Group" instead of using
+the "MDC LV Powercycle".
\subsection{RICH}
-All boards of the RICH subsystem (addresses 7xxx and 82xx) are powered by the supplies in the "RICH 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 old'' -> ``LV crates''), do a DAQ restart.
+All boards of the RICH subsystem (addresses 7xxx and 82xx) are powered by the supplies in the "RICH
+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.
-\subsection{ECal / RPC}
-There are two separate power supplies for ECal: The front-ends (Padiwa) can be power cycled using "ECAL Padiwa Powercycle". After that a DAQ restart is needed to load the correct settings again.
+A power cycle will trigger 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.
-The TRB boards share a common power supply with RPC (``ECAL RPC 48V Powercycle''), so that a "Reprogram FPGA" is needed afterwards.
+\subsection{Central Controls}
+If a power cycle of the ``Central Controls'' was done, don't forget to ``Reprogram FPGA'' and
+``BLR Reinit FPGA'' before the DAQ restart.
+\subsection{Other Subdetectors}
+Check section \ref{powersupplies} to see which power supply to switch.
\subsection{Full Powercycle}
-A full powercycle should only be done after contact with an expert. Follow the guide for the ``Daily Powercycle''.
+A full powercycle should only be done after contact with an expert. Follow the guide for the
+``Daily Powercycle''.
-\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.
+\section{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.
The calibration procedure is as follows:
jspc29 / daqdocu.git / commitdiff
