Skip to content

Conversation

@shahor02
Copy link
Collaborator

No description provided.

@shahor02 shahor02 added async-2024-pp-apass1 Request porting to async-2024-pp-apass1 async-2024-PbPb-apass1 labels Nov 24, 2024
@github-actions
Copy link
Contributor

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-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1

@shahor02 shahor02 merged commit 83049af into AliceO2Group:dev Nov 25, 2024
7 checks passed
@shahor02 shahor02 deleted the pr_AltroSyncSignal2map branch November 25, 2024 14:30
@chiarazampolli
Copy link
Collaborator

Hello @shahor02 ,

Why is this needed for apass1 of pp 2024? Data were already processed, and MC does not need this.

Chiara

@shahor02
Copy link
Collaborator Author

shahor02 commented Dec 5, 2024

Probably, I thought we were still processing it.

@alcaliva alcaliva removed the async-2024-pp-apass1 Request porting to async-2024-pp-apass1 label Dec 12, 2024
@alcaliva
Copy link
Collaborator

removed the label async-2024-pp-apass1 since it is not needed and it also gives conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants