-
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
Fix prodlike workflow to use DIGI instead of DIGI:pdigi_valid #33847
Fix prodlike workflow to use DIGI instead of DIGI:pdigi_valid #33847
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33847/22869
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. It involves the following packages: Configuration/PyReleaseValidation @jordan-martins, @chayanit, @wajidalikhan, @kpedro88, @cmsbuild, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please test |
@srimanob this was a deliberate choice to match the Phase 2 production campaigns which also use DIGI:pdigi_valid, e.g. https://twiki.cern.ch/twiki/bin/view/CMS/Phase2HLTTDRWinter20DR |
d = merge([stepDict[self.getStepName(step)][k]]) | ||
tmpsteps = [] | ||
for s in d["-s"].split(","): | ||
if s == "DIGI:pdigi_valid" in s: |
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.
I don't think this condition is correct
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.
Hmm.. Could you please guide? I get -s DIGI,DATAMIX,L1TrackTrigger,L1,DIGI2RAW,HLT:@fake2
as expected.
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.
Either if s == "DIGI:pdigi_valid"
or if "DIGI:pdigi_valid" in s
would potentially make sense. Right now, this is comparing a string to a bool at some point.
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, Fixed.
I understand that was a (my) mistake in the campaign setting. I think we should keep the proper cmsDriver, and no clue on the need of pdigi_valid in the production (with MC truth information). Is it really need for Phase-2 currently? |
There are a number of Phase 2 customizations in cmssw/SimGeneral/MixingModule/python/digitizers_cfi.py Lines 102 to 127 in 6d2f660
|
OK, thanks. I will look into it. |
-1 Failed Tests: RelVals RelVals |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-61760c/15411/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+1 I think, that saving of MC truth volume for HGCal is necessary. |
+Upgrade Plan to backport to 11_3. |
@cms-sw/pdmv-l2 do you have any comment? |
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@@ -104,10 +106,9 @@ | |||
|
|||
from Configuration.ProcessModifiers.run3_ecalclustering_cff import run3_ecalclustering | |||
(run3_ecalclustering | phase2_hgcal).toModify( theDigitizersValid, |
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.
this could just be run3_ecalclustering
now (phase2_hgcal
modification is now redundant)
@@ -104,10 +106,9 @@ | |||
|
|||
from Configuration.ProcessModifiers.run3_ecalclustering_cff import run3_ecalclustering | |||
(run3_ecalclustering | phase2_hgcal).toModify( theDigitizersValid, | |||
calotruth = cms.PSet( caloParticles ) ) # Doesn't HGCal need these also without validation? | |||
calotruth = cms.PSet( caloParticles ) ) | |||
(premix_stage2 & phase2_hgcal).toModify(theDigitizersValid, calotruth = dict(premixStage1 = True)) |
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.
this line is also now redundant with the above changes
(premix_stage2 & phase2_hgcal).toModify(theDigitizersValid, calotruth = dict(premixStage1 = True)) | ||
|
||
|
||
phase2_timing.toModify( theDigitizersValid.mergedtruth, |
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.
should check with @cms-sw/mtd-dpg-l2 if this behavior is needed for non-pdigi_valid workflow
Thanks @kpedro88 |
@srimanob @kpedro88 MC Truth is needed for vertex validation, so for any study concerning quality of vertices its presence should be welcome. We are not normally running these studies on large production samples to my knowledge, for smaller test production I believe one should define the target of the test to decide. |
Thanks @fabiocos, I propose to keep it for pdigi_valid only, as it is, then. |
PR description:
Currently, Phase-2 prod-like workflow uses DIGI:pdigi_valid instead of DIGI. This PR is to make a clear cut between production and relvals with DIGI and DIGI:pdigi_valid respectively. To run in production mode, we need to adapt
digitizers_cfi.py
to include Calo MCTruth for HGCAL in DIGI.No change is expected for relvals as pdigi_valid will be used as before. The change is only the size of events in production mode. With PU200 ttbar, it can save more than 30MB/events as MergeTrackTruth will not be stored.
PR validation:
Get proper cmsDriver(s) when use
runTheMatrix.py --what upgrade -l 23234.0,23234.21,23434.21,23434.9921 --dryRun
if this PR is a backport please specify the original PR and why you need to backport that PR:
Not a backport, and no need for backport