Simulation file and Config object have been updated to change the simulation configuration file. This improves the following:
The workflow files were linked directly in the observation schedule. This is not necessary, and in fact makes observation generation harder, as the workflows have to be generated at the same time as a result. Now, workflows are stored in a separate 'pipelines' section of the JSON file, and each observation (which has a name identifier) is allocated its workflow in this section.
Various parameters are more useful when defined using the Simulation object constructor. For example, if we want to loop through multiple planning algorithms, we can run simulations in a loop with the same config file, rather than using multiple config files.
Simulation file and
Configobject have been updated to change the simulation configuration file. This improves the following:nameidentifier) is allocated its workflow in this section.Simulationobject constructor. For example, if we want to loop through multiple planning algorithms, we can run simulations in a loop with the same config file, rather than using multiple config files.