Augment and dump script consolidation
The problem
@svanstro and I noticed that there's quite a proliferation of "augment with X and dump" type top level scripts. First of all, this seems healthy: it demonstrates the flexibility of CA and using common components from AthAnalysis, and it's great if people can make simple scripts that do only what they need.
On the other hand, it's a bit sad if you have to look at the CI tests to know which config file works with which script, and sort of defeats the purpose of having a config file.
!637 (merged) (#136 (closed)) got things started with the new "ca_blocks" config key. See the initial documentation on this feature for more info.
General steps:
-
have default config keys, but make the parsing fail if there are any unused fields. -
standardise top level config keys (e.g. presence of "dumper" key) -
support multiconfig
Scripts to replace
Here is a list of scripts we can replace with blocks. Tagging the main user of each script, please consider moving to the new "blocks" approach - some examples are in !642 (merged)