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
PF track propagator fix for pixel tracks #29307
PF track propagator fix for pixel tracks #29307
Conversation
…on and momentum instead of those at the outer location
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29307/14380
|
A new Pull Request was created by @hatakeyamak (Kenichi Hatakeyama) for master. It involves the following packages: RecoParticleFlow/PFTracking @perrotta, @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:
|
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, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR will fix the PF track propagator for pixel tracks for which the outer state is not defined. If the outer state is not defined, now it will use the position and momentum at the closest approach for propagation to calorimeters.
Results shown in this talk [1] is a good proof that this propagator fix does a reasonable job for patatrack pixel tracks in PF.
This PR should have no effect on PF based on full tracking (i.e. any matrix tests in jenkins).
[1] https://indico.cern.ch/event/894094/contributions/3797556/
PR validation:
Results presented in [1] may serve as validation.
Also, I made sure the that 11634.0 (TTbar_14TeV+TTbar_14TeV_TuneCP5_2021_....) runs fine.
if this PR is a backport please specify the original PR and why you need to backport that PR:
This is not a backport.
@bendavid @jsalfeld