-
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
[DD4hep] start on geometry XML payload producer #33548
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33548/22329
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
-1 |
913a14e
to
08abe62
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33548/23350
|
A new Pull Request was created by @ianna (Ianna Osborne) for master. It involves the following packages: Calibration/EcalCalibAlgos @perrotta, @malbouis, @civanch, @Dr15Jones, @makortel, @cvuosalo, @tlampen, @ianna, @kpedro88, @cmsbuild, @srimanob, @yuanchao, @mdhildreth, @slava77, @jpata, @pohsun, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -92,6 +92,8 @@ void PixelCPEFastESProducer::fillDescriptions(edm::ConfigurationDescriptions& de | |||
// specific to PixelCPEFastESProducer | |||
desc.add<std::string>("ComponentName", "PixelCPEFast"); | |||
desc.add<edm::ESInputTag>("MagneticFieldRecord", edm::ESInputTag()); | |||
desc.addOptional<bool>("useLAAlignmentOffsets", false)->setComment("deprecated"); |
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.
@ianna why this change?
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 rebase didn't take into an account reverted changes :-(
@@ -105,6 +105,8 @@ void PixelCPEGenericESProducer::fillDescriptions(edm::ConfigurationDescriptions& | |||
// specific to PixelCPEGenericESProducer | |||
desc.add<std::string>("ComponentName", "PixelCPEGeneric"); | |||
desc.add<edm::ESInputTag>("MagneticFieldRecord", edm::ESInputTag("")); | |||
desc.addOptional<bool>("useLAAlignmentOffsets", false)->setComment("deprecated"); |
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.
@ianna why this change?
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 rebase didn't take into an account reverted changes:
Revert "Update mtdParameters for D49 and D60 (Bug fix)", This reverts… … 1307d75
Revert "[backport] MTD geometry and reconstruction: synchronise with … … faf18ac
change ECAL pedestals requireStableBeam flag for MWGR test 2a9cbcd
Revert "Revert "[backport] MTD geometry and reconstruction: synchroni… …f2a994f
revert changes breaking online HLT menu in production release 93afbed
@@ -83,6 +83,7 @@ void PixelCPETemplateRecoESProducer::fillDescriptions(edm::ConfigurationDescript | |||
|
|||
// specific to PixelCPETemplateRecoESProducer | |||
desc.add<std::string>("ComponentName", "PixelCPETemplateReco"); | |||
desc.addOptional<bool>("DoLorentz", true)->setComment("deprecated"); |
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.
@ianna why this change?
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.
same reason as above
@ianna why restoring old parameters in |
I guess it is a similar issue as in the discussion with @mmusich ... There is no reason to go back anyway |
Yes, I have no idea why a rebase picked the other commits. I'll try to rebase again a bit later. If this will not work, I'll cherry-pick my commit and open a new PR. |
@ianna , better to start a new PR even if extra work will be needed. |
-1 it looks like the rebase went wrong and changes in reco code are not expected |
@ianna |
PR description:
@cvuosalo - IMHO, this is a very straightforward way: if
xml_geometry_payload
is defined, a big XML will be produced (std::cout
for now).Please, see the test:
PR validation:
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: