L1S(Nano): add CaloTowers to 2026 "L1ScoutingNano" workflows [16_0_X]#50375
L1S(Nano): add CaloTowers to 2026 "L1ScoutingNano" workflows [16_0_X]#50375missirol wants to merge 3 commits intocms-sw:CMSSW_16_0_Xfrom
16_0_X]#50375Conversation
…=True This changes the initialisation of the vector "selbxOffsets", which is used in case the parameter "skipNonExistingSrc" is set to True. Without this change, that vector is empty, and this leads to a segmentation fault at https://github.com/cms-sw/cmssw/blob/edd2f62bfb3fe43fdc5609ce38b82169e80251fb/DataFormats/NanoAOD/interface/OrbitFlatTable.h#L27
|
A new Pull Request was created by @missirol for CMSSW_16_0_X. It involves the following packages:
@AdrianoDee, @DickyChant, @antoniovagnerini, @battibass, @cmsbuild, @davidlange6, @emeschi, @fabiocos, @ftenchini, @ftorrresd, @mandrenguyen, @miquork, @smorovic can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
cms-bot internal usage |
Updates to add CaloTowers' information to the output of "L1ScoutingNano" for 2026 workflows. This is done by adding a modifier named "run3_l1scouting_2026", and including it in the Era "Run3_2026". Various updates are made to custom_l1scoutingrun3_cff, mainly - using a dedicated Sequence (rather than overriding the regular NANO sequence), and - making the customisation of the relevant output module(s) more robust (covering both the NANOEDMAOD and NANOAOD data tiers, and not relying solely on the label of the output module). Co-Authored-By: Rocco Ardino <rocco.ardino@cern.ch>
This change adds wfs to test on real data the NANOAOD flavours "L1Scout" and "L1ScoutSelect" for the Eras "Run3_2025" and "Run3_2026".
df11e0b to
4ed73ca
Compare
|
Pull request #50375 was updated. @AdrianoDee, @DickyChant, @antoniovagnerini, @battibass, @cmsbuild, @davidlange6, @emeschi, @fabiocos, @ftenchini, @ftorrresd, @mandrenguyen, @miquork, @smorovic can you please check and sign again. |
|
please test |
|
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
|
As expected, I don't see anything problematic in the outputs of the PR tests (DQM discrepancies for wf |
|
+daq |
|
Superseded by #50511. |
backport of #50374
PR description:
From the description of #50374:
PR validation:
None beyond the checks made for #50374 (see description of that PR).
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:
#50374
To facilitate private validation studies on 2026 L1-Scouting data (and maybe as a first step to eventually produce this NANO flavour "centrally" in some way, yet to be determined).