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:Simulation - DDDWorld Defines Regions and Sets G4 Production Cuts #27588
DD4hep:Simulation - DDDWorld Defines Regions and Sets G4 Production Cuts #27588
Conversation
The code-checks are being triggered in jenkins. |
@civanch - please, let me know if I should open a separate PR for the changes (included here) in the |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27588/11005
|
A new Pull Request was created by @ianna (Ianna Osborne) for master. It involves the following packages: DetectorDescription/DDCMS @civanch, @Dr15Jones, @cvuosalo, @ianna, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
@civanch - please, let me know when will you be able to review this PR. Thanks. |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
DDG4ProductionCuts
std::vector<std::pair<G4LogicalVolume*, const cms::DDSpecPar*>>
G4Region
and assign to itG4ProductionCuts
(if they are not already set!). Beware, the cuts defined only once per region. There is no check if they should be overwritten from an extra definition in the xml files.@civanch - FYI, as discussed during Sim meeting.
PR validation:
The output is written to simG4test.log
if this PR is a backport please specify the original PR:
Before submitting your pull requests, make sure you followed this checklist: