-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Update Phase2 MC GT to clean up unused Phase1 pixel conditions #42794
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42794/36906
|
A new Pull Request was created by @saumyaphor4252 (Saumya Phor) for master. It involves the following packages:
@perrotta, @cmsbuild, @consuegs, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Expand to see more relval errors ...Comparison SummarySummary:
|
failures in run3 fast-sim look spurious... |
@cmsbuild, please test
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d917f7/34786/summary.html Comparison SummarySummary:
|
+alca
|
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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
Did this PR cause
|
Another test
|
I fail to see how can that be related (i.e. why it should use a Phase-2 GT, the only thing changed here...) |
That test was also failing before this PR was merged. |
that makes more sense. Thank you. |
hopefully #42826 should fix the unit tests failures. |
in addition there are three failing relval workflows in IB: https://cmssdt.cern.ch/SDT/html/cmssdt-ib/#/relVal/CMSSW_13_3/2023-09-19-2300?selectedArchs=el8_amd64_gcc11&selectedFlavors=X&selectedStatus=failed:
All failing with:
|
Uhm, weird... |
we definitely should NOT run the phase-1 Pixel RawToDigi in a Phase-2 workflow. runTheMatrix should be patched in order to not run the pixel unpacker in phase2. |
runTheMatrix is just executing the workflows as they're written. Perhaps something in https://github.com/cms-sw/cmssw/blob/master/SimGeneral/MixingModule/python/pixelDigitizer_cfi.py or https://github.com/cms-sw/cmssw/blob/master/SimGeneral/MixingModule/python/SiPixelSimParameters_cfi.py needs to be changed for phase 1 vs. phase 2 (using appropriate Eras). Probably worth posting a dedicated issue for this. |
the unpacker has absolutely nothing to do with simulation (as you seem to imply, which I find quite worrisome). It's actually used in reconstruction. cmssw/Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py Lines 399 to 403 in df70e9e
the issue is in runTheMatrix and nowhere else! |
Apologies, I just misread the comment. Indeed, pixel RawToDigi is already excluded in cmssw/Configuration/StandardSequences/python/RawToDigi_cff.py Lines 89 to 92 in df70e9e
|
I guess we could make this line
an empty sequence with an era modifier (waiting to have a real phase-2 pixel unpacker) |
Yes, I'm just now preparing a PR with that change. |
@mmusich what about adding a line phase2_tracker.toReplaceWith(siPixelDigisTask, cms.Task()) in EventFilter/SiPixelRawToDigi/python/siPixelDigis_cff.py? It seems to me the right place where to apply the modification, and easier to revert when we'll have a real phase-2 pixel unpacker. By the way, I checked that it actually fixes the now failing workflows |
isn't this exactly what I suggested at: #42794 (comment)
also, I am afraid it does not... |
Well, you were suggesting to replace it in Configuration/StandardSequences/python/RawToDigi_cff.py, I am suggesting instead to modify it directly in siPixelDigis_cff.py
I succesfully run step3 of wf 24834.5 with it... |
try the ones with the |
for the record, #42830 solves. We can discuss if we instead we want to go #42794 (comment) (I need to ponder a bit pros and cons) |
I think the advantage of #42794 (comment) is that it avoids the need to remove |
Well, for siStrip the situation is different: it will not be there in Phase 2. I would suggest to empty the siPixelDigisTask in siPixelDigis_cff.py (with the intent to have it back in at some time) but keep removing the siStripDigis from RawToDigi_cff.py, as it is done now, because they are not supposed to get back. |
I agree with this assessment, that's why I originally remove it from the raw2digi in 1647c50
I couldn't think of adverse effects, hence that's what's currently implemented in #42830 |
PR description:
This is a follow-up on cms-AlCaDB/AlCaTools#88.
With #42612 now merged, we have updated and cut the official versioned Phase2 GT
132X_mcRun4_realistic_v1
that removes the following currently unused Phase-1 pixel conditions:The difference between the new GT from the last one is here:
PR validation:
Successfully tested locally with
runTheMatrix.py -l 22034.0, 23234.0, 24834.0 -j 8 --ibeos
which consumes theauto:phase2_realistic
keyIf 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:
Not a backport. Clean-up for future GTs, so no backport is expected so far.