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
Separate Algorithms for GE0 and GE1/1 GE2/1 Segments #32972
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32972/21210
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-32972/21211
|
A new Pull Request was created by @watson-ij (Ian J. Watson) for master. It involves the following packages: RecoLocalMuon/GEMSegment @perrotta, @kpedro88, @cmsbuild, @srimanob, @slava77, @jpata can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please test |
@watson-ij This is to complete the documentation for the PR. Thanks. |
@seulgi324, do you have a link to a presentation showing the difference? |
GEMSegments aren't currently tracked by DQM, so they won't show up directly, but it could have an impact on the muons. We saw that the default algorithm produces a lot of segments with only a few rechits, whereas the RU algorithm requires at least 4. The RU algorithm is also finding more segments with 6 rechits as is nominal for ME0. |
|
||
// Ask factory to build this algorithm, giving it appropriate ParameterSet | ||
algo = GEMSegmentBuilderPluginFactory::get()->create(algoName, segAlgoPSet); | ||
segAlgo = GEMSegmentBuilderPluginFactory::get()->create(segAlgoName, segAlgoPSet); | ||
// Ask factory to build this algorithm, giving it appropriate ParameterSet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having twice the same comment is probably redundant...
If you remove one, then in the other one: "this algorithm, giving it" -> "these algorithms, giving them"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, updated
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32972/21218
|
Please test |
To complete this: @seulgi324 gave a talk today showing the rechit distribution differences between the default and RU algorithms, in particular, showing the increase in 6-hit segments I mentioned earlier. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-86221f/13049/summary.html Comparison SummarySummary:
|
The RU segment builder is implemented for the GE0, instead of the GEMSegmentAlgorithm which is used for all other GEM stations. The RU segment builder is what was originally implemented for ME0, and the GEMSegmentAlgorithm replaced it for GE0 in previous #31480: but it turned out to be sub-optimal for the GE0 station (something which was already possibly anticipated in the comments of #31480). In the presentation at the GEM DPG linked here differences (expected) are reported for the number of segments and recHits. These differences cannot likely be noticed in the low stat Phase2 validations available in the automatic PR tests because of the low statistics: it looks like that they are however endorsed by the GEM DPG, something which was already possibly anticipated in the comments of #31480. As such, the PR could be considered suitable for being integrated in CMSSW. At page 6 of the same presentation there is however a note about "an issue with ME0": could you please elaborate further about it, and specify with some more detail what such an "issue" is, and whether you plan/need to fix it already in this PR? |
@perrotta, the issue referred to there was that the ME0 RecHit algorithm never implemented clustering, so that we have a rechit for every digi rather than clustering the contiguous digis into a single rechit, causing duplicate segments. This is already fixed for GE0 by virtue of the fact that the GEMRecHit algorithm includes a clusterizer, so GE0 digis are also clustered so we don't get unnecessary duplicates. |
+1
|
do you have any comments @cms-sw/upgrade-l2 ? |
+Upgrade |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
For ME0, the RU segment builder was default while GEMSegmentAlgorithm is used for the other GEM stations. This PR allows separate GE0 and other GEM algorithms, and defaults GE0 to use the RU algorithm, and GE1/1 / GE2/1 to use the GEMSegmentAlgorithm, as is the default for the ME0/GEM setup.
@jshlee
PR validation:
We checked the performance of the GE0 RU algorithm and found it to work as for ME0. I also ran runTheMatrix with workflow 34621.0 and confirmed that both station 0 and 1/2 segments are being created properly.
if this PR is a backport please specify the original PR and why you need to backport that PR:
Before submitting your pull requests, make sure you followed this checklist: