-
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
Use correct beamspot for 2016 MC + update MC tracker alignment scenario for 2016 pre-VFP era [11_0_X] #28824
Use correct beamspot for 2016 MC + update MC tracker alignment scenario for 2016 pre-VFP era [11_0_X] #28824
Conversation
…er represents 2015 beamspot
backport #28624 |
A new Pull Request was created by @christopheralanwest for CMSSW_11_0_X. It involves the following packages: Configuration/AlCa @pgunnell, @civanch, @chayanit, @zhenhu, @christopheralanwest, @mdhildreth, @cmsbuild, @franzoni, @tocheng, @tlampen, @pohsun, @santocch, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test workflow 7.22 |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1 |
+1 |
+1 |
+upgrade |
merge |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_11_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_1_X is complete. This pull request will be automatically merged. |
PR description:
This PR is a trivial backport of PR #28624. The updates contained in this PR will be included in the 10_6_X 2016 UL production and the changes have already been merged in master. A 10_6_X backport PR will be prepared as well.
I'm not certain that an 11_0_X backport is strictly necessary as no 2016 production campaign is planned for 11_0_X; the 10_6_X backport is more important. But since these changes will be used in both 11_1_X and 10_6_X, it seems less confusing to have the changes in 11_0_X as well. Since this PR is mainly intended for the bookkeeping of sensible default values for RelVal workflows, I will let PdmV experts decide if they want it merged in 11_0_X as well.
PR validation:
The changes have been validated within the 2016 10_6_X UL campaign: https://indico.cern.ch/event/865993/#15-tracker-on-ul-16
In addition, a technical test was performed:
runTheMatrix.py -l limited,7.22 --ibeos
if this PR is a backport please specify the original PR and why you need to backport that PR:
This PR is a backport of PR #28624.