new Run4 Data Processed by PR -updated
You can find the old version of this page
here.
For now the information there is valid but not complete,
soon I will delete this old information.
- The PC pass for the new Run4 data is done with 14.0.3,14.0.4,14.0.5,14.1.2b in PC1
at slac for the Rolling Calibrations.
- You can find the PC QA ps files on the web page:
http://www.slac.stanford.edu/babar-internal/qaPCER
the old style pages are here:
/BFROOT/www/Computing/Online/PromptReco/QaOpr
- The gzipped merged hbook files can be found in release directories here:
/nfs/farm/babar/qa/QaOpr/testqa/hbook/PC1
- The logfiles from the processing can be found here:
/nfs/oprserv01/u1/PC1/logfiles
- You can use oprruns to see what runs were processed in PC1:
oprruns -PCalibration -since 1
'-since 1' means the last day, or you can specify a run range.
- The ER pass of the runs is done in Padova on ER3 and now ER4 and now ER2.
- The runs are processed using a test released based on 14.0.3-roo-2 (14.0.3y)
or with 14.1.2b/c.
- You can find the QA plots for the runs on web pages at slac or Padova:
http://www.slac.stanford.edu/babar-internal/qaPCER
http://bbrweb.pd.infn.it:5211/farm/Operations/BaBarData/Comparisons
or on disk at SLAC in directories by farm and release:
/nfs/farm/babar/qa/QaOpr/testqa/hbook
/nfs/farm/babar/qa/QaOpr/testqa/psdir
(old directories:
/nfs/farm/babar/qapd/hbook
/nfs/farm/babar/qapd/psdir)
- You can use oprruns to see what runs were processed (and by what farm):
oprruns -f%,prfarm -since 1
'-since 1' means the last day, or you can specify a run range.
- The Data Files are being copied to SLAC:
- To read the data produced with 14.0.3y you need to use 14.0.3-roo-2,
To read the data produced with 14.1.2b/c you need to use 14.1.2b/c/d.
An example tcl is in BetaMiniUser/MyMiniAnalysis.tcl,
where you only have add the input collections and change
set ConfigPatch "MC" to set ConfigPatch "Run2" to run on data
(This is valid for all the Run2-4 data; there is no Run3/4 ConfigPatch).
- There is a new analysis conditions federation but for Run4: cond14boot,
which will be automatically updated with the new RC twice a day, and requires
about a 15min outage, so if you see the CDB inhibited, try again 15min later.
- We are writing out two streams AllEvents and the TriggerStream.
You can find tcl files with the collections to run on here:
/nfs/babar/kan001/vol4/rooTcl
e.g. /nfs/babar/kan001/vol4 > ls AllEvents_00040270_P14.0.3yV00fb.tcl
NOTE: There are N collections (where N is about 60) for each run since these are the
output of the N elven that processed that run. In the final production these N collections
will be merged into one collection per stream per run.
This directory will be updated automatically for new runs.
- Below is a list of runs that had trouble or were somehow
exceptions (way out of date!):
40039, ER only, IFR off
40040, ER only, IFR off
40052, ER only, Dirc off
40053, ER only, Dirc off
40192, ER only, there was trouble with the xtc file in the PC pass.
40255, BGfilter problem V00, reprocessed V01 ok
40293, BGfilter problem V00, reprocessed V01 ok
40317, BGfilter problem V00, reprocessed V01 ok
40352, BGfilter problem V00, reprocessed V01 ok
40354, BGfilter problem V00, reprocessed V01 ok
40379, BGfilter problem V00, reprocessed V01 ok
40400, BGfilter problem V00, need to be reprocessed
40416, BGfilter problem V00, need to be reprocessed
40426, BGfilter problem V00, need to be reprocessed
40427, BGfilter problem V00, need to be reprocessed
40470, problem with TarFile? no TriggerStream
40472, problem with TarFile? no TriggerStream
40479, ER only, data QA flag set unusable 100% deadtime in SVT
40490, V00 wrong conditions, use V01
40491, V00 wrong conditions, use V01
40492, V00 wrong conditions, V01 failed, use V02
40493, V00 wrong conditions, use V01
40499, technical problem (blackout) with V00, use V01
teela
Last modified: Sat Nov 15 01:00:20 PST 2003
|
