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

Allow for TFID == 0 in async QC timekeeping for testing purposes #2046

Merged
merged 1 commit into from
Nov 27, 2023

Conversation

knopers8
Copy link
Collaborator

As it has been demonstrated by a recent use case, some simulated data does not use correct TFID, having it as 0 instead. In such cases, we do not want to block the users from testing their sw, thus we allow for it and produce a warning. We overwrite TFID to 1, so it does not break the algorithm which computes the data timespan (production data starts with TFID == 1)

As it has been demonstrated by a recent use case, some simulated data does not use correct TFID, having it as 0 instead. In such cases, we do not want to block the users from testing their sw, thus we allow for it and produce a warning.
We overwrite TFID to 1, so it does not break the algorithm which computes the data timespan (production data starts with TFID == 1)
@knopers8 knopers8 requested a review from Barthelemy as a code owner November 24, 2023 08:46
@Barthelemy Barthelemy merged commit 0579659 into AliceO2Group:master Nov 27, 2023
2 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