Giovanna summary on the conf model for EHN1 (translation from Italian by Marco)
- We will need a compromise between the 10000 versions of the configurations we need to maintain and what the shifters can do
- It is reasonable to ask the shifters to enable/disable detector parts (e.g. PDS, un CRP, CTB, ...) and enable/disable TPG
- One configuration can cover all the combinations. For these simple tasks we already have tools for
- A configuration viewer (like the one developed by Alessandro) becomes a requirement so that it's clear what is enabled and disabled
- We cannot ask the shifter to change things like trigger configuration. This is due to the tools we have at our disposal right now, things might change in the future. For this we will need different configurations for every different configuration (thresholds, algorithm chains, etc).
- About the connection between DAQ version and configuration, we should put some boundaries:
- Changes in the configuration schema should at least imply a change in the minor version of the DAQ. We should not change schema in a patch.
John
- Automated display of OKS configurations (examples in the material)
- Can be put automatically in the documentation when we build or generate the doc
- Marco can help testing on other configurations
- Pierre: Where do we go from here?
- John: unclear, this is a prototype
Gordon
- PR in confmodel:
- Added get_all_enabled_applications (no need to use get_all_application and check for enabled anymore).
- Enhanced list-app script (need to compare it with Alessandro's python script)
- Bugfixes in DBE