TPC: Sending Pedestal/Threshold to DCS CCDB

[wiechula]

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

[wiechula]

@sawenzel the sim test is failing with "device shutting down. Reason: CTP is Zombie" any idea?

[wiechula]

Can this be merged?

[sawenzel]

@davidrohr @chiarazampolli

[chiarazampolli]

Hello @wiechula , can you remind me if these numbers are assigned in a specific way? I mean, how did you determine them? This is probably not important since this is a pedestal run.

[wiechula]

To my understanding they are arbitrary. I used what the mean vertex task is using.
The only thing is that the subspecs used in the during snapshop need to match what is configured here.

[chiarazampolli]

Hello @wiechula ,

Thanks! Can you confirm that this is for standalone calib runs? (pedestals). Then it would not matter. I will then check, for my knowledge, if the slots should be unique (in addition to have to match, of course).

Chiara

[davidrohr]

It is in the TPC standalone calib workflow, yes

[chiarazampolli]

Thanks.