You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[Developing QC modules on a machine with FLP suite](doc/Advanced.md#developing-qc-modules-on-a-machine-with-flp-suite)
103
+
*[Switch detector in the workflow <em>readout-dataflow</em>](doc/Advanced.md#switch-detector-in-the-workflow-readout-dataflow)
104
+
*[Get all the task output to the infologger](doc/Advanced.md#get-all-the-task-output-to-the-infologger)
105
+
*[Using a different config file with the general QC](doc/Advanced.md#using-a-different-config-file-with-the-general-qc)
106
+
*[Enable the repo cleaner](doc/Advanced.md#enable-the-repo-cleaner)
107
+
*[Configuration](doc/Advanced.md#configuration-1)
108
+
*[Merging multiple configuration files into one](doc/Advanced.md#merging-multiple-configuration-files-into-one)
109
+
*[Definition and access of simple user-defined task configuration ("taskParameters")](doc/Advanced.md#definition-and-access-of-simple-user-defined-task-configuration-taskparameters)
110
+
*[Definition and access of user-defined configuration ("extendedTaskParameters")](doc/Advanced.md#definition-and-access-of-user-defined-configuration-extendedtaskparameters)
111
+
*[Definition of new arguments](doc/Advanced.md#definition-of-new-arguments)
*[Understanding and reducing memory footprint](#understanding-and-reducing-memory-footprint)
33
-
*[Analysing memory usage with valgrind](#analysing-memory-usage-with-valgrind)
33
+
*[Analysing memory usage with valgrind](#analysing-memory-usage-with-valgrind)
34
34
*[CCDB / QCDB](#ccdb--qcdb)
35
35
*[Accessing objects in CCDB](#accessing-objects-in-ccdb)
36
36
*[Access GRP objects with GRP Geom Helper](#access-grp-objects-with-grp-geom-helper)
@@ -52,7 +52,8 @@ Advanced topics
52
52
*[Enable the repo cleaner](#enable-the-repo-cleaner)
53
53
*[Configuration](#configuration-1)
54
54
*[Merging multiple configuration files into one](#merging-multiple-configuration-files-into-one)
55
-
*[Definition and access of user-specific configuration](#definition-and-access-of-user-specific-configuration)
55
+
*[Definition and access of simple user-defined task configuration ("taskParameters")](#definition-and-access-of-simple-user-defined-task-configuration-taskparameters)
56
+
*[Definition and access of user-defined configuration ("extendedTaskParameters")](#definition-and-access-of-user-defined-configuration-extendedtaskparameters)
56
57
*[Definition of new arguments](#definition-of-new-arguments)
The MonitorObjects generated by Quality Control are stored in a dedicated repository (QCDB), which is based on CCDB.
771
772
The run conditions, on the other hand, are located in another, separate database.
772
-
The recommended way to access these is to use a `Lifetime::Condition` DPL input, which can be requested as in the query below:
773
+
774
+
The recommended way (excluding postprocessing) to access these conditions is to use a `Lifetime::Condition` DPL input, which can be requested as in the query below:
773
775
```json
774
776
"tasks": {
775
777
"MyTask": {
@@ -787,6 +789,10 @@ Geometry and General Run Parameters (GRP) can be also accessed with the [GRP Geo
787
789
788
790
If your task accesses CCDB objects using `TaskInterface::retrieveCondition`, please migrate to using one of the methods mentioned above.
789
791
792
+
### Accessing from a Postprocessing task
793
+
794
+
PostProcessingTasks do not take DPL inputs, so in this case `TaskInterface::retrieveCondition` should be used.
795
+
790
796
## Access GRP objects with GRP Geom Helper
791
797
792
798
To get GRP objects via a central facility, add the following structure to the task definition and set its values
- DO NOT USE `truncate` ! `truncate is unstable and any mistake can have dire consequences.
536
+
- All the scripts take the arguments `--dry-run`, `--print-list` and `--one-by-one`. Use them. Proceed with the actual deletion only, when you have thoroughly verified the output of a `print-list` and a `dry-run`
537
+
- Deletion commands can only be run on the QCDB server itself.
538
+
539
+
#### Remove all objects in a path
540
+
We use the script `o2-qc-repo-delete-time-interval` with an interval covering 0 to many years in the future.
0 commit comments