Anchor | ||||
---|---|---|---|---|
|
Nodes represent a physical entity or process within the system that occurs on a relatively localised basis. A water use node represents urban water demand and water consumption behaviour. The Urban Developer Plugin offers two methods for simulating water use behaviour:
- Average daily model (see Average Water Use node)
- Behavioural model (the Behavioural Water Use node)
The following table lists the node models currently available within the Urban Developer Plugin. Each node is represented by a specific icon. The table outlines the function of each node model; other sections of this User Guide contain a more comprehensive description of each node model.
and to release it in a controlled manner. | ||
Average Water use | A water use node |
representing average urban water demand and water consumption behaviour. | ||
Behavioural Water use | A water use node represents urban water demand and water consumption behaviour |
, |
- Alternative Supply - An alternative supply node represents any water supply stream in the model, such as bore water, snow melt, or others. An alternative supply node has no configurable parameters.
- Impervious Area - An impervious area node is used to model catchment areas of zero infiltration, such as roads, driveways, parking lots, and other concreted or paved surfaces.
- Junction - A junction is a point where outflows or runoff from two or more other nodes converge and are aggregated.
- Pervious Area - A pervious area node models areas within the catchment that allow infiltration and seepage to groundwater.
- Receiving Node - A receiving node is intended to be the most downstream node in a network, or part of a network, and is used for tracking purposes.
- Subnetwork - A subnetwork is a characterisation of a group or cluster of dwellings, water uses or general water demands, as a discrete unit.
- Wastewater Connection - A wastewater connection node is an optional end-point of the wastewater aspect of a modelled system.
Contents
Table of Contents | ||||
---|---|---|---|---|
|
Node Connection Rules
The node connection rules arebased on |
In Node Model detailed descriptions, each node model input and output has a link type listed. The table below summarises these connection rules in one place.
To use this table, look up the originating node in the left-most column, then the output you want to connect (the destination node).
Example: from a roof node, you can connect the runoff output to a buffer, but not the runoff to tank output.
This table shows the allowed connections between a source node, and a destination node. The Destination node column specifies which output of the source node can connect to the nodes below it. If a node is not listed in the Destination Node column, the connection is not permitted. For example, the Roof node's Runoff to Tank output can connect to a Tank node's Rainwater / Stormwater Tank inflow, but not an Average Water Use node's Rainwater / Stormwater inflow.
Destination node - destination input type
Runoff to Rank
- Tank - Rainwater / Stormwater **
Bypass Runoff
- Tank -Â Rainwater / Stormwater **
Spill
- Connection type not currently implemented
Detention Outflow
- Connection type not currently implemented
Demand
- Average Water Use - Mains, Rainwater Tank, Alt. Supply 1, Alt. Supply 2
- Behavioural Water Use - Mains, Rainwater Tank, Alt. Supply 1, Alt. Supply 2
Greywater
- Tank - Rainwater / Stormwater **
Blackwater
- Tank - Rainwater / Stormwater **
Irrigation/Other
- Tank - Rainwater / Stormwater **
a stochastic end-use demand simulation |