NanoAOD (L1-Scouting): CMSSW subpackages

[missirol]

As discussed in the XPOG meeting on Apr-01 (2026), the implementation of the NanoAOD flavours for L1-Scouting is currently organised as follows in CMSSW.

• DataFormats/NanoAOD (xpog).
  • Contains the l1ScoutingRun3::OrbitFlatTable data format (which inherits from nanoaod::FlatTable).
• PhysicsTools/NanoAOD (xpog).
  • Definition of the 2 NanoAOD flavours (python sequence, and customisations), incl. the L1-Scouting NanoAOD EventContents.
• L1TriggerScouting/Utilities (daq).
  • C++ implementation of the plugins (and related classes) specific to L1-Scouting NanoAOD, most notably OrbitNanoAODOutputModule.

Based on the discussion in that meeting, I understood that

• it would be good to have most of the implementation under a package which is reviewed by both XPOG and DAQ (incl. L1-Scouting experts), and
• having NanoAOD-related software under the generic L1TriggerScouting/Utilities is arguably unintuitive.

This would suggest the following re-arrangement.

• (unchanged) DataFormats/NanoAOD (xpog).
  • Contains the l1ScoutingRun3::OrbitFlatTable data format (which inherits from nanoaod::FlatTable).
• (new package) L1TriggerScouting/NanoAOD (xpog, daq).
  • Will contain all the python and C++ code related to L1-Scouting NanoAOD (which is currently in PhysicsTools/NanoAOD and L1TriggerScouting/Utilities).

The "double ownership" of L1TriggerScouting/NanoAOD follows what is done for packages like DPGAnalysis/*NanoAOD* (which are under XPOG, plus the relevant DPG).

As far as I can see, the only disadvantage is the creation of a new CMSSW subpackage; not sure if this is okay.

Note: in this draft proposal, OrbitNanoAODOutputModule would be moved to L1TriggerScouting/NanoAOD for now. It might make sense to move it to PhysicsTools/NanoAOD eventually, depending on what will come out of #50635.

Any objections, or suggestions ?

Attn: @cms-sw/xpog-l2 @cms-sw/daq-l2

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @missirol.

@Dr15Jones, @ftenchini, @makortel, @mandrenguyen, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[missirol]

The "double ownership" of L1TriggerScouting/NanoAOD follows what is done for packages like DPGAnalysis/NanoAOD (which are under XPOG, plus the relevant DPG).

As a side note, I wonder if it would make more sense to have this new package reviewed by @cms-sw/l1-l2 rather than @cms-sw/daq-l2, since the L1-Scouting NanoAOD flavour has some connection to the L1T-DPG NanoAOD flavour (and NanoAOD does not seem to me like a topic of interest to DAQ). Of course, it could also be assigned to all 3 groups (XPOG, L1T, DAQ).

[makortel]

assign xpog,daq,l1

[cmsbuild]

New categories assigned: xpog,daq,l1

@battibass,@BenjaminRS,@emeschi,@ftorrresd,@quinnanm,@smorovic you have been requested to review this Pull request/Issue and eventually sign? Thanks