Note: This is documentation for version 4.11 of Source. For a different version of Source go to the Space Directory.
Page tree
Skip to end of metadata
Go to start of metadata

The following walk through will go through:

  1. How to create an Urban Developer scenario
  2. Add a Behavioural Water User node to the network
  3. Configure the end use items within a Behavioural node. 

Supporting Files:

End Project: urban-walk-through-two-start.rsproj


1. Open Source with the Urban Developer plugin loaded (if the plugin is not loaded refer to Walk Through One) and create a new project, selecting to create an Urban Developer scenario. Be sure to enter a name for the Scenario so that its easy to identify it later e.g. "Detached with Tank"

2. Now we have a new Scenario named "Detached with Tank". From node palette select the Behavioural Water Use node and drag one onto your scenario schematic view (Clicking and dragging Behavioural Water Use node). You can also rename the node by right clicking and selecting rename from the menu. Then, you need to type the new name.

3. To configure the Behavioural Water User node, either double click the node, or right click and select edit from the menu which appears. 

4. The top level of the tree on the left allows for setting of the following inputs to the node. 

a. Number of Houses: This is the number of houses to model using the configuration of this node. 

b. Occupants Per House: This is the number of people to model in the household. It directly affects the likelihood of an event occurring each hour throughout the day. For the time being leave this at three people.

c. Use Average Demand: This switches the node between Stochastic and Average demand.

Stochastic demand will use random number generators to see if water use events occur throughout the day, based on passing the threshold of an hourly likelihood for the particular end use. Some end use items also have a random generator for the volume of water used and / or the length of the event. 

Average demand will calculate the average event likelihood and demand volume for the timestep. This means each end use will generate the same demand rate for all timesteps until parameters change to affect end use item rating being used, number of people in the house, or number of houses being modelled. Outdoor use is the only exception to this rule as it uses a datasource, function, or monthly pattern for this demand generation.

5. Each indoor end use item has the same layout and set of settings. Each does vary on how they are modelled internally. 

a. Head Rating: Allows for the selection of how efficient the end use item in the household is. For example the household could be in a older suburb and have older less efficient shower heads. 

b. Supply: This area allows for defining what source of water the household use to meet this end use items demand. For example a house hold drawing water from a rainwater tank for garden use, before using mains supply. Lower number priority will be used first. If the supply is not checked it will not be used. 

c. Discharge: This area allows for defining how the water leaves the dwelling. Parts is a normalised proportion of the total demand for the end use item. For example having 1 part blackwater, and 2 parts greywater and a demand of 30ML will result in 10ML discharged as blackwater, and 20ML as greywater. 

Review the default settings for each of the Shower, Taps and Dishwasher, Toilet, and Washing Machine to see how they are configured. There is currently no need to change any of these values. 

6. Outdoor tab will allow setting of the outdoor garden / irrigation demands. These can be one of a flat value, data source, function, or monthly pattern. The node will default to using a monthly pattern. Also note that discharge by default is set to 100% irrigation. 

Update the outdoor settings to priorities water tank over mains supply, however leave all the other settings as they are. 

7. Lastly review the Pool settings (nothing needs to change from pool defaults). Now click the OK button for the nodes dialog to save these settings. 

8. Save our project and name it "urban-walkthrough-one.rsproj"

9. Now we are close to being able to run the model and generate some demands. To proceed however we need to select some recorders to turn on so that we can see the results of the model. 

In the Project Hierarchy select the Behavioural node. Then in the Parameters list below, right click and select Record All for the following recorders. 

a. Blackwater Water Volume

b. Dishwasher Demand Volume

c. Main Supply Volume

d. Outdoor Demand Volume

e. Potential Tank Demand Volume

f. Shower Demand Volume

g. Tank Volume

10. To run the model we need to select the configuration type. To do this select the "Urban Configuration" from the drop down menu. 

11. Next we will need to set the run length. Do this by open the configuration dialog and setting the start and end dates of the run. For our scenario we will set the model to run for the year 2020. 

12. Lastly we can click the run button to have the model run for the given time period. To do this click the run menu button. Wait for the run progress to complete and then the results manager should open automatically for you (if not press F10 to open it). Now you will be able to see the results recorded from the model by selecting the recorder in the results manager. 

  • No labels