-
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
Revived being able to run modules inside a mixing module #40133
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40133/33124
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages:
@smuzaffar, @civanch, @Dr15Jones, @makortel, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -383,6 +383,8 @@ namespace edm { | |||
ModuleCallingContext moduleCallingContext(&moduleDescription()); | |||
ModuleContextSentry moduleContextSentry(&moduleCallingContext, parentContext); | |||
|
|||
setupPileUpEvent(setup); |
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.
Just to note that as far as I can tell, the necessity of this call has gone unnoticed because before we have not used the ability to run modules (that would consume EventSetup products) as part of the MixingModule. Would you agree?
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 you are probably correct.
This does not modify the old token, just allows the new token to have a different service for the same activity as the old token.
Uses the mixing modules assigned random engine as the basis for the engines given to the modules internal to the mixing module.
Share the implementation across RandomNumberGenerators
6971e19
to
cbdb75c
Compare
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40133/33274
|
Pull request #40133 was updated. @makortel, @smuzaffar, @civanch, @Dr15Jones, @mdhildreth can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9199ce/29435/summary.html Comparison SummarySummary:
|
The differences occur only in 11634.7 (which is the "all tracking iterations using mkFit" variant). Seems that similar spurious differences are visible in some other recent master PRs as well #39803 (comment). |
+core |
+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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
PR validation:
Tested generating pileup 'on the fly' by embedding the generator and OscarMTProducer within the mixing module. [This requires a further change to OscarMTProducer].