=========================================== 
 MCS 10 August 2004
 Summary of Data Quality Assurance for IFR
=========================================== 

* Introduction
DQA is performed on a weekly basis for each subdetector.
Weekly the RQM will post a HN pointing to the list of processed 
runs that needs to be checked for that week.
E.g. in the HN  
http://babar-hn.slac.stanford.edu:5090/HyperNews/get/DQG/481.html
the list of runs is 
http://www.slac.stanford.edu/BFROOT/www/Physics/BaBarData/QualityChecks/040812/runlist_to_be_checked.txt 

More infos can be found at the DQ web page:
http://www.slac.stanford.edu/BFROOT/www/Computing/DataQuality/

* OPR ps file
The .ps file produced from the OPR hbook file is available for each run
http://www.slac.stanford.edu/BFROOT/www/Physics/BaBarData/QualityChecks/040812/PSfiles-040812.html 

For the IFR the OPR hbook file is produced by the IfrQa module in the IfrOprMon
package. The IfrOprMon.kumac is used by OprQaUtils to produce the plots related 
to the IFR in the .ps file. This pass is performed both for PC (prompt calibration) 
and ER (event reconstruction). 

* Strip Charts
At the web page
http://www.slac.stanford.edu/BFROOT/www/Physics/BaBarData/StripCharts/
the RQM collects all the information related to DQG.
The stripcharts are a usefull tool to assess the quality of the runs to check.
In the stripcharts several quantities are plotted versus run number.
In this way is easy to identify a problem related to the time evolution 
of the subdetector performance.

* RqmRootTreeTools
For the IFR (and for all other subdetectors) the information of several IFR-related
quantities are extracted from the OPR hbook file using modules in the RqmRootTreeTools.
The RQM runs the code weekly and produces the stripcharts. Duty of the subdetector
experts is to provide the package for the extraction of the informations.
At the moment IfrTreeMaker and IfrStripChartsCollection are the modules implemented
for the IFR to extract the information and plot the quantities into stripcharts.
In IfrTreeMaker.cc you can see which quantities are used at the moment.
A list is here below:


  1) Avg. numb. of Fecs per evt
  2) Avg. numb. of 1D clusters per evt
  3) Avg. numb. of charged 3D clusters per evt
  4) Avg. numb. of neutral 3D clusters per evt
  5) Avg. numb. of 1D clusters per 3D cluster
 
  6) Events per run
 
Mean of the histograms for the hits in each IFR sector:

  7)  Digis/evt sect -11 (BECW top)
  8)  Digis/evt sect -10 (BECW mid)
  9)  Digis/evt sect -9 (BECW bot)
  10) Digis/evt sect -8 (BECE top)
  11) Digis/evt sect -7 (BECE mid)
  12) Digis/evt sect -6 (BECE bot)
  13) Digis/evt sect -5 (FECW top)
  14) Digis/evt sect -4 (FECW mid)
  15) Digis/evt sect -3 (FECW bot)
  16) Digis/evt sect -2 (FECE top)
  17) Digis/evt sect -1 (FECE mid)
  18) Digis/evt sect  0 (FECE bot)
  19) Digis/evt sect 1 (Barrel 0)
  20) Digis/evt sect 2 (Barrel 1)
  21) Digis/evt sect 3 (Barrel 2)
  22) Digis/evt sect 4 (Barrel 3)
  23) Digis/evt sect 5 (Barrel 4)
  24) Digis/evt sect 6 (Barrel 5)
  25) Digis/evt sect 7 (Cyl)
  26) Digis/evt sect 8 (Cyl)
  27) Digis/evt sect 9 (Cyl)
  28) Digis/evt sect 10 (Cyl)   
  29) Digis/evt sector 11 (Belt)
  30) Digis/evt sector 12 (Belt)
  31) Digis/evt sector 13 (Belt)
  32) Digis/evt sector 14 (Belt)
  33) Digis/evt sector 15 (Belt)
  34) Digis/evt sector 16 (Belt)
  35) Digis/evt sector 17 (Belt)
  36) Digis/evt sector 18 (Belt)
  37) Digis/evt sector 21 (Belt)
  38) Digis/evt sector 22 (Belt)

Efficiencies calculated using residuals and swimmer hits information:
   
  39) Efficiency Barrel
  40) Efficiency Forward Endcap
  41) Efficiency Backward Endcap
  42) Efficiency Inner RPC
  43) Efficiency Belt
 

* DqmJas
DqmJas is a software package developed to make easyer the browsing of the stripcharts.
At the moment, all the quantities monitored for the IFR have been implemented also 
in this package. 

* How QA is done for the IFR
What is pratically used to assess the quality of the runs of the weekly 
DQG list from the IFR point of view is the following:

1. the script IFRQA-auto.sh runs as a cron job every Wednsday at 4:00am.
   The script verifies that a new list of runs is present and performs few checks 
   on the existence and validity of the ER hbook files which are used to produce 
   the stripcharts.
   A mail is sent as summary report upon completition of the job.

2. DqmJas3 is used to browse the quantities present in the stripcharts.
   A good source of information for spotting possible problems is contained in the plot 
   representing the number of firing FECs per event. 
   Note that this quantity depends on the beam conditions and the length of the run. 
 
3. Reply to RQM mail in HN