Files required for an O2DPG production of prompt-photon MC, with a ga…

[smaff92]

…p trigger

[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

[smaff92]

Some additional information:

So prompt_gamma_gap calls Jaime's script directly, but it swaps out the HardQCD cfg with a PromptPhoton cfg. This means that we are still running the jet hooks on this one; we require a single jet at midrapidity.

hook_prompt_gamma_gap.ini instead calls a modified version of the jeje script, which swaps out the jet hook for a photon hook. So it only saves events which have a photon in the emcal acceptance.

The idea is that the former will be more of a general purpose production with full azimuthal acceptance, and the latter a more focused production only storing emcal triggers

[smaff92]

Apologies, forgot to mention which passes I want this to be anchored to:

+async-label async-2023-pp-apass4, async-2024-pp-apass1, async-2022-pp-apass7