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

Update Pythia Hook for BB4L #44061

Merged
merged 6 commits into from
Mar 14, 2024
Merged

Update Pythia Hook for BB4L #44061

merged 6 commits into from
Mar 14, 2024

Conversation

lauridsj
Copy link
Contributor

PR description:

This PR replaces the Pythia Hook used for showering events produced with the bb4l generator with a new version provided by the authors.

There are two reasons why this is necessary, both related to the new bb4l version that was released last year:

  • The old version that was in CMSSW beforehand had a bug that caused the hook to crash for events that had only an antitop and no top (i.e. tbarW events). This was never noticed because in the old bb4l, tW events were still labeled as ttbar events, while the new bb4l also has events labeled as tW.
  • The new bb4l version also includes the semileptonic decay channel of ttbar, which the old hook does not support.

I have copied the version provided by the authors with as few changes as necessary to adapt it to CMSSW and Pythia 8.2 (the original version was for Pythia 8.3).

Note that some of the flags present in the old hook are no longer present. These flags were meant as cross-checks by the bb4l authors to test the effects of several assumptions of the matching, and were never used in CMS for official MC production. Thus I did not bother to reimplement them in the new version of the hook. (Also note that the most important such flag for an "alternate" matching, POWHEG:bb4l:ScaleResonance:veto, is still there.)

In addition, I have added a new flag that was not present in the version of the authors: POWHEG:bb4l:vetoAllRadtypes. This flag is not meant for bb4l (and should be left at its default value of false when showering bb4l), but instead for the ttb_NLO_dec generator, which we might want to generate in the future as well. This generator also generates up to one real emission per decaying top, thus has the same final state as bb4l and can use the same hook. However, after checking with the authors, we were notified that it is necessary to modify the hook to also veto Powheg remnant events (radtype 2), which is not the case for bb4l. This alternate behavior is implemented with this flag.

PR validation:

I have confirmed that, when run on LHE files produced by the old bb4l, the new and old versions of the hook give exactly the same output.

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

The PR will need to be backported to all MC production releases, i.e.
10_6_X (UL)
12_4_X (2022)
13_0_X (2023 I think?)
(Any that I missed?)

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 22, 2024

cms-bot internal usage

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44061/39005

  • This PR adds an extra 24KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44061/39006

  • This PR adds an extra 24KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @lauridsj for master.

It involves the following packages:

  • GeneratorInterface/Pythia8Interface (generators)

@menglu21, @bbilin, @cmsbuild, @mkirsano, @SiewYan, @GurpreetSinghChahal, @alberto-sanchez can you please review it and eventually sign? Thanks.
@mkirsano, @alberto-sanchez this is something you requested to watch as well.
@rappoccio, @sextonkennedy, @antoniovilela you are the release manager for this.

cms-bot commands are listed here

@menglu21
Copy link
Contributor

@cmsbuild please test

@lauridsj
Copy link
Contributor Author

Hey @menglu21 , it looks like the tests are somehow stuck... do you know what is going on?

@lauridsj
Copy link
Contributor Author

lauridsj commented Mar 5, 2024

Hey @menglu21 @bbilin , sorry for spamming, but could you maybe have a look at why the tests are stuck / just restart them in case something went wrong? It would be great if we could merge this PR soon so that we could start the MC request for the new bb4l sample + variations.
Thanks a lot!

@menglu21
Copy link
Contributor

not sure what happened, @rappoccio, @sextonkennedy, @antoniovilela could you please have a look

@rappoccio
Copy link
Contributor

abort

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44061/39440

  • This PR adds an extra 28KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@cmsbuild
Copy link
Contributor

Pull request #44061 was updated. @mkirsano, @GurpreetSinghChahal, @SiewYan, @cmsbuild, @alberto-sanchez, @bbilin, @menglu21 can you please check and sign again.

@lauridsj
Copy link
Contributor Author

Hi @menglu21 @bbilin , sorry for the failing test. There was an unused variable in the hook sent by the authors that I didnt notice when compiling myself. I've removed it now.
Could you please restart the tests once again?
Thanks a lot!

@menglu21
Copy link
Contributor

@cmsbuild please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dc8b5d/38078/summary.html
COMMIT: f39d218
CMSSW: CMSSW_14_1_X_2024-03-12-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/44061/38078/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

@menglu21
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

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. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2)

@rappoccio
Copy link
Contributor

+1

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.

4 participants