*** empty log message ***

diff --git a/daqop_short.txt b/daqop_short.txt
new file mode 100644 (file)
index 0000000..bd3add3
--- /dev/null
+++ b/daqop_short.txt
@@ -0,0 +1,86 @@
+What is the starting point?  
+--------------------------- 
+
+Open the DAQ-Control GUI (HadesControl Icon), click on "Hmon". A firefox window will
+appear. Click on "Tactical Overview".
+
+DAQ-Operation:
+--------------
+
+The main task of the DAQ-Operator is to watch the
+Tactical-Overview window and check that all buttons are green.
+The essential numbers (like trigger rates) have to be in limits
+given by the shift leader.
+The "Operator Guide" offers a description of typical situations during data
+acquisition. It also contains instructions to solve typical
+problems. Following guides point to relevant chapters if necessary.
+
+ 
+
+DAQ-Control Window:
+------------------
+The DAQ-Control Window provides functions solutions of ocurring
+DAQ problems. The "HadesControl" Icon starts DAQ-Control.
+
+"DAQ-Operator" Buttons are necessary for a DAQ restart. The "DAQ-restart" guide
+describes the use of these buttons. 
+
+"Monitor Tools" contain all observation windows.
+        "CTS Mon": Opens the CTS Monitor.
+        "Hmon": Click on "Tatical Overview" in the new Firefox window to get 
+        "Epics":Opens the Epics Monitor.
+        "Epics FB": Shows a status window containing Eventbuilder
+        information.
+
+"Eventbuilder Tools" are necessary for an Eventbuilder restart. Details are
+described in the "Eventbuilder-Stop" guide.        
+
+
+
+
+Eventbuilder-Stop:
+------------------
+
+In the case of beam breaks etc. the shift leader decides to
+change the mode of data taking or even stop data taking (DAQ
+system is still running).
+
+1. ) Stop the data taking press the "StopEB" button in the "DAQ
+Control" window.  In the tactical overview the first button in
+the row "EB" the text will change from EB-running to EB-stopped.
+
+2.) To restart the EB with the current prefix, click on "Restart
+EB" in the DAQ-Control
+
+3.) To start the EB with a different prefix, click on one of the
+buttons "Prefix ...". N.B., that the "Prefix NoFile" button
+starts the event builder in dummy mode, i.e. no file is written.
+
+DAQ-Restart:
+------------
+
+In the case the DAQ is not working correctly, the DAQ has to be
+restarted. DAQ-Control provides the necessary operations for
+a DAQ restart.
+
+1. ) Press "Start DAQ" to restart DAQ. An orange window appears and
+should disappear after 30s-40s if the restart was successful.
+An unsuccessful attempt is indicated by an error message in
+the orange window. Try a second DAQ restart, if the first
+one failed.
+
+2. ) In the case of an unsuccessful DAQ restart a MDC Power Cycle 
+has to be performed. The steps of a MDC Power Cycle are described
+in the Operator Guide Chapter 34.2. After this operation the DAQ
+has to be restarted. Follow the instructions given in step "1. )".
+
+3. ) In the Case "2. )" failed, the "RebootMDCHub" icon should be used.
+After pressing "RebootMDCHub" the DAQ has to be restarted which is described in
+"1. )".
+
+4. ) In the case step "3. )" was not successful, a "Full Power Cycle" has to be
+performed. This procedure is described  in the "Operator Guide Chapter 33.1"
+Restart DAQ following the steps in "1.)" .
+
+5. ) The DAQ expert has to be called if the DAQ is still not working. 
+