Skip to content

Pythia8 ResonanceDecayFilter Fix #48383

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

manuel-gonzalez-henandez

PR description:

This pull request proposes a solution to the issue outlined in https://gitlab.cern.ch/cms-gen/gen_tasklist/-/issues/9. The ResonanceDecayFilter was not correctly accounting for the total number of tried events, leading to an incorrect cross section calculation (as the branching ratio was omitted). To address this, I introduced a counter in ResonanceDecayFilterHook.h to track the number of events vetoed by the filter, along with a function to reset the counter after each event. This data is then passed from Pythia8Hadronizer.cc to GenFilterEfficiencyProducer.cc using an object of the class ResonanceDecayFilterCounter I created.

The counter is applied only to the weight counts and not to the event counts, as requested by PDMV, to ensure the event-level GenFilter efficiency excludes the ResonanceDecayFilter information. This exclusion allows PDMV to accurately determine the number of LHE events required to generate a specific number of Gen events.

Additionally, I introduced the input_genfilter_efficiency variable in GenXsecAnalyzer.cc to ensure that when the ResonanceDecayFilter is enabled, the filter efficiency is always calculated using weight counts (where the filter information is stored) instead of event counts. This adjustment ensures consistent efficiency calculations for both LO and NLO processes and includes the filter’s contribution.

Furthermore, now it is possible to use matching between mother and daughter particles like:
'ResonanceDecayFilter:matching = on'
To indicate the matched decays, it is possible to use just one vector
'ResonanceDecayFilter:matchedDecays = {m1: dau11 dau12, m2: dau21 dau22,…, mN: dauN1 … dauNM}'
or “split” into small vectors
'ResonanceDecayFilter:matchedDecays = {m1: dau11 dau12}',
'ResonanceDecayFilter:matchedDecays += {m2: dau21 dau22}',
'ResonanceDecayFilter:matchedDecays += {mN: dauN1 … dauNM}' # N-body decays are allowed

Expected changes to the output are as follows:

  1. In the GenFilter luminosity block of the final root file, the sumtotal_w and sumtotal_w2 values now incorporate the ResonanceDecayFilter information, reflecting the true total number of tried events.
  2. In GenXsecAnalyzer.cc, the "Filter efficiency (taking into account weights)" now includes this filter’s contribution, which accounts for the branching ratio. Consequently, the final cross section and equivalent luminosity are calculated correctly, incorporating the branching ratio.

Be careful: if the decay properties are modified in Pythia (e.g. 'onIfMatch') and the ResonanceDecayFilter is used, the filter efficiency could not be the same as the branching ratio.

PR validation:

To verify the correctness of the cross section calculation, I used the LO Radion_GF_HH_M300_narrow gridpack (as referenced in https://gitlab.cern.ch/cms-gen/gen_tasklist/-/issues/9) and a simple NLO ttbar custom gridpack that I generated for testing. In both cases, the resulting cross section was calculated correctly.

I also performed the checks outlined in https://cms-sw.github.io/PRWorkflow.html. I executed the runTheMatrix suite of tests. The mistakes obtained by the tests were "No such file or directory" caused by missing root files. . To investigate further, I ran the same runTheMatrix tests using an unmodified version of CMSSW and observed identical errors. This strongly indicates that the issues are unrelated to my modifications.

This PR is a backport to the PR #46725 (Fix cross section when using ResonanceDecayFilter) because there were some issues related to code-checks (the patches given by the bot were impossible to implement).

@cmsbuild
Copy link
Contributor

cmsbuild commented Jun 23, 2025

cms-bot internal usage

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48383/45276

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

@manuel-gonzalez-henandez
Copy link
Author

backport of #46725

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48383/45277

@cmsbuild
Copy link
Contributor

Pull request #48383 was updated.

@manuel-gonzalez-henandez manuel-gonzalez-henandez marked this pull request as ready for review June 23, 2025 09:28
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.

2 participants