Modelling farm dams in Source using the Onstream Farm Dam node
Create Onstream Farm Dam node(s)
...
in
...
the Source model
Modelling farm dams in Source is more commonly undertaken as part of a catchment model, where sub-catchment flows provide the inflows to each farm dam node. However, the farm dam node is available from the Node palette and can also be used in a schematic river system model. The creation of a farm dam node (1) in a river system model from the Schematic Editor and (2) in a catchment model from the Geographic Editor, is different. The methods for both models are described separately below:
...
An onstream farm dam node is represented in the Node Palette as a green triangle 
. Dragging the node icon from the Node Palette to the Schematic Editor interface will drop a farm dam node in an existing Source model. This node can then be manually linked to other nodes in teh the model as needed. Accurate coordinates of farm dams’ positions are not required, but can be entered through the Source Feature Table if required.
...
- Prepare a location shapefile of the nodes for the fam farm dams - These to facilitate later conversion these exact locations should be already have been used during the model building and should already exist as e.g. Confluence nodes in the catchment model.
- Open Right click to select the Bulk Change Node Models editor - Clicking on the Model menu item Bulk Change Node Model will show the interface of . This will open the Bulk Change Node Models editor interface (Figure 3). Initially, the contents in the Nodes Located box and the selected item in the dropdown list of destination node types are empty.
- Configure Bulk Change Node Models editor - Clicking on the button of Click on the button to Load node location shape file (Figure 3). This will display the an Open dialogue box, which allows the user to select the a prepared location shape file. After the user clicks on the OK button on in the Open dialogue box, the node names of the matching nodes (e.g. 156, 157) in the Source model will be displayed in the Nodes Located box, and those . These nodes must have the exact locations as defined in the shapefile. The user must select Select Onstream Farm Dams Dam as the target node type from the dropdown list below the Nodes Located box.
- Convert the selected nodes to destination node type – Clicking on the button of Select Change all loaded nodes (as in Figure 3 will ) to convert all nodes in the Nodes Located box to the selected target node type in the dropdown list (e.g. Onstream Farm Dams Dam in Figure 3).
- The user can repeat the above steps to convert nodes to other types if needed. Otherwise, clicking click on the Done button can to close the window.
Note that : The Bulk Change Node Models tool can also can be used to convert the located nodes to other types such as Supply Points, Gauges, etc. The procedure is the same as the above one for onstream farm dams, and the user just needs to select the expected node type (e.g. g Supply PointsSupply Point) from the dropdown list instead of Onstream Farm DamsDam.
Figure 3 Bulk Change Node Model editorModels interface
Configure Onstream Farm
...
Dam node(s) in the Source model
There are two ways to configure the parameters of the onstream farm dam. One method is for the individual node of the Onstream Farm Dam, and another method is for all nodes of modelled Onstream Farm Dams. Two methods can be used jointly.
...
Clicking on the OK button in Figure 4 will save the setup of the farm dam. The Cancel button will discard the entered parameters.
...
Examine all Onstream Farm
...
Dam nodes
The Source Feature Table allows inputting, editing, checking, and outputting all parameters of all farm dams together. Tool menu item Edit » Feature Table... can access Feature Table for this functionality (Figure 13). Clicking on the Onstream Farm Dam in the left panel (Figure 13) will display the existing values of all editable parameters for all onstream farm dams in the right panel.
...
Recorder | Description | Note |
Bypass Flow (ML/d) | The input parameter of the capacity of bypass in the current farm dam. | |
Actual bypassed flows (ML) | The real bypass flows in the time step from the bypassway to the downstream at the current farm dam. It is limited by available upstream flow and Interstation station flow | |
Interstation Flow Reference series (ML/d) | The input Reference data for Interstation Flow. | |
Actual Interstation Flow (ML) | The real Interstation Flow in the time step to the current farm dam, and its value is the product of the Scaling Factor and Interstation Flow Reference series. | |
Evapotranspiration (mm/d) | The input data of evapotranspiration from the current farm dam. | |
Actual Evaporation Volume (ML) | The real evaporation volume in the time step from the current farm dam and its value is based on the dam surface area and inputted Evapotranspiration (mm/d) in the time step. | |
Rainfall (mm/d) | The input data of rainfall to the current farm dam. | |
Actual Rainfall Volume (ML) | The real rainfall volume in the time step to the current farm and its value is based on the dam surface area and inputted rainfall (mm/d) in the time step. | |
SeepageTS (mm/d) | The input data of seepage from the current farm dam. | |
Actual Seepage (ML) | The real seepage volume in the time step from the current farm dam and its value is based on the dam surface area and inputted SeepageTS (mm/d) in the time step. | |
Demand Timeseries Value (ML/d) | The input template data of demand timeseries from the current farm dam. | |
Actual Demand Volume (ML) | The real water volume is used for the demand request from the current farm dam in the time step. Its temporal distribution is determined by Demand Timeseries Value (ML/d) while its value can be different to Demand Timeseries Value (ML/d). | |
Supplied Demand Volume (ML) | The actual released water to meet the requested Actual Demand Volume (ML). It should equal to or less than the Actual Demand Volume (ML). | |
Diversion Fraction (%) | The input parameter defines how many percentages of the upstream flow will be directly diverted to the current farm dam. | |
Actual Diverted flows (ML/d) | The proportioned “upstream” flow, which includes both the upstream flow and interstation inflow, is involved in the water balance calculation for the current farm dam. It is the “upstream” flow scaled down/up by Diversion Fraction (%). | |
Dead Storage Volume (ML) | The input value/time series/function of the Dead Storage Volume (ML). This parameter and the Dead Storage Proportion (%) below are the same parameter in different types. The user only needs to enter one type, and Source will automatically convert one type to another and record both. | |
Dead Storage Proportion (%) | The input value/time series/function of the Dead Storage Volume (ML). This parameter exists as the percentage/proportion of dam capacity. | |
Storage Record (ML) | The simulated storage volume of the farm dam at the end of the time step. This recorder replaces the common recorder of Storage Volume (ML) in the Farm Dam node. | |
Release Volume (ML) | The input parameter for water rerelease requests. | |
Actual Release Volume (ML) | The actual water released to meet the Rerelease Volume requests and its value is limited by the available water. |
Migrate
...
an older Source model using the FarmDams plugin across to
...
core Source
Prior to Source version 5.30 onstream farm dam functionality in Source can be accessed from the plugin of FarmDamsplugin before Version V5.21 or CORE without the Farm Dams plugin after Version V5.21. Only Source projects using the Farm Dams plugin in Version 5.20 can be automatically mitigated to the project with farm darn functionality from CORE. The users need to upgrade their old models (using the Farm Dams plugin) to Source V5.20 with the farm dam plugin first and save it as the upgraded project. The user then opens the upgraded project in later versions such as late 5.21 without the Farm Dams plugin, and the Source will autumnally migrate the farm dam functionally in the project file from plugin to CORE.was accessed through the FarmDamPlugin community plugin and the ObservationPointNodeModel community plugin. Since Source version 5.30 the functionality in these plugins has been incorporated as part of core Source functionality. However, older Source models built using the plugins won't automatically open in Source version 5.30 or later. Only Source projects using these plugins in Version 5.20 can be automatically opened in later versions with farm dam functionality in core Source.
To migrate older Source farm dam projects requires first upgrading pre-Source version 5.30 models (those using the Farm Dams plugin) to Source version 5.20:
- open Source version 5.20 with the FarmDam plugin (and ObservationPointNodeModel plugin, if needed) installed
- load the existing model in Source version 5.20
- save the now upgraded project in Source version 5.20
The upgraded project can then be opened in later versions of Source without the Farm Dams plugin installed, and Source will automatically migrate the required functionality