## Current state of the `validate_config` function: - able to - somewhat - traverse the yaml and merge it with defaults - throw warnings at `USER` keyword + set it to `None` - throw error at `__USER__` keyword - test for paths, if parameter in corresponding list ## Issues: - code rather verbose and hard to maintain - keyword `USER` always set to None -> might be better to set more sensible defaults ## Ideas: - check, if input is correct, e.g. numbers in range, string sensible etc., not just the paths - better handling of optional params
