-
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
Fix mismatch between EB and EE recHits in Phase2 supercluster producer configs #45973
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45973/41732 |
A new Pull Request was created by @RSalvatico for master. It involves the following packages:
@Martin-Grunewald, @cmsbuild, @mmusich can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
type egamma, bug-fix |
Please open a CMSHLT JIRA ticket for this. |
For the records: |
+1 Size: This PR adds an extra 40KB to repository Comparison SummarySummary:
|
+hlt
|
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. @rappoccio, @antoniovilela, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Several Phase2 HLT modules using the
PFECALSuperClusterProducer
are taking as input theEcalRecHitsEE
as barrelRecHits andEcalRecHitsEB
as endcapRecHits. These are not used in the building of the moustache supercluster, which is the only supercluster algorithm used online at the moment, also for Phase2. Nevertheless, this is still a nasty bug and could cause problems in the future - they are in fact used for example for the DNN supercluster in PFECALSuperClusterAlgo.I have not found offline modules with the same issue - I think they are all created by the fillDescription of the PFECALSuperClusterProducer, which is correct.
On the other hand, note that the modules
hltParticleFlowSuperClusterECALL1Seeded
andhltParticleFlowSuperClusterECALUnseeded
in ConfDB present the same issue and should be fixed as well.PR validation:
As explained above, I would not expect to see differences.