Generalized "Runner"
kireet opened this issue · 0 comments
An experiment is defined by a json file. If you want to run many variations of your model, it may be hard to manage if you have to create almost identical copies of the json file for each variant.
Instead we could imagine having a single general, parameterized json file and then multiple configurations in order to run experiments. To do so effectively, the json structure should remain the same across all variants.
This may mean that pre-built components should have an enabled/disabled flag. So that even if they are included in an experiment, they can be disabled easily via a parameter.
Additionally we can have a "runner" class that can take in a json and config file and run the experiment once for each config with some reports. For now the runner can run the experiments sequentially on a machine, but we could imagine people writing more advanced launchers to do things in parallel.