-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 [10_6_X] #28989
Use correct beamspot for 2016 MC + update MC tracker alignment scenario for 2016 pre-VFP era [10_6_X] #28989
Conversation
…n for 10_6_X branch
A new Pull Request was created by @christopheralanwest for CMSSW_10_6_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 |
backport #28624 |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
+1 |
+upgrade |
+1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR is a backport of PR #28624, which changes the default beamspot for 2016 scenarios and updates the tracker APEs for MC of the 2016 pre-VFP era. Commits 5d50378 and
e514a31 are cherry-picked from the PR to master. The 10_6_X branch requires an additional two changes of the beamspot scenario, in commit 662b68c. Finally, the global tags are updated in commit 5ea966a. The changes to the GTs can be understood by comparing the diffs with respect to the previous 10_6_X autoCond GTs or by comparison with those in master.
Comparison with previous 10_6_X GT
2016 design MC
Updated to use ideal beamspot
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_design_v6/106X_mcRun2_design_v7
2016 preVFP pp collision MC
Updated to use 25ns beamspot rather than 50ns beamspot. Update to tracker APEs
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_asymptotic_preVFP_v1/106X_mcRun2_asymptotic_preVFP_v3
2016 pp collision MC
Updated to use 25ns beamspot rather than 50ns beamspot.
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_asymptotic_v8/106X_mcRun2_asymptotic_v9
2016 cosmic MC
Updated to use 25ns beamspot rather than 50ns beamspot. Not relevant but change is made to minimize unnecessary differences between cosmic and pp collision GTs
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2cosmics_startup_deco_v5/106X_mcRun2cosmics_startup_deco_v6
Comparison between 10_6_X and master
2016 design MC
Only differences are in tau tags added in 11_0_X and obsolete pixel tags
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2_design_v5/106X_mcRun2_design_v7
2016 preVFP pp collision MC
Only differences are in tau tags added in 11_0_X, addition to AlCaReco bits added in 11_1_X, and obsolete pixel tags
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2_asymptotic_preVFP_v4/106X_mcRun2_asymptotic_preVFP_v3
2016 pp collision MC
Only differences are in tau tags added in 11_0_X, addition to AlCaReco bits added in 11_1_X, and obsolete pixel tags
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2_asymptotic_v7/106X_mcRun2_asymptotic_v9
2016 cosmic MC
Only differences is addition to AlCaReco bits added in 11_1_X
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2cosmics_startup_deco_v6/106X_mcRun2cosmics_startup_deco_v6
PR validation:
Please see description of PR #28624 for details of physics validation. 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 is a backport of PR #28624. The backport corresponds to the configuration that is already in use for the ultra-legacy reprocessing.