-
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
SiStripClusters2ApproxClusters
: run peakFilter
only if cluster is usable
#42486
Conversation
type bug-fix |
Cc: @Ksavva1021 |
test parameters:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42486/36492
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@cmsbuild, @mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test for CMSSW_13_3_DBG_X |
concerning the HeaderConsistency failure reported by the cms-bot: I believe it's not coming from this PR (see log) |
so analyzing the output of the bot tests:
I am going to relaunch the tests with the regular build to get rid of the failures. |
@cmsbuild, please test |
… is incompatible with the SiStripApproximateClusterCollection in cms-sw#42486
-1 Failed Tests: RelVals-INPUT RelVals-INPUTThe relvals timed out after 4 hours. Comparison SummarySummary:
|
let's try again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-db4e21/34160/summary.html 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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
… is incompatible with the SiStripApproximateClusterCollection in cms-sw#42486
… is incompatible with the SiStripApproximateClusterCollection in cms-sw#42486
…put data is incompatible with the SiStripApproximateClusterCollection in cms-sw#42486" This reverts commit e016e14.
resolves #42131
resolves #42162
PR description:
The goal of this PR is to solve the issues #42131 and #42132.
Those issues are caused because there is a condition (
SiStripNoises
) which is read off its domain from this call:cmssw/RecoTracker/PixelLowPtUtilities/interface/SlidingPeakFinder.h
Line 72 in fe01c0e
when it looks for the noise of strip n. 768 for Detid 369120277.
Having established at #42162 (comment) that for this detId (and similar modules), the strip range is from 0 to 767 (also independently, see mmusich@c1e1ca0), thus excluding possible issues with conditions, and following the line of thought that (see #42162 (comment)) a very similar code was already used in
cmssw/RecoTracker/PixelLowPtUtilities/src/StripSubClusterShapeTrajectoryFilter.cc
Line 84 in c2e865a
StripSubClusterShapeTrajectoryFilter
.I propose in this PR to follow (almost) the same prescription used in that file before running the filter, namely using the output of
ClusterShapeHitFilter::getSizes
cmssw/RecoTracker/PixelLowPtUtilities/src/StripSubClusterShapeTrajectoryFilter.cc
Lines 258 to 259 in c2e865a
and the check on the measured (and predicted) cluster widths
cmssw/RecoTracker/PixelLowPtUtilities/src/StripSubClusterShapeTrajectoryFilter.cc
Lines 265 to 267 in c2e865a
Since
ClusterShapeHitFilter::getSizes
is not called with the measured trajectory direction, but rather with an approximated direction (the line joining the BeamSpot to the cluster) I enlarge the window to encompass 2 cluster pitches rather than 1.5.PR validation:
In
CMSSW_13_3_DBG_X_2023-08-01-2300
run successfullyrunTheMatrix.py -l 140.58 --ibeos
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:
Not a backport, but to be backported to CMSSW_13_2_X.