Proper treatment (which means just ingoring) of DDL files in case of software trigger...
authorcvetan <cvetan@f7af4fe6-9843-0410-8265-dc069ae4e863>
Mon, 10 Mar 2008 14:20:34 +0000 (14:20 +0000)
committercvetan <cvetan@f7af4fe6-9843-0410-8265-dc069ae4e863>
Mon, 10 Mar 2008 14:20:34 +0000 (14:20 +0000)
MONITOR/root2date.cxx

index 0128370d9fbe1d12893803c84e1fd8bc3fc9e88f..c17ea5b64e47ea27630707d27451190cd185f08f 100644 (file)
@@ -41,7 +41,7 @@ int Root2Date(AliRawEvent *gdcRootEvent, unsigned char *gdcDateEvent, char *ddlD
    }
    memcpy(p, aliEquipment->GetRawData()->GetBuffer(), chunkSize=aliEquipment->GetRawData()->GetSize()); // Write Equipment payload (including CDH)
    // Write ddl files if requested by the user
-   if (ddlDir) {
+   if (ddlDir && aliEquipmentHeader->GetEquipmentSize()) {
      Int_t ddlIndex;
      Int_t detId = AliDAQ::DetectorIDFromDdlID(aliEquipmentHeader->GetId(),ddlIndex);
      char ddlFileName[256];