-
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
[12.4.X] New high granularity pixel alignment for the PCL #38497
[12.4.X] New high granularity pixel alignment for the PCL #38497
Conversation
Add HG(LG) PCL alignment to 1001.2 workflow add relval customization to override the 20 LS window for the Alignment PCL workflows Fix entries in HG PCL alignment and change entries in relval customizer Restructure and clean configs for HG PCL alignment Use PixelTopologyMap for indexing alignables and booking histograms in HG PCL alignment Rename TrackerAlignmenRcd and update DropBoxMetadata and testPCLAlCaHarvesting for HG PCL alignment Fix testCalibrationTkAlCaRecoProducers and use clone instead of deepcopy for HG PCL alignment Don't use indexing helper for LG PCL alignment Fix HG alignment threshold logic when using new threshold payload Configurable tracker alignment record for HG PCL alignment
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_4_X. It involves the following packages:
@perrotta, @malbouis, @yuanchao, @jordan-martins, @bbilin, @tvami, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @ggovi, @qliphy, @francescobrivio, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type new-feature,trk |
test parameters:
|
urgent
|
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-547554/25769/summary.html Comparison SummaryThe workflows 1001.2 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons @slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+1 |
Pull request #38497 was updated. @perrotta, @malbouis, @yuanchao, @jordan-martins, @bbilin, @tvami, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @ggovi, @qliphy, @francescobrivio, @fabiocos, @davidlange6 can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-547554/25800/summary.html Comparison SummarySummary:
|
+1
|
+pdmv |
+Upgrade Backport |
@cms-sw/orp-l2 we are essentially fully signed for this PR |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. This pull request will be automatically merged. |
backport of #38449 and #38508
PR description:
This is the last PR towards using a higher granularity (HG) for the pixel alignment in the PCL, following #38371. It is planned to run the HG alignment in parallel to the LG alignment, with only the LG alignment updating the conditions. More details can also be found in [1].
In detail the following things are changed/added in this PR:
MillePedeFileReader
andMillePedeDQMModule
to read and store the high granularity alignmentMillePedeDQMModule
andMillePedeAlignmentAlgorithm
pede
results for the HG alignment in/from a separate folder, to avoid overwriting the LG result in the harvesting step.CommonAlignmentProducer
runTheMatrix.py
command* Add a relval customizer in
CommonAlignmentProducer
to override the 20 LS veto and required entries per structure in the HG aligmentPR validation:
The PR can be tested using the adapted relval workflow with
runTheMatrix.py -l 1001.2
.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:
verbatim backport of #38449 and #38508. As explained in the description it's needed for deplyoment of the new workflow in the 2022 high intensity data-taking.
cc:
@dmeuser, @connorpa, @antoniovagnerini, @consuegs
[1] https://indico.cern.ch/event/1167313/contributions/4906905/attachments/2461217/4219804/AlCaDB_Meeting_13_06_22.pdf