Removing obsolete code, EOD is handled by DPL

Sending of control events in the TPCSector header has been removed from
all workflows a while ago.

Author: matthiasrichter

Detectors/GlobalTrackingWorkflow/src/TPCITSMatchingSpec.cxx

@@ -96,19 +96,6 @@ void TPCITSMatchingDPL::run(ProcessingContext& pc)
       throw std::runtime_error("sector header missing on header stack");
     }
     const int& sector = sectorHeader->sector();
-    // check the current operation, this is used to either signal eod or noop
-    // FIXME: the noop is not needed any more once the lane configuration with one
-    // channel per sector is used
-    if (sector < 0) {
-      if (operation < 0 && operation != sector) {
-        // we expect the same operation on all inputs
-        LOG(ERROR) << "inconsistent lane operation, got " << sector << ", expecting " << operation;
-      } else if (operation == 0) {
-        // store the operation
-        operation = sector;
-      }
-      continue;
-    }
     // the TPCSectorHeader now allows to transport information for more than one sector,
     // e.g. for transporting clusters in one single data block. For the moment, the
     // implemenation here requires single sectors
@@ -126,11 +113,6 @@ void TPCITSMatchingDPL::run(ProcessingContext& pc)
     datarefs[sector] = ref;
   }
 
-  if (operation == -1) {
-    // EOD is transmitted in the sectorHeader with sector number equal to -1
-    LOG(WARNING) << "operation = " << operation;
-  }
-
   auto printInputLog = [&validSectors, &activeSectors](auto& r, const char* comment, auto& s) {
     LOG(INFO) << comment << " " << *(r.spec) << ", size " << DataRefUtils::getPayloadSize(r) //
               << " for sector " << s                                                         //

Detectors/GlobalTrackingWorkflow/tpcinterpolationworkflow/src/TPCInterpolationSpec.cxx

@@ -67,19 +67,6 @@ void TPCInterpolationDPL::run(ProcessingContext& pc)
       throw std::runtime_error("sector header missing on header stack");
     }
     const int& sector = sectorHeader->sector();
-    // check the current operation, this is used to either signal eod or noop
-    // FIXME: the noop is not needed any more once the lane configuration with one
-    // channel per sector is used
-    if (sector < 0) {
-      if (operation < 0 && operation != sector) {
-        // we expect the same operation on all inputs
-        LOG(ERROR) << "inconsistent lane operation, got " << sector << ", expecting " << operation;
-      } else if (operation == 0) {
-        // store the operation
-        operation = sector;
-      }
-      continue;
-    }
     // the TPCSectorHeader now allows to transport information for more than one sector,
     // e.g. for transporting clusters in one single data block. For the moment, the
     // implemenation here requires single sectors
@@ -97,11 +84,6 @@ void TPCInterpolationDPL::run(ProcessingContext& pc)
     datarefs[sector] = ref;
   }
 
-  if (operation == -1) {
-    // EOD is transmitted in the sectorHeader with sector number equal to -1
-    LOG(WARNING) << "operation = " << operation;
-  }
-
   auto printInputLog = [&validSectors, &activeSectors](auto& r, const char* comment, auto& s) {
     LOG(INFO) << comment << " " << *(r.spec) << ", size " << DataRefUtils::getPayloadSize(r) //
               << " for sector " << s                                                         //