From 3311a243d97149955fd398a734a1933b617bb752 Mon Sep 17 00:00:00 2001 From: Piotr Konopka Date: Fri, 24 May 2024 13:49:00 +0200 Subject: [PATCH] QC-1178 window length should be infinite if moving windows are not used This is an optimization to avoid having QC tasks on grid publish objects often than needed, i.e. when they don't use moving windows, it's enough to publish them at end of stream. --- Framework/src/TaskRunner.cxx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Framework/src/TaskRunner.cxx b/Framework/src/TaskRunner.cxx index c395d7529c..dd7c020b21 100644 --- a/Framework/src/TaskRunner.cxx +++ b/Framework/src/TaskRunner.cxx @@ -149,7 +149,8 @@ void TaskRunner::init(InitContext& iCtx) // setup timekeeping mDeploymentMode = DefaultsHelpers::deploymentMode(); - mTimekeeper = TimekeeperFactory::create(mDeploymentMode, mTaskConfig.cycleDurations.back().first * 1000); + auto windowLengthMs = mTaskConfig.movingWindows.empty() ? 0 : (mTaskConfig.cycleDurations.back().first * 1000); + mTimekeeper = TimekeeperFactory::create(mDeploymentMode, windowLengthMs); mTimekeeper->setCCDBOrbitsPerTFAccessor([]() { // getNHBFPerTF() returns 128 if it does not know, which can be very misleading. // instead we use 0, which will trigger another try when processing another timeslice.