FIT: MC digitizer settings for 2024

[andreasmolander]

Temporary gain settings for 2024 MC. Will be reverted once we can take this from CCDB.

[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

[andreasmolander]

+async-label async-2024-pp-apass1, async-2024-pp-cpass0, async-2024-PbPb-apass1, async-2024-ppRef-apass1, async-2024-PbPb-apass2

[sawenzel]

@andreasmolander : We probably do not need these back-portings for MCs using the 2-tag approach (https://aliceo2group.github.io/simulation/docs/o2dpgworkflow/anchored.html?highlight=anchorMC#the-2-software-tag-approach-for-anchored-mc-productions)

How urgent is this, and for whom? Can't we wait for this to come from CCDB?

[andreasmolander]

Hi @sawenzel my guess is that this is not urgent at all to be honest. I would have to double check with the rest of the team. Actually I think we can adjust the labels so that you don't need to cherry pick or back port anything, it's fine if it's included naturally the next time you checkout from or rebase onto the master branch. So that means no labels?

Unfortunately I cannot give an estimate for when we can take these from CCDB, so I would still like to include this. Our JIRA ticket for getting these from CCDB is blocked by a ticket to revert these temporary solutions, so it should not be forgotten.