-
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
MonitorTrackResiduals
: do not apply PV compatibility cut when running cosmics [12.0.X]
#35812
MonitorTrackResiduals
: do not apply PV compatibility cut when running cosmics [12.0.X]
#35812
Conversation
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_0_X. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
type bug-fix |
urgent
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be5abf/19877/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
test parameters:
|
please test |
73a5a16
to
610fecf
Compare
Pull request #35812 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be5abf/19885/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
Is there any further concern on this PR? Please let me know, thank you! |
Not really: just waiting for the IB tests results in CMSSW_12_1_X_2021-10-25-2300, as a last check (as usual) |
+1
|
backport of #35811
PR description:
I was casually looking at the Strip residuals in a CRAFT 2021 run but they don't make much sense e.g. the number of hits in TIB1 (https://tinyurl.com/yzwdcdc6) is less than BPIX1 (https://tinyurl.com/ygftohy4).
Also the Strip EndCap residuals plots are empty (https://tinyurl.com/ygxqol8b).
I strongly suspect this is due to the Primary Vertex compatibility cut at:
cmssw/DQM/TrackerMonitorTrack/src/MonitorTrackResiduals.cc
Line 251 in 6d2f660
that makes no sense in cosmic data-taking and is severely limiting the phase-space from which the cosmic tracks are considered (https://tinyurl.com/yjzgap6c)
The correct behavior is implemented instead in the Pixel residuals code:
cmssw/DQM/SiPixelPhase1Track/plugins/SiPixelPhase1TrackResiduals.cc
Lines 80 to 82 in c6d0025
in which the PV compatibility cut is put in OR with a switch that is set to false in cosmics (and indeed the pixel residuals in cosmic runs are filled).
This PR implements the same mechanism also for Strip residuals.
No regression is expected for collision runs (pp or HI).
PR validation:
I've run workflow 138.2 (from 2021 cosmics commissioning, Run 343498) with 1000 events:
runTheMatrix.py -l 138.2 -j 8 --command='-n 1000'
if this PR is a backport please specify the original PR and why you need to backport that PR:
backport of #35811