The tool currently supports two distinct yaml configuration formats:
- Run config (batch trace processing), parsed by
config.load_config
- Post-summary config (summarising existing results), parsed by
postprocess.load_post_runs_config
While the schemas are intentionally different but they did the same thing:
- reading the same yaml structure -
default_settings and runs
- doing similar validations
Hence it leads to duplicated parsing across the package, increased maintenance cost when extending the config behaviour and increased risk of inconsistency handling over time.
The tool currently supports two distinct yaml configuration formats:
config.load_configpostprocess.load_post_runs_configWhile the schemas are intentionally different but they did the same thing:
default_settingsandrunsHence it leads to duplicated parsing across the package, increased maintenance cost when extending the config behaviour and increased risk of inconsistency handling over time.