Add default PDT Pythia table to the repository

[cardinia]

This merge request includes only one file, namely the default PDT table used for the names of particles handled by Pythia. The file is taken directly from:
CMSSW: SimGeneral/HepPDTESSource/data/pythiaparticle.tbl
https://github.com/cms-sw/cmssw/blob/master/SimGeneral/HepPDTESSource/data/pythiaparticle.tbl

It does not interfere with preceding processing, but it is instead needed to cover for an issue found within the charged long-lived particle simulation, and discussed in the context of a PR to the EXO-MC group:
https://gitlab.cern.ch/cms-exo-mci/EXO-MCsampleRequests/-/merge_requests/434#note_11730857

Following the link points to a longer discussion of the problem found and the proposed solution, I will just write a short version here.
When simulating charged LLPs and allowing a charged BSM particle to interact with the detector simulation, the MC production tools require a PDT table provided alongside the genfragment, even if the default table (the one in this merge request) would be fine.
This is because the get_hscp_particle_names_from_pdt function within the SimG4Core/CustomPhysics/python/Exotica_HSCP_SIM_cfi.py custom physics does not recognize the relative path defined by default for HepPDTESSource.pdtFileName and replaces it with one pointing to the externals directory in the CMSSW_RELEASE_BASE directory found in cvmfs, where the default PDT table is not found.

For the SmuonToMuGravitino MC request for 2024, we used a stop PDT table already found in this repository, but we were suggested by the Exo MC&I conveners to find a more stable solution for this problem and make the default PDT table actually accessible to charged LLP MC productions.

The simplest solution found was to include the default PDT table in this repository so that it could be used for central production when there is no need to use a dedicated PDT table, but BSM interactions with the detector are considered.

Could you please let us know if this is an acceptable solution to the case at hand, and if the file can be included in the repository?

[cmsbuild]

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

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

[cmsbuild]

cms-bot internal usage

[sensrcn]

Thanks for the detailed explanation. My only minor concern was keeping the two copies of pythiaparticle.tbl synchronized if the SimGeneral/HepPDTESSource/data/pythiaparticle.tbl version is ever updated. However, the file appears to be very stable, so I don't see this as an issue.

I don't see any issue with adding it to this repository.

[sensrcn]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-55629b/54430/summary.html
COMMIT: 12842df
CMSSW: CMSSW_20_1_X_2026-06-30-1100/el9_amd64_gcc13
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-data/Configuration-Generator/22/54430/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:

• @belforte Update crabclient and crabserver versions cms-sw/cmsdist#10688

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

Comparison Summary

Summary:

• You potentially added 9 lines to the logs
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 45
• DQMHistoTests: Total histograms compared: 3414477
• DQMHistoTests: Total failures: 46
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3414413
• DQMHistoTests: Total skipped: 18
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 44 files compared)
• Checked 195 log files, 163 edm output root files, 45 DQM output files
• TriggerResults: no differences found

[cardinia]

Thanks for the detailed explanation. My only minor concern was keeping the two copies of pythiaparticle.tbl synchronized if the SimGeneral/HepPDTESSource/data/pythiaparticle.tbl version is ever updated. However, the file appears to be very stable, so I don't see this as an issue.

I don't see any issue with adding it to this repository.

Yeah, before making this merge request, I had checked how often the file was changed and realized it had never been changed after its first integration in CMSSW.

[sensrcn]

+generators

[cardinia]

Sorry, forgot to write this: we would need the change backported to CMSSW 124x and 130x for producing 2022/23 MC

[lviliani]

Can we please hold this PR for a while before merging? We were discussing an additional test with @cardinia