cms-jet / jettoolbox Goto Github PK

I want to run the toolbox (ak8+puppi+Softdrop) twice, each with a different pfCandidates collection as input. As far as I can tell, this is not currently going to work, since both collections would end up having the same name.
Could you add an option to customize the name of the output collections? I.e. perhaps using a postfix?

Thanks!

Hi,

As the preliminary Data/MC scale factors for the jet energy resolution were made public recently, I was wondering if there are plans to include them in the JetToolbox?

Thanks,
Jasper

It was pointed out to me today that running my group's ntuple code in 92X (https://github.com/TreeMaker/TreeMaker/tree/Run2_2017) produces a file called jettoolbox.root, even though we haven't explicitly requested it.

The problem seems to be that the implementation of Tasks in the toolbox always adds this to the config:

process.out = cms.OutputModule("PoolOutputModule",
    fileName = cms.untracked.string('jettoolbox.root'),
    outputCommands = cms.untracked.vstring('keep *_ak8PFJetsCHSCleanPrunedMass_*_*', 
        'keep *_NjettinessAK8CHSClean_*_*', 
        'keep *_selectedPatJetsAK8PFCHSClean_*_*', 
        'drop *_selectedPatJetsAK8PFCHSClean_calo*_*', 
        'drop *_selectedPatJetsAK8PFCHSClean_tagInfos_*', 
        'drop *_selectedPatJets*_genJets_*', 
        'drop recoGenJets_*_*_*', 
        'drop *_selectedclean_tagInfos_*', 
        'keep *_patCaloMet_*_*', 
        'keep *_patCaloMet_*_*', 
        'keep *_patCaloMet_*_*')
)
process.endpath = cms.EndPath(process.out, process.myTask)

I'm not sure what the best solution is, but there needs to be some way for the user to turn this off.

I am currently working in a CMSSW_9_4_X release and I have checked out the jetToolbox_91X_v1 tag of the JetToolbox. This was the latest recommended version on the JetToolbox twiki. However, when running the toolbox I get this error:

----- Begin Fatal Exception 15-Feb-2018 12:13:42 CST-----------------------
An exception of category ‘ConfigFileReadError’ occurred while
[0] Processing the python configuration file named treeMaker_stopRA2.py
Exception Message:
python encountered the error: <type ‘exceptions.ImportError’>
cannot import name hepTopTagPFJetsCHS
----- End Fatal Exception --------

I checked through the CMSSW_9_4_X code base on GitHub and found that hepTopTagPFJetsCHS is no longer available. Is there a recommended workaround? Will a 94X version of the JetToolbox be available soon?

Hi,
we updated the jettoolbox used in CMSSW 10_6_5 (and CMSSW 10_2_10) to the newest version (commit 4cc5a6c)
. Since then, we got the following error message:

An exception of category 'ScheduleExecutionFailure' occurred while
   [0] Calling beginJob
Exception Message:
Unrunnable schedule
Module run order problem found: 
patJetsAK4PF after patJetsAK8PFPuppiPATJetswithUserData [path path], patJetsAK8PFPuppiPATJetswithUserData after ak8PFJetsPuppiConstituents [path path], ak8PFJetsPuppiConstituents after ak8PFJetsPuppi [path path], ak8PFJetsPuppi after patJetsAK8PFCHSPATJetswithUserData [path path], patJetsAK8PFCHSPATJetswithUserData after ak8PFJetsCHSConstituents [path path], ak8PFJetsCHSConstituents after ak8PFJetsCHS [path path], ak8PFJetsCHS after patJetsAK8PFPATJetswithUserData [path path], patJetsAK8PFPATJetswithUserData after ak8PFJetsConstituents [path path], ak8PFJetsConstituents after ak8PFJets [path path], ak8PFJets after patJetsAK4PFPuppiPATJetswithUserData [path path], patJetsAK4PFPuppiPATJetswithUserData after ak4PFJetsPuppiConstituents [path path], ak4PFJetsPuppiConstituents after ak4PFJetsPuppi [path path], ak4PFJetsPuppi after puppi [path path], puppi after AK4PFCHSpileupJetIdEvaluator [path path], AK4PFCHSpileupJetIdEvaluator after AK4PFCHSpileupJetIdCalculator [path path], AK4PFCHSpileupJetIdCalculator after patJetsAK4PFCHSPATJetswithUserData [path path], patJetsAK4PFCHSPATJetswithUserData after ak4PFJetsCHSConstituents [path path], ak4PFJetsCHSConstituents after ak4PFJetsCHS [path path], ak4PFJetsCHS after chs [path path], chs after patJetsAK4PFPATJetswithUserData [path path], patJetsAK4PFPATJetswithUserData consumes patJetsAK4PF
 Running in the threaded framework would lead to indeterminate results.
 Please change order of modules in mentioned Path(s) to avoid inconsistent module ordering.

Switching to an older commit (88aa03c) tagged as jettoolbox_102X_v1solved the problem.
For both version we used the same config except for dataTier / miniAOD option.

Are there any other configurations required that are not meantioned in the wiki (https://twiki.cern.ch/twiki/bin/viewauth/CMS/JetToolbox)?

Best Regards,
Matthias

Dear all,
I am looking for JetToolbox for 2018 but I see this is available for upto 94X.
Can you please let me know when this will be available for 10_2X so that we can start analysing 2018 data ASAP.

Thanks,
Deepak from bbDM Team

Currently, it needs to specify the btag discrminator for miniAOD, otherwise it is searching for the AOD collections.

I am trying to create the analog of the slimmedGenJetsAK8 collection but with neutrinos included in the clustering. I am trying to do this using the the jetToolbox; giving it a collection of status=1 packedGenParticles (using CandPtrSelector).

Before I get ahead of myself I am trying to understand some behavior of the jetToolbox where it seems to be automatically selecting lots of parameters "behind my back"; where I feel my configuration should explicitly forbid these things.
Two specific things:
a) I am not specifying a PU mitigation method or jet corrections, but it seems to be applying the usual ('AK8PF', ['L2Relative', 'L3Absolute'], 'None') corrections.
b) I have specified not to run on MC, although from looking at my log file it seems as though the ak8GenJetsNoNu producer is running. (along with many other gen/parton things).

jetToolbox(
process,
'ak8',
'jetSequence',
'noOutput',
miniAOD='True',
newPFCollection="True",
#nameNewPFCollection="stablePackedGenParticles",
nameNewPFCollection='packedPFCandidates',
PUMethod = '',
Cut='pt>=170.',
postFix='example',
runOnMC='False'
)

I have attached my configuration file for reproducibility.

example_cfg.py.zip

If one is using AOD with the CHS pileup method, jetToolbox_cff.py will not be able to assign a value to srcForPFJets before attempting to use it in line 235, resulting in a fatal error. This is due to the "if" statement on line 226 having no corresponding "else". Is the "if" statement on line 226 even necessary?