-
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
PPS: adding missing IO rule for class TotemRPUVPattern #31075
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31075/17600
|
A new Pull Request was created by @jan-kaspar for master. It involves the following packages: DataFormats/CTPPSReco @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@jan-kaspar @forthommel : the UL release cycle 10_6 still uses ClassVersion 2, and therefore no backport is needed. Do you think a backport to 11_1 can be useful? I.e., do you foresee any usage in the Phase2 HLT-TDR related samples (produced with V2 and readout in 11_1 with V3) and/or MWGRs? I don't think so, but please confirm. |
PPS doesn't plan on using strip RPs (related to the class in question) in the future (except special runs). Therefore all the studies I can imagine would be related to Run2 data where 10_6 can be used. Consequently, I don't think we need a backport to 11_1. |
+1 |
PR description:
#28252 renamed data members of class
TotemRPUVPattern
. It provided IO rules for backward compatibility with previously created ROOT files. Unfortunately, an IO rule forprojection
data member was missing. The present PR adds this missing PR.PR validation
This PR was tested with a UL AOD file (created with 10_6 which doesn't have the class members renamed). Before applying the proposed change, the method
TotemRPUVPattern::projection()
returns 0 (invalid). With the proposed changes, the method returns 1 or 2, as expected.