RQM (Run Quality Manager)
Data
Quality Group (DQG) is in charge of checking the data and deciding
which runs are useful for the physics analysis. The RQM (Run Quality Manager) in
that group provides weekly the list of the runs taken in IR2 to the
subsystem experts and makes the summary of the useful runs after the weekly
meeting.
RQM mission:
Weekly to be done:
- Prepare the run list to be checked by the subsystem experts
- Prepare the web page which has the run list and the links to OPR
histograms of PC (Prompt Reconstruction) and ER (Event Reconstruction)
- Stripcharts for PR and ER
- Produce the web page with thumbnail stripcharts
Jinwei Wu made a script "doall_test.csh" which
does all the jobs listed above automatically. A directory is set up in the
official DQG area for RQM jobs
DIR = /nfs/babar/DQG/dqg-rqm/rqmtools-14.5.2
The $DIR/workdir/doall_test.csh will execute
$BFROOT/www/Physics/BaBarData/QualityChecks/current/get_run5.pl.
The "get_run5.pl" script will collect all the "Colliding Beam" runs taken in IR2
and look for the OPR hbook and ps files in /nfs/babar/DQG/hbook and /nfs/babar/DQG/psdir
directories, respectively. The output of that script will be the list of the
runs to be checked weekly, "runlist.txt", and the html file containing the links to the ps files, "PSfiles-current.html".
Both outputs will be in the same directory of the script. The "doall_test.csh"
script executes "$BFROOT/www/Physics/BaBarData/QualityChecks/current/get_pc_runs.pl"
to create "runlist-pc.txt" which will be used in PC stripcharts
production.
Once those files are generated, $BFROOT/www/Physics/BaBarData/QualityChecks/YYMMDD
directory is created manually and two files are copied here with the name of "runlist_to_be_checked.txt"
and "PSfiles-YYMMDD.html" and are linked to the weekly announcement mail. After
the DQG meeting, "runlist_to_be_checked.txt" will be divided into two file, one
containing the bad runs, "bad-runlist.txt", and the other one with good
runs list, "good-runlist.txt". All these files need to be added under "Lists of
runs to be checked:" in
$BFROOT/www/Physics/BaBarData/StripCharts/index.html
manually.
The stripcharts are produced by RqmRootTreeTools package.
In doall_test.csh first runs the "RqmMakeAll" which produces the
root files for PC and ER pass for the given run range and for the weekly runs,
reading from
$BFROOT/www/Physics/BaBarData/QualityChecks/current/runlist.txt
(ER)
$BFROOT/www/Physics/BaBarData/QualityChecks/current/runlist-pc.txt
(PC)
Then "RqmDoCharts" is executed to produce
stripcharts for PC and ER. The output of this are "stripER.ps", "stripER.root", "stripPC.ps",
"stripPC.root". These four files are copied to $BFROOT/www/Physics/BaBarData/StripCharts/
directory with the same name as well as stripER-YYMMDD.ps, stripER-YYMMDD.root, etc names.
The thumbnail of stripcharts are produced in $BFROOT/www/Physics/BaBarData/StripCharts/
by executing "doall.csh" for PC and ER options separetely. This script
reads the
stripPC.root and stripER.root from the same directory and updates
the page of "Easy surfing of the Stripchart" in
index.html .
"doall_test.csh" can be run everyday either
manually or automatically ( use cronjob). If you want to run it as
cronjob, edit a file via "trscrontab -e". This will open an emacs editor and add
the following command
noric 0 14 * * * /nfs/babar/DQG/dqg-rqm/rqmtools-14.5.2/workdir/doall_test.csh
>> /nfs/babar/DQG/dqg-rqm/rqmtools-14.5.2/workdir/crontab.log 2>&1
will run the job everyday at 2PM.
- Summary of the week should be prepared
Once the weekly data is
checked by the experts, the RQM prepares the summary of the week with the
information on checked runs, luminosity of the bad, good and flawed runs.
A second announcement should be made to the DQG HN.
First execute the "$BFROOT/www/Physics/BaBarData/QualityChecks/setQAStatus.pl"
which takes the "good-runlist.txt " and makes the list of runs and the
status given by each subsystem experts. This output is $BFROOT/www/Physics/BaBarData/QualityChecks/YYMMDD/setQA.csh.
BbkQAStatus --NoQuery
--run 50220 --ProcSpec P14.4.2cV00fb --SetAll Good --PhysCal
BbkQAStatus --NoQuery --run
50221 --ProcSpec P14.4.2cV00fb --SetAll Good --PhysCal
BbkQAStatus --NoQuery --run
50222 --ProcSpec P14.4.2cV00fb --SetAll Good --PhysCal
###
###
BbkQAStatus --NoQuery --run
50242 --ProcSpec P14.4.2cV00fb --SetAll Good --PhysCal
BbkQAStatus --NoQuery --run
50242 --ProcSpec P14.4.2cV00fb --Stat Flaw --SetSub SVT
BbkQAStatus --NoQuery --run
50242 --ProcSpec P14.4.2cV00fb --Stat Flaw --SetSub TRK
BbkQAStatus --NoQuery --run
50242 --ProcSpec P14.4.2cV00fb --Stat Bad --SetSub RQM --Comment "short run,
fail PC, reprocess"
The bad runs are entered to setQA.csh
file manually and the QA database is updated for the status of each run using this
file. Source this file where BbkQAStatus command is found. Then in /nfs/babar/DQG/rqmtools-14.5.2/workdir/
create BbkQATable.txt by
BbkQAStatus --range <run low>-<run high> >! BbkQATable.txt
Using "get_bad.pl" reading BbkQATable.txt
will generate bad.txt, flaw.txt, cal.txt and bad.txt. To get
the luminosity for the runs in those files:
lumi --OPR --file xxx.txt
Monthly to be done :
- Make the list of "unusuable runs" and go over this run list,
find out if there is any run which can be reprocessed.
ir2runs -t Colliding 40000-52000 | grep Colliding | awk '{print $1}' | xargs
ir2runs --dqm glb | grep glb | awk '$3 ~ /0/ { print $1, $2, $3 }'
will list the
runs with status flag set to 0 (i.e UNUSUABLE). Run4 has 149 of them.
In general:
- Meetings to attend - The meetings are weekly organized:
QA Tools Meeting
- Tuesday @ 11:00 in Madrone
OPR Meeting
- Thursday @ 09:30 in Cedar
DQG Meeting
- Thursday @ 10:300 in Pam/Flora
This page is maintained by the RQM:
Tulay Donszelmann
Last Update: 17 November 2004
|
