Add Non-HFE–enhanced dataset

[rashigupt]

We will produce a Non-HFE–enhanced dataset by generating Monte Carlo samples with increased π⁰ and η production, to improve the statistical precision of the non-HFE efficiency measurement.

[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

[stefanopolitano]

Hi @rashigupt ! Thanks for the development. I just have a doubt from my side: why using a gap-triggered configuration if you disable all HF decays? Why can't you use a standard generator?

[rashigupt]

hi @stefanopolitano, Yes, I disabled all HF decays while producing the enhanced sample because I want to generate enhanced pion and eta statistics in order to obtain a sufficient number of non-heavy-flavour (background) electrons. When I used the general-purpose dataset, the statistics for Non-HFE were too low.

[jackal1-66]

Hello @rashigupt , I see from your PR that you have GeneratorHF_Non_Hfe_enhance.ini, but GeneratorHF_Non_Hfe.C as test. This will not work because the CI will check a .C macro named in the same way as your ini file. Could you please rename the test?

[stefanopolitano]

Hi @rashigupt ! Sorry for the late response, but I think I am not getting your point. For my understanding, if you want pions and eta not coming from HF, what is the point of using gap trigger to include ccbar/bbbar events?

[rashigupt]

Hello @rashigupt , I see from your PR that you have GeneratorHF_Non_Hfe_enhance.ini, but GeneratorHF_Non_Hfe.C as test. This will not work because the CI will check a .C macro named in the same way as your ini file. Could you please rename the test?

ok

[rashigupt]

Hi @rashigupt ! Sorry for the late response, but I think I am not getting your point. For my understanding, if you want pions and eta not coming from HF, what is the point of using gap trigger to include ccbar/bbbar events?

Hi, sorry for the late reply. You're right — using a gap trigger doesn't make sense for non-HFE pions and η. I've updated the code and created a separate file without the gap trigger for the non-HFE case.