Correct xml file being called for different beam settings in CI

[simonge]

Briefly, what does this PR introduce?

Fixes xml being used so that it matches the MC sample being run.

It was noted in the Exclusive Diffractive and Tagging meeting that some of the campaigns appear to be being run with the wrong beamline settings. This only address the problem where I can see it in the CI.

What kind of change does this PR introduce?

• Bug fix (issue #__)
• New feature (issue #__)
• Documentation update
• Other: __

Please check if this PR fulfills the following:

• Tests for the changes have been added
• Documentation has been added / updated
• Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

No

Does this PR change default behavior?

Means the beam is being steered correctly for the MC samples being run in the CI

[simonge]

Is this the script which is run for all of the hepmc3 campaigns?
https://github.com/eic/simulation_campaign_hepmc3/blob/main/scripts/run.sh

[veprbl]

Is this the script which is run for all of the hepmc3 campaigns? https://github.com/eic/simulation_campaign_hepmc3/blob/main/scripts/run.sh

I believe so, yes. cc @rahmans1

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Capybara summary for PR 1616

• rec_dis_10x100_minQ2=0_craterlake
• rec_dis_10x100_minQ2=1000_craterlake_tracking_only
• rec_e_1GeV_20GeV_craterlake
• rec_pi_1GeV_20GeV_craterlake
  ^{_{Last updated 2024-09-16T18:22-04:00 8c41cab}}

[simonge]

Will the missing capybara reports return with new names in the next PR?

[veprbl]

I assumed that was because the files with those configurations were never produced on main.

[veprbl]

(Long way to say "Yes")