Ntupliser fails: An exception of category 'ProductNotFound' occurred

Output of mkNtuple -t

+ das-cmssw el8 mkNtuples -t config_22c6c808f60d7d5.json
Opening config_22c6c808f60d7d5.json
/FSQJet2/Run2017H-09Aug2019_UL2017_LowPU-v1/MINIAOD
+ dasgoclient --query="file dataset=/FSQJet2/Run2017H-09Aug2019_UL2017_LowPU-v1/MINIAOD" -limit=1
+ cmsRun /afs/cern.ch/user/z/zhye/DasAnalysisSystem/CMSSW_12_4_0/src/Core/Ntupliser/python/Ntupliser_cfg.py inputFiles=root://cms-xrd-global.cern.ch//store/data/Run2017H/FSQJet2/MINIAOD/09Aug2019_UL2017_LowPU-v1/230000/A5169B9D-668B-5A4F-9BAC-AA9938149A00.root outputFile=FSQJet2_22c6c808f60d7d5/test_FSQ2H_V1_Run2017H-09Aug2019_UL2017_LowPU-v1.root maxEvents=1000 configFile=FSQJet2_22c6c808f60d7d5/test_FSQ2H_V1_Run2017H-09Aug2019_UL2017_LowPU-v1.json
MaxEvents=1000
106X_dataRun2_v37
No MET filters
|---- jetToolbox: Initializing collection... (with postfix )
|---- jetToolBox: btag discriminators are recommended for AK4 and AK8 jets. For a different cone size, please especify the discriminators. Turning OFF all the default btag discriminators.
|---- jetToolBox: JETTOOLBOX RUNNING ON MiniAOD FOR AK4 JETS USING CHS
|---- jetToolBox: Applying these corrections: ('AK4PFchs', ['L1FastJet', 'L2Relative', 'L3Absolute', 'L2L3Residual'], 'None')
|---- jetToolBox: Creating selectedPatJetsAK4PFCHS collection.
************** MC dependence removal ************
removing MC dependencies for jets
%MSG-w CondDBESSource:  (NoModuleName) 20-Feb-2025 07:11:37 CET pre-events
Plugin for Record PGeometricDetExtraRcd has not been found.
%MSG
20-Feb-2025 07:11:37 CET  Initiating request to open file root://cms-xrd-global.cern.ch//store/data/Run2017H/FSQJet2/MINIAOD/09Aug2019_UL2017_LowPU-v1/230000/A5169B9D-668B-5A4F-9BAC-AA9938149A00.root
%MSG-w XrdAdaptor:  file_open 20-Feb-2025 07:11:55 CET pre-events
Data is served from gridka.de instead of original site cern.ch
%MSG
20-Feb-2025 07:11:57 CET  Successfully opened file root://cms-xrd-global.cern.ch//store/data/Run2017H/FSQJet2/MINIAOD/09Aug2019_UL2017_LowPU-v1/230000/A5169B9D-668B-5A4F-9BAC-AA9938149A00.root
/afs/cern.ch/user/z/zhye/DasAnalysisSystem/CMSSW_12_4_0/src/Core/Ntupliser/plugins/Ntupliser.cc:Ntupliser
/afs/cern.ch/user/z/zhye/DasAnalysisSystem/CMSSW_12_4_0/src/Core/Ntupliser/plugins/Ntupliser.cc:beginJob
Extracting pileup normalisation from "/eos/home-z/zhye/MN-analysis/rootfile/table/PUprofile/pileup_JSON.json"
----- Begin Fatal Exception 20-Feb-2025 07:12:05 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 307014 lumi: 1236 event: 1759571332 stream: 0
   [1] Running path 'p'
   [2] Calling method for module Ntupliser/'ntupliser'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: pat::PackedTriggerPrescales
Looking for module label: patTrigger
Looking for productInstanceName: 
Looking for process: PAT
   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "SkipEvent = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------

First guess problem happened at here

        // HLT
        iEvent.getByToken(p.triggerPrescalesToken,triggerPrescales);

        // L1
        iEvent.getByToken(p.triggerPrescalesl1minToken, triggerPrescalesl1min);
        iEvent.getByToken(p.triggerPrescalesl1maxToken, triggerPrescalesl1max);

added typesoftware label

my config

{
    "name": "FSQ2runH_V1",
    "maxEvents": 1000,
    "flags": {
        "R": 4,
        "labels": ["AK", "CHS"],
        "options" : ["triggers", "jets"]
    },
    "crab": {
        "storageSite": "T3_CH_CERNBOX"
    },
    "luminosity": {
        "mask": "/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions17/13TeV/Final/Cert_306896-307082_13TeV_PromptReco_Collisions17_JSON_LowPU.txt"
    },
    "datasets": {
        "/FSQJet2/Run2017H-09Aug2019_UL2017_LowPU-v1/MINIAOD": {"splitting": "Automatic"}
    }
}

added DasAnalysisSystem#3 as parent epic

assigned to @paconnor

mentioned in issue #187 (closed)

Similar to 2023 MC in #187 (closed), in 2024 MC the patTrigger collection comes from the PAT process.

$ edmDumpEventContent /eos/cms/store/mc/Run3Winter25MiniAOD/QCD_Bin-Pt-470to600_TuneCP5_13p6TeV_pythia8/MINIAODSIM/142X_mcRun3_2025_realistic_v7-v2/2560000/42278774-c6f6-4d26-b68a-abf32957dad6.root | grep -i trig
edm::TriggerResults                   "TriggerResults"            ""                "SIM"     
edm::TriggerResults                   "TriggerResults"            ""                "HLT"     
L1GlobalTriggerReadoutRecord          "gtDigis"                   ""                "RECO"    
edm::TriggerResults                   "TriggerResults"            ""                "RECO"    
edm::TriggerResults                   "TriggerResults"            ""                "PAT"     
pat::PackedTriggerPrescales           "patTrigger"                ""                "PAT"     
pat::PackedTriggerPrescales           "patTrigger"                "l1max"           "PAT"     
pat::PackedTriggerPrescales           "patTrigger"                "l1min"           "PAT"     
vector<pat::TriggerObjectStandAlone>    "slimmedPatTrigger"         ""                "PAT"     
vector<string>                        "slimmedPatTrigger"         "filterLabels"    "PAT"

Same is true for data, at least /eos/cms/store/data/Run2023C/MinimumBias/MINIAOD/22Sep2023_v4-v1/40000/ea557681-a107-4939-93e1-d94d673d97d7.root.

assigned to @lmoureau and unassigned @paconnor

mentioned in merge request !234

mentioned in merge request !235

changed milestone to %N-tupliser configuration