Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[14_0_0] Backport of #44510 AXOL1TL emulator update for L1 Menu parsing with UTMv12 #44511

Merged
merged 2 commits into from
Mar 28, 2024

Conversation

artlbv
Copy link
Contributor

@artlbv artlbv commented Mar 22, 2024

PR description:

This is a backport of #44510 needed for the AXOL1TL L1 emulator to be compatible with the new and old UTM grammar for the seed and model selection. The description below is copied from the above PR.

This PR is an amendment of the AXOL1TL emulator PRs: #44054 (original backport: #44397).
Essentially reverting and extending the AXO-only part of this revert: #44466

The main changes are:

  • As the original PR, this introduces compatibility with the new UTM "grammar" (v12) for the AXO seed, i.e. what is used in the L1Menu_Collisions2024_v1_1_0 (see the AXO seeds in that menu here.
  • New: Added backward compatibility with the previous UTM "grammar" (pre v12) for the AXO seed, i.e. what is used in the L1Menu_Collisions2024_v1_0_0 (see the AXO seeds in that menu here). Note that UTM v12 supports the old and new AXO condition type.
    For this kind of seeds the AXO model is hard-coded to the v3 version as this is currently the baseline.
  • New: cleaned up the AXO model setting in the L1GlobalProducer/Board code as the model version is not defined globally anymore, but on the seed level.

No additional PRs are needed to test this PR.

PR validation:

I tested this PR in 14_1 (and 14_0) with the following command with the default 1_0_0 L1 menu (old UTM), but also with 1_1_0 (new UTM for AXO) and a menu where I mix both old and new AXO conditions. Note this is inspired by the workflow 141.044_RunJetMET2023D but faster for testing.

Rerunning L1 and HLT with the default L1 Menu 1_0_0:

cmsDriver.py repackuGT_reHLT -s L1REPACK:Full,HLT:@relval2024 --process reHLT --datatier NANOAOD --eventcontent NANOAOD \
-n 100 --era=Run3 \            
--data --conditions=auto:run3_hlt_relval  \
--filein=/store/data/Run2023D/JetMET0/RAW/v1/000/369/978/00000/00b9eba7-c847-465b-a6de-98bceae93613.root

Rerunning L1 and HLT with the 1_0_1 L1 Menu by specifying it via:

--customise=L1Trigger/Configuration/customiseUtils.L1TGlobalMenuXML

In all cases L1 and HLT properly ran. Note though that given the current HLS4ML issues (see #44435), the AXO seeds fire in all events in the current master.
This can be circumvented by adding this to the config (removing the CICADA emulator from the L1 chain):

process.SimL1Emulator.remove(process.simCaloStage2Layer1Summary)

The results are in line with what is expected:

../repackuGT_reHLT_L1_101_L1REPACK_HLT.root
Trigs for 100 events:
DST_PFScouting_AXONominal    100
DST_PFScouting_AXOTight      100
HLT_L1AXOVTight              100
dtype: int64
../repackuGT_reHLT_L1_101_L1REPACK_HLT_noCICADA.root
Trigs for 100 events:
DST_PFScouting_AXONominal    0
DST_PFScouting_AXOTight      0
HLT_L1AXOVTight              0
dtype: int64
../repackuGT_reHLT_def_L1REPACK_HLT.root
Trigs for 100 events:
DST_PFScouting_AXONominal    100
DST_PFScouting_AXOTight      100
HLT_L1AXOVTight              100
dtype: int64
../repackuGT_reHLT_def_L1REPACK_HLT_noCICADA.root
Trigs for 100 events:
DST_PFScouting_AXONominal    2
DST_PFScouting_AXOTight      1
HLT_L1AXOVTight              0

The results for L1 were checked with the L1 menu ntuples and show agreement for using different UTM grammar within the same XML:

141 L1ReEmu
seed                	unp	emu	mism
L1_AXO_Nominal      	0	2	2
L1_AXO_Tight        	0	1	1
L1_AXO_VLoose       	0	11	11
L1_AXO_VLooseNewUTMv3	0	11	11
L1_AXO_VTight       	0	0	0

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:

Original PR: #44510

Reason for backport: add compatibility for the AXOL1TL emulator with the new UTM grammar which is required for proper O2O of the L1 conditions. Needed in CMSSW_14_0_X for the initial data-taking in 2024.

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 22, 2024

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

It involves the following packages:

  • HLTrigger/Configuration (hlt)
  • L1Trigger/L1TGlobal (l1)

@mmusich, @epalencia, @aloeliger, @Martin-Grunewald, @cmsbuild can you please review it and eventually sign? Thanks.
@silviodonato, @missirol, @Martin-Grunewald 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

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 22, 2024

cms-bot internal usage

@cmsbuild
Copy link
Contributor

Pull request #44511 was updated. @epalencia, @mmusich, @Martin-Grunewald, @aloeliger, @cmsbuild can you please check and sign again.

@epalencia
Copy link
Contributor

Please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ccb314/38345/summary.html
COMMIT: a888655
CMSSW: CMSSW_14_0_X_2024-03-21-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/44511/38345/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

@artlbv
Copy link
Contributor Author

artlbv commented Mar 23, 2024

Backport of #44510

@artlbv
Copy link
Contributor Author

artlbv commented Mar 23, 2024

@epalencia
Copy link
Contributor

Please test

@mmusich
Copy link
Contributor

mmusich commented Mar 25, 2024

@cmsbuild, please abort

@mmusich
Copy link
Contributor

mmusich commented Mar 25, 2024

test parameters:

@mmusich
Copy link
Contributor

mmusich commented Mar 25, 2024

@artlbv, please squash the commits

@artlbv
Copy link
Contributor Author

artlbv commented Mar 25, 2024

I will update/squash the commits after the tests are done and the main PR review is done to avoid duplication.

@mmusich
Copy link
Contributor

mmusich commented Mar 26, 2024

allow @artlbv test rights

@mmusich
Copy link
Contributor

mmusich commented Mar 26, 2024

@cmsbuild, please test

@artlbv
Copy link
Contributor Author

artlbv commented Mar 26, 2024

@mmusich do we still want to test this with the externals? (the backports are not merged yet, though the results will not change in 14_0)

@mmusich
Copy link
Contributor

mmusich commented Mar 26, 2024

do we still want to test this with the externals?

yes and we are: #44511 (comment)

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ccb314/38424/summary.html
COMMIT: 948a910
CMSSW: CMSSW_14_0_X_2024-03-26-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/44511/38424/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

@aloeliger
Copy link
Contributor

+l1

  • PR to main branch already signed.

@aloeliger
Copy link
Contributor

Actually, @artlbv before I get ahead of myself, did this have the extra string removed? I'm on my phone right now and it's not easy to check.

@aloeliger
Copy link
Contributor

Actually, @artlbv before I get ahead of myself, did this have the extra string removed? I'm on my phone right now and it's not easy to check.

Ahh. Looks like it. Sorry for the noise.

@artlbv
Copy link
Contributor Author

artlbv commented Mar 26, 2024

@Martin-Grunewald
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

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

@antoniovilela
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 5bb82a5 into cms-sw:CMSSW_14_0_X Mar 28, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants