-
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
Fix SiPixel Layer 1 efficiency calculation #37778
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37778/29678
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37778/29681
|
A new Pull Request was created by @tsusa (Tatjana Susa) for master. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d01c91/24414/summary.html Comparison SummarySummary:
|
@tsusa can you change the title to reflect this targets SiPixel? |
+1 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d01c91/24490/summary.html Comparison SummarySummary:
|
@tsusa could you please confirm that the differences reported in the PR tests after the last changes are still the ones expected? |
@perrotta the changes in pixel plots are the same as before the last commit (see for example the changes in the plots that you pointed out https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_4_X_2022-05-03-1100+d01c91/50016/11634.911_TTbar_14TeV+2021_DD4hep+TTbar_14TeV_TuneCP5_GenSim+Digi+RecoNano+HARVESTNano+ALCA/PixelPhase1_Tracks_PXBarrel_Shell_pO_PXLayer_1.html) There are two additional failed wf (10224.0 and 312.0) after the last commit (not present before) but the differences come from the MessageLogger. |
+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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
type trk |
type bug-fix |
@mmusich @tsusa this is DQM, and therefore I see no counterindication in backporting it in 12_3. If you think that it can be useful to monitor the first part of this year data taking, feel free to prepare a backport PR |
here it is: #37859 |
PR description:
Following #35058 a few fixes/changes in L1 efficiency calculation/hit classification are introduced: reject TrajectoryMeasurements w/o pixel hit, fix min.distance calculation and filling of the inactive hits, initialize valid/missing/passcuts_hit for each loop iteration.
Changes expected in L1 efficiency and hit classification.
PR validation:
Matrix run, no issue.