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
Generic post-processing task for quality objects (#1689)
* Added generic post-processing task for quality objects
- the task provides trending of user-defined quality flags as well as a summary in human-readable format in a dedicated canvas
- added task and task configuration helper class
- added example in postprocessing.json
- added task description in PostProcessing documentation
* Combine features of QualityTask and QualityObserver
Some of the decisions I took:
- I used the dataSources key to list all the input objects groups
- The aggregated quality is treated like any other quality. To reproduce the previous behaviour one can put it first in the global list of input objects groups.
- All input objects may have additional comments which depend on the quality, which allows to still get the old behaviour for the aggregated quality, but also for any other (which would be asked for anyway at some point, I believe).
- the inputObjects list contain separate JSON objects with all the possible keys for easier extensibility of configuration while letting users skip some optional fields.
- when a QO cannot be retrieved, we still print the corresponding line, so this fact is known
- input object groups get both a title and a name. The name is used for paths in QCDB to corresponding trends and histograms
- observeDetails and qualityDetailChoice was reduced to ignoreQualitiesDetails, since an empty list would be in fact equal to "observeDetails" : "true" with all qualities listed, so does not using this setting at all. The parameter is per group and an actual JSON list is used, to avoid errors in parsing.
- timestamps are kept separate to configuration, since they are state, not configuration.
* fix sharing the same quality across multiple groups
* add missing picture
---------
Co-authored-by: Piotr Konopka <piotr.jan.konopka@cern.ch>
0 commit comments