...
The next example runs the project from start to finish and puts all recorded values in the file ‘test.csv’.
| Code Block |
|---|
>RiverSystem.CommandLine.exe -p "C:\ProjectDir\test.rsproj" -o test.csv Loading 100% Meta-Parameters: + $inflow + Forest\Catchment for node #2\Quick Flow\Flow + Straight-Through Routing\Default Link #1\Upstream Flow Volume + Straight-Through Routing\Default Link #1\Downstream Flow Volume + Straight-Through Routing\Default Link #1\Mass Balance + Inflow\Inflow 1\Upstream Flow Volume + Inflow\Inflow 1\Downstream Flow Volume + Inflow\Inflow 1\Inflow Volume + Inflow\Inflow 1\Mass Balance + Gauge\Gauge 2\Upstream Flow Volume + Gauge\Gauge 2\Mass Balance + Global Expressions\$inflow\Value Running 100% |
...
Display option commands | Function | Example |
|---|---|---|
-p, --project | Path to project, or project name on server followed by these optional parameters: scenario within that project, start and end times, name of data input set | -p "projectName.rsproj" or -p "c:\somePath\projectName.rsproj;someScenarioName;1/1/2011;31/12/2011;dry" |
-m, --mode | Application mode Client/Server/InProcess. | -m Client or -m Server |
-d, --directory | Directory in which to look for projects. | -d "c:\ProjectFiles" |
-o, --output | File to save output into. The extension selects the output format based on the standard TIME I/O formats. A directory of the name specifed will be created if the format only supports a single time series. | -o "output.csv" for CSV or -o "output.nc" for NetCDF etc. |
-r, --results | Which results to return. This can appear multiple times. Results requested need to already be set to record in the project file. This option only allows you to reduce the number of results saved out. When this option isn't used, all recorded results are saved into the output file specified. To check the name needed, save out the result and the name to use is the column name for the time series. | -r "someResult" -r "someOtherResult" |
-v, --value | Set value of meta-parameter or internal setting. | -v "$metaparam=25", or -v "$anotherMetaParam=2.3" |
-s, --step | Number of time-steps to run. | --step 1 |
-t, --reset | Reset the loaded project. | |
-e, --timeout | Operation timeout for WCF service in seconds. | -e 2000 |
-b, -baseSIUnits | Ignore units set within project and output base SI units | |
-a, --address | Address for server to create, or client to connect. | -a "net.pipe://localhost/PipeReverse" or "net.tcp://localhost:8523/eWater/Services/RiverSystemService" |
PEST calibration using the command line
PEST (Parameter ESTimation and uncertainty analysis) allows analysis of complex environmental models, and can be used in Source for calibration of catchments. You can use the command line to do calibration and uncertainty in a catchments model. The steps to do the calibration are as follows:
- Starting with a Source Catchment project file, use the new calibration tool to set up ‘global expressions’ for the parameters of the rainfall runoff models. When defining the metaparameters in the Calibration Wizard, the list of Existing Metaparameters will be used in the parameter file for invoking riversystem.commandline;
- Turn on any recorders for the hydrological quantities that will be used in the objective function. In step 4 of the Calibration Wizard, choose Manual optimisation and enable Create global expressions for use from an external tool;
- Save the project;
- Set up the Riversystem.Commandline input file;
- Setup the PEST input and template files;
- Prepare a batch file to invoke the commandline and pre-processors; and
- Run PEST.
Once the Calibration wizard has been set up, start the command line server (riversystem.commandline -p projectname.rsproj -m server) and then PEST (pest pestcontrolfile.pst).
Batch running using the command line
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Please see Batch running using the command line in the Source community for details and an example.