Running a scenario is the Urban Developer process of applying observed time series inputs or drivers to the currently selected scenario.
After a scenario run, you can see the results in the Recording Manager (page 78) at the bottom of the Urban Developer main window.
Before running a scenario, you must:
• Construct a model in the Urban Developer schematic editor using an appropriate configuration of nodes and links, and adjust node properties as required
• Configure the appropriate climate data, including rainfall.
• Use the Project Explorer to select the outputs to record.
The model can then be run through ‘Run’ button on the main Urban Developer toolbar.
Recording model outputs
After setting up a scenario, you then select the model outputs of interest.
When you run the models in a scenario, every node and link produces results in the form of predicted water flows, volumes and other data outputs specific to each node and link.
Some node or link types can produce many data outputs. You can change the outputs that Urban Developer records by default.
Note 1 Urban Developer does not automatically record all possible outputs of all nodes and links. You must use the Project Explorer to check that the output you want will be recorded (see below).
In general, the more outputs you record, the longer the simulation will take, though this depends on exactly what you record: recording mass-balance is more computationally intensive than recording inflow, for example.
Note 3 Urban Developer automatically saves the list of model outputs selected for recording into the project file, however Urban Developer does not automatically save the model run results themselves. You must save or export the model run results using the options in the Recording Manager (page 78) toolbar.
Using the Project Hierarchy to select and record the model outputs of interest
Viewing results from the Recording Manager
The Recording Manager (View > Recording Manager) is located at the bottom of the Urban Developer main window, and lists the recorded outputs of scenarios after they are run.
The outputs displayed are set using the Project Explorer; see Recording Model Outputs (page 77).
Errors and warnings
If the scenario run caused any errors, the error icon appears on the tab.
If the scenario run had any associated warnings (usually, missing configuration data), the warning icon appears on the tab. See the Log Reporter (page 34) for details on the error or warning.