Skip to content
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

Merged
merged 8 commits into from Dec 5, 2022

Conversation

Dr15Jones
Copy link
Contributor

PR description:

  • enabled esConsumes from internal modules to the Process
  • enable RandomNumberGenerator service handling to embedded modules

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].

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40133/33124

  • This PR adds an extra 40KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dr15Jones (Chris Jones) for master.

It involves the following packages:

  • FWCore/ServiceRegistry (core)
  • Mixing/Base (simulation)
  • SimGeneral/MixingModule (simulation)

@smuzaffar, @civanch, @Dr15Jones, @makortel, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks.
@makortel, @wddgit, @missirol, @fwyzard, @fabiocos, @slomeo this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

Mixing/Base/src/PileupRandomNumberGenerator.cc Outdated Show resolved Hide resolved
@@ -383,6 +383,8 @@ namespace edm {
ModuleCallingContext moduleCallingContext(&moduleDescription());
ModuleContextSentry moduleContextSentry(&moduleCallingContext, parentContext);

setupPileUpEvent(setup);
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@cmsbuild cmsbuild modified the milestones: CMSSW_12_6_X, CMSSW_13_0_X Nov 24, 2022
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
@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 2, 2022

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40133/33274

  • This PR adds an extra 28KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 2, 2022

Pull request #40133 was updated. @makortel, @smuzaffar, @civanch, @Dr15Jones, @mdhildreth can you please check and sign again.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 3, 2022

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9199ce/29435/summary.html
COMMIT: cbdb75c
CMSSW: CMSSW_13_0_X_2022-12-02-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/40133/29435/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 30 differences found in the comparisons
  • DQMHistoTests: Total files compared: 48
  • DQMHistoTests: Total histograms compared: 3421159
  • DQMHistoTests: Total failures: 1176
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3419961
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
  • Checked 206 log files, 158 edm output root files, 48 DQM output files
  • TriggerResults: no differences found

@makortel
Copy link
Contributor

makortel commented Dec 5, 2022

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).

@makortel
Copy link
Contributor

makortel commented Dec 5, 2022

+core

@civanch
Copy link
Contributor

civanch commented Dec 5, 2022

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 5, 2022

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)

@rappoccio
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 4c4e62b into cms-sw:master Dec 5, 2022
@Dr15Jones Dr15Jones deleted the reviveModulesInsideMixing branch December 13, 2022 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants