P20 Pass 5 Data (Run 2b-3, post-2009)
Run 2b-3 data are being reconstructed using d0reco
p20.16.06.
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.16.xx -- Pass 5.
- p20.16.05 -- First p20.16.xx release used for physics.
- p20.16.06 -- Fix crashes.
- p20.16.07 -- Updated calorimeter calibration. Also used for fixing.
- p20.16.08 -- Fix rare calorimeter bug. Also used for reprocessing
p20.16.07 "hot cell" data.
Pass 1 and pass 3 are obsolete. The full run 2b dataset is therefore
the union of pass 2, pass 4, and pass 5 data.
Skimming of pass 5 data was done using production release
p21.18.00.
Caf produciton of pass 5 data was also done using production release
p21.18.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.18.00,
as a base release for analyzing any kind of run 2 data. Production
releases before
p21.15.00 are not compatible with run 2b-3 data. The latest p21 production
releases should be backward compatible with caf format data from all of run 2.
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.
- p21.15.00 - Update geometry. Update track classes to add FTK variables. For Run 2b-3 data.
- p21.16.00 - Synchronize some packages (e.g. alignment) with d0reco production release p20.16.03 (shouldn't affect cafe based analyses).
- p21.17.00 - Synchronized with d0reco production release p20.16.05.
- p21.18.00 - Synchronized with d0reco production release p20.16.06.
Updated muonid, including relaxed cosmic timing cut.
Run 2b-3 data were reconstructed using d0reco versions
p20-16-05-p20.16.08 (d0reco versions p20.16.05 and p20.16.06 were
fixed to update the calorimeter calibration).
Run 2b-3 data reconstructed using d0reco versions earlier than
p20.16.05 have been reprocessed and should not be used for physics analysis.
Run Ranges
The first run 2b-3 run is 255329, taken on Sept. 15, 2009.
Here are the run ranges processed by the different d0reco versions for
run 2b-3.
- p20.16.07 - 255329-255416
- p20.16.06 - 255424-256290
- p20.16.05 - 256296-256917
- p20.16.06 - 256924-257623
- p20.16.07 - 257626-260098
- p20.16.08 - 258166-258587 (reprocessed 3-hot-cell data).
- p20.16.08 - 259693-259698 (reprocessed 1-hot-cell data).
- p20.16.08 - 260099-262856
Reconstructed 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 d0reco and VERSION p20.16.06) and DATA_TIER thumbnail) and TRIG_CONFIG_TYPE physics) and PHYSICAL_DATASTREAM_NAME all%"
Use the following predefined datasets to find reconstructed data in sam.
Warning - d0reco p20.16.07 and d0reco p20.16.08 data are not disjoint, as
they both include data from the 3-hot-cell run range, 258166-258587, and
the 1-hot-cell run range, 259693-259698.
The following two run ranges, which were originally reconstructed using
p20.16.07 d0reco, have been reprocessed using p20.16.08 d0reco for
the purpose of killing hot calorimeter cells.
- 258166-258587 (3-hot-cell data).
- 259693-259698 (1-hot-cell data).
As a result of the reprocessing, data in the above two run ranges have
been reconstructed (and skimmed and caffed) twice. Analyzers need to take
care to avoid getting duplicate data. Note that it is preferable to lose
the p20.16.07 d0reco data and keep the p20.16.08 d0reco data in these
run ranges, because tha latter have good data quality.
Excluding Duplicate Data at the SAM Level
P20.16.08 d0reco data in the above hot-cell
run ranges can be excluded at the sam level
using a run number constraint because skimmed p20.16.08 data
were not merged accross hot-cell run boundaries.
Naturally, it is preferable to exclude reprocessed
p20.16.07 d0reco data in the hot-cell run ranges.
Excluding p20.16.07 data are more complicated because
p20.16.07 data were originally merged accross the hot-cell
run boundaries (a simple
run number constraint won't work). Therefore,
special "reduced" datasets have been defined for skimmed data that exclude
only runs in the hot-cell run ranges.
- Dataasets that end in the word "reduced" exclude the 3-hot-cell run range.
- Datasets that end in the word "reduced2" exclude both the 3-hot-cell
and 1-hot-cell run range.
For example, here are typical names of tmb and caf format datasets that
exclude 3-hot-cell and 1-hot-cell runs.
- TMB format (excludes 3-hot-cell and 1-hot-cell runs) -
CSskim-<skim>-PASS5-p21.18.00-p20.16.07-reduced2.
- CAF format (excludes 3-hot-cell and 1-hot-cell runs) -
CSG_CAF_<skim>_PASS5_p21.18.00_p20.16.07_reduced2.
All data originally reconstructed using d0reco versions p20.16.05 and
p20.16.06 have been fixed in order to update the calorimeter calibration
(therefore, the fixer run range is 255424-257623).
The fixer release is p20.16.07, the same release as d0reco.
Fixed all stream data can be found using the following sam query,
sam translate constraints --dim="APPL_NAME tmbfixer and VERSION csg-p20.16.07 and DATA_TIER thumbnail"
or use the following predefined dataset.
Calorimeter Gain Fixing Algorithm
Here is information about the p20.16.07 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_2009.rcp
from cvs package fixp13tmb_calprob.
To use fixed data from all stream, tmb skims, or caf skims, use p20.16.07
fixed datasets in place of p20.16.05 and p20.16.06 d0reco datasets.
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.
Note that the MUhigh caf subskim is identical with the HAS_MU_10
logical skim from the above page.
Thumbnails
All stream d0reco p20.16.05 data were skimmed using production release
p21.17.00.
All stream d0reco p20.16.06 and p20.16.07 data are being skimmed using
production release p21.18.00.
To find skimmed thumbnails in sam, use the following constraints:
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.18.00-p20.16.07) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
or use the following predefined datasets where
XXXXX is the skim name.
- CSskim-XXXXX-PASS5-p21.17.00-p20.16.05.
- CSskim-XXXXX-PASS5-p21.18.00-p20.16.06.
- CSskim-XXXXX-PASS5-p21.18.00-p20.16.07.
- CSskim-XXXXX-PASS5-p21.18.00-p20.16.08.
CAF Trees
CAF trees are being generated using production
release p21.17.00 (for p20.16.05 d0reco data) or p21.18.00 (for d0reco
p20.16.06 and p20.16.07 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.18.00-p20.16.07) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
or use the predefined datasets:
- CSG_CAF_XXXXX_PASS5_p21.17.00_p20.16.05
- CSG_CAF_XXXXX_PASS5_p21.18.00_p20.16.06
- CSG_CAF_XXXXX_PASS5_p21.18.00_p20.16.07
- CSG_CAF_XXXXX_PASS5_p21.18.00_p20.16.08
where XXXXX is the skim name.
Warning - The unfixed skimmed datasets listed below are not
disjoint between d0reco p20.16.07 and d0reco p20.16.08, as
they both include data from the 3-hot-cell run range, 258166-258587, and
the 1-hot-cell run range, 259693-259698.
To get disjoint datasets, use the unified datasets listed
below.
Datasets for D0reco p20.16.05 and later data.
Thumbnails
All stream data fixed using p20.16.07 were skimmed using production release
p21.18.00.
To find skimmed thumbnails in sam, use the following constraints:
sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.18.00-p20.16.07-fix) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"
or use the following predefined datasets where
XXXXX is the skim name.
- CSskim-XXXXX-PASS5-p21.18.00-p20.16.07-fix.
CAF Trees
CAF trees are being generated using production release p21.18.00 for fixer
p20.16.07 data.
To find CAF trees made from skimmed fixed thumbnails in sam, use the
following constraints:
sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.18.00-p20.16.07-fix) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)
or use the predefined datasets:
- CSG_CAF_XXXXX_PASS5_p21.18.00_p20.16.07_fix
where XXXXX is the skim name.
Datasets for fixed p20.16.07 data.
Unified data for run 2b-3 consists of p20.16.07 fixed data,
non-3-hot-cell-non-1-hot-cell p20.16.07 d0reco data, and
p20.16.08 d0reco data.
No special datasets other than those listed above are needed.
The p20.16.07 d0reco datasets listed below (which have the word
"reduced2"
appended to their names) differ from the full unfixed p20.16.07 datasets by
the exclusion of data in the 3-hot-cell run range (258166-258587) and
the 1-hot-cell run range (259693-259698).
Datasets (Unified Data)
Data for winter 2010 (Moriond) analyses consist of the entire sample of
p20.16.07 fixed data, p20.16.07 d0reco data up to run 258040, plus run 2b-2,
run 2b-1, and run 2a data. As d0reco p20.16.07 is still in use and producing
data, frozen datasets have been defined for p20.16.07 d0reco data that only
include data up to the cutoff run. These frozen datasets have "winter2010"
in the name.
Thumbnails
The following predefined datasets should be used for skimmed thumbnails.
CSskim-XXXXX-PASS5-p21.18.00-p20.16.07-winter2010
where XXXXX is the skim name.
CAF Trees
The following predefined datasets should be used for skimmed caf trees.
CSG_CAF_XXXXX_PASS5_p21.18.00_p20.16.07_winter2010
where XXXXX is the skim name.
Datasets (Frozen Winter 2010 Data)
Data for summer 2010 (ICHEP) analyses consist of the entire sample of
p20.16.07 fixed data, p20.16.07 d0reco data up to run 259547, plus run 2b-2,
run 2b-1, and run 2a data. As d0reco p20.16.07 is still in use and producing
data, frozen datasets have been defined for p20.16.07 d0reco data that only
include data up to the cutoff run. These frozen datasets have "summer2010"
in the name.
Thumbnails
The following predefined datasets should be used for skimmed thumbnails.
CSskim-XXXXX-PASS5-p21.18.00-p20.16.07-summer2010
where XXXXX is the skim name.
CAF Trees
The following predefined datasets should be used for skimmed caf trees.
CSG_CAF_XXXXX_PASS5_p21.18.00_p20.16.07_summer2010
where XXXXX is the skim name.
Datasets (Frozen Summer 2010 Data)
Comments
to CSG Conveners
Last updated: Mar. 30, 2010