-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
new package L1Trigger/L1TMuonOverlapPhase1 (new version of the L1 Trigger Overlap Muon Track Finder (OMTF) emulator) #35111
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35111/25002
|
A new Pull Request was created by @kbunkow for master. It involves the following packages:
The following packages do not have a category, yet: L1Trigger/L1TMuonOverlapPhase1 @malbouis, @andrius-k, @yuanchao, @kmaeshima, @ErnestaP, @ahmad3213, @rvenditti, @cmsbuild, @rekovic, @jfernan2, @ggovi, @francescobrivio, @cecilecaillol, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Hi @kbunkow please change the title to something that's more descriptive of what's in the PR. Also can you please squash the commits into fewer commits? (For example "a small fix", "changes from scram build code-format", etc could go into one commit, and so on) |
8a422fe
to
6876446
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35111/25022
|
Pull request #35111 was updated. @malbouis, @andrius-k, @yuanchao, @kmaeshima, @ErnestaP, @ahmad3213, @rvenditti, @cmsbuild, @rekovic, @jfernan2, @ggovi, @francescobrivio, @cecilecaillol, @tvami can you please check and sign again. |
Hi @tvami |
test parameters: |
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b76fe9/18905/summary.html Comparison SummarySummary:
|
+1 |
+1 |
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@kbunkow could you please provide some ETA for the full replacement of the OMTF emulator? IOW, when do you plan to fully remove from CMSSW the old one, now replaced by this L1TMuonOverlapPhase1? Supposing this PR enters in pre4, could the removal of the old code be already made effective within the following pre5 (last open pre)? @jfernan2 could you please confirm that the differences visible in the L1ETMU DQM plots are compatible with the replacement of the old emulator with the new one? In particular, why so many more entries in the summary plots (9/2 times the ones that were there with the old emulator)? |
I am afraid I don't know the answer, sorry. I understand the number of entries are improved by the new emulator, @kbunkow any explanation? |
Regarding the ETA for the full replacement of the OMTF emulator: if old (L1TMuonOverlap) and new (L1TMuonOverlapPhase1) versions of the emulator are both in at least one pre-release (let’s say CMSSW_12_1_0_pre4) then it is OK for us. So we have nothing against removing the L1TMuonOverlap from the next pre-release (e.g. pre5). However, it would be good if @rekovic commented if there are no other constraints.
Regarding the differences in the DQM: |
+1
|
PR description:
This PR contains a new version of the L1 Trigger Overlap Muon Track Finder (OMTF) emulator: L1Trigger/L1TMuonOverlapPhase1. It should replace the current OMTF emulator L1Trigger/L1TMuonOverlap. The changes in the codes are so significant that we decided to create the new package (L1TMuonOverlapPhase1) rather than updating the old one (L1TMuonOverlap). At some point, L1TMuonOverlap can be removed from the CMSSW (for the moment keeping both packages allows comparing the results easily) .
The OMTF algorithm for the Run3 was significantly improved, these improvements decrease the rate while keeping slightly higher efficiency than the Run2 algorithm.
The L1TMuonOverlapPhase1 can emulate properly the OMTF firmware version with the above-mentioned improvements (this firmware is already deployed in the P5 and was used during the CRUZET).
Additionally, L1TMuonOverlapPhase1 emulates properly the Run2 OMTF firmware – the data-to-emulator agreement on the 2018D data is slightly better for the L1TMuonOverlapPhase1 than for the L1TMuonOverlap.
Besides the new package there are also changes in the CondFormats needed to configure the OMTF emulator:
CondFormats/L1TObjects/interface/L1TMuonOverlapParams.h
There is one more parameter added in the L1TMuonOverlapParams, which is needed for Run3 OMTF algorithm. This change is fully backward compatible, i.e. both L1TMuonOverlapPhase1 and L1TMuonOverlap work correctly with the Run2 records which don’t have this new parameter.
L1TMuonOverlapParams record for the Run3 OMTF algorithm is not yet in the database, if needed the L1TMuonOverlapPhase1 can be configured to emulate the Run3 algorithm with the use of the L1Trigger/L1TMuonOverlapPhase1/python/fakeOmtfParams_cff.py
These two files are also updated:
DQM/L1TMonitor/python/L1TStage2Emulator_cff.py
and
L1Trigger/L1TMuon/python/simDigis_cff.py
in both cases switching to use the new emulator i.e. L1Trigger.L1TMuonOverlapPhase1.simOmtfDigis_cfi
PR validation:
I run the recommended test:
runTheMatrix.py -l limited -i all –ibeos
and the result is:
39 38 37 28 18 4 1 1 1 tests passed, 0 0 0 0 0 0 0 0 0 failed
Also, I run the DQM data-to-emulator comparison (cmsRun DQM/Integration/python/clients/l1tstage2emulator_dqm_sourceclient-live_cfg.py with) for a few data files. Both for the recent cosmic run in which the updated OMTF firmware was used, and for the 2018D collision data the data-to-emulator disagreements are at the level of 1%, so similar (or slightly less) than in the case of the old emulator L1TMuonOverlap. The reasons for the disagreements are understood (and unfortunately are very difficult to fix).
if this PR is a backport please specify the original PR and why you need to backport that PR:
This PR is not a backport