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.
...
- Right-click on the scenario input set that you wish to be the parent, and choose Add Child Scenario Input Set from the contextual menu (Figure 1).
Figure 4. New Scenario Input Set
Input parameter entry
Parameters specific to a scenario input set are defined and managed using the parameter set editor in the Scenario Input Sets dialog (as shown in Figure 2). The panel on the right allows you to specify parameters, either manually, or by loading a text file.
...
- An auto-complete functionality, press Ctrl + space to get a list of available elements;
- Typing additional characters filters the auto-completion list. 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 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. |
...
| Parameter type | Example shown in Figure2Figure 2 |
|---|---|
| Boolean | True |
| Dates | 3031/0605/2009 2001 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
...
a parameter that can take as input either a day of year
...
or a function (eg. on farm storage planting decision plant date), if you change the input from a specified day and month to a function or vice versa, you need to set a boolean as well
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| icon | false |
|---|
...
. An example of changing from a specified day of year to a function is shown in Figure 2, an example of changing from a function to a specified day of year is:
Nodes.Wheat Fields.Inactive Demand Models.Irrigator #0.Crops.Wheat Crop.Planting Decision.Plant Date.Use Expression=False
Nodes.Wheat Fields.Inactive Demand Models.Irrigator #0.Crops.Wheat Crop.Planting Decision.Plant Date.Day=20
Nodes.Wheat Fields.Inactive Demand Models.Irrigator #0.Crops.Wheat Crop.Planting Decision.Plant Date.Month=12
You can also use scenario input sets to change the active demand model at a water user node
...
, for example:
Nodes.Water User 3.Demand Model=MyInactiveDemandModel
If you wish to change some parameters in an inactive demand model, and also make it the active model, then you need to specify the parameter changes first. An example is shown in Figure 2 for the inactive demand model Irrigator #0.
| Anchor | ||||
|---|---|---|---|---|
|
The file-based parameter entry (shown in Figure 25) 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.
Note that the Reload on Run and Relative path checkboxes follows the same rules as for data sources.
Figure
...
5. Input parameter set using a file