Introduction¶
The purpose of scenario analysis is to compare two or more scenarios and see the difference. For example what is the impact of increased water demand in 2050 compared to today? The Scenario Comparison one or more scenario comparison templates can be stored for fast viewing. Models for which scenario simulations have been carried out, can be stored in these templates, and new simulations and scenarios are automatically included in the template.
Create new comparison template¶
To create a new comparison template:
Right click on the Comparison Configuration group and select New comparison from the context menu
When the template node has been created it is recommended to rename the template with a descriptive name.
Right click on the template node and select Rename from the context menu
Make a comparison¶
Description | Illustration |
---|---|
A model with scenarios can be associated with the comparison template. Right click on a model node and select Compare from the contest menu, and chose among available comparison templates. |
|
The model scenario simulations need to be compared. This is achieved by: Right click on a template node and select Run Comparison from the contest menu. |
|
The template can now be opened and the Scenario Comparison Configuration view will open in the Data View. Right click on the Comparison template node and select Open from the context menu. |
|
A scenario comparison configuration menu is opened in the Data View. The menu consists of two taps: Under the Variables configuration the input variables and the output variables of the relevant objects are listed Under the Simulation configuration: Select the model Select the simulation to be compared |
|
Under the Variables Configuration: Select the output of the model object which should be displayed. Select the tool from the Tool Explore to be used to visualize the difference between the scenarios. For example: To chart |
|
For example: Duration curve |
Compare scenarios across models¶
Description | Illustration |
---|---|
To compare simulations created from different models, start by creating a new comparison node. | |
Add the models that contain the simulations that shall be compared to the new Comparison node by selecting Compare / \ Alternatively, open the comparison view, and drag-drop the model setup nodes to the Model setups list. |
|
Open the comparison view by selecting the Open entry in the comparison context menu. The included models are now listed in the Model setups list, and all simulations created from the included models are now listed in the Compared simulations view. |
|
Select the simulations that shall be compared. Notice that the simulations may belong to different models. |
|
Now, swich to the variables configuration view. On the top level all included models are represented in a list. At this level the search functionality can be used to search for model object variables across models. |
|
If the variable that shall be compared has the same name in all included models, type in the name in the search box. | |
When the search is executed, the model object variables that match the specified name are listed. In this example the model object variable named E84|Flow was found in Model A and Model B. |
|
Next, create a sequence that processes and presents the data in a suitable way. For this example, a simple sequence containing only the To chart tool (saved with the name E84) was created. The sequence will add the input series to a chart named E84. A template named Model comparison E84 will be applied. |
|
Now, associate the sequence to the model object variables by drag-and-drop from the sequence in the toolbox to the model object variable. | |
Finally, run the comparison by selecting “Run comparison” from the comparison node context menu in the scenario explorer. The sequences associated to the model object variables will be executed, and the output produced. Notice: if the variables that are compared do not have the same name in the compared models, it will still be possible to compare, but the sequences must be assigned by manually browsing to the relevant model object variables. |