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 retrieving latest QOs in QualityTask (#2416)
* [COMMON] allow retrieving latest QOs in QualityTask
Instead of retrieving the QOs based on the time stamp of the update trigger,
the latest version of the QOs is retrieved, even if their validities are
ending before the update time stamp.
A `maxObjectAgeSeconds` configuration parameter allows to consider only
QOs that were created not more than a given number of seconds before the
time at which the `update()` function was called.
* [COMMON] updated QualityTask documentation
Copy file name to clipboardExpand all lines: doc/PostProcessing.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -730,6 +730,8 @@ A **title** can be added, which is used in the summary canvas to denote given Qu
730
730
If it is absent, **name** is used instead.
731
731
Optionally, one can add **messageBad**, **messageMedium**, **messageGood**, **messageNull** to add a message when a particular Quality is seen.
732
732
733
+
At each update, the task retrieves the latest version of each input QualityObject, even if their validity range ends in the past. A task configuration parameter, called `maxObjectAgeSeconds`, allows to define the maximum allowed age (in seconds) of the retrieved objects. The age is defined as the difference between the the time stamp of the task update and the creation time stamp of the retrieved object.
734
+
733
735
Here is a complete example of `QualityTask` configuration:
734
736
```json
735
737
{
@@ -743,6 +745,9 @@ Here is a complete example of `QualityTask` configuration:
0 commit comments