Ideally we can identify configuration and settings files. These might be:
xml
json
yaml
ini
etc
One challenge is that some of these formats (e.g. json) might also be "data files". We could check the number of keys--it is unlikely that a json file with thousands of keys or lines would be something for a human to edit.
Typically, settings files will enable the modeler to set parameter values. Here is an example of a settings json file for DSSAT/Pythia.
Ideally we can identify configuration and settings files. These might be:
xmljsonyamliniOne challenge is that some of these formats (e.g.
json) might also be "data files". We could check the number of keys--it is unlikely that ajsonfile with thousands of keys or lines would be something for a human to edit.Typically, settings files will enable the modeler to set parameter values. Here is an example of a settings
jsonfile for DSSAT/Pythia.