From: Jan Michel Date: Thu, 27 Jan 2022 09:37:16 +0000 (+0100) Subject: couple of updates to Operator manual X-Git-Url: https://jspc29.x-matter.uni-frankfurt.de/git/?a=commitdiff_plain;h=f203375c4cfebb08a03acbba05deb761deb1cd70;p=daqdocu.git couple of updates to Operator manual --- diff --git a/hadesoperator/expert_powersupplies.tex b/hadesoperator/expert_powersupplies.tex index aa6955f..1aaf70c 100644 --- a/hadesoperator/expert_powersupplies.tex +++ b/hadesoperator/expert_powersupplies.tex @@ -17,12 +17,13 @@ There are several interfaces for control, depending on the supply. \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[ECal 1/2/3] ECal Padiwa (two channels per sector) + \item[CentralControls] Channel 1: iTOF Trb\\ Channel 2: Trigger fanout at CTS, Triggerbox, +Beammonitor\\Channel 3+4: CTS Trb, BLR \item[STS 1/2] STS Fee - \item[Start] Start Trb, Start Fee + \item[Start] Channel 2+4: Start Trb \\Channel 1: Start Padiwa\\Channel 3: Start Fans \item[Veto] Hodo Trb, Hodo Fee - \item[iTofHV] iTOF + \item[iTofHV] Channel 4: iTOF SiPM power \end{description} \item Power Switches\newline diff --git a/hadesoperator/generalremarks.tex b/hadesoperator/generalremarks.tex index 21b032e..b18a1d4 100644 --- a/hadesoperator/generalremarks.tex +++ b/hadesoperator/generalremarks.tex @@ -3,7 +3,9 @@ \textbf{2022/01/19 - this page will be updated during the beamtime} \begin{itemize*} - \item MDC 0x2052 turns off immediately after DAQ start and can’t be recovered by the operator + \item There are 2 or 3 MDC front-ends that fail quite soon after a restart + \item Every couple of hours, when you do a DAQ restart, please do a ``Reload ECal'' before - this +should take just a couple of seconds. \end{itemize*} \clearpage @@ -38,16 +40,25 @@ hints are listed here}. \item The DAQ operator should always be present in the \textbf{Mumble channel} ``Operators Corner'' - DAQi will provide some audible (sometimes even recognizable) hints if something is wrong. -\item \textbf{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 2 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 Don't forget to monitor the \textbf{QA plots} to see whether data quality is ok. \item If you notice something noteworthy in the Hmon monitoring, use the \textbf{``Hmon Snapshot''} button to store the current plots for later analysis. +\item Don’t hesitate to \textbf{call the expert} if there is a problem you can’t solve or you don't +fully understand! + +\item Almost \textbf{everything can be accessed} from the web page (\url{http://hades33/mon} and +the Control GUI (icon on desktop) + + +\item At the end of the 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 +statistics. + + \item \textbf{Before making changes} to configuration or doing a power cycle, don't forget to stop triggering (Start Stop Trigger) to prevent corrupted data from being recorded. @@ -55,23 +66,17 @@ triggering (Start Stop Trigger) to prevent corrupted data from being recorded. Files”. When beam comes back, check in the EB Summary monitor that all building nodes are still active after switching back to "beam" files. +\item \textbf{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 2 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 Please don’t do any power cycle without asking an expert – unless it is explicitly stated in the manual or help texts. -\item Don’t hesitate to \textbf{call the expert} if there is a problem you can’t solve or you don't -fully understand! - \item At least once a day, when there is a break >15 minutes, a \textbf{full restart} of the system 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 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 -statistics. - \end{itemize*} diff --git a/hadesoperator/hmonwindows.tex b/hadesoperator/hmonwindows.tex index 3ddd890..9cabdf2 100644 --- a/hadesoperator/hmonwindows.tex +++ b/hadesoperator/hmonwindows.tex @@ -2,6 +2,7 @@ \item[AtmosPress] Atmospheric Pressure from MDC sensors \item[CTSRates] Rates on the inputs and outputs of the CTS \item[CtsMuxRatio] Ratio between the two CTS histogramming channels + \item[DutyFactor] Q-Factor of the beam micro-spill structure \item[EBCPU] Processor Usage of all main servers \item[EBDisks] Disk Usage of all main servers \item[EBSummary] Central plot of eventbuilder status @@ -44,9 +45,10 @@ fast and slow channels and their ratio \item[MdcPressurePlane3] Trend plot of overpressure inside each of 6 Plane 3 drift-chambers. \item[MdcPressurePlane4] Trend plot of overpressure inside each of 6 Plane 4 drift-chambers. \item[MdcScales] Trend plot of the air temperature inside the cave + \item[MicroSpillStructure] The beam intensity in 20us bins, from Start detector \item[Muxhist] \item[Pt3AcceptRatio] - \item[QA] + \item[QA] Main tactictal overview \item[RichGas] Plots showing the gas sensors of the RICH \item[RichHV] \item[RichInnerTemp] Display of the temperature sensors attached to the spokes inside the RICH detector @@ -56,25 +58,27 @@ fast and slow channels and their ratio \item[RichTempHistoDiRICH] \item[RichThresh] Two dimensional display of the DiRICH threshold settings \item[RpcRate] - \item[RpcTofRate] - \item[RpcTofSectorRate] + \item[RpcTofRate] Rates of RPC and TOF combined + \item[RpcTofSectorRate] Rates of RPC and TOF combined \item[SpillInfoHodoX\_0] - \item[SpillInfoStart] - \item[SpillShapeAnalysisX] - \item[SpillShapeAnalysisY] +% \item[SpillInfoStart] +% \item[SpillShapeAnalysisX] +% \item[SpillShapeAnalysisY] \item[SpillStructure] \item[StartCountSpill] Start counts per spill \item[StartPosition] - \item[StartPositionRMS\_VW] - \item[StartPosition\_VW] + \item[StartPositionRMS] +% \item[StartPosition\_VW] \item[StartRateNumbers] - \item[StartRateNumbers\_VW] +% \item[StartRateNumbers\_VW] \item[StartRateSimple] - \item[StartRateSimple\_VW] - \item[StartRateX] - \item[StartRateXhistbar\_VW] - \item[StartRateY] - \item[StartRateYhistbar\_VW] +% \item[StartRateSimple\_VW] +% \item[StartRateX] + \item[StartRateXhistbar] +% \item[StartRateY] + \item[StartRateYhistbar] + \item[StartSpillShapeAnalysisX\_0] + \item[StartSpillShapeAnalysisY\_0] \item[StsRate] STS rate for each channel \item[StsRateSplit] STS for each channel, separated in STS-1 and STS-2 \item[TDCErrors] TDC Error numbers @@ -90,7 +94,7 @@ fast and slow channels and their ratio \item[eventrate] DAQ event rate, 1 minute long \item[eventratelong] DAQ event rate, 10 minutes long \item[eventrateshort] DAQ event rate, 20 seconds long - \item[goofy1] MDC Goofy monitoring +% \item[goofy1] MDC Goofy monitoring \item[hldlast] List of latest hld files written to disk \item[hubmon] Monitor for link activity on DAQ hubs \item[logfile] Logfile with DAQ error messages