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
More diagnostic plots for CSC trigger primitives in validation step #35329
More diagnostic plots for CSC trigger primitives in validation step #35329
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35329/25374
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-35329/25375
|
A new Pull Request was created by @dildick (Sven Dildick) for master. 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 |
-1 Failed Tests: RelVals AddOn RelVals
Expand to see more relval errors ...AddOn Tests
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35329/25414
|
Pull request #35329 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please check and sign again. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35329/25636
|
Pull request #35329 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please check and sign again. |
please test |
I was able to run WF 11634.0
quartstripbit and eighthstripbit plots were removed. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f3372e/19251/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: 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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@qliphy Can you sign off, please? |
+1 |
It seems highly likely that this change introduced a call to a thread-unsafe ROOT function which is causing jobs in the IB RelVals to fail with
|
@Dr15Jones It's not obvious to me which ROOT function is doing that. If you have an idea, let me know, and I will try to address it. |
The problem is almost certainly here cmssw/Validation/MuonHits/src/CSCSimHitMatcher.cc Lines 239 to 240 in 6d2f660
See #18370 for the resolution of the same problem. |
I will submit a fix. |
PR description:
New class to plot CSC TP position and bending resolutions in release validation. Plots are made for CLCT bending resolution, and CLCT 1/2-strip, 1/4-strip and 1/8-strip resolution. The latter two only make sense for chambers that have the CCLUT algorithm enabled (MEX/1 in the baseline commissioning model).
I also added diagnostic plots for ALCT, CLCT, CLCT pre-trigger, and LCT for each chamber type and for each endcap (sometimes we see asymmetries in the performance). I borrowed a lot of code from the L1T CSC DQM tools which I wrote earlier this year. I organized the plots by object, and by type of plot, so it's not all in one directory. The screenshot below shows the directory structure (tested on 100 1TeV muon events). Not every object has each type of plot. E.g. I don't have resolution plots for ALCTs.
This PR is part of an investigation into the EMTF performance for 1 TeV muons with Run-3 CSC trigger primitives.
PR validation:
Ran 1000 events from
/RelValSingleMuPt1000/CMSSW_12_0_0_pre4-120X_mcRun3_2021_realistic_v2-v1/GEN-SIM-DIGI-RAW
withPlots should automatically appear in
MuonCSCDigisV/CSCDigiTask/Stub/Resolution/
. I added a few examples belowif this PR is a backport please specify the original PR and why you need to backport that PR:
N.A.
Before submitting your pull requests, make sure you followed this checklist:
FYI @ptcox @AFJohan92