New pdl files with new Bs and Bs* mass points for MC production

[friti]

Hello!

This PR adds new .pdl files, each corresponding to a Bs mass point ranging from 3.6 GeV to 10 GeV in 0.5 GeV steps.

Additionally, the Bs* mass has been updated to allow for Bs* → Bs decays, maintaining the same mass ratio between Bs* and Bs as in the SM.

Below is the difference between the pdl file for one mass point (5.5GeV) evt_2014_bsmass_5p5gev.pdl and the original evt_2014.pdl:

295c295
< add  p Particle  B_s0                             531  5.3667700e+00  0.0000000e+00  0.0000000e+00     0     0  4.4129450e-01        531
---
> add  p Particle  B_s0                             531  5.5	      0.0000000e+00  0.0000000e+00     0     0  4.4129450e-01        531
333c333
< add  p Particle  anti-B_s*0                      -533  5.4154000e+00  6.5821220e-06  1.0000000e-04     0     2  0.0000000e+00       -533
---
> add  p Particle  anti-B_s*0                      -533  5.54983        6.5821220e-06  1.0000000e-04     0     2  0.0000000e+00       -533
439c439
< add  p Particle  anti-B_s0                       -531  5.3667700e+00  0.0000000e+00  0.0000000e+00     0     0  4.4129450e-01       -531
---
> add  p Particle  anti-B_s0                       -531  5.5	      0.0000000e+00  0.0000000e+00     0     0  4.4129450e-01       -531
465c465
< add  p Particle  B_s*0                            533  5.4154000e+00  6.5821220e-06  1.0000000e-04     0     2  0.0000000e+00        533
---
> add  p Particle  B_s*0                            533  5.54983        6.5821220e-06  1.0000000e-04     0     2  0.0000000e+00        533

These mass points are needed for the MC production used for the mass regression of the Bs for the Bs-> tautau analysis in ttbar events (B2G group).

Please let me know if you require any additional information.

Thanks in advance,
Federica on behalf of the analysis team

[cmsbuild]

A new Pull Request was created by @friti for branch master.

@akritkbehera, @bbilin, @cmsbuild, @iarspider, @lviliani, @menglu21, @mkirsano, @smuzaffar can you please review it and eventually sign? Thanks.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.
cms-bot commands are listed here

[cmsbuild]

cms-bot internal usage

[lviliani]

please test

[theofil]

@lviliani maybe abort and restart ?

[iarspider]

The tests (relvals) just started.

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dd3ad9/46783/summary.html
COMMIT: be1ae58
CMSSW: CMSSW_15_1_X_2025-06-16-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-data/GeneratorInterface-EvtGenInterface/28/46783/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

• @cms-sw Update of python packages cms-sw/cmsdist#9929

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dd3ad9/46783/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dd3ad9/46783/git-merge-result

Comparison Summary

Summary:

• You potentially added 16 lines to the logs
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 4050825
• DQMHistoTests: Total failures: 2
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 4050803
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 215 log files, 184 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[lviliani]

+1

[cecilecaillol]

@smuzaffar Could you please check and sign off?

[smuzaffar]

@friti @lviliani @cecilecaillol , this pr only adds new data files which i think are not used by any existing tests. Is there any cmssw pr to check / test these new data files?

[cecilecaillol]

@smuzaffar These files will be used to generate signal samples for one analysis and wont be used by any other MC request. Therefore integrating in central tests probably does not make much sense. We are going to open the PR for the signal generation reading these files in cms-data.

[smuzaffar]

+externals

[cmsbuild]

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

[cecilecaillol]

@smuzaffar We would need these pdl files to make Run-2 samples in slc7_amd64_gcc12. Would it possible for you to do a backport to have them in /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/data-GeneratorInterface-EvtGenInterface/V02-11-00/GeneratorInterface/EvtGenInterface/data/? Thank you!

[smuzaffar]

@cecilecaillol , we need to know the cmssw release cycle name for which this should be back ported.

[cecilecaillol]

@smuzaffar Can we please have the backport to CMSSW_10_6_47?

[smuzaffar]

@cecilecaillol , we can backport it to CMSSW_10_6_X release cycle and it can be available for next CMSSW_10_6_48 full release. Note that we can not change externals/cms-data for already built releases (e.g. CMSSW_10_6_47).

[cecilecaillol]

@smuzaffar Can you please backport it to 10_6_X then? What is the timescale for 10_6_48? If it is far from now, would it be possible to have 10_6_47_patch4?

[smuzaffar]

What is the timescale for 10_6_48?

one need to request such release in ORP (offline line planning meeting). @antoniovilela, @mandrenguyen, @rappoccio can tell when it can be build.

If it is far from now, would it be possible to have 10_6_47_patch4?

No, patch release can not have new externals. So you really jhave to wait for 10_6_48

[cecilecaillol]

@smuzaffar Can you please do the backport to 10_6_X?
@antoniovilela, @mandrenguyen, @rappoccio : How can we ask for the release of 10_6_48? We need it to produce signal samples with the official production through MCM.
Thanks all!

[smuzaffar]

cms-sw/cmsdist#10019 opened to backport it to 10.6.X

[mandrenguyen]

@smuzaffar Can you please do the backport to 10_6_X? @antoniovilela, @mandrenguyen, @rappoccio : How can we ask for the release of 10_6_48? We need it to produce signal samples with the official production through MCM. Thanks all!

No problem to build a new 10_6_X. However, according to our backport policy, if this is backported to 10_6_X it should also be backported to all active release cycles in between.
Please backport to all release cycles for which there is an IB running, which you can find on the following monitoring page:
https://cmssdt.cern.ch/SDT/html/cmssdt-ib/

Thanks!

[cecilecaillol]

@smuzaffar Would it be possible for you to also open the backports to 12_4_X, 13_0_X, 13_1_X, 13_2_X, 13_3_X, 14_0_X, 14_1_X, 14_2_X, 15_0_X, and 15_1_X? Thank you!

[mandrenguyen]

+1

[cecilecaillol]

Thanks for opening the backports!
@mandrenguyen Now that backports to running IBs exist, could you please tell us the timescale to release 10_6_48 such that we can start the official MC production through McM? Thanks!

[iarspider]

Thanks for opening the backports! @mandrenguyen Now that backports to running IBs exist, could you please tell us the timescale to release 10_6_48 such that we can start the official MC production through McM? Thanks!

As far as I understand, it's already available - cms-sw/cmssw#48766

[cecilecaillol]

Indeed, I had missed it. Thanks all!