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
[12_0_X] HCAL: switch off auxiliary M3 reconstruction fit for Run3 #35807
Conversation
A new Pull Request was created by @abdoulline (Salavat Abdullin) for CMSSW_12_0_X. It involves the following packages:
@jpata, @missirol, @cmsbuild, @Martin-Grunewald, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #35806 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d6adf3/19873/summary.html Comparison SummarySummary:
|
@@ -2654,3 +2654,6 @@ | |||
PixelCPE = cms.string('PixelCPEGeneric'), | |||
StripCPE = cms.string('StripCPEfromTrackAngle') | |||
) | |||
|
|||
from Configuration.Eras.Modifier_run3_common_cff import run3_common | |||
run3_common.toModify(hltHbhereco, algorithm = dict(useM3 = False)) |
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.
HLT does not use Eras and anway has useM3 = cms.bool( False )
so this is not needed for HLT.
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.
@Martin-Grunewald thank you for calrification, I (naively) thought this might be a kind of standalone config used for some purposes. I've removed this modification.
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.
Sorry, I see that that file (PhaseII) actually sets useM3 = True which seems nonsensical but then it has to be switched to false after all. Apologies for the confusion!
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.
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.
@Martin-Grunewald just to avoid any (more) confusion: do you suggest to bring the (just removed) customization back ?
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.
Yes, but also I want Andrea Bocci @fwyzard to clarify why in that Phase-II file useM3 = True is used.
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.
Sorry for the delay - this configuration is not used by the actual Phase-2 HLT menu (which anyway is not yet in 12.0.x/12.1.x...).
I don't know where it comes from, or if it used for anything - I guess only E/Gamma people can comment here.
@cmsbuild , please test |
@rappoccio thanks for the config file! It's all OK now (see above). |
+reconstruction
I'm signing this a bit out of order (before #35806, just in case a release is needed sooner in 12_0_X) |
+hlt
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_1_X is complete. 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) |
@slava77 indeed, we plan to refill these DQM plots ("M3" flavor, now become empty) with what will be "auxEnergy" Run3 replacement, most probably SOI+1 MAHI energy. |
urgent
|
one doesn't get to change things by hand at the tier0 - someone checked also a config created from configuration dataprocessing with this change? |
@davidlange6 (1) HCAL-related "SwitchProducerCUDA" uses a clone of properly modified config: (2) I've dumped a simple Run3 MC config (with this PR in 12_0_3) and can see that there are only useM3 = False instances... |
Hi @davidlange6 yes, understood, @germanfgv is working on how to create a new config. |
@davidlange6 I'm actually not sure on how we can produce the PSet using this patch. Our usual procedure just loads the python packages from /cvmfs/. I have generated the [1] |
I think someone just needs to use this tool
https://github.com/cms-sw/cmssw/blob/master/Configuration/DataProcessing/test/RunPromptReco.py
… On Oct 26, 2021, at 3:34 PM, Germán Felipe Giraldo Villa ***@***.***> wrote:
@davidlange6 I'm actually not sure on how we can produce the PSet using this patch. Our usual procedure just loads the python packages from /cvmfs/. I have generated the process_funcArgs.json file[1], but I'm not sure how to procede.
[1] /afs/cern.ch/user/c/cmst0/public/PausedJobs/PilotBeam/Replay/job_3665/patch35807/job/WMTaskSpace/cmsRun1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
+1
|
PR description:
M3 signal fit is an auxiliary one (MAHI is default), but it stays activated in HCAL Offline reconstruction (while swithed off since long time for HLT) and it wasn't explcitly looked at in the context of Run3 preparations and it's not used by any downstream consumers.
HCAL is now discussing to possibly use corresponding HBHERecHit member (auxEnergy) for saving next-to-trigger BX (SOI+1 in HCAL notations) energy from MAHI for LLP studies.
NB: this PR serves as a workaround for recently reported issue #35785
while (in parallel) HCAL DPG figures out what went wrong with M3 as reported here:
https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/2294.html
PR validation:
runTheMatrix.py -l limited
This PR is a backport of
#35806