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

Run range (period) Stream Processing Tag Full D3PD Slimmed D3PD GRL to be used
152166-153200 (period A) MinBias r1297 (repro04) Available Samples Available Samples GRL
153565-155160 (period B) MinBias r1297 (repro04) Available Samples Available Samples GRL
152166-153200 (period A) L1Calo r1297 (repro04) Available Samples Available Samples GRL
153565-155160 (period B) L1Calo r1297,r1299 (repro04) Available Samples Available Samples GRL
155228-155697 (period C1) L1Calo f259-f261 (t0pro04) Available Samples Available Samples GRL
156682-156682 (period C2) L1Calo f265 (t0pro04) Available Samples Available Samples GRL
158045-158299 (period D1) L1Calo f270-f271 (t0pro04) Available Samples Available Samples Not yet ready...

Monte Carlo Processing Tag Full D3PD Slimmed D3PD
Pythia J0-J6 (ID=105009-105015) r1303 (repro04) Available Samples Available Samples
Herwig+Jimmy J0-J6 (ID=105038, 105030-105035) r1303 (repro04) Available Samples Available Samples
Alpgen+Jimmy Njets/BBjets (ID=113129-113183) r1302 (repro04) Available Samples Available Samples

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

luminosity_summary.gif

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)

AntiKt4_J5 EPS GIF AntiKt6_J5 EPS GIF

L1_J10

Run Prescale (LumiBlock)
158045 3 (103-117)
158116 3 (110-270), 2 (271-306)

L1_J15

Run Prescale (LumiBlock)

L1_2J5

Run Prescale (LumiBlock)

L1_3J10

Run Prescale (LumiBlock)

L1_FJ5

Run Prescale (LumiBlock)
158045 3 (103-117)
158116 3 (110-270), 2 (271-285)

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 $N^{PV}_{trk} \geq 5$ tracks and $|Z|<100mm$.

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

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formateps L1inc_AntiKt4_A2_B1_B2_C1_C2_Jx.eps r1 manage 15.5 K 2010-07-01 - 22:11 KojiTerashi  
GIFgif L1inc_AntiKt4_A2_B1_B2_C1_C2_Jx.gif r1 manage 41.4 K 2010-07-01 - 22:10 KojiTerashi  
Unknown file formateps L1inc_AntiKt6_A2_B1_B2_C1_C2_Jx.eps r1 manage 15.5 K 2010-07-01 - 22:11 KojiTerashi  
GIFgif L1inc_AntiKt6_A2_B1_B2_C1_C2_Jx.gif r1 manage 41.2 K 2010-07-01 - 22:11 KojiTerashi  
XMLxml MyLBCollection_PeriodA_jetetmiss_7TeV_plus_LUMI.xml r1 manage 4.4 K 2010-07-01 - 19:06 KojiTerashi  
XMLxml MyLBCollection_PeriodB_jetetmiss_7TeV_plus_LUMI.xml r1 manage 3.8 K 2010-07-01 - 19:06 KojiTerashi  
XMLxml MyLBCollection_PeriodC1_jetetmiss_7TeV_plus_LUMI.xml r1 manage 3.3 K 2010-07-01 - 19:06 KojiTerashi  
XMLxml MyLBCollection_PeriodC2_jetetmiss_7TeV_plus_LUMI_minus_LB438.xml r1 manage 2.3 K 2010-07-01 - 19:06 KojiTerashi  
Texttxt branches_Data2010_HCPConfNote.txt r1 manage 1.4 K 2010-07-01 - 23:28 KojiTerashi  
Texttxt branches_MC2010_HCPConfNote.txt r1 manage 2.0 K 2010-07-01 - 23:28 KojiTerashi  
GIFgif luminosity_summary.gif r1 manage 18.1 K 2010-07-01 - 19:30 KojiTerashi  
Compressed Zip archivetgz trigger_ps.tgz r1 manage 5041.9 K 2010-07-01 - 23:35 KojiTerashi  
Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2020-06-18 - MaximKonyushikhin
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback