[14_0_X][L1T] Adding a reduced data format: phase2_l1scout for use in the Spring24 MC Campaign (Phase 2)

[eyigitba]

PR description:

Adding in new configuration options providing a reduced data format: phase2_l1scout for use in the Spring24 MC Campaign. Previously disucssed a bit in #51259

I modified @BenjaminRS's PR based on @mmusich suggestion.

The idea behind this is to reduce the event size by a factor of ~50 to be able to request more MC statistics for Phase-2 L1 Scouting use.

PR validation:

Ran the code locally over ~50 events using Phase2Spring24 MC campaign setup commands. It produces the expected result without crashing. File size goes from ~3 GB to ~100 MB.

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:

Backport of #51330

[cmsbuild]

A new Pull Request was created by @eyigitba for CMSSW_14_0_X.

It involves the following packages:

• Configuration/EventContent (operations)
• Configuration/ProcessModifiers (operations)
• L1Trigger/Configuration (l1)

@BenjaminRS, @cmsbuild, @davidlange6, @fabiocos, @ftenchini, @mandrenguyen, @quinnanm can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @makortel, @missirol, @mmusich this is something you requested to watch as well.
@ftenchini, @mandrenguyen, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

[cmsbuild]

cms-bot internal usage

[BenjaminRS]

please test

[cmsbuild]

+1

Size: This PR adds an extra 28KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-189ad8/54274/summary.html
COMMIT: db20fbc
CMSSW: CMSSW_14_0_X_2026-06-24-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/51319/54274/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 76 lines to the logs
• Reco comparison results: 34 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3349879
• DQMHistoTests: Total failures: 388
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3349471
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 202 log files, 165 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[srimanob]

Hi @eyigitba @BenjaminRS
I understand the goal of PR. However, could you clarify:

• Do you expect it to be useful for next phase-2 campaign, then it should go to master first, then 17_0, then 14_0 as in this PR
• Or useful only current campaign, then it should go to 17_0 first, then this PR.

Thanks.

[BenjaminRS]

Hi @srimanob -- probably it would be useful to have these options available in the future, i.e. CMSSW20+. Why do we need it in 17 too?

[srimanob]

Hi @srimanob -- probably it would be useful to have these options available in the future, i.e. CMSSW20+. Why do we need it in 17 too?

I am not sure the policy of backport now. Master + 14 is a good combination. 17 is as Run1/2/3/ master, I think we used to agree to have it in that too. But I maybe wrong, please consult with ORP.

[eyigitba]

Hi @srimanob I think this will be useful in future campaigns too so I can also make a PR to master and if necessary to 17 too.