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

Base: allow to create alignment for individual detectors other than ITS #13896

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

f3sch
Copy link
Collaborator

@f3sch f3sch commented Jan 23, 2025

Previously the matcher would stop at the first not found binding, e.g. ITS.
Meaning one could request alignment only for lower provenance detectors like TPC&TRD&TOF, which does not really make sense generally, but for IT3 it does.

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

@shahor02 shahor02 merged commit 95d419d into AliceO2Group:dev Jan 23, 2025
11 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants