Where do take the config from in what order?

There are many config files around and it is not really clear what the final chip/daq config will be:

• testbench.yaml with overwrites to chip config and scan configuration
• scan_configuration in the scan
• Parameters in scan.scan(), scan.configure(), scan.start() calls
• Changes in scan.configure() step
• Parameters in the command line interface
• mask_file concept
• rd53a_default.cfg.yaml chip config
• Previous (successful) scans
• h5 file or cfg.yaml. Where are the mask files?

We want:

• Chaining scans (seperate calls and meta scans)
• Storing all info to reproduce scan
• Easy change of chip parameters

Proposal:

1. h5-file with masks (fallback to std. config with std. mask) or provide explicitly
2. Scan config with:
   • Scan pars (per chip)
   • Chip pars overwrite
3. Configure step overwrites

Disadvantages:

• Maybe big config file
• Not editable cfg file