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
Add a mechanism to adjust the pileup distribution in PreMixingModule #25770
Conversation
The code-checks are being triggered in jenkins. |
@cmsbuild, please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25770/8189
|
The tests are being triggered in jenkins. |
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: DQM/SiStripMonitorHardware @smuzaffar, @andrius-k, @Dr15Jones, @kmaeshima, @schneiml, @civanch, @mdhildreth, @cmsbuild, @jfernan2 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
Pull request #25770 was updated. @smuzaffar, @andrius-k, @Dr15Jones, @kmaeshima, @schneiml, @civanch, @mdhildreth, @cmsbuild, @jfernan2 can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 the added unit tests run successfully |
This PR adds a mechanism to adjust the pileup distribution of the premixed pileup library in premixing stage2 (pileup overlay). The mechanism (that is off by default) is the following
PreMixingModule
reads an event from the pileup libraryIf a pileup event is encountered with a true pileup value outside of the range in configuration, the probability is considered to be 0. Naively this would lead to an infinite loop on misconfiguration (if the configured pileup range would not cover at all the generated pileup), so a following protection is included: an exception is thrown if N consecutive pileup events landing outside of the configured pileup range are encountered (N is configurable, the exception can also be disabled).
This mechanism required adding a way to skip events in
VectorInputSource
.Example configuration
Tested in 10_4_0, no changes expected.