-
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
[11.1.X] Add CDC Tracks to TkAlCosmics0T ALCARECO #30014
Conversation
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_11_1_X. It involves the following packages: Alignment/CommonAlignmentProducer @andrius-k, @kmaeshima, @christopheralanwest, @schneiml, @tocheng, @cmsbuild, @silviodonato, @franzoni, @jfernan2, @fioriNTU, @tlampen, @pohsun, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
@cmsbuild, please test workflow 7.0,7.1,7.2,7.21,7.22,7.23,7.3,7.4 |
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 |
+operations |
This pull request is fully signed and it will be integrated in one of the next CMSSW_11_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #30013
PR description:
In view of upcoming work foreseen on the Cosmics During Collisions (CDC) reconstruction, we add to the regular Tracker Alignment cosmics AlcaReco
TkAlCosmics0T
these tracks in order to have them produced during standard interfill, so that these can be used as "standard candle" for reconstruction optimization.We provide also additional DQM monitoring for the newly added track collection.
PR validation:
This branch has been extensively used for privare re-recos of 2018 Data (see presentations from @skeshri here and here ) and also has gone through more technical validation via:
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 #30013. It is requested in order to be able to ask larger data re-recos with the production release.
cc:
@mtosi @connorpa @vbotta