Separate the cgf files for each baryon

[chengtt0406]

1. Previous approved PR with discussion was here: New files for producing eventpool of undecayed XiC #2056
2. Now, suggest to separate the cfg file for each baryon; therefore, we need to update the corresponding .ini

[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

[chengtt0406]

Dear all,
I just noticed the build failed; however, the log shows no errors found. Could you please help cross-check?
Many Thanks!

[stefanopolitano]

Hi @chengtt0406 ,
Thanks for the update. I went through the code and didn’t spot anything clearly wrong, and the build log didn’t show a definitive error either. Maybe we could try re-triggering the tests with a dummy commit (e.g., adding a space in a commented line) to see if the failure persists

[chengtt0406]

Hi @chengtt0406 , Thanks for the update. I went through the code and didn’t spot anything clearly wrong, and the build log didn’t show a definitive error either. Maybe we could try re-triggering the tests with a dummy commit (e.g., adding a space in a commented line) to see if the failure persists

Hi @stefanopolitano, thank you very much for reviewing.
I just made a dummy commit, hope it works today.