add decay files for UpsilonXS

[michael-pitt]

Following a request of a new Upsilon MC production with fixed feed-down, and consulting with this readme file.

Regards,
Michael

[cmsbuild]

A new Pull Request was created by @michael-pitt (Michael Pitt) for branch master.

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

[tanmayvb]

Hello Experts, Could you please review it and probably merge it?

[smuzaffar]

@michael-pitt @tanmayvb , is there any cmssw PR which makes use of these new data files?

[michael-pitt]

Hi @smuzaffar, A new MC production request will use these new data files. In the Pythia fragment, we can read decay tables provided by users. For example, in our case, we are using: SMP-RunIISummer20UL16GEN-00050

[smuzaffar]

@michael-pitt , so by default it will go in to 14.0.X release cycle. Should we backport it to other release cycle(s)?

[smuzaffar]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-794b04/36298/summary.html
COMMIT: 54ff9d1
CMSSW: CMSSW_14_0_X_2023-12-03-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-data/GeneratorInterface-EvtGenInterface/24/36298/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:

• @mkirsano upgrade lhapdf to 6.5.4, sets to 6.5.1c cms-sw/cmsdist#8852

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

Comparison Summary

Summary:

• You potentially removed 174 lines from the logs
• Reco comparison results: 16 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 3370032
• DQMHistoTests: Total failures: 79
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3369931
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 214 log files, 167 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[smuzaffar]

+externals

[michael-pitt]

@michael-pitt , so by default it will go in to 14.0.X release cycle. Should we backport it to other release cycle(s)?

These files will be accessed after setting up the 10.6.X release used in Run2 production campaigns.

[smuzaffar]

I will merge it for 14.0.X as soon as any generator L2 signs it

[bbilin]

+1

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

[michael-pitt]

Hi @smuzaffar what is needed to make these files available in the release? I tried to run production code that uses these files, but I received the following error:
edm::FileInPath unable to find file GeneratorInterface/EvtGenInterface/data/Upsilon1S.dec anywhere in the search path.

[michael-pitt]

Hi @antoniovilela @sextonkennedy @rappoccio can you check this PR? we are waiting for this PR to be merged to start a new MC production

[antoniovilela]

+1

[javi-llorente]

Hi all,
Thank you very much for taking care of these samples.
I would like to understand what are the next steps for producing them, as this is a bit of a bottle neck for our analysis. Is everything ready now for launching the production?
If there is something I can do to accelerate the process, I can also put my hands on this myself if needed.

Thank you very much. Best regards,
Javier.