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.
...
Scenario input sets can define both input parameters and data sources. Input parameters specific to a scenario are defined in the Scenario Input Set dialog, either manually or using a file (see below). Data sources are assigned to scenario input sets using the Load Data Source dialog, as explained here.
...
The general format for a parameter is: path1.path2...pathN=value (eg. Nodes.Inflow1.Flow=10 ML/d).
| Anchor | ||||
|---|---|---|---|---|
|
Figure 1 shows an example of manual parameter entry using the manual parameter set editor. This editor has the following features:
- An auto-complete functionality that is activated when an accepted scenario base node is entered for the first element of the path;
- Typing additional characters filters the auto-completion list. 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 scenario runs. If disabled, the values take precedence for a single scenario run ONLY. Also, an error appears if there is a problem with one of the parameter specifications. |
...
| 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 |
| Anchor | ||||
|---|---|---|---|---|
|
The file-based parameter entry (shown in Figure 2) allows the specification of a file that will contain the element path and values. The formatting of this file must adhere to the same rules as the manual parameter set editor.
...
Child scenario input sets allow you to further refine model structure. 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 3. Child Scenario Input Sets, Example
For parent and child scenario input sets:
...