ValueError when submitting Run 3 MC with trigger info

When trying to produce Run 3 MC samples (tried both /QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8/Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v9-v2/MINIAODSIM and /QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8/Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v10-v2/MINIAODSIM) with mkNtuples -t the following error occured:

         mkNtuples -t Run3Pythia8CP5_FlatAK4.json 
Opening Run3Pythia8CP5_FlatAK4.json
latest commit: Merge branch 'bugfix/macosx' into 'master'

adapting the tests to Mac OS X

See merge request Proto/Darwin!110               by Louis Moureaux (41bc9d0df003318)
+ das-cmssw el8 mkNtuples -t Run3Pythia8CP5_FlatAK4_41bc9d0df003318.json
Opening Run3Pythia8CP5_FlatAK4_41bc9d0df003318.json
/QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8/Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v9-v2/MINIAODSIM
+ dasgoclient --query="file dataset=/QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8/Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v9-v2/MINIAODSIM" -limit=1
+ cmsRun /eos/home-a/aziaka/DAS_TriggerMC/CMSSW_12_4_0/src/Core/Ntupliser/python/Ntupliser_cfg.py inputFiles=root://cms-xrd-global.cern.ch//store/mc/Run3Winter24MiniAOD/QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8/MINIAODSIM/133X_mcRun3_2024_realistic_v9-v2/2830000/86bc33cd-6e64-476c-aca3-fcbcf3198d54.root outputFile=QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8_41bc9d0df003318/test_Pythia8CP5_Flat_UL18AK4_Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v9-v2.root maxEvents=100 configFile=QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8_41bc9d0df003318/test_Pythia8CP5_Flat_UL18AK4_Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v9-v2.json
MaxEvents=100
133X_mcRun3_2024_realistic_v10
No MET filters
----- Begin Fatal Exception 10-Mar-2025 18:54:51 CET-----------------------
An exception of category 'ConfigFileReadError' occurred while
   [0] Processing the python configuration file named /eos/home-a/aziaka/DAS_TriggerMC/CMSSW_12_4_0/src/Core/Ntupliser/python/Ntupliser_cfg.py
Exception Message:
 unknown python problem occurred.
ValueError: No PU jet ID could be determined

At:
  /eos/home-a/aziaka/DAS_TriggerMC/CMSSW_12_4_0/src/Core/Ntupliser/python/Ntupliser_cfg.py(349): <module>

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

This ValueError can be traced to the Ntupliser configuration file (L336-349), where the undefined _stdalgos variable for 2024 may cause the issue, since it is later used in determining the algorithm of the process (L351-357). However, according to the JetMET recommendations, PU jet ID is not mandatory for Run 3 analyses.

The .json file used for the submission was written as follows:

{
       "name": "Pythia8CP5_Flat_UL18AK4",
       "maxEvents": 1000,
       "flags": {
           "R": 4,
           "labels": ["AK", "PUUPI"],
           "options" : ["jets", "triggers", "muons"]
       },
        "crab": {
          "storageSite": "T3_CH_CERNBOX"
      },
      "datasets": {
          "/QCD_PT-15to7000_TuneCP5_Flat2022_13p6TeV_pythia8/Run3Winter24MiniAOD-133X_mcRun3_2024_realistic_v9-v2/MINIAODSIM": {}
      }
  }

Since it is not recommended, I think that it is sufficient to change https://gitlab.cern.ch/cms-analysis/general/DasAnalysisSystem/Core/-/blob/feature/run3/Ntupliser/python/Ntupliser_cfg.py?ref_type=heads#L291 as follows:

getPUjetID = jets and 'CHS' in labels and radius == 0.4 and year < 2019

assigned to @aziaka

added DasAnalysisSystem#3 as parent epic

added changepatch statusongoing typesoftware labels

changed the description

added statusfinalising label and removed statusongoing label

changed milestone to %N-tupliser configuration

changed title from ValueError when submitting Run 3 MC to ValueError when submitting Run 3 MC with trigger info