[16.0.X] switch off usePixelQualityFlag in TrackerTrackHitFilter in presence of the PixelCPEGeneric modifier#50619
Conversation
…f the PixelCPEGeneric modifier
usePixelQualityFlag in TrackerTrackHitFilter in presence of the PixelCPEGeneric modifierusePixelQualityFlag in TrackerTrackHitFilter in presence of the PixelCPEGeneric modifier
|
A new Pull Request was created by @mmusich for CMSSW_16_0_X. It involves the following packages:
@Alejandro1400, @JanChyczynski, @Moanwar, @arunhep, @atpathak, @cmsbuild, @ctarricone, @gabrielmscampos, @jfernan2, @mandrenguyen, @nothingface0, @perrotta, @rseidita, @srimanob, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
cms-bot internal usage |
|
test parameters:
|
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
|
|
+analysis |
|
+alca |
|
+1 |
|
+dqm |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_16_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_16_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @sextonkennedy, @ftenchini (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
backport of #50616
PR description:
This PR is a follow-up to #50480.
In that PR the default CPE for track fitting in the 2026 Era was moved to the CPE generic.
Unfortunately this has a knock-on effect on the
TrackerTrackHitFilterwhich has a flag (usePixelQualityFlag) which relies on the template fit information to do hit rejection:cmssw/RecoTracker/FinalTrackSelectors/plugins/TrackerTrackHitFilter.cc
Lines 976 to 997 in 0733146
This is of course not available when the template fit is not run.
This has lead to missing alignment PCL results (see e.g. https://cern.ch/wygsf) and potentially wrong DQM results.
PR validation:
I've re-run the following command (previously failing in
CMSSW_16_0_4_patch2):and verfied the alignment PCL works correctly.
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:
Verbatim backport of #50616 to the 2026 data-taking release.