The output files from running multiple optimisations are currently saved in a folder within the location folder. A new file structure is proposed which separates the location-specific files into three categories:
inputs, which are files that are solely modified by the user such as location data and utilisation profiles;
auto_generated, which are files that CLOVER auto-generates as part of its operation, such as the solar profiles and load profiles, which the user may wish to view but which aren't a "final" output of CLOVER, i.e., they may be read in again by CLOVER at a later stage;
and outputs, which are files that are solely outputted by CLOVER's simulation and optimisation runs, along with the various plots generated by the analysis module. These files aren't read in again by CLOVER apart from the purpose of generated plots and data analysis.
The output files from running multiple optimisations are currently saved in a folder within the location folder. A new file structure is proposed which separates the location-specific files into three categories:
inputs
, which are files that are solely modified by the user such as location data and utilisation profiles;auto_generated
, which are files that CLOVER auto-generates as part of its operation, such as the solar profiles and load profiles, which the user may wish to view but which aren't a "final" output of CLOVER, i.e., they may be read in again by CLOVER at a later stage;outputs
, which are files that are solely outputted by CLOVER's simulation and optimisation runs, along with the various plots generated by theanalysis
module. These files aren't read in again by CLOVER apart from the purpose of generated plots and data analysis.