P20 Pass 4 Data (Run 2b-2, 2007-2009)
Run 2b-2 data have been reconstructed using d0reco
p20.12.xx. Run 2b-2 data that were previously processed using
d0reco p20.11.xx have been reprocessed using p20.12.00.
What is the difference between pass 3 and pass 4 run 2b-2 data?
The pass number is reflective of the d0reco version that is used to
reconstruct data, as opposed to the number of times the data was
reconstructed.
Here is a summary
of the major d0reco versions that have been used in run 2b so far.
- p20.04.01 -- Pass 1 (obsolete).
- p20.07.01/p20.08.xx -- Pass 2.
- p20.11.xx -- Pass 3 (obsolete).
- p20.12.xx -- Pass 4.
- p20.12.00
- p20.12.01 - Optimzed to not read a particular rcp file each event
(no algorithm changes).
- p20.12.02 - Calibration database update (no code changes).
- p20.12.04 - Calorimeter hot cell overflow bug fix.
- p20.12.05 - Modified to be able to handle data affected by
l1caltrack hardware problem. Releases p20.12.05x (x=b,c,d)
have no code updates compared to p20.12.05, but there
were calibration updates.
- p20.12.05b - Calibration update.
- p20.12.05c - Calibration update.
- p20.12.05d - CPS calibration update. Used to reprocess "bad cps
gain data."
Pass 1 and pass 3 are obsolete. The full run 2b dataset is therefore
the union of pass 2 and pass 4 data.
Skimming of pass 4 data was done using production releases
p21.08.00 for d0reco versions p20.12.00-p21.12.04 and p21.12.00 for
d0reco versions p20.12.05 and later.
Caf produciton of pass 4 was done using production releases
p21.10.00, p21.12.00, and p21.13.00. Some early data that were originally
caffed using
p21.08.00 was later recaffed using p21.10.00.
Which release should you use for analysis?
For your own analysis, it is usually best to use the latest frozen p21
release, currently p21.13.00 with root 4.04 or p21.14.00 with root 5.22,
as a base release for analyzing any kind of run 2 data
Here is a brief summary of differences since p21.03.00.
- p21.03.00 - Update skimming for pass 2 data.
- p21.04.00 - Update tmb_analyze (caf production) for pass 2 data.
- p21.05.00 - Fix tmb_analyze EM spatial track match bug.
- p21.06.00 - Fix tmb_analyze per tick luminosity information for
mc min bias overlay.
- p21.07.00 - Updated JES. Updated trigger branches in CAF.
- p21.08.00 - Final run 2a JES. EM scale and track match fixes.
- p21.09.00 - Central MC lumi profiles. Updated EM smearing, NN
tagger trfs.
- p21.10.00 - Recaffing (updated emid, track misses, additional
branches).
- p21.11.00 - MC recaffing (hf skimming, updated cft clusters).
- p21.11.01 - MC recaffing (update mc caf contents to be same as data).
- p21.12.00 - Update fps format for skimming & caffing p20.12.05 d0reco data.
- p21.13.00 - Fake track killer (update track formats to include quality
parameter).
- p21.14.00 - Root version updated from 4.04 to 5.22.
Pass 4 unfixed data has been reconstructed using d0reco versions
p20.12.00, p20.12.01, p20.12.02, p20.12.04, p20.12.05, p20.12.05b, and
p20.12.05c.
Run Ranges
The first run 2b-2 run is 237342, taken on Oct. 28, 2007.
Store 5544, runs 234207-234213, which were not processed with
run 2b-1 data, are also included in run 2b-2 skimming.
The run range for p20.12.00 d0reco data is 237342-240790
(except 240561-240585).
The run range for p20.12.01 d0reco data is 240801-241002.
The following run ranges were processed with p20.12.02 d0reco.
- 234207-234213 (store 5544).
- 240561-240585 (Mar. 6-7, 2008 reprocessing).
- 241003-245473 (except for runs processed using p20.12.04).
D0reco p20.12.04 was only used to process runs that couldn't be processed
using d0reco p20.12.02 due to crashes due to hot cell overflow.
The full list of runs processed
using p20.12.04 is:
242102,
242963-242967,
243014,
243020,
243036,
243038,
243067-243069.
The last run processed using p20.12.02, which is also the last run
included in the Moriond 2009 dataset, is 245473, taken on Sept. 12, 2008.
D0reco p20.12.05, p20.12.05b, and p20.12.05c cover run range 245474-252918,
until the summer 2009 shutdown.
- p20.12.05 - 245474-246067.
- p20.12.05b - 246427-247041.
- p20.12.05c - 247304-252918.
Unfixed/Unreprocessed All Stream Data in SAM
To find all stream data in sam, use a constraint similar to the following.
sam translate constraints --dim="(((APPL_NAME recon_root, d0reco and VERSION p20.12.05c) and DATA_TIER thumbnail) and TRIG_CONFIG_TYPE physics) and PHYSICAL_DATASTREAM_NAME all%"
When using the genLBNtables
script for the generation of the
parentage tables use the option -pass
p21pass4.
Use the following predefined datasets to find unskimmed, unfixed,
unreprocessed data in sam.
Some data that was originally reconstructed and skimmed has been fixed
or reprocessed. There are two such episodes.
- A subset of data that was originally reconstructed using d0reco p20.12.00
was fixed using fixer release p20.13.00 to correct the calorimater
"inconsistent gain" problem. The run range for this fixer pass is
237342-238297, which amounts to 17% of data reconstructed using d0reco
p20.12.00.
- A subset of data that was originally reconstructed using d0reco
p20.12.05c was reprocessed from raw data after the start of the
summer 2009 shutdown using d0reco p20.12.05d because of the
"wrong cps gain" problem. The run range for this reprocessing is
250706-251282, which amounts to 8% of data reconstructed using
d0reco p20.12.05c.
Inconsistent Calorimater Gain Data
Inconsistent gain data are from runs 237342-238297. These data were
fixed using fixer release p20.13.00.
Fixed all stream data can be found using the following constraints:
sam translate constraints --dim="(APPL_NAME tmbfixer and VERSION csg-p20.13.00) and DATA_TIER thumbnail"
Or use the following predefined dataset.
There is also a unified all stream dataset giving fixed or unfixed data
depending on run number.
Fixing Algorithm
Here is information about the p20.13.00 fixing algorithm. In general,
the purpose of this fixing pass is to redo calorimeter reconstruction
with
improved gain calibration.
The top level rcp file for fixing is runP20TMBfixer[SAM]_TMB_IG.rcp
from
cvs package fixp13tmb_calprob.
Wrong CPS Gain Data
Wrong cps gain data are from runs 250706-251282. These data were reprocessed
using d0reco p20.12.05d, which has identical code to all p20.12.05x releases,
but used a different cps calibration.
Reprocessed all stream data can be found using the following constraints:
sam translate constraints --dim="APPL_NAME d0reco and VERSION p20.12.05d and DATA_TIER thumbnail and TRIG_CONFIG_TYPE physics and PHYSICAL_DATASTREAM_NAME all%"
Or use the following predefined dataset.
There is also a unified all stream dataset giving reprocessed or unreprocessed
data depending on run number, which covers the full d0reco p20.12.05x run
range (all data originally processed using d0reco p20.12.05,
p20.12.05b, and p20.12.05c).
Fixing and reprocessing is finished. In general, you should use
unified datasets for all stream, skimmed tmbs, and caf
trees for analysis. Unified datasets are the union of
fixed/reprocessed data and unfixed/unreprocessed data, depending on
run number.
When using the genLBNtables
script for the generation of the parentage
tables use the option -pass
p21pass4fixed, even when using the unified
datasets (the genLBNtables script will pick up the correct parentage also for
the unfixed files).
Detailed information about Run 2 Monte Carlo samples is available on
the Run 2 MC
web page.
Skim definitions have not changed since release p21.03.00 (triggers
used for skimming are updated automatically and are read from the
trigger database). The following link contains the (still valid) skim
definitions from p21.11.00.
Thumbnails
All stream data have been skimmed using release p21.08.00.
To find skimmed thumbnails in sam, use the following constraints for
p20.12.00-p20.12.05 d0reco data respectively:
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.08.00-p20.12.00) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.08.00-p20.12.01) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.08.00-p20.12.02) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.08.00-p20.12.04) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.12.00-p20.12.05) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
or use the following predefined datasets for different d0reco versions
where
XXXXX is the skim name..
- P20.12.00 d0reco data -- CSskim-XXXXX-PASS4-p21.08.00.
- P20.12.01 d0reco data -- CSskim-XXXXX-PASS4-p21.08.00-p20.12.01.
- P20.12.02 d0reco data -- CSskim-XXXXX-PASS4-p21.08.00-p20.12.02.
- P20.12.04 d0reco data -- CSskim-XXXXX-PASS4-p21.08.00-p20.12.04.
- P20.12.05 d0reco data -- CSskim-XXXXX-PASS4-p21.12.00-p20.12.05.
CAF Trees
CAF trees have been generated for all skimmed data using production
release
p21.08.00 for p20.12.00 d0reco data, and releases p21.10.00 or
p21.11.00 for p20.12.01, p20.12.02, p20.12.04, and p20.12.05 d0reco data.
To find CAF trees made from skimmed thumbnails in sam, use the
following constraints:
sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.08.00-p20.12.00) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.10.00-p20.12.01) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.10.00-p20.12.02) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.10.00-p20.12.04) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.12.00-p20.12.05) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
or use the predefined datasets:
CSG_CAF_XXXXX_PASS4_p21.08.00
CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.01
CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.02
CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.04
CSG_CAF_XXXXX_PASS4_p21.12.00_p20.12.05
where XXXXX is the skim name.
When using the genLBNtables
script for the generation of the
parentage tables use the option -pass
p21pass4.
Datasets
Unified data and datasets for d0reco p20.12.00 and p20.12.05c data consist
of the union of fixed/reprocessed and unfixed/unreprocessed
data, depending on run number. The unified datasets contain the
identical events as the corresponding unfixed datasets for d0reco
p20.12.00 and p20.12.05c data.
D0reco p20.12.01, p20.12.02, p20.12.04, p20.12.05, and p20.12.05b data
do not need to be fixed or reprocessed. The
full run 2b-2 data is the union of d0reco p20.12.00, p20.12.01,
p20.12.02, p20.12.04, and p20.12.05x data.
Thumbnails
Use the following predefined datasets for unified skimmed d0reco p20.12.00
thumbnails
CSskim-XXXXX-PASS4-p21.08.00-allfix2008
Use the following predefined datasets for unified skimmed d0reco p20.12.05x
thumbnails.
CSskim-XXXXX-PASS4-p21.12.00-p20.12.05-allfix
where XXXXX is the skim name.
Use the unfixed/unreprocessed skimmed tmb datasets for other d0reco versions.
Regenerated CAF Trees
CAF trees for d0reco p20.12.00 data have been completely regenerated
starting from unified skimmed tmb datasets using production release p21.11.00.
Use the following predefined datasets to find these caf trees:
CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.00
Use the following predefined datasets for unified reprocessed p20.12.05x
d0reco data.
CSG_CAF_XXXXX_PASS4_p21.12.00_p20.12.05_allfix
where XXXXX is the skim name.
Use the unfixed/unreprocessed caf datasets for other d0reco versions.
When using the genLBNtables
script for the generation of the parentage
tables use the option -pass
p21pass4fixed, even when using the unified
datasets (the genLBNtables script will pick up the correct parentage also for
the unfixed files).
Datasets (Unified Data)
Frozen datasets for summer 2008 (ICHEP) analyses have been defined for
p20.12.02 d0reco data. Run 2b-2 data reconstructed using d0reco versions
p20.12.00 and p20.12.01 are no longer growing, and do not have or need
separete frozen datasets. For these d0reco versions, use the (fixed or
unfixed) datasets specified above. Summer 2008 analyses should include
the following run 2b-2 data:
- Fixed or unfixed p20.12.00 d0reco data (see above).
- P20.12.01 d0reco data (see above).
- P20.12.02 d0reco frozen datasets given in this section.
Frozen summer 2008 datasets include all data that was reconstructed up
to May 6, 2008. This definition of the summer 2008 dataset includes
a superset of data for which offline data quality information is available
in dq_defs version v2008-05-01.
Thumbnails
The following predefined datasets should be used for skimmed thumbnails.
CSskim-XXXXX-PASS4-p21.08.00-p20.12.02-summer2008
where XXXXX is the skim name.
CAF Trees
The following predefined datasets should be used for skimmed caf trees.
CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.02_summer2008
where XXXXX is the skim name.
Datasets (Frozen Summer 2008 Data)
Data for winter 2009 (Moriond) analyses will consist of data reconstructed
using d0reco versions p20.12.00 - p20.12.04 in their entirety (plus run 2b-1
and run 2a data).
Data reconstructed using d0reco p20.12.05 and later in the run range
(245474-247960) may optionally be included
in Moriond 2009 analyses.
Frozen datasets for summer 2009 analyses have been defined for
p20.12.05 (including p20.12.05b and p20.12.05c) d0reco data.
Run 2b-2 data reconstructed using earlier d0reco versions
p20.12.00 - p20.12.04 are no longer growing, and do not have or need
separete frozen datasets. For these d0reco versions, use the full
datasets specified above. Summer 2009 analyses should include
the following run 2b-2 data:
- Full p20.12.00, p20.12.01, p20.12.02, p20.12.04 d0reco data (see above).
- P20.12.05 d0reco frozen datasets given in this section.
Frozen summer 2009 datasets include all data up to
and including run 251254.
Thumbnails
The following predefined datasets should be used for skimmed thumbnails.
CSskim-XXXXX-PASS4-p21.12.00-p20.12.05-summer2009
where XXXXX is the skim name.
CAF Trees
The following predefined datasets should be used for skimmed caf trees.
CSG_CAF_XXXXX_PASS4_p21.12.00_p20.12.05_summer2009
where XXXXX is the skim name, except for MUhigh skim, use the following
dataset.
CSG_CAF_MUhigh_PASS4_p21.13.00_p20.12.05_summer2009
Datasets (Frozen Summer 2009 Data)
Comments
to CSG Conveners
Last updated: Feb. 8, 2008