Scenario input sets allow you to easily keep model structure, while switching between groups of input data and parameters. These may be used to represent changeable physical attributes, such as climate, land use decisions or even proposed infrastructure characteristics. You can switch between different scenario input sets to compare the effects on a model. For example, you can have one scenario input set consisting of rainfall, inflow and evapotranspiration data for natural conditions, another for wet conditions and a third set for dry conditions.
...
- An auto-complete functionality that is activated when an accepted scenario base node is entered for the first element of the path, press Ctrl + space to get a list of available elements;
- Typing additional characters filters the auto-completion list. Pressing Items can also be selected by pressing the down arrow key ('↓');
- Once the correct element is selected, pressing Tab or Return auto-fills an element from the auto-completion list;
- Pressing the period character ('.') displays a list of valid elements for the next step in the path;
- For a valid path, pressing the equals character ('=') displays candidate values;
- Click the Insert units icon for a list of available units. Note that these are not scenario-dependent so you must choose the correct item; and
- An invalid parameter is identified with an underline (illustrated in Figure 2 for the Loss 3 node, which was deleted after the parameter was created). Acceptable parameter types are provided in Table 1.
| Info | ||
|---|---|---|
| ||
| Note: Clicking the Apply values to scenario immediately icon will override any other values specified for the same parameter elsewhere in Source for ALL all scenario runs. If disabled, the values take precedence for a single scenario run ONLY only. Also, an error appears if there is a problem with one of the parameter specifications. |
Table 1. Types of parameter values
| Parameter type | Example shown in Figure2 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Boolean | True | ||||||||
| Dates | 30/06/2009 12:00:00 AM | ||||||||
| Enumerated or fixed list | OwnerFlowFunction (one available option for Ownership Sharing Method) | ||||||||
| Floating types associated with units - units should be valid for the type of parameter being set | 123 ML/d | ||||||||
| Interpolated functions | [[0 0][100 10][200 12]]{ML/d ML/d} | ||||||||
| Patterns - numeric values separated with a space and of a defined number | [11 12 13 14 15 16 17 18 19 20 21 22]{ML/d} | ||||||||
| Unit type | m3/s | ||||||||
| Function | $Folder1.Function1 | ||||||||
| Data source | ExampleDataSource_csv.Example Inflow | ||||||||
For functions that specify day of year such as On farm storage example you need to set a boolean as well as a function.
|
| Info | ||
|---|---|---|
| ||
Note: You can also use input sets to change the active demand model at a water user node. For example, the following parameter set entry is valid: Nodes.Water User 3.Demand Model = MyInactiveDemandModel |
...
Child scenario input sets allow you to further refine model scenarios. A child scenario input set inherits all parameters and data sources specified in its parent. You can then set additional parameters, or alter existing ones. When you run a model with a child scenario input set, for any parameters that differ between the parent and child, the parameters from the child will take precedence.
Figure 4. Child Scenario Input Sets, Example
For parent and child scenario input sets:
...