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
[Common] allow ignoring period and pass when retrieving reference plots (#2381)
The period and pass names were always included in the QCDB queries for
retrieving the reference plots. This means that a run from a given
period and pass could not be used as reference for a different period
and/or pass, which is a strong limitation that needs to be made configurable.
The new code adds two configuration parameters that control whether the
period and/or pass names should be ignored or not in the queries (see
documentation for details).
Copy file name to clipboardExpand all lines: doc/PostProcessing.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -458,6 +458,8 @@ This post-processing task draws a given set of plots in comparison with their co
458
458
459
459
Currently the source of reference data is specified as a run-type and beam-type specific `referenceRun` number. This will be modified once a centralized way of accessing reference plots will become available in the framework.
460
460
The `notOlderThan` option allows to ignore monitor objects that are older than a given number of seconds. A value of -1 means "no limit".
461
+
The `ignorePeriodForReference` and `ignorePassForReference` boolean parameters control whether the period and/or pass names should be matched or not when querying the reference plots from the database.
462
+
A value of `"1"` (default) means that the reference plots are not required to match the period and/or pass names of the current run, while a value of `"0"` means that the reference plot is retrieved only if the corresponding period and/or pass names match those of the current run.
461
463
462
464
The input MonitorObjects to be processed are logically divided in **dataGroups**. Each group is configured via the following parameters:
463
465
*`inputPath`: path in the QCDB where the input objects are located
@@ -504,7 +506,9 @@ In the example configuration below, the relationship between the input and outpu
0 commit comments