remove config.yaml

[meiertgrootes]

No description provided.

[meiertgrootes]

@SarahAlidoost @vmgaribay @vanlankveldthijs During our meeting we discussed removing the config.yaml file, because the default values (which are what is generally being used) are implemented in config.py.

However, we have retained the ability to initialize from a yaml file. This makes sense, certainly in the case of running different scenarios/models.

Maybe we should rename config.yaml to config_template.yaml and highlight this in documentation

[vanlankveldthijs]

This makes sense.

However, while implementing the recent save state functionality, I didn't really like having all the default config parameters duplicated in config.py and config.yaml.
Any time a config parameter is renamed, or moved between the main config and the steering parameters, it had to be updated in both places.

If we want to keep a config template file, we may want to make it a deliberately slimmed down set of parameters.

[SarahAlidoost]

To avoid maintaining two separate sets of configurations (config.py and config.yaml), we could allow users to generate the config template file as needed. For example, util.get_config_template(cfg_filename) could be used to generate a template based on the values in config.py. The functionality to_yaml() already exists; see the example.