P20 Pass 4 Data and MC (Postshutdown 2007)

D0reco Releases

What is the difference between pass 3 and pass 4 postshutdown 2007 data?

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.

Analysis Releases

Which release should you use for analysis?

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 - Recaffing (hf skimming, updated cft clusters).

Unfixed Data

Pass 4 unfixed data has been reconstructed using d0reco versions p20.12.00, p20.12.01, and p20.12.02.

Run Ranges

Store 5544, runs 234207-234213, which were not processed with preshutdown data, are also included in postshutdown 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-current.

Unfixed Data in SAM

sam translate constraints --dim="(((APPL_NAME recon_root, d0reco and VERSION p20.12.00, p20.12.01, p20.12.02) and DATA_TIER thumbnail) and TRIG_CONFIG_TYPE physics) and FILE_NAME recoT_all_%"

When using the genLBNtables script for the generation of the parentage tables use the option -pass p21pass4.

The following predefined dataset can also be used.

• CSG_Skim_p20.12.00.
• CSG_Skim_p20.12.01.
• CSG_Skim_p20.12.02.
• CSG_Skim_p20.12.00_p20.12.02.

Fixed Data

Inconsistent Gain Data

Unfixed data from this run range can be found using the following predefined sam dataset.

• CSG_Skim_p20.12.00_IG.

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"

• CSG_Skim_p20.12.00_IG_fixed.

There is also a unified all stream dataset giving fixed or unfixed data depending on run number.

• CSG_Skim_p20.12.00_fixed.

Fixing Algorithm

The top level rcp file for fixing is runP20TMBfixer[SAM]_TMB_IG.rcp from cvs package fixp13tmb_calprob.

• Expanded list of rcps.
• Synopsis of fixing algorithm.

How to use fixed data in physics analysis

Monte Carlo

Recaffed MC Samples

sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.11.00-v4 and DATA_TIER root-tree-bygroup) and GLOBAL.REQUESTID XXXXX)

CSG_CAF_MCv4-XXXXX_p21.11.00

where XXXXX is the request id.

Older MC Caf Samples

sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-RELEASE) and DATA_TIER root-tree-bygroup) and GLOBAL.REQUESTID XXXXX)

or use the predefined datasets

CSG_CAF_MCv2-XXXXX_RELEASE

where RELEASE is the tmb_analyze release, and XXXXX is the request id.

Recommended tmb_analyze releases and datasets associated with different request ids. are as follows:

• p21.04.00 - Not recommended.
• p21.05.00 - Not recommended.
• p21.06.00 - Bug in EM cluster energy (effect of a few percent level).
• p21.08.00 - dataset CSG_CAF_MCv2-XXXXX_p21.08.00.

Other information

For individuals who would like to run tmb_analyze on some MC samples by themselves, one could do:

setup D0RunII p21.11.01 -O SRT_QUAL=maxopt
setup d0tools
runTMBAnalyze -format=MCSmear -fpe -maxopt -defname=req-id-${REQID}-tmb-good-genuine -${BATCH} -scratch=${SCRATCH}

Skimming Overview

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.03.00.

• Skim definitions for p21.03.00

Skimmed Unfixed Data

Thumbnails

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)"

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.01 d0reco data -- CSskim-XXXXX-PASS4-p21.08.00-p20.12.02.

CAF Trees

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)

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

where XXXXX is the skim name.

When using the genLBNtables script for the generation of the parentage tables use the option -pass p21pass4.

Datasets

Skimmed Fixed Data

Thumbnails

sam translate constraints --dim="(((APPL_NAME tmbskim and VERSION csg-p21.08.00-fix) and DATA_TIER thumbnail) and SKIM.NAME xxxxx)"

or use the predefined dataset CSskim-XXXXX-PASS4-p21.08.00-fix2008 where XXXXX is the skim name. xxxxx)

Datasets (Fixed Data)

Skimmed Unified Data

Recall that d0reco p20.12.01 and p20.12.02 data do not need to be fixed. The full postshutdown data is the union of d0reco p20.12.00, p20.12.01, and p20.12.02 data.

Thumbnails

The sam constraints for extracting unified data from sam are quite complicated. Therefore, it is recommended to use the following predefined datasets.

CSskim-XXXXX-PASS4-p21.08.00-allfix2008

where XXXXX is the skim name.

Regenerated CAF Trees

To find regenerated CAF trees in sam, use the following constraints.

sam translate constraints --dim="(((APPL_NAME tmb_analyze and VERSION csg-p21.10.00-p20.12.00) and DATA_TIER root-tree-bygroup) and SKIM.NAME xxxxx)

or use the predefined datasets:

CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.00

where XXXXX is the skim name.

Recall that caf trees for d0reco p20.12.01 and p20.12.02 data were originally generated using production release p21.10.00 or p21.11.00, and so don't need to be regenerated.

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)

Fronzen Datasets for Summer 2008 Analyses

• 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

CSskim-XXXXX-PASS4-p21.08.00-p20.12.02-summer2008

where XXXXX is the skim name.

CAF Trees

CSG_CAF_XXXXX_PASS4_p21.10.00_p20.12.00

where XXXXX is the skim name.

Datasets (Frozen Summer 2008 Data)