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
Ecal cluster seed flags #28514
Ecal cluster seed flags #28514
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28514/12973
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28514/12974
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+1
|
This pull request is fully signed and it will be integrated in one of the next master IBs (but tests are reportedly failing). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
please test |
+1 the failure is independent on this PR |
merge |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
PR description:
This PR adds two related developments:
Make Seeding aware of RecHit flags while Clustering Ecal. It will allow for example for seeding to avoid recovered channels, allowing to validate and eventually enable Migrate EcalDeadChannelRecoveryBDTG to GBRForest #28040
Allow seeding to select only above-threshold hits. A new DB record has been introduced for this purpose
PR validation:
Standard PR tests