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
L1T: remove l1ExtraParticles from stage 2 reco #36916
Conversation
urgent |
type bug-fix |
@cmsbuild , please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36916/28225
|
A new Pull Request was created by @bundocka for master. It involves the following packages:
@epalencia, @rekovic, @cecilecaillol can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-1 Failed Tests: RelVals RelVals
|
|
Sorry I was probably wrong, I guess the l1extraparticles somehow propagate to the HLTriggerOfflineExotica in the MC @bundocka I think what you need to do is to have the Run-3 era connected to this change, so it will be kept for the MC (if it's really used there -- if not, please change the MC code so it doesnt consume it) |
# | ||
from Configuration.Eras.Modifier_stage2L1Trigger_cff import stage2L1Trigger | ||
stage2L1Trigger.toReplaceWith(L1Reco_L1Extra,cms.Sequence()) | ||
stage2L1Trigger.toReplaceWith(L1Reco_L1Extra_L1GtRecord,cms.Sequence()) | ||
stage2L1Trigger.toReplaceWith(L1Reco, cms.Sequence(l1extraParticles)) | ||
stage2L1Trigger.toReplaceWith(L1Reco, cms.Sequence()) | ||
|
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.
stage2L1Trigger.toReplaceWith(L1Reco, cms.Sequence(l1extraParticles)) | |
from Configuration.Eras.Era_Run3_cff import Run3 | |
_L1Reco_forRun3 = L1Reco.copyAndExclude([l1extraParticles]) | |
Run3.toReplaceWith(L1Reco, _L1Reco_forRun3) |
wouldnt this work?
Hi @bundocka |
The DQM code of the HLT needs to be reviewed and updated. (this solves the crash in 12434.0 , I'm currently checking the other wfs) |
…Stage 1 L1CaloGeometry record
Thanks, @silviodonato for reviewing |
@cms-sw/l1-l2 |
Yes, the original issue was that this was going to be the only non-DD4HEP tag. Since apparently it's "not consumed" while it's consumed (I dont really understand what was happening in On the other hand |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6054b0/22330/summary.html Comparison SummarySummary:
|
Maybe I don't fully understand the issue of cpu-time we spend in the wrong sequence here. Is this documented somewhere? If it is not a big deal, I would propose we do this in the moment that we understand better the situation of L1T development. In addition to Carl's comment, the tag is neither DDD nor DD4hep. It should not be counted as DD4hep migration. |
Dear all, we have stopped the building of 12_2_1 because we were asked to wait for this PR. |
My opinion is that since this PR finally converged we should merge it, but it's not under AlCa signature so kindly pinging @cms-sw/dqm-l2 @cms-sw/l1-l2 |
+1 |
+l1 |
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) |
Hi, All, since it's already there, we should merge it. This will allow us to process the entire 0.5B events as a step chain, so this will be much more efficient, if we can get it to work. Considering the geometry (including DD4HEP) migration was also really "due" last fall, it's beyond time to get it in. |
+1
|
I don't understand why you say that we can't run stepchain without this PR. This part is under L1Reco where we do stepchain since Run-2. No? |
Fix addressing #36806 #36806
Removes l1ExtraParticles from Stage 2 L1T reconstruction, which should not be included for Stage 2 (only Stage 1).
Tested with:
runTheMatrix.py --what standard -l 138.4 --command "--conditions 123X_dataRun3_Prompt_dd4hep_Candidate_2022_02_07_15_17_27 -n 1000" -t 8
No longer see error:
"No "L1CaloGeometryRecord" record found in the EventSetup."
since the l1ExtraParticles producer that asks for this record is no longer called in the Stage 2 L1T reco.