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] Timing calibration for diamond rechits/tracks #26327
[PPS] Timing calibration for diamond rechits/tracks #26327
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26327/9224
|
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR modifies the rechits producer for PPS diamond detectors to insert the calibrated hit time of arrival, and propagates this information onto a general track time, following the same recipe as introduced #25465 for TOTEM vertical timing detectors.
As most of the algorithmic part is common, the overall track-from-hits timing extraction method is moved to the base class.
The calibration objects are also shared between the two reconstruction codes, introduced in #25777 (with ESSource modified in #26207 for diamond calibration files parsing).
This track timing information is propagated (with no code change) up to the
CTPPSLocalTrackLite
miniAOD-optimised object.PR validation:
runTheMatrix.py -l limited
test ongoing.Warning as no GT is currently holding the diamond timing calibration for all periods defined in 2017-18, it its current state, this PR should return an uncorrected (thus unmodified) rechits collection.
if this PR is a backport please specify the original PR:
Before submitting your pull requests, make sure you followed this checklist: