Replicate Runner

Overview

The Replicate Runner runs a single eWater Source model multiple times using an ensemble of time-series inputs. The runner can be used, for example, to run an eWater Source model with a range of alternative climate data inputs.

There are two means of specifying the time series ensembles:

Generating variants of an existing time series using the Time Series Cycle Creator (TSCC)
Loading a set of pre-generated time series

Option 2 is not currently available for Source Cloud.

eWater Source Project Setup

To run a Replicate job, the eWater Source project must already be created with the time-series to be cycled loaded in Data Sources. It is possible to cycle a single Data Source or multiple Data Sources.

In order to be cycled, the time-series Data Sources must be configured as follows:

Reload on Run must enabled (which instructs eWater Source to reload the data from a file on disk before simulating the model).
The location of the data file must be specified as a Relative Path, and it must be in the same directory, or a sub-directory, of the eWater Source project file.
The data file must be in the CSV file format

For time series that are not to be cycled, Reload on Run must be disabled.

Once configured, the eWater Source project and CSV files (containing the time series to be replicated) must be placed in a ZIP file. The CSV files can be located in sub-directories of the eWater Source project file.

Source Cloud Job Creation

Upload Data

Click "Choose project zip" and select the .zip file that contains your Replicate project. It may take a few seconds for the file to upload.

Source Project Configuration

Table 2 lists the eWater Source project configuration options

Table 2. eWater Source project configuration options.

Configuration Option	Description
Scenario	Choose the eWater Source scenario to be run
Running Configuration	Choose which Running Configuration should be simulated

Time Series Cycle Creator (TSCC) Configuration

The TSCC generates variants (called replicates) of an existing time series by repetitively 'cycling' the start of the time series to the end. The user can choose whether the data is cycled on a daily, weekly, monthly or annual basis. Table 1 lists the TSCC parameters.

Table 1. TSCC parameters.

Parameters	Requirement	Description
Number of Replicates	Required	The number of replicates (output time-series) that will be created
Start Cycle Date	Optional	The first data date that will be used by the TSCC to generate the replicates (data prior to this date is cycled to the end of the time series before generating any replicates). This will default to the start date of the input time series, if not specified.
Start Year Replicates	Optional	The year that the replicates will be reported as starting in. (The replicates will always use the same start day and month as the input time-series.) This will default to the first year of the input time-series, if not specified.
Cycle Time Step	Optional	The interval of data that will be cycled to the end of the time-series to create the replicates. The user can choose between a daily, weekly, monthly or annual interval. Defaults to annual.

Examples

Consider a daily time-series that spans the following 10 year period: 1/01/2000, 2/01/2000, 3/01/2000, ..., 31/12/2009.

Running the TSCC with the following parameters would produce 3 replicates:

Number of Replicates = 3
Start Cycle Date = 1/01/2002
Start Year Replicates = 2010
Time Step = Annual

The start date for all the replicates would be reported as 1/01/2010 (and the end date would be 31/12/2019). The values of the replicates would be as follows:

Replicate 0: the values would correspond to the following years of the input time-series: 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2000, 2001.

Replicate 1: the first year of replicate 0 would be moved to the end. Hence, the values of replicate 1 would correspond to the following years of the input time-series: 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2000, 2001, 2002.

Replicate 2: the first year of replicate 1 would be moved to the end. Hence, the values of replicate 2 would correspond to the following years of the input time-series: 2004, 2005, 2006, 2007, 2008, 2009, 2000, 2001, 2002, 2003.

If a Monthly Time Step was used, then the values of the replicates would be as follows:

Replicate 0: the values would correspond to the following years of the input time-series: 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2000, 2001.

Replicate 1: the first month of replicate 0 would be moved to the end. Hence, the values of replicate 1 would correspond to the following months of the input time-series: Feb 2002, Mar 2002, ..., Dec 2009, Jan 2000, ..., Dec 2001, Jan 2002.

Replicate 2: the first month of replicate 1 would be moved to the end. Hence, the values of replicate 2 would correspond to the following months of the input time-series: Mar 2002, ..., Dec 2009, Jan 2000, ..., Dec 2001, Jan 2002, Feb 2002.

Queue Job

Job NameSpecify a custom name for the job

Finally, select Queue to add the Replicate Runner to the queue of jobs to be run.