Pythia filter to focus on the probe side of B decays

[gkaratha]

PR description:

Currently in CMSSW we do not have any Filter to look at the probe side of an event if the decay itself has a identical particle. eg. In B parking we want to generate B->mumuK in which the mu should not have to pass any filter (probe B). Additionally, we want the filter to be passed by another muon in the event (B+->mu1mu2K, B- -> mu3X, we want to filter mu3 and only mu3).

PR validation:

The code has been validated in mumuK(), J/psi(->mumu)K() with direct comparison to the analysis code. The gain using the existing filters and this new filter, has also been studied

if this PR is a backport please specify the original PR:

[cmsbuild]

A new Pull Request was created by @gkaratha for CMSSW_10_2_X.

It involves the following packages:

GeneratorInterface/GenFilters

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

cms-bot commands are listed here

• Backported from Pythia filter to focus on the probe side of B decays (backport) #26300

[gkaratha]

Perhaps @jordanm wants to follow this

[alberto-sanchez]

@gkaratha, @jordanm make sure to make the appropriate PR to master as well.

[alberto-sanchez]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/33834/console Started: 2019/03/28 18:25

[gkaratha]

Dear Alberto,

Yes I am going to try again tonight for 10_6_X. I tried several times already, from different machines but I constantly get "ERROR: Unable to find release area for "CMSSW" version "CMSSW_10_6_X_2019-03-27-2300" for arch slc6_amd64_gcc700". I tried for different days and times with the same result. But when I changed from CMSSW_10_6_X_2019-03-27-2300 -> CMSSW_10_2_X_2019-03-27-2300 , it worked fine! This is why the "backport" came first. Also because I think that this release will be used for MC production. I will try later to properly propagated to 10_6_X as well. Thanks.

Best regards,
George Karathanasis

[alberto-sanchez]

You should use a slc7 (or equivalente machine). Perhaps lxplus7.
Any new features/fix has to go to master, no matter if the production is a different release. Once integrate there, the backport can be made.

[gkaratha]

Dear Alberto,

Ok thanks! I will try on lxplus7 then.

Best regards,
George

[cmsbuild]

+1
Tested at: fb3dc18
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-26286/33834/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 31
• DQMHistoTests: Total histograms compared: 3007400
• DQMHistoTests: Total failures: 4
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3007206
• DQMHistoTests: Total skipped: 190
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 30 files compared)
• Checked 129 log files, 14 edm output root files, 31 DQM output files

[gkaratha]

Dear @alberto-sanchez ,

I have made the backport in 10_6_X using the slc7 as you proposed. That was the problem after all. The PR is here: #26300 .Thanks.

Best,
George

[alberto-sanchez]

backport of #26300

[alberto-sanchez]

+1

@fabiocos, We will need this in production at the earliest, once integrated in master. Thanks!

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_10_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_10_6_X is complete. 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)

[fabiocos]

+1