Links utili
CMSSW_3_9_X codice da Jordan
Code to check out:
CMSSW39X JEC:
cvs co -r V03-01-21 CondFormats/JetMETObjects
cvs co -r V02-02-03 JetMETCorrections/Algorithms
cvs co -r V05-00-17 JetMETCorrections/Modules
cvs co -r V03-02-07 JetMETCorrections/Configuration
MET corrections:
cvs co -r V04-04-00 JetMETCorrections/Type1MET
Beam Halo:
cvs co -r V00-00-07 RecoMET/METAnalyzers
EDanalyzer in form of non-PAT Ntpl producer:
ExampleAnalyzer/METanalyzer
Configureation scripts to run the Ntpl producer:
ExampleAnalyzer/METanalyzer/test/
GammaJet_Dec22_cfg.py - python
crabMET_GammaJet_2010A.cfg, crabMET_GammaJet_2010B.cfg - crab cfg for 2010A and 2010B with preset Dec22 re-reco PD sets
in crab cfgs have to change the scheduler and copy location for the root-tuples
JSON file (local copy is presented):
Cert_136033-149442_7TeV_Dec22ReReco_Collisions10_JSON_v3.txt
After the CRAB submission have to "hadd" all the root-tuples to one file
Ntpl-reader is at:
ExampleAnalyzer/METanalyzer/test/scripts
the input root-tuple is expected to be named METana.root
compiling the reather:
./comp METgammaJet
running the ntpl-reader:
./runAllPileUp.csh
result from the ntpl-reader:
data?PV.root - where ?=1,2,...,6 - this is selection on the number of primary vertexes in the event
data1PV.root - events with 1PV, e.g. no pile-up
data2PVge.root - events with >1PV , e.g. all the events with pile-up
the content of the data?PV.root:
response and resolution vs qT for : Calo Type II, TC, PF, PF Type I MET.
a_uparXXX - response
a_RMSparXXX - resolution RMS(U||), absolute value in GeV with scale correction (e.g. 1/response)
a_RMSperpXXX - resolution RMS(U_pepr), absolute value in GeV with scale correction (e.g. 1/response)
per qT bin distributions for u||/qt and u_perp/qT ar RbinsXXXXX and
RbinsPXXXX respectively - could be usefull at some point.
------------------------------------------------------------------
La mia roba e' su luana in
/data/egallo/CMSSW_3_9_7/src/ExampleAnalyzer/METanalyzer/test
I miei files di ouptut vengono scritti su castor in:
GammaJet/DATA397/
MC, in DBS
search for:
G_Pt_0to15_TuneZ2_7TeV_pythia6
G_Pt_15to30_TuneZ2_7TeV_pythia6
G_Pt_30to50_TuneZ2_7TeV_pythia6
G_Pt_50to80_TuneZ2_7TeV_pythia6
G_Pt_80to120_TuneZ2_7TeV_pythia6
G_Pt_120to170_TuneZ2_7TeV_pythia6
G_Pt_170to300_TuneZ2_7TeV_pythia6
G_Pt_300to470_TuneZ2_7TeV_pythia6
G_Pt_470to800_TuneZ2_7TeV_pythia6
G_Pt_800to1400_TuneZ2_7TeV_pythia6
G_Pt_1400to1800_TuneZ2_7TeV_pythia6
G_Pt_1800_TuneZ2_7TeV_pythia6
G_Pt_15to3000_TuneZ2_Flat_7TeV_pythia6
G_Pt_50to80_TuneZ2_7TeV_pythia6/Spring11-PU_S1_START311_V1G1-v1/AODSIM
Prova codice cosi' come e', solo commentato il trigger per il MC:
28/3 Run2010B, quasi tutto pronto in test/DATA2010B/GammaJet_data2010AB.root,
282294 events OK, funziona, output files in test/DATA2010B
1 job su gamma MC in test/MC/G50to80_Z2_pythia_ProbDist.root
Nphoclean e' l'indice del photone clean, quando nphotons==1? senno'-999
Numero eventi selezionati in data dovrebbe essere con phoHLTacc==1
Provare con questo per high PU? /QCD Pt 15to3000 TuneZ2 Flat 7TeV pythia6/Spring11-E7TeV_FlatDist10_2011EarlyData_50ns_START311_V1G1-v1/GENSIMRECODE
stesso del talk di Florent......running in MC
Provare a confrontare le solite cose per low-high NPV
jobs all aborted on Winter10 sample???
PFnoPU etc., istruzioni da Florent
> First I saw that you used Winter10 or Spring11
> samples, which one is best, and can you point me to the
> right web page for the MC production.
Spring11 should be 3_11_1_p2 MC (at least it is the case for the
Zmumu sample I am using, you can check in DBS for your own sample).
The 3_11 MC includes the TS change in HF, so it is better to use this
one than Winter10 MC. The point is that you probably want to use
sample with in time and OOT PU, ie you should have something like
2011EarlyData_50ns in the name of the sample.
I don't know if there is a web page somewhere with the various MC
production with PU. If you find it, please let me know!
You will found the number of in time PU in the PileupSummaryInfo
collection, however the number of OOT PU is not available. It is only
the case in 42X MC. So the best would be to use 42X MC, but I don't
think that this MC is available yet (anyway PF2PAT is not working in
42X).
> Secondly, to run PFnoPU (I am using 3_9_7) is there a twiki
somewhere or
> some instructions, I could not find it starting from
> the JetMET twiki.
I didn't succeed to read 3_11 MC with 39X release, so I had to switch
to 3_11_3 release.
The documentation to run PF2PAT is here:
https://twiki.cern.ch/twiki/bin/view/CMS/PF2PAT
However, PF2PAT is not working out of the box in 3_11 :(
To make it working I had to make some few changes.
Here is the recipe:
cmsrel CMSSW_3_11_3
cd CMSSW_3_11_3/src
cmsenv
# addpkg of PF2PAT packages:
addpkg PhysicsTools/PatAlgos
addpkg PhysicsTools/PFCandProducer
# change to fix the taus:
cvs co -r V04-07-01-00
PhysicsTools/PFCandProducer/python/pfTaus_cff.py
cvs co -r V08-06-01-07 PhysicsTools/PatAlgos/python/tools/tauTools.py
cvs co -r V08-06-01-07 PhysicsTools/PatAlgos/python/tools/pfTools.py
# if you want to use DA vertex:
# (cf https://twiki.cern.ch/twiki/bin/viewauth/CMS/PrimaryVertex2011)
cvs co -r CMSSW_4_2_0_pre7 RecoVertex/PrimaryVertexProducer
# and you need to change PFPileUP.cc, ie use the new version which is
now in:
# V00-01-03 CommonTools/ParticleFlow
# so I did:
emacs PhysicsTools/PFCandProducer/plugins/PFPileUp.cc &
# remove everything and replace it with
#http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/CommonTools/ParticleFlow/pl
ugins/PFPileUp.cc?revision=1.4&view=markup
# you need also to change the vertex collection used in pfNoPU:
emacs PhysicsTools/PFCandProducer/python/pfPileUp_cfi.py &
# Vertices = cms.InputTag("offlinePrimaryVerticesDA"),
# and call DA before pfNoPU:
emacs PhysicsTools/PFCandProducer/python/pfNoPileUp_cff.py
#from RecoVertex.PrimaryVertexProducer.OfflinePrimaryVertices_cfi
import *
#offlinePrimaryVerticesDA = offlinePrimaryVertices.clone()
#pfNoPileUpSequence = cms.Sequence(
# offlinePrimaryVerticesDA +
# PFnoPU is enable by default, however, the pfMET is computed without
it, so if you want the pfMET after PFnoPU, you have to do:
emacs PhysicsTools/PFCandProducer/python/PF2PAT_cff.py &
# put pfMET after pfNoPU
emacs PhysicsTools/PFCandProducer/python/pfMET_cfi.py &
# src = cms.InputTag("pfNoPileUpPFlow"),
# the last thing is that you probably may want to keep more
collection in the final output tree, so edit:
emacs PhysicsTools/PatAlgos/test/patTuple_PF2PAT_cfg.py &
# and put keep *your favorite branches*
# like: 'keep PileupSummaryInfo_*_*_*'
/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions11/7TeV/Prompt
/Cert_160404-161216_7TeV_PromptReco_Collisions11_JSON.txt
/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions11/7TeV/Prompt
/Cert_161079-161352_7TeV_PromptReco_Collisions11_JSON_noESpbl.txt USE THIS
Le 30/03/2011 19:46, Guofan a ?crit?: Hi Ken,
The changes are committed in
CommonTools/ParticleFlow with tag V00-01-04
PhysicsToolos/PFCandProducer with tag V04-07-02
If you have been working on PFnoPU, the fix is trivially easy.
The only file that needs fix is PFPileUp.cc
I am sending you a diff of PFPileUp.cc after the fix.
http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/CommonTools/ParticleFlow/pl
ugins/PFPileUp.cc?r1=1.4&r2=1.5
So you can apply the changes on your local files.
Hope this helps,
Guofan
To be able to propagate the L1FastJet corrections to the met, I had to
perform some small changes in the JetMETCorrections/Type1MET package.
The new code is available in CVS: JetMETCorrections/Type1MET V04-04-02
I have added this new tag in the queue for 41X, 42X and 43X releases.
.......
CMSSW_4_1_4
Quello che ho provato il 4/4
setenv SCRAM_ARCH slc5_amd64_gcc434
cmsrel CMSSW_4_1_4
cd CMSSW_4_1_4/src
cmsenv
messo tutti il codice di Jordan + gammaJet.tar con METanalyzer cambiato per realdata/MC:
cvs co -r V03-01-21 CondFormats/JetMETObjects
cvs co -r V02-02-03 JetMETCorrections/Algorithms
cvs co -r V05-00-17 JetMETCorrections/Modules
cvs co -r V03-02-07 JetMETCorrections/Configuration
MET corrections:
cvs co -r V04-04-00 JetMETCorrections/Type1MET
Beam Halo:
cvs co -r V00-00-07 RecoMET/METAnalyzers
cp /data/egallo/CMSSW_3_9_7/src/ExampleAnalyzer/METanalyzer/src/METanalyzer.cc .
mi dice:
>> Local Products Rules ..... started
>> Local Products Rules ..... done
****ERROR: Non-XML BuildFiles found. Please convert these to xml format using 'scram build -c'
=> src/ExampleAnalyzer/METanalyzer/BuildFile
=> src/RecoMET/METAnalyzers/BuildFile
>> Building CMSSW version CMSSW_4_1_4 ----
>> Entering Package CondFormats/JetMETObjects
gmake: *** [Non-xml BuildFile check] Error 1
gmake: *** Waiting for unfinished jobs....
scram build -c
e poi ha funzionato
Prova con PFnoPU il 18/4
in CMSSW_4_1_4/src/:
addpkg PhysicsTools/PatAlgos
addpkg PhysicsTools/PFCandProducer
scram b -j 4
it compiles ....
this has revision 1.5 of PFPileUp.cc
http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/CommonTools/ParticleFlow/pl
ugins/PFPileUp.cc?r1=1.4&r2=1.5
changed PFPileUp with revision 1.4, the directory for PFPileUp.h had
to be changed too.
PhysicsTools/PFCandProducer/python/pfNoPileUp_cff.py looks ok
PhysicsTools/PFCandProducer/python/pfPileUp_cfi.py looks ok
PhysicsTools/PFCandProducer/python/TopProjectors/pfNoPileUp_cfi.py looks ok
it compiles....
per cambiare la pfMET, ora e' cambiato il python in
PhysicsTools/PFCandProducer/python/pfMET_cfi.py:
# Clone pfMET producer from RecoMET
from RecoMET.METProducers.PFMET_cfi import *
per cui bisogna cambiare RecoMET/METProducers/python/PFMET_cfi.py:
per cui:
addpkg RecoMET/METProducers
and changed in
RecoMET/METProducers/python/PFMET_cfi.py
# src = cms.InputTag("particleFlow"),
src = cms.InputTag("pfNoPileUpPFlow"),
it compiles.....
to run the data:
in ../test/DATA2011A -> cmsRun GammaJet_2011_cfg.py
(usa il JSON locale)
to run the MC:
in ../test/MC/GammaJet_MC_cfg.py in crab
Note:
-----
in CommonTools/ParticleFlow/python/ ci sono tutti i config per il PF
per es.
CommonTools/ParticleFlow/python/pfType1MET_cfi.py
CommonTools/ParticleFlow/python/ParticleSelectors/pfAllPhotons_cfi.py
CommonTools/ParticleFlow/plugins/PFMET.cc
Non funziona
Samples
2011 data
RUNS 160329-161312 75 nsec
1) GammaJet_Run2011A_dataAOD_FirstJSON.root first ~ 5pb-1 OK
2) GammaJet_Run2011A_dataAOD_FirstJSON_PFnoPU2.root with PFnoPU OK
3) Cert_160404-163369_7TeV_PromptReco_Collisions11_JSON.txt ~46 pb-1 running on crab in DATA2011A
GammaJet_Run2011A_PromptReco_160404-163369.root not clear if all new runs are there WRONG
4) GammaJet_Run2011A_PromptReco_162718-163737_PFnoPU2.root
ready 38.3 pb-1 ? From 162713 it should be 50 nsec (rechecked)
5) GammaJet_Run2011A_PromptRecov1_PFnoPU3.root
v1 sample with usual PFMET=PFnoPu but fractions added
6) GammaJet_Run2011A_PromptRecov2_162718-163737_PFnoPU3.root
v1 with fraction variables in it, PFMet raw
7) 11 maggio
2011/GammaJet_Run2011A_PromptRecov2_162718-163757_PFMET4.root
PFmet raw piu' variabili e 153 pb-1
analogo per v1 e per GammaMC
2011/GammaJet_Run2011A_PromptRecov1_PFMET4.root
Spring11/G_Pt_15to3000_Z2Flat_Spring11_PUS1_PFMET4.root
----------------
in-time pileup, flat Gamma sample
/G_Pt_15to3000_TuneZ2_Flat_7TeV_pythia6/Spring11-PU_S1_START311_V1G1-v1/AODSIM
Spring11/GPt15to3000_Spring11_311.root normal MET
Spring11/GPt15to3000_Spring11_311_PFnoPU2.root
OOT pileup, bugged
/QCD_Pt_15to3000_TuneZ2_Flat_7TeV_pythia6/Spring11-E7TeV_FlatDist10_2011
EarlyData_50ns_START311_V1G1-v1/GEN-SIM-RECODEBUG
OOT pileup, fixed, QCD sample
/QCD_Pt_15to3000_TuneZ2_Flat_7TeV_pythia6/Spring11-PU_S2_START311_V2-v2/GEN-SIM-RECODEBUG
QCD_Pt_15to3000_Z2Flat_Spring11_PUS2_PFnoPU.root
RUNNING crab_0_110427_105353
resubmitted on Friday
BeamHalo, Filters, etc.
If you are a user, you should be aware of an important
observation. One of the handles for identifying halo was the presence
of a local chamber-level trigger which reports an early bunch-crossing
number (e.g., BX = -2 or BX = -3). Now that we are in the era of
50ns and 75ns bunch-spacings, it is probable that soft collision muon
activity from BX = -2 or BX = -3 can mimic this signature for an event
recorded at BX = 0. See the evidence of this given in this recent talk
by M. Rodenburg [1].
The result of this phenomena will be an over-efficiency for the
BeamHaloSummary::CSCLooseHaloId() flag. We therefore recommend that
users switch to BeamHaloSummary::CSCTightHaloId() flag for the
meanwhile, which should be protected as it requires other evidence of
halo to be coincident with the early trigger. Fortunately, an update
to this vulnerable part of the code had been planned, so this will be
remedied in 4_4_X and consequently in future re-reco's of the 2011
data. The plan is to use muon timing variables and relative segment
times to identify incoming halo independent of the absolute time of
the hits. More details to follow in the next few weeks.
Nota: I have already Tight in my selection
------------------------------------------------------------
20/5/2010 Inizio con la 4_2_3, quello che ho fatto:
ssh -X luana
cd /data/egallo
setenv SCRAM_ARCH slc5_amd64_gcc434
cmsrel CMSSW_4_2_3
cd CMSSW_4_2_3/src
cmsenv
cp ../../CMSSW_4_1_4/src/gammaJet.tar .
tar xvf gammaJet.tar # gammajet code frm Jordan
cd ExampleAnalyzer/METanalyzer/src/
cp /data/egallo/CMSSW_4_1_4/src/ExampleAnalyzer/METanalyzer/src/METanalyzer.cc . # my modifications
cvs co -r V03-01-21 CondFormats/JetMETObjects
cvs co -r V02-02-03 JetMETCorrections/Algorithms
cvs co -r V05-00-17 JetMETCorrections/Modules
cvs co -r V03-02-07 JetMETCorrections/Configuration
MET corrections:
cvs co -r V04-04-00 JetMETCorrections/Type1MET
Beam Halo:
cvs co -r V00-00-07 RecoMET/METAnalyzers
scram build -c
scram build -j 4
cd ExampleAnalyzer/METanalyzer/test
rm -rf crab_0*
mkdir MC
cd MC
cp /data/egallo/CMSSW_4_1_4/src/ExampleAnalyzer/METanalyzer/test/MC/GammaJet_MC_cfg.py .
cp /data/egallo/CMSSW_4_1_4/src/ExampleAnalyzer/METanalyzer/test/MC/crab.cfg .
modify these two files
try on
G_Pt-15to3000_TuneD6T_Flat_7TeV_pythia6/Summer11-PU_S3_START42_V11-v2/AODSIM
output files:
G_Pt_15to3000_D6TFlat_Summer11_PUS3_PFMET4.root
funziona con global tag per 39X, ma non con quelli nuovi
Poiche' i nuovi global tags non funzionavano, ho provato:
cvs co -r V04-04-04 JetMETCorrections/Type1MET
scram b -j 4
compila...
Prova con MC_42_V12 su un job in MC/, RUNNING
Start on all MC samples (gamma+QCD):
/G_Pt-15to30_TuneZ2_7TeV_pythia6/Summer11-PU_S3_START42_V11-v2/AODSIM
global tag START42_V12 OK con PFMET5 e nuove variabili (3 per npu, 3 per pfmet)
GPt50-80 RUNNING con anche piu' triggers, da controllare
Gpt-80-120 non c'e'
GPt120-170 RUNNING con anche piu' triggers, da controllare
poi ho fatto, per PFnoPU con la 4_2_3
cvs co -r V00-01-04 CommonTools/ParticleFlow
( NOT ! cvs co -r V04-07-02 PhysicsTools/PFCandProducer, not needed anymore)
scram b -j 4
compila......
addpkg RecoMET/METProducers
uses either
/data/egallo/CMSSW_4_2_3/src/PhysicsTools/PFCandProducer/plugins/PFPileUp.cc
or
/data/egallo/CMSSW_4_2_3/src/PhysicsTools/PFCandProducer/plugins/PFMET.cc
and change in
RecoMET/METProducers/python/PFMET_cfi.py
# src = cms.InputTag("particleFlow"),
src = cms.InputTag("pfNoPileUpPFlow"),
it compiles.....
questo qui sotto non ha funzionato:
addpkg PhysicsTools/PatAlgos
addpkg PhysicsTools/PFCandProducer
No package found in the release.
Provare, direttamente con la 4_2_3:
/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions11/7TeV/Prompt
/Cert_160404-165121_7TeV_PromptReco_Collisions11_JSON.txt 193.568 pb-1
the new ReReco JSONs file (Golden JSON and Muon Phys one), produced with
CMSSW_4_2_3, covering runs in the range 160404 - 163869 are available, some
infos:
-- ReReco datasets and run range:
- /Run2011A-May10ReReco/DQM 160404 - 163869 (last run
before the MD and technical stop)
- full list of 203 runs (below)
-- JSON and Logfile location:
x
All DPG GOOD: (golden JSON)
/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions11/7Te
V/Reprocessing/Cert_160404-163869_7TeV_May10ReReco_Collisions11_JSON.
txt 204.160 pb-1
--------------------- IMPORTANT !!! -----------------------------
---- Changes in 423 release and impact on certification:--------
. change in Global Tag
. change in reconstruction
.. software
.. configuration
Since 4_2_3 vertex reconstruction is with DA and not gap:
https://twiki.cern.ch/twiki/bin/view/CMS/PrimaryVertex2011
generator xsec:
edm::Handle gen;
if(aRun.getByLabel(edm::InputTag("generator"),gen)){
genCrossSection_ = gen->crossSection();
genFilterEfficiency_ = gen->filterEfficiency();
...
Pileup Reweighting
I have placed an initial version of a pileup reweighting function in
PhysicsTools/Utilities, CVS tag V08-03-00. This will be appearing in
releases soon. It can be used in 4_1_X and 4_2_X.
Documentation on how to use it can be found at
PileupMCReweightingUtilities
which is linked from the main Pileup Studies page
PileupInformation
that contains supporting information.
Quello che ho fatto io:
./estimatePileupD.py --maxPileupBin=50 -i Cert_160404-165121_7TeV_PromptReco_Collisions11_JSON.txt pudist_160404-165121_7TeV_PromptReco.root > & estimatepileup.log &
Recent Datasets
DATA:
Photon:
/Photon/Run2011A-May7ReReco-v1/AOD 3305 files, 16427693 events, 2594.46 GB
/Photon/Run2011A-May7ReReco-v1/DQM 188 files, 5307311 events, 1.78 GB
/Photon/Run2011A-May7ReReco-v1/RECO 4459 files, 16433907 events, 9409.75 GB
RECO is 100% complete for Photon, but we had some failed merge jobs for AOD
and DQM which we are working to recover.
MC:
- for Smumer11_R1 two pileup scenarios are available
S3: async OOT PU produced with 4_2_2_patch2
S4: sync OOP PU produced with 4_2_3_patch3
/G_Pt-170to300_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/AODSIM
/G_Pt-170to300_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/GEN-SIM-REC
O
/G_Pt-80to120_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/AODSIM
/G_Pt-80to120_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/DQM
/G_Pt-80to120_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/GEN-SIM-RECO
/QCD_Pt-15to3000_Tune1_Flat_7TeV_pythia8/Summer11-PU_S4_START42_V11-v1/AODSI
M
/QCD_Pt-15to3000_Tune1_Flat_7TeV_pythia8/Summer11-PU_S4_START42_V11-v1/DQM
/QCD_Pt-15to3000_Tune1_Flat_7TeV_pythia8/Summer11-PU_S4_START42_V11-v1/GEN-S
IM-RECO
/G_Pt-170to300_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/AODSIM
/G_Pt-80to120_TuneZ2_7TeV_pythia6/Summer11-PU_S4_START42_V11-v1/AODSIM
------------------------------------------------------------
Codice di Sucadeep, quello che ho fatto:
- scaricato i due pacchetti e compilato
cvs co -d RecoParticleFlow UserCode/sbose/RecoParticleFlow
cvs co -d RecoLocalCalo UserCode/sbose/RecoLocalCalo
ho fatto scram b clean prima e ho tolto i pacchetti Marionneau etc.
-----------------------------------------------------------
codice di Christian, da fare:
cvs co -r V04-05-05 JetMETCorrections/Type1MET
cvs co -r b4_2_X_cvMEtCorr_14Oct2011 PhysicsTools/PatUtils
cvs co -r CMSSW_4_2_4_patch1 DataFormats/METReco
cvs up -r 1.28 DataFormats/METReco/src/classes.h
cvs up -r 1.25 DataFormats/METReco/src/classes_def.xml
cvs co -r V02-03-00 JetMETCorrections/Algorithms
rm JetMETCorrections/Algorithms/interface/L1JPTOffsetCorrector.h
rm JetMETCorrections/Algorithms/src/L1JPTOffsetCorrector.cc
cvs co -r V03-01-00 JetMETCorrections/Objects
cvs up -r 1.2 PhysicsTools/PatUtils/interface/SmearedJetProducerT.h
(perche' non compilava)
# to be added in cfg:--------------------------------------------------------------------------------
# smear PFJets
process.ak5PFJetsL2L3 = cms.EDProducer('PFJetCorrectionProducer',
src = cms.InputTag('ak5PFJets'),
correctors = cms.vstring('ak5PFL2L3')
)
process.totalAnalysisSequence += process.ak5PFJetsL2L3
process.load("RecoJets/Configuration/GenJetParticles_cff")
process.load("RecoJets/Configuration/RecoGenJets_cff")
process.totalAnalysisSequence += process.genParticlesForJetsNoNu
process.totalAnalysisSequence += process.ak5GenJetsNoNu
process.smearedAK5PFJets = cms.EDProducer("SmearedPFJetProducer",
src = cms.InputTag('ak5PFJetsL2L3'),
inputFileName = cms.FileInPath('PhysicsTools/PatUtils/data/pfJetResolutionMCtoDataCorrLUT.root'),
lutName = cms.string('pfJetResolutionMCtoDataCorrLUT'),
smearBy = cms.double(1.0),
srcGenJets = cms.InputTag('ak5GenJetsNoNu'),
dRmaxGenJetMatch = cms.double(0.5)
)
etc. per la Type1, Type2