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
* [QC-1037] IncreasingEntries: tolerate a number of bad cycles
* [QC-1037] IncreasingEntries: tolerate a number of bad cycles
* Update Modules/Common/src/IncreasingEntries.cxx
Co-authored-by: Piotr Konopka <piotr.jan.konopka@cern.ch>
* change name of parameter
* doc
* fix format
* format
---------
Co-authored-by: Piotr Konopka <piotr.jan.konopka@cern.ch>
Copy file name to clipboardExpand all lines: doc/Advanced.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1478,7 +1478,7 @@ One can also enable publishing metrics related to CPU/memory usage. To do so, us
1478
1478
1479
1479
## Common check `IncreasingEntries`
1480
1480
1481
-
This check make sures that the number of entries has increased in the past cycle. If not it will display a pavetext
1481
+
This check make sures that the number of entries has increased in the past cycle(s). If not, it will display a pavetext
1482
1482
on the plot and set the quality to bad.
1483
1483
1484
1484
If you use `SetBinContent` the number of entries does not increase creating a false positive. Please call `ResetStats()`
@@ -1491,6 +1491,18 @@ The behaviour of the check can be inverted by setting the customparameter "mustI
1491
1491
}
1492
1492
```
1493
1493
1494
+
The number of cycles during which we tolerate increasing (or not respectively) the number of entries can be set with the custom parameter `nBadCyclesLimit`:
1495
+
```
1496
+
"extendedCheckParameters": {
1497
+
"default": {
1498
+
"default": {
1499
+
"nBadCyclesLimit": "3",
1500
+
}
1501
+
}
1502
+
}
1503
+
```
1504
+
In the example above, the quality goes to bad when there are 3 cycles in a row with no increase in the number of entries.
1505
+
1494
1506
## Update the shmem segment size of a detector
1495
1507
1496
1508
In consul go to `o2/runtime/aliecs/defaults` and modify the file corresponding to the detector: [det]_qc_shm_segment_size
0 commit comments