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
Remove duplicate label definition #32785
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32785/20952
|
A new Pull Request was created by @lecriste (Leonardo Cristella) for master. It involves the following packages: SimDataFormats/Associations @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @mdhildreth, @civanch, @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-0906d8/12642/summary.html Comparison SummarySummary:
|
+1 |
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@@ -1,12 +1,8 @@ | |||
import FWCore.ParameterSet.Config as cms | |||
from Validation.HGCalValidation.HGCalValidator_cfi import hgcalValidator |
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.
A DataFormat package should not depend on Validation package (even on python level). If a dependence between two packages is needed, the dependence should go in the other direction.
Written that, a DataFormat package should not define plugins (e.g. EDProducers). By quick look SimCalorimetry/HGCalAssociatorProducers
could be a reasonable place for the producers.
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.
@makortel thanks for the comment.
By moving the plugin definition into
SimCalorimetry/HGCalAssociatorProducers
, can I keep the dependency on Validation package there or shall I still swap the dependency direction?
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.
I think also there the dependence should go by Validation depending on Simulation.
PR description:
This PR removes a duplication of label definitions. No changes are expected in the output.
PR validation:
runTheMatrix -l limited