Config: Section Based Config Files

Allow users to define network configs through references to section-specific configs. This means that a user can create a config file for specific data sources, for example, and swap between sources by changing a single line.

Example:

Before

application_config.ini

[image_input]
path_to_search = /a/long/path
filename_contains = t2
filename_not_contains = ._
spatial_window_size = (64, 64, 32)

[NETWORK]
name=vae
decay = 1e-7
reg_type = L2
batch_size = 50
normalisation = False
whitening = False

[TRAIN]
...

[INFERENCE]
...

After

application_config.ini

[image_input]
config=image_dataset_x.ini

[NETWORK]
name=vae
decay = 1e-7
reg_type = L2
batch_size = 50
normalisation = False
whitening = False

[TRAIN]
...

[INFERENCE]
...

image_dataset_x.ini

path_to_search = /a/long/path
filename_contains = t2
filename_not_contains = ._
spatial_window_size = (64, 64, 32)

This work appears to have been done, at least in part, as part of 168-migrate-configuration-files-to-yaml. I'm not sure as of writing this page whether this branch extends that functionality to ini files, as in the above examples.