From 45ec0f34bde59a6fe1f83397de2413a3c43327b8 Mon Sep 17 00:00:00 2001 From: Piotr Konopka Date: Fri, 24 Nov 2023 09:41:37 +0100 Subject: [PATCH] Allow for TFID == 0 in async QC timekeeping for testing purposes 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) --- Framework/src/TimekeeperAsynchronous.cxx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Framework/src/TimekeeperAsynchronous.cxx b/Framework/src/TimekeeperAsynchronous.cxx index ef1c66f856..360428fc43 100644 --- a/Framework/src/TimekeeperAsynchronous.cxx +++ b/Framework/src/TimekeeperAsynchronous.cxx @@ -45,10 +45,10 @@ void TimekeeperAsynchronous::updateByTimeFrameID(uint32_t tfid) } if (tfid == 0) { if (!mWarnedAboutTfIdZero) { - ILOG(Warning, Devel) << "Seen TFID equal to 0, which is not expected. Will not update TF-based validity, will not warn further." << ENDM; + ILOG(Warning, Support) << "Seen TFID equal to 0, which is not expected in production data. Will use 1 instead, will not warn further." << ENDM; mWarnedAboutTfIdZero = true; + tfid = 1; } - return; } auto tfValidity = computeTimestampFromTimeframeID(tfid);