Changed beam energy in pythia8

[sejeong8]

Changed beam energy in pythia8

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[jackal1-66]

Tagging @stefanopolitano. Is there a reason why to move the energy to 5.36 TeV in pp? I see this configuration is currently used only in MC/config/PWGHF/ini/GeneratorHF_HFe_ccbar_and_bbar_gap5_Mode2.ini

[sejeong8]

It is for the production of the pp reference MC

[stefanopolitano]

Hi @sejeong8 and @jackal1-66 ! Thanks for the work. Indeed, I would suggest not to modify the energy value in this config, but rather creating a dedicated one for the ppref (as previously done, see here ) to avoid confusion in the future