| Anchor | ||||
|---|---|---|---|---|
|
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 (data prior to this data will not be used to generate replicatesdate 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 100 10 year period: 1/01/19002000, 2/01/19002000, 3/01/19002000, ..., 31/12/19992009.
Running the TSCC with the following parameters would produce 3 replicates:
- Number of Replicates = 3
- Start Cycle Date = 1/01/19102002
- Start Year Replicates = 20002010
- Time Step = Annual
The start date for all the replicates would be reported as 1/01/20002010 (and the end date would be 31/12/20892019). The values of the replicates would be as follows:
Replicate 0: the values would be the same as correspond to the following years of the input time-series from 1910 to 1999, inclusive: 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: 1911, 1912, ..., 1999, 19102003, 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: 1912, ..., 1999, 1910, 19112004, 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 be the same as correspond to the following years of the input time-series from 1910 to 1999, inclusive: 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 19102002, Mar 19102002, ..., Dec 2009, Jan 2001, ..., Dec 19992001, Jan 19102002.
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 19102002, ..., Dec 2009, Jan 2001, ..., Dec 19992001, Jan 19102002, Feb 19102002.
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.
Configure Job
Table 2 lists the configuration options for the Replicate Runner.
Table 2. Replicate Runner job configuration.
| Configuration Option | Description |
|---|---|
| General Options | |
| Scenario | Choose the eWater Source scenario to be run |
| Running Configuration | Choose which Running Configuration should be simulated |
| Job Name | Specify a custom name for the job |
| Time Series Cycle Creator Options* | |
| Number of Replicates | The number of replicates (output time-series) that will be created |
| Start Cycle Date | The first data date that will be used by the TSCC to generate the replicates . Data (data prior to this data will not be used to generate replicatesdate 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 | 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 | 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. |
Queue Job
Finally, select Queue to add the Replicate Runner to the queue of jobs to be run.