Update GTs and modifiers for L1T 2024 menu L1Menu_Collisions2024_v1_3_0_xml

[perrotta]

Update L1T menu in the 2024 MC GTs with L1Menu_Collisions2024_v1_3_0_xml, as from cmsTalk, as well as the modifier for the L1T menu to be used in data RelVals.

The new L1T menu tag replaces the previous L1Menu_Collisions2024_v1_2_0_xml. The difference wrt the previous tag is summarized here , and the new or removed seeds can be visible also via the Payload Inspector:

The updated 2024 MC GTs in autoCond are the following:

• 140X_mcRun3_2024_realistic_v15
• 140X_mcRun3_2024_design_v11
• 140X_mcRun3_2024cosmics_realistic_deco_v13
• 140X_mcRun3_2024cosmics_design_deco_v11

And the difference wrt the GTs previously in autocond are the following:

• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024_realistic_v14/140X_mcRun3_2024_realistic_v15
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024_design_v10/140X_mcRun3_2024_design_v11
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024cosmics_realistic_deco_v12/140X_mcRun3_2024cosmics_realistic_deco_v13
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024cosmics_design_deco_v10/140X_mcRun3_2024cosmics_design_deco_v11

Please notice that the new phase1_2024_realistic GT includes also three additional updates that were not yet propagated to autocond, and therefore pile-up here on top of the L1T menu change:

• 140X_mcRun3_2024_realistic_v12:
  • Update GEM Channel mapping for 2024 MC conditions. See cmsTalk
• 140X_mcRun3_2024_realistic_v13:
  • Update HLT PF hadron Calibration and JECs in preparation for Run3Summer24 campaign See details of the conditions in cmsTalk
• 140X_mcRun3_2024_realistic_v14:
  • Update offline PF hadron calibration for 2024 MC i.e. Run3Summer24 campaign (See details in cmsTalk). The offline JECs derived with this PF HC should follow soon once they are ready

Validation

I verified that this PR does not conflict in github with #45387, therefore the two PRs can be kept and merged independently

[cmsbuild]

cms-bot internal usage

[perrotta]

please test

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45389/40840

• There are other open Pull requests which might conflict with changes you have proposed:
  • File Configuration/AlCa/python/autoCond.py modified in PR(s): New SimBeamSpotHLLHC tags in Phase-2 MC GT and make Phase-2 workflows consume it #45387
  • File Configuration/AlCa/python/autoCondModifiers.py modified in PR(s): New SimBeamSpotHLLHC tags in Phase-2 MC GT and make Phase-2 workflows consume it #45387

[cmsbuild]

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

It involves the following packages:

• Configuration/AlCa (alca)

@consuegs, @perrotta, @saumyaphor4252 can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @missirol, @mmusich, @rsreds, @tocheng, @yuanchao this is something you requested to watch as well.
@antoniovilela, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

[perrotta]

please test
(IBs not cleaned yet, but let see if at least we can collect some output)

[cmsbuild]

+1

Size: This PR adds an extra 12KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c94767/40273/summary.html
COMMIT: 8532954
CMSSW: CMSSW_14_1_X_2024-07-07-0000/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/45389/40273/install.sh to create a dev area with all the needed externals and cmssw changes.

• DAS Queries: The DAS query tests failed, see the summary page for details.

Comparison Summary

There are some workflows for which there are errors in the baseline:
29634.911 step 2
The results for the comparisons for these workflows could be incomplete
This means most likely that the IB is having errors in the relvals.The error does NOT come from this pull request

Summary:

• You potentially removed 21 lines from the logs
• ROOTFileChecks: Some differences in event products or their sizes found
• Reco comparison results: 2700 differences found in the comparisons
• DQMHistoTests: Total files compared: 47
• DQMHistoTests: Total histograms compared: 3246793
• DQMHistoTests: Total failures: 499
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3246274
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 46 files compared)
• Checked 199 log files, 163 edm output root files, 47 DQM output files
• TriggerResults: found differences in 6 / 45 workflows

[perrotta]

+1

• Quite several differences are visible in the tests: they are all compatible with the updates of PF hadron calibrations and Jet Energy corrections integrated with the versions v13 and v14 of the 140X_mcRun3_2024_realistic_v* GT
• A few differences in the TriggerResults are understood because of the modified L1 menu, see Update GTs and modifiers for L1T 2024 menu L1Menu_Collisions2024_v1_3_0_xml #45389 (comment) (this bullet was modified from its original formulation thanks to the observation in Update GTs and modifiers for L1T 2024 menu L1Menu_Collisions2024_v1_3_0_xml #45389 (comment) and the following discussion)

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[mmusich]

As expected, no effect on the outputs of the current workflows because of the modified L1 menu: the HLT menu that uses the new seeds is not yet included in those workflows

In the trigger results changes I see:

      Events    Accepted      Gained        Lost       Other  Trigger
         100           2         +18          -1           -  DST_PFScouting_AXOVLoose_v2
         100           1         +15           -           -  DST_PFScouting_AXOLoose_v2
         100           0         +15           -           -  DST_PFScouting_AXONominal_v4
         100           0         +14           -           -  DST_PFScouting_AXOTight_v4
         100           0          +6           -           -  DST_PFScouting_AXOVTight_v2
         100           0          +6           -           -  HLT_L1AXOVTight_v2

IIUC, this must come from the updated L1T menu. @caruta please confirm.

[caruta]

As expected, no effect on the outputs of the current workflows because of the modified L1 menu: the HLT menu that uses the new seeds is not yet included in those workflows

In the trigger results changes I see:

      Events    Accepted      Gained        Lost       Other  Trigger
         100           2         +18          -1           -  DST_PFScouting_AXOVLoose_v2
         100           1         +15           -           -  DST_PFScouting_AXOLoose_v2
         100           0         +15           -           -  DST_PFScouting_AXONominal_v4
         100           0         +14           -           -  DST_PFScouting_AXOTight_v4
         100           0          +6           -           -  DST_PFScouting_AXOVTight_v2
         100           0          +6           -           -  HLT_L1AXOVTight_v2

IIUC, this must come from the updated L1T menu. @caruta please confirm.

Hi @mmusich, indeed in the new L1T menu we have changed the NN model and thresholds for the AXO seeds, but we didn't change their name. So some differences in the HLT paths consuming these seeds (which are the ones shown here) are expected.

[perrotta]

Thank you @mmusich for the check, and @caruta for confirming that the changes are the expected ones.
Indeed, I forgot the modifications applied to the existing seeds, that were all listed here (cited in the PR description)

Therefore "+1" from alca is confirmed

[antoniovilela]

Thank you @mmusich for the check, and @caruta for confirming that the changes are the expected ones. Indeed, I forgot the modifications applied to the existing seeds, that were all listed here (cited in the PR description)

Therefore "+1" from alca is confirmed

Thanks.

[antoniovilela]

+1