Instruction and Duties of the offline shifter (March 2005):
=====================================================================

			MONITORING OF THE RECONSTRUCTION
			================================


0) Please report every day in the offline loogbook your activity!

1) Each morning look at the reconstructed runs of the previous day/night 
   (do for example: list_runs)
2) Take note of the runs which have not been reconstructed. 
   Note that a run is reconstructed if the following 
   conditions (+others) are fullfilled:
      1) the emc calibration has completed (it needs usually few hours), i.e.
         calib_word>3327
      2) the run is flagged as good, i.e. the reconstruct_id is = 100.
      3) physmon has processed the run
      3) there are reasonable values of luminosity, currents, etc...

   Therefore if the run XXX is not reconstructed check the following causes:
      1,2) the value of the calibration word and reconstruction_id. 
	   Do:
	   dbonl "select run_nr,calib_word,reconstruct_id,TRGMON_INT_LUM 
	   from logger.run_logger where run_nr>=XXX"

        3) Look if physmon has runned. Da fibm35, as kloerec, do
	  setup offline
	  ./dbprint XXX 3

	4) check that there aren't  strange values of luminosity, currents, 
	   etc.... for example do list_runs and look if there are question 
	   marks in the fields  "bnc trglum  L3bha intlum tag"
	   	

   EXAMPLE:
   =======

   Runs: 35205 is not reconstructed.


   fibm11:datarec > dbonl "select run_nr,calib_word,reconstruct_id,
   TRGMON_INT_LUM from logger.run_logger where run_nr>35203"


   RUN_NR   CALIB_WORD RECONSTRUCT_ID TRGMON_INT_LUM
   ========-=========-=========-=========
    35204      3329       100 2.232e+35
    35205      3329       100 2.199e+35
    35206      3328       100 3.316e+34
    35207      3329       100 2.042e+35
    35208      3329       100 1.441e+35
    35209      3329       100 2.295e+35
 
   So it seems ok for the calibration and reconstruction_id

   Look if physmon has runned:
   setup offline
   ./dbprint_dr 35205 3

   HEPDB   1.21/00 960329 12:00 CERN PROGRAM LIBRARY HEPDB=Q180
   This version created on 960328 at 1130
   RTDBOP: Database RN normally Opened
   RTDBOP: Database R1 normally Opened
   35205 BPOS2    .0343    .0140    .8501    .0556   1.1432
   35205 BMOM3 -15.4831    .0037   -.3939   2.3079   2.2532   2.6862  1019.691   .045
   RTDBCL: Database CDRN normally Closed
   RTDBCL: Database CDR1 normally Closed

   The values are ok.

   In fact the runs is not reconstructed, since datarec is not finished... 
   yeah, yeah ;) 




3) Check that counters, sqrts, and other varibles are fine. Just do, 
from the home directory of fibm35:
exe /kloe/soft/off/datarec/kumac/history_plots.kumac run_first run_last dbv
exe /kloe/soft/off/datarec/kumac/runstatenl.kumac run_first run_last dbv

Eventually take note of some anomaly in the distributions.
sqrt(s) should be around 1019.4



4) Check that DST's are produced. Look for possible errors in the log file.
Note that the dts are submitted on fibm36, and the working area" is
     /analysis/dst/logs