-
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
Modifications to L1REPACK:FullSimTP to prevent crashes and make it more compatible with other REPACK options #45132
Modifications to L1REPACK:FullSimTP to prevent crashes and make it more compatible with other REPACK options #45132
Conversation
…. Modified the config to use unpacked muon TF inputs instead of re-emulated muon TPs.
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45132/40472
|
A new Pull Request was created by @eyigitba for master. It involves the following packages:
@antoniovilela, @davidlange6, @fabiocos, @rappoccio, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -114,7 +140,7 @@ | |||
|
|||
|
|||
SimL1EmulatorTask = cms.Task() | |||
stage2L1Trigger.toReplaceWith(SimL1EmulatorTask, cms.Task(unpackEcal,unpackHcal,unpackCSC,unpackDT,unpackRPC,unpackEmtf,unpackCsctf,unpackBmtf | |||
stage2L1Trigger.toReplaceWith(SimL1EmulatorTask, cms.Task(unpackEcal,unpackHcal,unpackCSC,unpackDT,unpackRPC,unpackGEM,unpackEmtf,unpackBmtf,unpackOmtf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small point: iiuc, GEM has its own modifier, so maybe something like the following should be done.
cmssw/Configuration/StandardSequences/python/SimL1EmulatorRepack_Full_cff.py
Lines 157 to 165 in 1e7c61e
SimL1EmulatorTask = cms.Task() | |
stage2L1Trigger.toReplaceWith(SimL1EmulatorTask, cms.Task(unpackEcal,unpackHcal,unpackCSC,unpackDT,unpackRPC,unpackRPCTwinMux,unpackTwinMux,unpackOmtf,unpackEmtf,unpackCsctf,unpackBmtf | |
,unpackTcds | |
,SimL1EmulatorCoreTask,packCaloStage2 | |
,packGmtStage2,packGtStage2,rawDataCollector)) | |
_SimL1EmulatorTaskWithGEM = SimL1EmulatorTask.copy() | |
_SimL1EmulatorTaskWithGEM.add(unpackGEM) | |
(stage2L1Trigger & run3_GEM).toReplaceWith(SimL1EmulatorTask, _SimL1EmulatorTaskWithGEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Marino. I think this makes more sense to decouple Stage-2 and Run 3. I'll change it now
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45132/40477
|
Pull request #45132 was updated. @rappoccio, @davidlange6, @cmsbuild, @fabiocos, @antoniovilela can you please check and sign again. |
Thanks for this update ! Indeed, I think it would be useful to backport it to 14_0_X. |
Thanks @missirol ! I'll make the backport now. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8ef7c7/39809/summary.html Comparison SummarySummary:
|
+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 be automatically merged. |
PR description:
This PR started as a modification to L1REPACK:FullSimTP to prevent a crash due to missing GEM unpacker. However, while going through the config I realized some outdated options which I ended up removing. This config was already modifed to work only with L1T Stage-2 options, so there was no reason to keep around CSCTF/DTTF options.
Furthermore, I am changing the config for now to use unpacked muon TF inputs instead of calling muon TP re-emulation modules. This is mostly done to bypass a problem I observe in DT TP re-emulation that causes lower rates. I kept the muon TP re-emulation options in place to allow people to switch quickly between the two options.
PR validation:
I validated by running L1REPACK:uGT and L1REPACK:FullSimTP and comparing them. There are no crashes and the final rates are comparable up to re-emulation level mismatches.
The normal CMSSW workflows are probably no enough to check this PR, otherwise the crash would have been caught before.
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:
I think we will backport this to 14_0_X in case we need to use it again in this year's data workflows. It's not urgent, so I would wait until the discussion on this PR is settled.
FYI @missirol