Pre-process analysis settings if multiple timepoints are being considered
lhc_process_sample_run_subsets_overTime(FILEPATH, SPARTAN_PARAMETER_FILE,
PARAMETERS, NUMSAMPLES, NUMRUNSPERSAMPLE, MEASURES, RESULTFILENAME,
ALTFILENAME, OUTPUTCOLSTART, OUTPUTCOLEND, LHC_ALL_SIM_RESULTS_FILE,
TIMEPOINTS, TIMEPOINTSCALE)Directory where the simulation runs of single CSV file can be found
Location of the file output by the latin-hypercube sampling method. Note if providing a single CSV file with parameter/response pairings, you do not need to provide this file, and can thus enter this parameter as NULL.
Array containing the names of the parameters of which parameter samples will be generated
The number of parameter subsets that were generated in the LHC design. Only required if analysing results provided within Folder structure setup.
The number of runs performed for each parameter subset. This figure is generated through Aleatory Analysis. Only required if analysing results provided within Folder structure setup.
Array containing the names of the output measures which are used to analyse the simulation
Name of the simulation results file. In the current version, XML and CSV files can be processed. If performing this analysis over multiple timepoints, it is assumed that the timepoint follows the file name, e.g. trackedCells_Close_12.csv.
In some cases, it may be relevant to read from a further results file if the initial file contains no results. This filename is set here. In the current version, XML and CSV files can be processed.
Column number in the simulation results file where output begins - saves (a) reading in unnecessary data, and (b) errors where the first column is a label, and therefore could contain duplicates.
Column number in the simulation results file where the last output measure is.
Name to be given to the CSV file that summarises all simulation runs for all parameter sets
Implemented so this method can be used when analysing multiple simulation timepoints. If only analysing one timepoint, this should be set to NULL. If not, this should be an array of timepoints, e.g. c(12,36,48,60)
Implemented so this method can be used when analysing multiple simulation timepoints. Sets the scale of the timepoints being analysed, e.g. "Hours"