Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

porting of MID aQC workflow to MC #1531

Merged
merged 1 commit into from
Mar 14, 2024

Conversation

lmassacr
Copy link
Contributor

No description provided.

Copy link

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-2022-pp-apass4
async-2023-pbpb-apass
async-2023-pp-apass1
async-data
async-mc
async-2022-pp-apass6

@benedikt-voelkel
Copy link
Contributor

Looks good to me.
Are there any other comments from you @JianLIUhep @chiarazampolli ?

@lmassacr should this be included in the next tag for productions? E.g. PbPb apass3?

@JianLIUhep
Copy link
Contributor

It's fine with me as well. No further comments on my side.

@lmassacr
Copy link
Contributor Author

Hi @benedikt-voelkel,

It can be included in any tag that will be used for MC production starting from now. However there is no emergency as we don't have yet a realistic Muon detector description in simulations.

I am working now on the porting of aQC for MCH as well.

Thanks,
Laure

@benedikt-voelkel benedikt-voelkel added async-2023-pbpb-apass async-2023-pbpb-apass4 Request porting to async-2023-pbpb-apass4 mc labels Mar 14, 2024
@benedikt-voelkel benedikt-voelkel merged commit cb357d0 into AliceO2Group:master Mar 14, 2024
7 checks passed
@chiarazampolli
Copy link
Collaborator

Hello @lmassacr , @benedikt-voelkel ,

Does this need updated QC?

If so, we need to ask @Barthelemy .

@benedikt-voelkel : why did you add async-2023-pp-apass1? We are now running apass3.

Chiara

@benedikt-voelkel
Copy link
Contributor

@chiarazampolli sorry for the additional label. I will remove it. I thought at this point that we would use it for pp 2023 in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants