Update tune from SCCR to QCDCR for pO and OO

[wuctlby]

No description provided.

[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

[wuctlby]

Dear @jackal1-66 , could you please have a look at what causes the test errors? The error messages are not super clear to me. Thanks a lot!

[wuctlby]

Besides, the grid test with the same cfg and ini files is successful. I just put the link here https://alimonitor.cern.ch/catalogue/?path=%2Falice%2Fcern.ch%2Fuser%2Fc%2Fchuntai%2F%2FMC_production%2Fnew_OO%2Ftest_10k_OO_qcd_test-20260201-154720

[jackal1-66]

Ciao @wuctlby , something seems to be wrong on the framework side. I'm investigating what the problem might be

[jackal1-66]

I couldn't find anything clear in the framework. Other generators and tests seem to be working fine. @wuctlby could you please check that the replaceParticle function logic is working as expected? The issue seems to be triggered there. I would look also in the correct cycling over the iPart variable. I'm investigating why this works for specific tags (until 28 of January it seems) and it's broken in more recent ones. I'm asking the experts (@ktf) also if something minor has changed that could trigger the memory fault somehow. Pythia doesn't seem to be the issue (last version is from 8 months ago).