As you will see, almost none of this is implemented. There's a bit o=
f
work to do yet. All of the tools exist of course, it's now matter of
making macros.
Feedback is invited. There are things to work out yet, and we should
discuss them now. For example, when you check the high voltage, how =
do
you know what it is supposed to be? Suppose some section has the hig=
h
voltage turned off to counter a short. How do you distinguish someth=
ing
intentional from a mistake? Perhaps there is a sheet in the DC logbo=
ok
(and on the wall) that contains the nominal high voltages, trip setti=
ngs
and all exceptions. As far as I know, nothing like this was in place=
for
the last run.=20
Onward!
\ R A Thompson /
/ Dept of Physics and Astronomy University of Pittsburgh \
\ Pittsburgh, PA 15260 /
/ richardt@cebaf.gov 757-269-7475 \
------------------------cut here-------------------------------------=
--
\documentstyle[12pt]{article}
%
% macro definitions
%
%
\oddsidemargin 0in
\evensidemargin 0in
\topmargin 0in
\headheight 0in
\headsep 0in
\textwidth 6.5in
\textheight 9in
\begin{document}
\begin{center}
{\large \bf Drift Chamber Online Monitoring}
{Richard A Thompson}
{\sc \today}\\*[1cm]
{\large DRAFT }
\end{center}
\section{Overview}
Drift chamber monitoring is divided into two parts: a checklist to be=
performed before the beginning of a shift, and a checklist to be per=
ormed for each run. The shift checklist is meant to familiarize the =
shift taker with the status of the drift chambers and diagnostics. T=
he very brief run checklist is only meant to confirm that the drift c=
hambers are taking data.
The monitoring kumacs should be executed from a PAW session running f=
rom the {\it /this/is/where/the/monitoring/stuff/is} directory on a c=
lon machine other than clon00.=20
If an item on the checklist is not satisfied, the shift taker, in con=
sultation with the shift leader, should access the impact of the fail=
ure on the quality of the data. If they determine that the failure p=
revents the taking of usable data, or that the failure should be addr=
essed immediately, they should call a drift chamber expert in. If th=
ey determine that they can proceed with data taking and that the fail=
ure does not need to be adddressed immediately, they should make a no=
te in the logbook and send a brief email message to {\it richardt@ceb=
af.gov}. If needed, the ``standards'' will be updated at least once =
per day by a drift chamber expert.
\subsection{monitoring utilities}
Following are the monitoring utilities that the shift taker will use.
\begin{itemize}
\item HVMon - the drift chamber high voltage control interface
\item Strip\_Tool - EPICS history plotting
\item RunHistory - a utility that tracks quantities derived from hboo=
k files created by monitoring utilities
\item Monitor - makes histograms of raw data from the DD ring
\item Recsis - makes histograms of data analyzed from the DD ring
\end{itemize}
\pagebreak
\section{Shift Checklist}
Before the beginning of your shift, become familiar with the status=
of the drift chambers.
\subsection{hardware}
=20
HVMon: High voltage - {\it Not yet implemented. Procedures to co=
me.}
\begin{itemize}
\item HV set values
\item current draw history
\item current trip levels
\end{itemize}
=20
Strip\_Tool: gas system - {\it Not yet implemented. Procedures t=
o come.}
\begin{itemize}
\item in and out flow rates =20
\item chamber gas pressures
\item mixing ratios
\item $O_{2}$ and $H_{2}O$ levels
\end{itemize}
=20
\subsection{data integrity}
RunHistory: {\it Not yet implemented. Procedures to come.}
\begin{itemize}
% \item number of bad hits per event from RNTUP
% \item number of edges per hit from RNTUP
\item tdc spectra from Monitor=20
\item number of hits per event from Monitor
\item tdc difference between hits ($t_{i} - t_{j}$) from Monitor
\item number of tracks per event from Recsis
\item number of hits per track from Recsis
\item tdc spectra hits on tracks from Recsis=20
\end{itemize}
From the runs done on the previous shift, select a good run and e=
xamine the following diagnostics by running the kumac {\bf dcshift nn=
nn} where {\it nnnn} is the run number you wish to examine. Compare =
them with the stardards.
\begin{itemize}
\item tdc spectra from Monitor
\item occupancy from Monitor
\item tdc difference ($t_{i}-t_{j}$) from Monitor
\item number of tracks per event from Recsis
\item number of hits per track from Recsis
\item tdc spectra for hits on tracks from Recsis
\end{itemize}
=20
\pagebreak
\section{Run Checklist}
\subsection{before beginning of a run}
You should know that the following are not in an alarm state:
\begin{itemize}
\item high voltage
\item gas system
\end{itemize}
\subsection{during the run}
Verify that the monitor utilities are up and running from the DD =
ring:
\begin{itemize}
\item Monitor
\item Recsis=20
% \item RNTUP
\item CED
\end{itemize}
Check the following monitoring histograms by running the kumac {\=
bf dcrun}. Compare them with the stardards.
\begin{itemize}
\item Monitor: occupancy for all hits
\item Recsis: occupancy for hits on tracks=20
\end{itemize}
\pagebreak
\section{Standards}
This section will contain screen shot examples of what the monitori=
ng histograms should look like, with brief explanations.=20
\end{document}