-
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
Store track momentum at hit for PbPb UPC dEdX calibration #45446
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45446/40896 |
A new Pull Request was created by @stahlleiton for master. It involves the following packages:
@cmsbuild, @ftorrresd, @hqucms, @jfernan2, @mandrenguyen, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
2b4bb34
to
5f1453a
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45446/40897 |
Pull request #45446 was updated. @cmsbuild, @ftorrresd, @hqucms, @jfernan2, @mandrenguyen, @vlimant can you please check and sign again. |
+1 |
please abort |
please test workflow 180, 180.1, 181, 181.1, 142.901 |
+1 Size: This PR adds an extra 12KB to repository
Comparison SummarySummary:
|
+1 |
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. @sextonkennedy, @rappoccio, @antoniovilela, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
+orp |
+1 |
@mandrenguyen , I will check why bot is not recognizing your signatures |
PR description:
This PR creates a value map containing the magnitude of the track global momentum at each hit needed to perform the dEdx calibration for PbPb UPC. This value map is only produced and stored when using the run3_upc era modifier.
@mandrenguyen @sikler
PR validation:
Tested with relvals 180, 180.1, 181, 181.1 and 142.901
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: