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

Backport of #29567 (biased tau decayer) to CMSSW_9_4_X #29807

Merged
merged 1 commit into from May 12, 2020

Conversation

mseidel42
Copy link
Contributor

PR description:

Backport of #29567 by @smrenna to require at least one tau decaying only to leptons after heavy resonance decays:

Pythia8 has the capability to define a decay handler for specific particles through DecayHandler.
This request is a special tau decayer that can be used to bias tau pair decays to contain at least one lepton. It is meant to be used with Powheg samples containing taus so that no Powheg events are lost.
Since DecayHandler is meant to decay one particle at a time, while the standard Pythia tau decayer decays the correlated pair, part of the decay history is saved and then used to fill the products of the second (correlated) tau.

PR validation:

Validation plots for W and Z, things look as expected: https://mseidel.web.cern.ch/mseidel/cms/PDG_TAUS/

In particular, here is the number of tau->charged lepton decays in Z events:
image
As expected, 0 lepton is depleted completely, and the ratio betwen 1 and 2 leptons stays the same.

To check spin correlations, here is a plot of the dPhi between the two charged leptons, in case of both taus decaying to charged leptons:
image

if this PR is a backport please specify the original PR and why you need to backport that PR:

Backport of #29567, needed for 2017 low-PU MC

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @intrepid42 (Markus Seidel) for CMSSW_9_4_X.

It involves the following packages:

GeneratorInterface/Pythia8Interface

@SiewYan, @efeyazgan, @mkirsano, @cmsbuild, @GurpreetSinghChahal, @agrohsje, @alberto-sanchez, @qliphy can you please review it and eventually sign? Thanks.
@alberto-sanchez, @agrohsje, @mkirsano this is something you requested to watch as well.
@silviodonato, @dpiparo you are the release manager for this.

cms-bot commands are listed here

@qliphy
Copy link
Contributor

qliphy commented May 12, 2020

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 12, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/6243/console Started: 2020/05/12 11:31

@cmsbuild
Copy link
Contributor

+1
Tested at: e2b2565
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2bb40e/6243/summary.html
CMSSW: CMSSW_9_4_X_2020-05-10-0000
SCRAM_ARCH: slc6_amd64_gcc630

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2bb40e/6243/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 27
  • DQMHistoTests: Total histograms compared: 2721493
  • DQMHistoTests: Total failures: 104
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2721227
  • DQMHistoTests: Total skipped: 162
  • DQMHistoTests: Total Missing objects: 0

@qliphy
Copy link
Contributor

qliphy commented May 12, 2020

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_9_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2)

@silviodonato
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 15a42c0 into cms-sw:CMSSW_9_4_X May 12, 2020
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

4 participants