...
Modelling farm dams in Source using the Onstream Farm Dam node
...
Create Onstream Farm Dam node(s)
...
in a Source model
The creation of a farm dam node (iModelling 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 (ii2) in a catchment model from the Geographic Editor, is different. The methods for both models are described separately below:
(1) From the Schematic Editor
The green triangle icon on the Node Palette represents the An onstream farm dam . Dragging the icon from node is represented in the Node Palette to as a green triangle . Dragging the node icon from the Node Palette to the Schematic Editor interface can create will drop a farm dam node . The accurate in an existing Source model. This node can then be manually linked to other nodes in the model as needed. Accurate coordinates of farm dams’ positions are not required, but can be entered through the Source Feature Table if required.
(2) From the Geographic Editor
There are two ways to add the onstream farm to the Onstream farm dam nodes can be applied to a catchment model from the Geographic Editor individually or in bulk:
...
a. Change
...
a single existing model element in a Source catchment model to an onstream farm dam
...
The first step is to select an existing model element (e.g., a Confluence node)
...
. Right-click on
...
the selected node to display the context menu
...
.
...
Click on
...
Change Node Model (step 1 in Figure 2) on the context menu
...
to display
...
an additional context menu
...
. Select the Onstream Farm Dam option (step 2 in Figure 2)
...
to change the node to an Onstream Farm Dam that is displayed as a green triangle
...
. If there is no existing model element, the Add Node option (step 3 in Figure 2) can be used to add a Confluence
...
for subsequent node model
...
changes.
Figure 2 Modeling Onstream Farm Dam node from Geographic Editor
...
b. Bulk Change Node Models for onstream farm dams
...
Right-clicking on any place in the Geographic Editor model interface
...
will display a context menu, which includes
...
the Bulk Change Node Model menu item (step 4 in Figure 2). This menu item allows the user to bulk change a group of nodes to onstream farm dams
...
:
- 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 the . 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
...
: The Bulk Change Node Models tool can also
...
be used to convert the located nodes to other types such as Supply Points, Gauges, etc. The procedure is the same as
...
above
...
for onstream farm dams, and the user just needs to select the expected node type (e.g.
...
Supply Point) from the dropdown list instead of Onstream Farm
...
Dam.
Figure 3 Bulk Change Node Models
...
interface
Configure Onstream Farm
...
Dam node(s) in
...
a Source model
There are two ways to configure the The parameters of the an 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.
For an individual node of the Onstream Farm Dam
The user can use Future Editor (such as Edit in Figure 2) to set up the parameters of the farm damcan be configured individually per node using the Feature Editor of each node. Since a farm dam model typically contains many farm dam nodes, this method can be time consuming. Another option is to configure multiple nodes of modelled onstream farm dams using the Source Feature Table. These two methods can be used in conjunction to facilitate model configuration.
1 Configure an individual Onstream Farm Dam node
Double click on a node or right click to access the Edit option will open the node Feature Editor. The user can then use the Feature Editor to set up the farm dam node parameters. Clicking on Edit from the selected farm dam node will open the farm dam editor (Figure 4)
Figure 4 Farm dam Dam editor – Dam Information
...
a. Dam Information
The farm dam information is on the default interface of the farm dam editor (Figure 4). The parameters
...
Dam Capacity, Max. Dam Surface Area and Initial Storage Percentage in Figure 4 are self-
...
explanatory. Other parameters are described below.
- Diversion Fraction - decides how much the “upstream” flow, which includes both the upstream flow and interstation diverted flows are not included in the water balance calculation. This parameter indicates how much of the upstream inflow, will be involved included in the water balance calculation in for the edited farm damnode. The remaining water in the “upstream” flow will be diverted directly to the downstream flow.
- Dead Storage Volume (/Dead Storage Proportion) – is the volume of the farm dam stored below the level of the lowest outlet (the minimum supply level). The demand and release requirements cannot access this water, but the natural loss (e.g. evaporation, seepage) in this water still occurs. Dead Storage Volume can also be
...
- input as
...
- a percentage or proportion of Dam Capacity by ticking the Use Proportion checkbox. The parameter name will
...
- change to Dead Storage Proportion when the Use Proportion checkbox is ticked. The user can click on the %/
...
- proportion button to swap the type between percentage (%) and proportion.
Note that the values entered from different types (i.e., volume, percentage, and proportion) for the same farm dam
...
will only be automatically converted
...
once the configuration is saved by clicking on the OK button of the Editor interface.
The Dead Storage Volume can be entered
...
as (a)
...
a
...
Value, (b)
...
a Data Source
...
- normally
...
a time series
...
, or (c)
...
a Function.
The allowable range of Dead Storage Volume is between zero and max capacity.
...
Percentage and proportion
...
ranges are from 0 to 100 and 0 to 1 respectively. If the entered values are not within the permitted range,
...
a run error will occur. The user then needs to fix this issue. The example screen of the error message (e.g. for entering -1) is shown in Figure 5. “166” in Figure 5 is the name of the associated farm dam node.
Figure 5
...
Run error screen for unsuitable input of Dead Storage Volume
- Bypass Flow - defines the maximum capacity of the flow bypassed from the upstream flow directly to the downstream defines a low flow/environmental flow bypass requirement for onstream farm dams. Flow is transferred from upstream directly to the downstream of the farm dam.
Now Bypass Flow can be entered by four types of data sources: (a) from a value, (b) from Data Source, normally it is a time series, (c) from the function and (d) a Monthly Pattern shown in Figure 6.
Figure 6 The Editor Screen of Select Source for ByPass Flow
The Bypass Flow is designed to be greater or equal to zero. If the entered value is negative,
...
a run error will occur. The user then needs to fix this issue. The example screen of the error message (for entering -2 for Bypass Flow) is shown in Figure 7.
Figure 7 Running error message for unsuitable input of Bypass Flow and Release Volume
- Release Volume - defines the voluntary water release requested from the farm dam. The volume(s) can be entered by three types: (a) from a value, (b) from Data Source, which normally is a time series and (c) from the function.
The Release Volume is also greater or equal to zero. If the entered value is negative, the running error will occur (Figure 7). The user then needs to fix this issue.
- Dam Surface Area Options - provides three options for the dam surface area during the water balance calculation:
- Constant dam surfaces area using ‘Max. Dam Surface Area’ parameter – The entered constant value of Dam Surface Area is used in water balance calculation such as converting rainfall and evaporation from the depth to volume in the farm dam storage.
- Allow dam surface area to vary according to dam volume - The area will be calculated on the basis of the storage volume, default equations and parameters. The storage volume is from the beginning of the time step. The calculated dam surface area at each time step will be used in water balance calculation. Custom Equation Parameters check box is unticked.
- Custom Equation Parameters – This function works only when the option Allow dam surface area to vary according to dam volume is selected and the Custom Equation Parameters check box is ticked. The dam surface area will be calculated based on the storage volume at the beginning of the time step, and the equation of Volume =A*Area^B. Where A and B are input parameters from the Interface. The calculated area at each time step will be used in water balance calculation.
...
b. Interstation Flow
...
Inflows into a farm dam in this farm dam model come from two alternative sources: (i) overflows from the upstream dam(s) and (ii) the local flow generated by the interstation area between the upstream dams and this dam.
...
Clicking on the Interstation Flow in the left panel of Figure 4 will display the Interstation flow parameters in the right panel for the configuration (Figure 8). The parameters include Scaling Factor and Reference Timeseries Values/Data Source. The user can select the option Values for the constant value or Data Source for a timeseries defined in Source Data Sources.
The interstation inflow is calculated based on a reference value or time series (i.e., at a flow gauge) that has been scaled down/up. If the scaling factor is 0.8 and the reference timeseries value is 0.25 ML/d, the Actual Interstation Flow (ML) is 0.2 ML/d. The scaling factor reflects (a) the interstation catchment area relative to the reference catchment area; and (b) the nonlinear relationship between the catchment area and flow.
Figure 8 Farm dam editor – Interstation Flow
...
c. Seepage
Seepage from the farm dam into the underlying soil can be modelled by defining an exfiltration rate (e.g., mm/d). The water that seeps from the farm dam is lost from the catchment and does not re-enter the system downstream.
...
Clicking on the Seepage in the left panel of Figure 4 will display the Seepage parameter in the right panel for configuration (Figure 9). The parameters can be configured by the constant value or time series from Data Source.
Figure 9 Farm dam editor – Seepage
...
d. Demand
Clinking on the Demand in the left panel of Figure 4 will display the demand parameters in the right panel for configuration (Figure 10). The demand parameters include Demand Factor and Demand Timeseries Values/Data Source. The demand factor can be estimated from the ratio of the average annual demand of the farm dam volume.
In this farm dam model, the demand is not directly using Demand Timeseries. The demand volume is determined by the demand factor and farm dam volume, and its temporal distribution is determined by the Demand Timeseries Values/Data Source.
Figure 10 Farm dam editor – demand
...
e. Rainfall
...
Clicking on the Rainfall in the left panel of Figure 4 will display the rainfall parameters in the right panel (Figure 11). The parameter is the rainfall to the edited farm dam, and it can be configured by constant Values or timeseries data in Data Sources. Its unit is depth such as mm, and Source will convert it to volume by the dam area calculated as the description in section (1) The farm dam information.
Figure 11 Farm dam editor – Rainfall
...
f. Evapotranspiration
...
Clicking on
...
Evapotranspiration in the left panel of Figure 4 will display the evapotranspiration parameters in the right panel (Figure 12). The parameter is the evapotranspiration from the edited farm dam, and it can be configured by constant Values to timeseries in Data Source. Its unit is depth such as (mm/day) and Source will convert it to volume using the calculated dam area as the description in section (1) The farm dam information.
Figure 12 Farm dam editor – Evapotranspiration
Clicking on the The OK button in (Figure 4) will save the setup of the farm dam setup. The Cancel button will discard the entered parameters.
...
2 Configure multiple 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 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 mitigated to the project opened in later versions 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 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 the Source will autumnally automatically migrate the farm dam functionally in the project file from plugin to CORE.required functionality