v0.19.3

• Advanced random data producer
• Documentation

v0.19.2

• Fix last warning

v0.19.1

Fix the missing override in a test.

v0.19.0

New features

• Add version as metadata to objects.
• Post-processing framework.
• CCDB cleaner : Add a policy that does nothing to spare some folders.
• Dummy database implementation for benchmarks.

Bug fixes

• Fix the path to consul

Detectors code

• Adding projections for EMCAL and DCAL, first checkers.

v0.18.3

• Print version number
• Fix test in TPC
• Add new streamerinfos to be able to open MO v4.

v0.18.2

• TPC module
• Tests
• Allow to specify a full path of a library

v0.18.1

Fix a test.

v0.18.0

Features

• Storage in CCDB now uses TFiles. It enables schema evolution and lets users access the data in a ROOT session transparently.
• Addition of a detector name in the configuration of the tasks.
• The paths in CCDB is now more structured : /qc/<detector name>/<task name>/<object name>
• o2-qc-run-qc becomes o2-qc to save users a few keystrokes.
• Access CCDB data (condition and calibration) in Tasks.

Detectors' code update

• N/A

Documentation

• Quite some udpates, in particular about the storage and the quickstart.

Bug fixes

• Fix newline in new module's script that broke it on Mac.

v0.17.0: Reduce compilation time of the QC project (#219)

Features

Merging workflows.

The DPL framework now allows to merge workflows which are configured separately. This gives us a possibility to attach a QC workflow to any other processing workflows. One can do it by adding the o2-qc-run-qc executable after a pipe character '|' and passing a configuration file path. For example, our basic QC example (o2-qc-run-basic) now can be also ran as follows:

o2-qc-run-producer | o2-qc-run-qc --config json://${QUALITYCONTROL_ROOT}/etc/basic.json

Keep in mind, that having unsatisfied inputs (having no corresponding output to connect) will cause a workflow to be invalid. This might happen for example if one declares a Data Sampling Policy which cannot be satisfied. In the future we plan to have all Policies inputs optional.

New data query format in Data Sampling Policies

The following JSON structure

"dataHeaders": [
  {
    "binding": "sum",
    "dataOrigin": "TST",
    "dataDescription": "SUM"
  },
  {
    "binding": "param",
    "dataOrigin": "TST",
    "dataDescription": "PARAM"
  }
],
"subSpec": "2", 

can now be simplified to

"query" : "sum:TST/SUM/2;param:TST/PARAM/2",

We will keep the old way of configuration available for a minimum of 2 weeks, afterwards only the new format will be supported. All the code in QC (including detector code) has been updated accordingly.

Detectors' code update

Updated all the configuration files to the new Data Sampling Policy query format.

Documentation

Updated accordingly to the new features described above.

Bug fixes

Fixed DataSamplingReadoutProxy's problem of assigning forbidden subSpecs (unable to relay part).

Other

• QC build time is 12-25% faster.
• QC library has been split in order to extract the base types into a dedicated library called QualityControlTypes. This should help with reading and writing the QC data.

v0.16.0

Features

• Custom Data Sampling Conditions (details here)

Detectors' code update

• EMC
• TOF