Overview

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 Source Results Manager.

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 Parameters area of the Source Project Explorer to select the outputs to record.
Select the Simulation Type

The model can then be run through ‘Run’ button on the main Source toolbar.

Contents

Recording Model Outputs

After setting up a scenario you must select the model outputs of interest.

When you run a model, 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. Urban Developer does not automatically record all possible outputs of all nodes and links. You must use the Parameters area of the Project Explorer to select which outputs to record.

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.

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 Results Manager.

Errors and warnings

If the scenario run has any associated warnings or errors, these will be displayed in the Log Reporter.

Simulation Type

Urban Configuration

The Urban Configuration runs a single Urban Scenario.

Urban Combination Configuration

The Urban Combination simulation is designed to be used when linking Urban Developer with Source River System Scenarios.

The user configures a single Behavioural Water Use node to represent a typical household type (such as an apartment, or detached house with a rainwater tank). The Urban Combination simulation generates a database of the average water demand for every combination of occupancy and end usage type defined in the scenario.

To use the Urban Combination Configuration:

Exactly one behavioural demand node must be present in the scenario (roof and tank nodes can also be present)
Configure the demand node (and tank and roof nodes, if present) to represent a single dwelling.
Ensure Sampled Appliance and Occupancy is disabled (it will be disabled by default)
Choose the Urban Combination Configuration
Run the model.

The Urban Combination results will be available from within Source River System Scenarios within the same Source project file and can be used to configure Urban Water User nodes with customised distributions and dwelling numbers.

Acknowledgements

This material has been adapted from:

eWater Cooperative Research Centre (2011) Urban Developer User Guide: Urban Developer v1.0.0, eWater Cooperative Research Centre, Canberra, 29 June 2011. ISBN 978-1-921543-40-1

Browser not supported