[QC-304] TrendingTask - specify multiple data source objects under the same path (#352)

* TrendingTask - specify multiple data source objects under the same path

* clang format

Author: knopers8

Framework/postprocessing.json

@@ -47,14 +47,14 @@
           {
             "type": "repository",
             "path": "qc/TST/QcTask",
-            "name": "example",
+            "names": [ "example" ],
             "reductorName": "o2::quality_control_modules::common::TH1Reductor",
             "moduleName": "QcCommon"
           },
           {
             "type": "repository-quality",
             "path": "qc/checks",
-            "name": "QcCheck",
+            "names": [ "QcCheck" ],
             "reductorName": "o2::quality_control_modules::common::QualityReductor",
             "moduleName": "QcCommon"
           }

Framework/src/TrendingTaskConfig.cxx

@@ -30,11 +30,24 @@ TrendingTaskConfig::TrendingTaskConfig(std::string name, configuration::Configur
                       plotConfig.second.get<std::string>("option", "") });
   }
   for (const auto& dataSourceConfig : config.getRecursive("qc.postprocessing." + name + ".dataSources")) {
-    dataSources.push_back({ dataSourceConfig.second.get<std::string>("type", "repository"),
-                            dataSourceConfig.second.get<std::string>("path"),
-                            dataSourceConfig.second.get<std::string>("name"),
-                            dataSourceConfig.second.get<std::string>("reductorName", ""),
-                            dataSourceConfig.second.get<std::string>("moduleName", "") });
+    if (const auto& sourceNames = dataSourceConfig.second.get_child_optional("names"); sourceNames.has_value()) {
+      for (const auto& sourceName : sourceNames.value()) {
+        dataSources.push_back({ dataSourceConfig.second.get<std::string>("type", "repository"),
+                                dataSourceConfig.second.get<std::string>("path"),
+                                sourceName.second.data(),
+                                dataSourceConfig.second.get<std::string>("reductorName"),
+                                dataSourceConfig.second.get<std::string>("moduleName") });
+      }
+    } else if (!dataSourceConfig.second.get<std::string>("name").empty()) {
+      // "name" : [ "something" ] would return an empty string here
+      dataSources.push_back({ dataSourceConfig.second.get<std::string>("type", "repository"),
+                              dataSourceConfig.second.get<std::string>("path"),
+                              dataSourceConfig.second.get<std::string>("name"),
+                              dataSourceConfig.second.get<std::string>("reductorName"),
+                              dataSourceConfig.second.get<std::string>("moduleName") });
+    } else {
+      throw std::runtime_error("No 'name' value or a 'names' vector in the path 'qc.postprocessing." + name + ".dataSources'");
+    }
   }
 }
 

Framework/test/testTrendingTask.json

@@ -39,7 +39,7 @@
           {
             "type": "repository-quality",
             "path": "qc/checks/TST",
-            "name": "testTrendingTaskCheck",
+            "names": [ "testTrendingTaskCheck" ],
             "reductorName": "o2::quality_control_modules::common::QualityReductor",
             "moduleName": "QcCommon"
           }

doc/PostProcessing.md

@@ -167,7 +167,7 @@ As this class is a post-processing task, it inherits also its configuration JSON
 }
 ```
 
-Data sources are defined by filling the corresponding structure, as in the example below. For the key `"type"` use the value `"repository"` if you access a Monitor Object and `"repository-quality"` if that should be a Quality (this will be unified in the future). The fields `"path"` and `"name"` should point to the object in the repository. The values of `"reductorName"` and `"moduleName"` should point to a full name of a data Reductor and a library where it is located. One can use the Reductors available in the `Common` module or write their own by inheriting the interface class.
+Data sources are defined by filling the corresponding structure, as in the example below. For the key `"type"` use the value `"repository"` if you access a Monitor Object and `"repository-quality"` if that should be a Quality (this will be unified in the future). The `"names"` array should point to one or more objects under a common `"path"` in the repository. The values of `"reductorName"` and `"moduleName"` should point to a full name of a data Reductor and a library where it is located. One can use the Reductors available in the `Common` module or write their own by inheriting the interface class.
 
 ``` json
 {
@@ -176,14 +176,14 @@ Data sources are defined by filling the corresponding structure, as in the examp
           {
             "type": "repository",
             "path": "qc/TST/QcTask",
-            "name": "example",
+            "names": [ "example" ],
             "reductorName": "o2::quality_control_modules::common::TH1Reductor",
             "moduleName": "QcCommon"
           },
           {
             "type": "repository-quality",
             "path": "qc/checks",
-            "name": "QcCheck",
+            "names": [ "QcCheck" ],
             "reductorName": "o2::quality_control_modules::common::QualityReductor",
             "moduleName": "QcCommon"
           }