-
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
Backport (update) option to override GEN decays with FastSim decays #41399
Conversation
A new Pull Request was created by @sbein (Sam Bein) for CMSSW_10_6_X. It involves the following packages:
@cmsbuild, @ssekmen, @civanch, @mdhildreth, @sbein can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-aade37/32124/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_1_X is complete. 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) |
Regression problems are only in FastSim WFs that is expected. |
While the fix absolutely makes sense, still we are updating a closed release with some fix that changes the fastsim output: shouldn't we apply a modifier then to identify the fastsim productions made with and without this fix? |
@perrotta I think you're right, but it gets a little complicated. This fix supersedes a previous bug fix involving the decayer, e.g., #36352, which got its own proc modifier. That fix was kind of a hack that solved a specific issue for exotic decays, but later issues were discovered with the decayer even in SM events, which came to light when studying FastSim for use cases beyond the SUS PAG. We decided to just disable the decayer by default since it causes more trouble than it's worth, rather than have bug fixes on top of previous bug fixes. These changes don't make a difference with respect to current SUS campaigns, but they will be necessary if TOP decides to make requests. In my opinion, it would serve to cut a bit of red tape here, but we also need to work closely with the PAGs as FastSim becomes more used by more than one PAG. My two cents, thanks a lot. |
Really SUS events are untouched by this change? In the test matrix there are only ZEE and TOP FS workflows, therefore this cannot be verified: it would be worth testing with a couple of SUSY FASTSIM workflow to verify. Could you please suggest a couple of them so that we can run the tests with them? On the other hand, if that is true and FastSim in 10_6_X was not used so far for any non SUSY campaign (including MB backgrounds), then I have no objections in merging this without a modifier: could please @cms-sw/pdmv-l2 remind us here which FastSim campaigns were run so far in the legacy 10_6_X? |
hold
|
Pull request has been put on hold by @rappoccio |
Indeed the only campaigns so far were SUSY signal scans. However, to preserve default physics, the original fixLongLivedBug modifier is restored and the option to ignore all FastSim decays in place of the GEN decays is made as an option activated with a proc modifer. This PR is superseded by: #41596 |
PR description:
The backport #39022 was missing two key lines that were in the HEAD, which this PR corrects for. These changes are needed to achieve better agreement between FastSim and FullSim for Standard Model production, e.g., ttbar, for Run 2 UL productions.
PR validation: