Adding slha files for EXO DisappTrk Run 3 analysis

[borzari]

Distinct mass/ctau slha files for the central production of LL charginos signal samples for the EXO disappearing tracks analysis in Run 3.

[cmsbuild]

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

@SiewYan, @smuzaffar, @mkirsano, @aandvalenzuela, @iarspider, @Saptaparna, @cmsbuild, @alberto-sanchez, @menglu21, @GurpreetSinghChahal 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

[tvami]

@cmsbuild , please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-18e078/34694/summary.html
COMMIT: adeb544
CMSSW: CMSSW_13_3_X_2023-09-11-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-data/Configuration-Generator/14/34694/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 13 lines to the logs
• Reco comparison results: 6 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3153414
• DQMHistoTests: Total failures: 3
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3153389
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 207 log files, 159 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[menglu21]

+1

[tvami]

hi @smuzaffar can you please merge this?

[smuzaffar]

This PR only adds new files, so testing without cmssw PR (which actually make sure of these files) is only going to check if packaging works. Is there any cmssw PR to go with it?

[tvami]

Is there any cmssw PR to go with it?

hi @smuzaffar this is used in McM for signal generation, so there is no main cmssw PR to go with.

[smuzaffar]

+externals

[smuzaffar]

so by default itwill go to 13.3.X release cycle. let us know if this should be backported to any older release cycle

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

[tvami]

let us know if this should be backported to any older release cycle

yes, it needs to go back to 12_4_X for the 2022 MC productions. I remember that there used to be a tag update in cmsdist to do this, but I dont see the master PR for that automatically triggered.

[tvami]

but I dont see the master PR for that automatically triggered.

nvm, it did come up 4 min after I wrote this :)

[smuzaffar]

we are updating bot scripts to python3 and automatic master branch PR creation script had a bug. cms-sw/cms-bot@a4f7e3e has fixed the issue :-)