You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Motivations

Details

In dataMonitoring/Common Common-06-10-00 there's a first attempt at a piece of code to be run in the pipeline.

It takes the digi and merit trending root files for a given run and the basic usage is:

Usage: pBadTimeIntervalLogger.py [options] digitrend merittrend

Options:
  -h, --help            show this help message and exit
  -r R, --root-output=R
                        path to the output root file
  -i, --interactive     run in interactive mode (show the plots)
  -p P, --png-output=P  path to the output png file
  -x X, --xml-output=X  path to the output xml file
  -f F, --flare-threshold=F
                        threshold on the normalized ACD hit rate for the flare
                        intervals
  -c C, --count-threshold=C
                        threshold on the normalized ACD tile count for the bad
                        time intervals
  -t T, --min-time-padding=T
                        minimum time padding (in s) for fitting the normalized
                        transient rate outside any flare interval
  -M M, --min-int-loss=M
                        minimum integral loss (in s) for defining a bad time
                        interval
  -m M, --min-diff-loss=M
                        minimum differential loss for defining a bad time
                        interval
  -s S, --int-loss-start=S
                        integrated loss (in s) defining the start of a bad
                        time interval
  -e E, --frac-loss-end=E
                        fraction of the total integrated loss defining the end
                        of a bad time interval
  -n N, --num-plateau-points=N
                        number of points for the evaluation of the total
                        integrated loss
Usage: pBadTimeIntervalLogger.py [options] digitrend merittrend

Test procedure

  • No labels