4.2.5. Using PAT On Data
Contents
This is an example for how to run on data in the
Jet
PD.
4.5.1. Prescription
To know more about what data are available for analysis and what are the conditions under which they have been taken have a look to the
PdmV2012Analysis page of the PPD.
A prescription to run the first data in CMSSW_7_4_15 is available on
SWGuidePATReleaseNotes41X. Please follow this link to keep up to date with latest updates. Due to the rapidly changing start-up conditions in software it is beneficial to check this often for the next few weeks.
Input files
The triggers for the
Jet
PD are listed
here
.
Let's take all of them :
Jet = cms.vstring( 'HLT_DiJetAve100U_v4',
'HLT_DiJetAve140U_v4',
'HLT_DiJetAve15U_v4',
'HLT_DiJetAve180U_v4',
'HLT_DiJetAve300U_v4',
'HLT_DiJetAve30U_v4',
'HLT_DiJetAve50U_v4',
'HLT_DiJetAve70U_v4',
'HLT_Jet110_v1',
'HLT_Jet150_v1',
'HLT_Jet190_v1',
'HLT_Jet240_v1',
'HLT_Jet30_v1',
'HLT_Jet370_NoJetID_v1',
'HLT_Jet370_v1',
'HLT_Jet60_v1',
'HLT_Jet80_v1' ),
The first few files are given below:
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/E4D2CB53-9881-E011-8D99-003048F024DC.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/DC453887-7481-E011-89B9-001617E30D0A.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/DABFB9E8-9B81-E011-9FF7-0030487CD812.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/D4E6F338-9B81-E011-A8DE-003048F110BE.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/CEC22BF3-9681-E011-AA91-003048CFB40C.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/BC737791-9581-E011-90E2-0030487CD6DA.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/B6E2792E-8881-E011-9C34-000423D9A212.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/A47B3EF5-9D81-E011-AC11-003048F024FA.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/84253FEF-9B81-E011-9DB7-001617DBD230.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/80749EFD-AB81-E011-A6E3-0030487CD76A.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/749CCE90-9581-E011-862A-000423D9A212.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/6CDB388A-9681-E011-B324-0030487CD178.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/464C7F95-9581-E011-BAEC-0030487CAEAC.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/42B01B46-9D81-E011-AF75-003048F1C58C.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/36C0F1A9-1382-E011-A5B5-003048F11942.root',
'/store/data/Run2011A/Jet/AOD/PromptReco-v4/000/165/121/10691D45-9D81-E011-9A9A-003048F118C2.root',
These files are used in the configuration file in the next section.
Making PAT-tuples
The PAT-tuples are made (without DCSTRONLY for the moment) with
this configuration file
. This file will produce
pat::Jets
from
reco::PFJets
and use
the
PFJetIDSelectionFunctor
in the
full framework to write out only jets that pass jet ID. Thus it is unnecessary to apply jet ID in FWLite.
To run it do the following:
cmsRun PhysicsTools/PatExamples/test/patTuple_data_cfg.py
This will create a file called "jet2011A_aod.root" out of the first 1000 events. The event content is:
cmslpc06:$ edmDumpEventContent jet2011A_aod.root
Type Module Label Process
---------------------------------------------------------------------------------------------
edm::TriggerResults "TriggerResults" "" "HLT"
trigger::TriggerEvent "hltTriggerSummaryAOD" "" "HLT"
L1GlobalTriggerReadoutRecord "gtDigis" "" "RECO"
edm::ConditionsInEventBlock "conditionsInEdm" "" "RECO"
edm::SortedCollection<CaloTower,edm::StrictWeakOrdering<CaloTower> > "towerMaker" "" "RECO"
edm::TriggerResults "TriggerResults" "" "RECO"
reco::BeamSpot "offlineBeamSpot" "" "RECO"
vector<reco::Track> "generalTracks" "" "RECO"
vector<reco::Vertex> "offlinePrimaryVertices" "" "RECO"
vector<reco::Vertex> "offlinePrimaryVerticesWithBS" "" "RECO"
edm::OwnVector<reco::BaseTagInfo,edm::ClonePolicy<reco::BaseTagInfo> > "selectedPatJets" "tagInfos" "PAT"
edm::TriggerResults "TriggerResults" "" "PAT"
vector<CaloTower> "selectedPatJets" "caloTowers" "PAT"
vector<pat::Electron> "selectedPatElectrons" "" "PAT"
vector<pat::Jet> "goodPatJets" "" "PAT"
vector<pat::MET> "patMETs" "" "PAT"
vector<pat::MET> "patMETsPF" "" "PAT"
vector<pat::Muon> "selectedPatMuons" "" "PAT"
vector<pat::Photon> "selectedPatPhotons" "" "PAT"
vector<reco::GenJet> "selectedPatJets" "genJets" "PAT"
vector<reco::PFCandidate> "selectedPatJets" "pfCandidates" "PAT"
Running with FWLite
In order to analyse this in FWLite, use
this executable
and
this configuration file
.
PatBasicFWLiteJetAnalyzer PhysicsTools/PatExamples/bin/analyzePatJetFWLite_cfg.py
This will make some distributions of the
Jets
in the event and write to the file
analyzePatBasics.root
. The histograms are:
KEY: TH1F jetPt;1 pt
KEY: TH1F jetEta;1 eta
KEY: TH1F jetPhi;1 phi
KEY: TH1F disc;1 Discriminant
KEY: TH1F constituentPt;1 Constituent pT
Have fun!!!
--
SalvatoreRoccoRappoccio - 21-Mar-2011