NanoAOD ntupler for Phase-2 L1 Objects
Tested under latest CMSSW_14_0 pre-release: CMSSW_14_0_0_pre3:
cmsrel CMSSW_14_0_0_pre3
cd CMSSW_14_0_0_pre3/src
git clone [email protected]:cms-l1-dpg/Phase2-L1Nano.git PhysicsTools/L1Nano
scram b -j 8In the test directory there is a cmsRun config to rerun the L1 trigger + the P2GT emulator and produce the nano ntuple from these outputs.
Usage: cmsRun rerunL1_140pre3_Nano_cfg.py
One can append the L1Nano output to the cmsDriver command via this customisation:
--eventcontent NANOAOD
-s USER:PhysicsTools/L1Nano/l1tPh2Nano_cff.l1tPh2NanoTask --customise PhysicsTools/L1Nano/l1tPh2Nano_cff.addFullPh2L1NanoExample command (w/o Track Trigger, based on the 1400pre2 recipe from the Offline SW twiki):
cmsDriver.py step1 --conditions 131X_mcRun4_realistic_v9 -n 2 --era Phase2C17I13M9 --eventcontent NANOAOD -s RAW2DIGI,L1,L1P2GT,USER:PhysicsTools/L1Nano/l1tPh2Nano_cff.l1tPh2NanoTask --datatier GEN-SIM-DIGI-RAW-MINIAOD --fileout file:test.root --customise SLHCUpgradeSimulations/Configuration/aging.customise_aging_1000,Configuration/DataProcessing/Utils.addMonitoring,L1Trigger/Configuration/customisePhase2.addHcalTriggerPrimitives,PhysicsTools/L1Nano/l1tPh2Nano_cff.addFullPh2L1Nano --geometry Extended2026D95 --nThreads 8 --filein /store/mc/Phase2Spring23DIGIRECOMiniAOD/TT_TuneCP5_14TeV-powheg-pythia8/GEN-SIM-DIGI-RAW-MINIAOD/PU200_L1TFix_Trk1GeV_131X_mcRun4_realistic_v9-v1/50000/005bc30b-cf79-4b3b-9ec1-a80e13072afd.root --mc --inputCommands="keep *, drop l1tPFJets_*_*_*" --outputCommands="drop l1tPFJets_*_*_*"The output file is a nanoAOD file with the output branches in the Events tree.
An overview of the corresponding content is shown here: https://alobanov.web.cern.ch/L1T/Phase2/L1Nano/l1menu_nano_14X_doc_report.html
Size report: https://alobanov.web.cern.ch/L1T/Phase2/L1Nano/l1menu_nano_14X_size_report.html
Example:
['run',
'luminosityBlock',
'event',
'bunchCrossing',
'nL1caloJet',
'L1caloJet_et',
'L1caloJet_eta',
'L1caloJet_phi',
'L1caloJet_pt',
'L1caloJet_z0',
'nL1caloTau',
'L1caloTau_eta',
'L1caloTau_phi',
'L1caloTau_pt',
'nGenJet',
'GenJet_eta',
'GenJet_mass',
...This can be easily handled with uproot/awkward like this:
f = uproot.open("l1nano.root")
events = f["Events"].arrays() The GT emulator decisions are stored like this for now:
'nL1GT', -> number of algorithms, the names are not stored, but are alphabetically sorted
'L1GT_final', -> final decision
'L1GT_initial', -> initial decision (no difference at the moment)
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent