C.A. Based Configuration of Trigger Cost Mon
This MR adds two types of configuration for online-style execution of trigger cost monitoring on data or MC (but would not be used e.g. for a MC campaign).
-
newJOtest.py
callstriggerRunCfg
which calls and mergesTrigCostMonitorMTCfg
. This is the preferred setup. - A non-ComponentAccumulator setup is provided in
full_menu.py
full_menu.py
is not yet tested due to a strange crash, but as I've already merged from upstream today, I will wait to debug this in tomorrow's nightly.
NOTE: Small change to the ComponentAccumulator logic. Ping @wlampl & @emoyse
I was triggering this throw
AthenaConfiguration.Deduplication.DeduplicationFailed: AppMgr property AuditAlgorithms set twice: True and True
As this property is set True
by my new code below and also by https://acode-browser.usatlas.bnl.gov/lxr/source/athena/Control/AthenaConfiguration/python/MainServicesConfig.py#0157 . So long as all C.As agree on how they need to set a property of theApp
, then I don't think this is an error. Hence have added a check against ==
in ComponentAccumulator.py
.