Add ScoutingMuonNoVtx and ScoutingMuonVtx in Run3Scouting Nano starting from 2024 data taking

[patinkaew]

PR description:

This PR adds two versions of scouting muon collections, ScoutingMuonNoVtx and ScoutingMuonVtx, following this change CMSHLT-3089:Add hltScoutingMuonPackerVtx to Scouting EventContent.

This fixes issue Missing "hltScoutingMuonPacker" in ScoutingNANO using recent Run-3 data#44817.

This PR also introduces run3_scouting_nanoAOD_post2023 Modifier used to modify configuration and top level Run3_post2023 ModifierChain based on Run3 with run3_scouting_nanoAOD_post2023 Modifier.

PR validation:

Tested by producing scouting NanoAOD from a 2024 scouting HLTSCOUT datatier file using the following cmsDriver.py command:

cmsDriver.py step2 -s NANO:@Scout --process NANO \
--data --eventcontent NANOAOD --datatier NANOAOD -n 10000 \
--era Run3_post2023 --conditions auto:run3_data --filein fileIN.root

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

This PR is not a backport, but backport to 140X will follow.

cc: @elfontan @karim @silviodonato @vlimant

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44970/40251

• This PR adds an extra 28KB to repository

• There are other open Pull requests which might conflict with changes you have proposed:

  • File Configuration/StandardSequences/python/Eras.py modified in PR(s): Add run3 tracking low pu era #33532, add Era_Run3_2024, Era_Run3_2025, Tier0 reco scenario for 2024, and change default era in PyReleaseValidation #43761

[cmsbuild]

A new Pull Request was created by @patinkaew for master.

It involves the following packages:

• Configuration/Eras (operations)
• Configuration/StandardSequences (operations)
• PhysicsTools/NanoAOD (xpog)

@rappoccio, @hqucms, @fabiocos, @vlimant, @antoniovilela, @cmsbuild, @davidlange6 can you please review it and eventually sign? Thanks.
@GiacomoSguazzoni, @rovere, @slomeo, @fabiocos, @felicepantaleo, @VourMa, @VinInn, @sameasy, @missirol, @makortel, @mtosi, @mmusich, @gpetruc, @Martin-Grunewald, @JanFSchulte, @AnnikaStein, @dgulhan this is something you requested to watch as well.
@sextonkennedy, @antoniovilela, @rappoccio you are the release manager for this.

cms-bot commands are listed here

[vlimant]

please remove the intermediate run3_scouting_nanoAOD_post2023 modifier, unless there's a citable policy to do so

[patinkaew]

Sorry I might be completely wrong here. From here, I understand that top level like Run3 as ModifierChain has no method like toModify or toReplaceWith. Therefore, I create run3_scouting_nanoAOD_post2023 as Modifier and call toReplaceWith to replace the tables.

[vlimant]

please include a test workflow in the nano matrix

[vlimant]

enable nano

[vlimant]

our initial comment in #44817 about having Run3_post2023 instead of Run3_2024 and Run3_2025 was to simplify things and limit the number of modifiers. if @cms-sw/orp-l2 and others feel otherwise, we might roll back to Run3_2024 and Run3_2025

[vlimant]

@patinkaew : please go ahead and modify back to Run3_2024 and we will also need a dedicated "scenario" (similar to https://github.com/cms-sw/cmssw/blob/master/Configuration/DataProcessing/python/Impl/ppEra_Run3_2023.py) to be able to run this at Tier0 ; I'm rusty with how to implement this exactly ...

[mmusich]

lease go ahead and modify back to Run3_2024 and we will also need a dedicated "scenario"

This is what was already done in #43761 (now amended to comply with PPD prescription). This PR could simply piggy-back on that one (once merged).

[patinkaew]

Thanks. I'm waiting for #43761 to get merged and then I will make changes accordingly.