Suggestions for improving the E-log documentation (by Victor A.)

  1. At the beginning of each new set of measurements indicate the goal of
     the study and briefly the experimental sutup: 

     sub-detectors involved: HB, HE, HO, ECAL, HF
     Table position (eta, phi and codes), ECAL position,
     Trigger type (4*4 = A*B*D), trigger rate, beam rate.
     Beam type and energy (Pions, -100, defocused, table H2.81)    
     Other non-standard items: change in HV, adding Al absorber, 
     collimator, QUAD and TRIM settings, steps in X or Y, ...

  2. Please, indicate, which RUN is considered as a valuable for
     analysis (data taking RUN), and which run is just for beam tuning and/or
     checking the apparatus.  Number of written events.

  3. At the end of the study summarize briefly the data quality and your
     conclusion about the goal of the measurements. If some analysis of 
     the data is performed during the shift, please, make a few comments.

  4. Indicate, which hardware or software has a problem.

  5. Make the explicit recommendations to the next shifts about measurements
     which has to be done.                 

  6. Example of RUN information:

  Goal: Transverse scan of HE by a pion beam. Setup:  ECAL(19,4)+AL+HE. 
  Trigger: AB=14*14, 100 GeV, H2.81 defocused, TRIM7=50, TRIM8=20, QUAD16=0, 
  Collimators: 3=+/-20; 6=+/-5; 9=+/-20; 12=+/-20; 13=+/40.
  Beam rate: 14*14=40k; 4*4=9000; 2*2=3000; 900 ev./spill. 

  8.00am Run#9538, pi- 100 GeV, eta=19.0(10434), phi=3.0(55676),  5k (tune)
  8.30am Run#9539, pi- 100 GeV, eta=19.0(10434), phi=3.0(55676), 50k (data)
  8.50am Run#9540, pi- 100 GeV, eta=19.0(10434), phi=3.5(47105), 50k (data)
  9.20am Run#9541, pi- 100 GeV, eta=19.0(10434), phi=4.0(38534), 50k (data)