HCP Conference Note Analysis
|
Introduction
The purpose of this page is to provide information about data analysis aiming CONF note for HCP 2010 conference. The datasets, GoodRunsList, luminosity, and trigger related information are provided.
Datasets
Primary data format for HCP conference note analysis is QCD D3PDs produced from ESDs. Both May 2010 reprocessed data (repro04) and Tier-0 processed data with repro04 settings (t0pro04) are used in the
D3PD production. The table below summarizes available
D3PD datasets for different run ranges (period), physics streams as input, and GoodRunsLists to be used. Branches stored in the slimmed
D3PDs are listed here (
Data,
MC).
Note
- AlpgenJimmyNjets sample cross sections in AMI are wrong. Refer to here for correct cross sections.
- Pt binning in samples and a feature of Jimmy which sometimes produces partons with higher pT than hard scattering often create a "bump" in the normalized pT spectrum. See here for details and solution. A code to fix this at D3PD level is also provided here.
Good Runs List
The GRLs have been produced using the
standard JetEtMiss selections plus green LUMI flag as recommended by the JetEtMiss and Luminosity groups;
For the period C2, one lumi-block 438 is manually removed from the GRL because RAW->ESD reconstruction job failed and the luminosity calculation is not reliable for this lumi-block. See more information in
this thread.
Luminosity
Below is the summary table of the luminosities for each period and the sum (calculated with
LumiCalc tool using above GRLs,
LumiBlockComps-00-01-08 and lumitag=OffLumi-7TeV-001 + 1.13 factor):
Use the numbers for the actual normalization of histograms, etc. For the plots, please use a number with 2 significant digits + 11% uncertainty, e.g, 17 +/- 2 nb-1 for the sum. See more details of luminosity numbers
here.
Note that the L1_J5 luminosities for period C1 and C2 are slightly smaller than those for L1_J10 and J15 triggers because the J5 trigger was prescaled in a few LBs for some runs (see below).
Trigger
Primary triggers (used so far in jet studies) are L1_MBTS_1, L1_J5, L1_J10, and L1_J15 triggers. A few other triggers like 2J5 (2J10), 3J10, and FJ5 (FJ10) will be used in the near future. Below is the run and lumi-block information where the respective trigger was prescaled with a factor > 1. If there is no entry, it means the trigger is not prescaled yet.
L1_J5
Run |
Prescale (LumiBlock) |
155678 |
3 (231-233, 240-249) |
156682 |
2 (406-448) |
158045 |
23 (103-117), 2 (118-130) |
158116 |
23 (110-270), 21 (271-279), 19 (280-285), 17 (286-306), 4 (307-312), 3 (313-327), 2 (328-554) |
EPS GIF
EPS GIF
L1_J10
L1_J15
L1_2J5
L1_3J10
L1_FJ5
Event and Jet Selection
See
JetEtmissDataAnalysisRecommendationSummer2010 for recommendations by JetEtMiss group.
Trigger
- L1Calo trigger was under commissioning and not fully calibrated in timing before run 152777. A recommendation is to use MBTS_1 trigger before this run. After and including 152777, L1_J* triggers are fully available for jet studies.
- Trigger configuration metadata (trigger decisions before and after prescale, prescale values, etc.) are stored in QCD D3PDs and can be decoded using this example ROOT macro.
- Trigger prescales per lumi-block can be also obtained with this macro.
Primary vertex selection
- A recommendation is to require at least one primary vertex being consistent with the beamspot position (beamspot constraint included in the data processing).
- For reference: inclusive jet/dijet CONF analysis for ICHEP requires at least one primary vertex with tracks and .
To reweight the z vertex distribution in Monte Carlo to match that in data, see instructions from A. Lister here (used in
MinBias analysis):
Reweight z vertex in MC to data
- Reweighting histogram used for unfolding corrections in inclusive jet analysis was derived from data of Period A & B. Will be updated soon including Period C data.
- Histogram can be found here (latest namecycle).
- Example for a function:
double vertex_z_weight( double z ) {
int w_bin = m_weightHistogram->FindBin(z);
return m_weightHistogram->GetBinContent( w_bin );
}
Jet collection and calibration
- Anti-kt, R = 0.4, topo-cluster, EM+JES scale
- Anti-kt, R = 0.6, topo-cluster, EM+JES scale
Jet selection
- Standard JetEtMiss selection + new jet cleaning cut (HECf > 1. - |quality|) as an option
- For reference: inclusive jet/dijet CONF analysis uses only GOOD jets for standard selection
- More info: How to access cleaning variables
- Recommended to check jets if they are removed by the new cleaning cut
- Construct jet TLorentzVector with the eta and phi measured with respect to the primary vertex position:
double jetenergy = jet_Es_em[jetEntry] * jet_emjes[jetEntry]/1000.;
double jetphi = jet_phis_em[jetEntry] + (jet_phis_phys[jetEntry] - jet_phis_gcw[jetEntry]);
double jeteta = jet_etas_em[jetEntry] + (jet_etas_phys[jetEntry] - jet_etas_gcw[jetEntry]);
double jetm = jet_ms_em[jetEntry] * jet_emjes[jetEntry] * (jet_ms_phys[jetEntry] / jet_ms_gcw[jetEntry]) / 1000.;
double jetp = sqrt(jetenergy*jetenergy - jetm*jetm);
double jetpt = jetp / cosh( jeteta );
TLorentzVector jet;
jet.SetPtEtaPhiM(jetpt, jeteta, jetphi, jetm);
Cosmics/Beam-Induced background
Several runs are selected and QCD
D3PDs are produced from events in CosmicCalo stream to check cosmic background in the main data sample.
Run (period) |
Full D3PD |
GRL to be used |
152409 (period A) |
group10.perf-jets.data10_7TeV.00152409.physics_CosmicCalo.merge.ESD.r1297_p161_JetEtMissDPDModifier000025.v1_EXT0 |
GRL |
153565 (period B) |
group10.perf-jets.data10_7TeV.00153565.physics_CosmicCalo.merge.ESD.r1297_p161_JetEtMissDPDModifier000025.v1_EXT0 |
GRL |
155112 (period B) |
group10.perf-jets.data10_7TeV.00155112.physics_CosmicCalo.merge.ESD.r1299_p161_JetEtMissDPDModifier000025.v1_EXT0 |
GRL |
155678 (period C1) |
group10.perf-jets.data10_7TeV.00155678.physics_CosmicCalo.recon.ESD.f261_JetEtMissDPDModifier000025.v1_EXT0 |
GRL |
156682 (period C2) |
group10.perf-jets.data10_7TeV.00156682.physics_CosmicCalo.recon.ESD.f265_JetEtMissDPDModifier000025.v1_EXT0 |
GRL |
158116 (period D1) |
In production |
Not yer ready |
For beam-induced backgrounds, a recommendation is to check "UNPAIRED" bunch crossing triggers (e.g, L1_J5_UNPAIRED). Events passing UNPAIRED triggers are sent out in the physics streams (e.g, L1Calo). The UNPAIRED trigger decisions are available in QCD
D3PDs by reading trigger configuration metadata. See
here for an example.
Debug stream events
QCD
D3PDs from debug sream events are produced by the Exotics group.
Here is the available samples from debugrec_hltacc datasets.
Debug stream event analysis in context of inclusive jets/dijets can be found
here and
here. Similar analysis for multi-jet studies is
here.
%RESPONSIBLE%
KojiTerashi
%REVIEW%
Never reviewed
Major modifications:
--
KojiTerashi - 29-Jun-2010