You can undertake thousands of different model runs, each with varying time series inputs. This can be accomplished by running multiple instances on a single server (locally - one per CPU), or over a cluster of servers (across a network).
To undertake a batch run, you either:
- Configure the script settings directly;
- Pass a .cmd settings file to the script; or
- Run a simple GUI for editing configurations and running them.
The parameters required to configure a local batch run are summarised in Table 2.
Table 2. Parameters for Local Run Settings
| Parameter | Description | Example |
|---|---|---|
| Server.Exe | Location of the RiverSystem.CommandLine.exe that will be run for the server. This should be the same as ClientExe when running locally or a path than can be reached from the server. | \\Server\Source\RiverSystem.Commandline.exe
|
| ProjectFile | The template project file that will be run on the server. The file location (including the directory tree) will be copied multiple times and merged with the directories from InputDir. | \ExampleMasterProject\Batch.rsproj |
| ProjectDestinationDir | The working location that should be accessible from the Server and client machines. Files from the InputDir will be copied to this location to change input files. | \\Server\Volume_1\ExampleProjectLoadLocation |
| InputDir | Contains a directory for each run. Files that change should be in these directories, and are copied to the ProjectDestinationDir during a run. | |
| OutputDir | The location that output files from runs are saved in the form Result_nameOfInputDir. | |
| NumServers | The number of servers that will be started for the job to be distributed over. |
The example contains a number of files and folders and a small example project that was built in 3.6.3beta.
An example can be downloaded here: Example Batch Run scripts using Source 3.6.3beta