Irrigator operates on a daily basis generating demands and extracting water to meet these demands via the water user and supply nodes. Irrigator maintains a daily water balance for each cropping area during its planting season, to calculate the daily soil water deficit and an irrigation requirement. The irrigation requirements are used by the Water User to generate orders and opportunistic requests and to subsequently place orders and requests and to extract water from a water source.The model can be applied in both regulated and unregulated systems.
These same Irrigator Demand Model configuration options described here at the Water User Node can be used to represent rain-fed agriculture when modeled in a Catchments Scenario using the Agricultural Runoff Rainfall-Runoff model.
Configuring generic crop settings
| Info | ||
|---|---|---|
| ||
| Note: The Irrigator model is based on FAO56 - "Crop evapotranspiration - Guidelines for computing crop water requirements - FAO Irrigation and drainage paper 56, and is available here. Prior to configuring an Irrigator Demand Model on a Water User node, you must specify crop factors for the entire scenario using Crop factors defined in this way are accessible for each water user node. More details regarding this can be found at IQQM Crop Demand Model. |
To configure an irrigator demand model in Source, right click Demand Models in the Water User node's feature editor and choose Add Irrigator.
District Configuration
This describes a number of parameters (outlined in Table 1) that can be set at an irrigation district level.
Figure 1. Irrigator demand model
Table 1. Irrigator demand model, District configuration parameters
| Parameter | Description |
|---|---|
| Maximum irrigated area | Represents the maximum area that can be irrigated within a district. It is used to calculate the fallow area at each time-step, which impacts on the rainfall runoff from the fallow area. The total irrigated area can exceed the maximum irrigated area if incorrectly configured, causing a warning message to be recorded at run time. |
| Soil moisture capacity | This is assumed constant for all crops in the district. Soil moisture capacity is nominally the difference between the soils field capacity and permanent wilting point. |
| Irrigation season start and end dates | If these are configured, orders and requests will only be generated within the irrigation season. |
| Demand Limiting Factor | Allows you to limit any spikes in demand that may happen. Typically, these spikes would occur when a crop is first planted to reach the target moisture level. This is a factor of the time-step's evaporation depth. For example, if this has a value of 2, demand is limited to a maximum of twice the day's evaporation depth. For ponded crops, the demand limiting factor only applies to the minimum pond level (regulated requirement), it does not apply to the maximum pond level (opportunistic requirement). |
| Use Opportunistic Water up to Max Pond Level | This option is checked on by default. When checked on it allows the water user in a regulated system to take opportunistic water to supply ponded crops up to maximum pond levels. |
| Use Predicted Demand in Flow Phase | Relevant in Functions, this option is available to return the volumes required by the Irrigator Demand Model recorded in the Order phase in the Flow phase (used in Victoria) For example, the Demand Model might specify requirement x, but the associated order is not x due to account restrictions, distribution loss etc. During the order phase, the Demand Model specifies x based on forecasts, but in the Flow Phase it is recalculated as y (no forecasts applied). Without this option: x is reported in the Order Phase, and y in the Flow Phase With this option: x is specified in both phases, even though the work is still done to calculate y and the internal state of the crops is updated based on the factors that led to y |
Target Modifier
Irrigation modifiers are included in Source to allow a simple mechanism to reduce irrigation intensity for recurring time periods. To enable a target modifier, right click on the demand model and choose Add Target Modifier (as shown in Figure 1). This provides equivalent functionality to demand reductions in the PRIDE model. By specifying a target modifier, a new soil depletion target is calculated during the specified period that results in a reduction in irrigation demand equivalent to the modifier you specified.
If the Target Modifier is 0%, the target equals the readily available water (RAW) while the negative Target Modifier allows the target to be less than RAW.
Multiple Target Modifiers can be configured to apply for different specified time period. When multiple Target Modifiers are configured and there is an overlapped time period, then the multipliers apply in the same priority order as they are added and are listed. The top Target Multiplier will override any listed below for the overlapped period.
District Supply Escape
The district requirement is adjusted to allow for any district delivery supply escapes and losses associated with delivering water to the district. The volume removed before getting to the crop is called the escape volume. The escape volume can either be lost from the system or returned back to the water user as a return flow. This is an optional parameter in the demand model and can be added by right clicking Irrigator, then choosing Supply Escape. It is expressed as a percentage.
District Return Efficiency
Returned water is surplus drainage water from irrigation or from rainfall runoff. This water can be redirected into the on farm storage or otherwise can be returned to the river via a confluence node. This is optional in the demand model configuration and can be added by right clicking Irrigator and choosing Add Return Efficiency. This is also expressed as a percentage.
Ordering configuration
You can configure two climate parameters using the Ordering Configuration tree menu item:
- Average Evaporation is used when forecasting orders (shown in Figure 2). You can enter a daily pattern of average evaporaration, specify a function, or select to calculate an average evaporation runtime over a specified number of time-steps; and
- Average Rainfall is used to specify the forecast average rainfall. Its configuration window is similar to Figure 2.
| Info | ||
|---|---|---|
| ||
| Note: For Average Evaporation, the default number of time-steps is 7. For Average Rainfall, this is 0. |
Figure 2. Irrigator demand model (Ordering configuration, Average evaporation)
Climate Configuration
There are two parameters that can be defined for climatic data:
- Evapotranspiration (shown in Figure 3) - defined in FAO56 as the amount of transpiration that would occur from a reference crop. Procedures for calculating evapotranspiration are documented in FAO56. In addition, the BOM and SILO climate products produce daily estimates for FAO56. Alternatively, pan evapotranspiration and pan factors can be used to define evapotranspiration; and
- Rainfall - This can be specified as a constant value, a time series or a function. The configuration window is similar to Figure 3.
Figure 3. Irrigator demand model (Evapotranspiration)
Fallow Crop
Maximum Irrigated Area which is not being cropped is referred to as fallow. Every irrigator demand model has, by default, one fallow area. Fallow area occurs between cropping seasons or during the irrigation season if the maximum developed area is not planted. The fallow cropping area does not order or receive irrigation water. However, a soil water balance of the fallow crop is maintained, and impacts on rainfall runoff from the fallow area and the initial soil moisture assigned to new crops area. The depth of rootzone for fallow represents the depth of soil from which evaporation can occur.
Undeveloped Area
This allows representation of runoff from undeveloped areas. These areas can not be used for crops unlike fallow. This is relevant where on farm storages can harvest this runoff. The undeveloped area does not interact with cropped or fallow area models. It does not cause orders.
Crop Configuration
This is used to define parameters specifically related to the crop to be planted. To add a new crop, right click Irrigator and choose Add Crop Type. Figure 4 shows an example of a crop, named Wheat, that has been added to the model. Consult the Source Scientific Reference Guide for detail on the parameters for configuration.
A list of crop names and associated crop types, can be exported to a .csv file and then imported at another water user node (or Agricultural Runoff Rainfall-Runoff Model). The crop types must already be configured in the list of generic Crop Parameters at . The Import and Export options are available on the right click at the level of the Irrigator demand model:
Soil Configuration
Crop specific soil factors can be defined on the same page as General Configuration (see Figure 4). Soil moisture capacity is specified at the district level and this is assumed constant for all crops in the district. You must also specify Depth of the Root Zone, Depletion Factor and Initial Depletion for each crop.
Figure 4. Irrigator demand model (General and Soil Configurations)
Crop Factors
Crop factors as specified for a crop in the generic crop parameters page under
Planting DecisionAnchor Planting Decision Planting Decision
Planting decisions are represented as a trigger in the Irrigator Demand Model and include a decision type, plant date, optional harvest date and an under irrigation factor (see Figure 5). The number and size of cropped areas changes over time in response to planting decision triggers and available water.
| Info | ||
|---|---|---|
| ||
| Note: Irrigator allows more flexible representations of crop based planting decisions than earlier crop demand models, which better align with economic modelling. If the planted area is defined using the Function Editor, then other factors such as economics can be considered. In addition, planting decisions can be reviewed periodically during the season. This allows decisions to be made to cut back the irrigated area, reduce irrigation intensity or potentially trade water if there is insufficient water to finish the crop. |
Figure 5. Irrigator demand model (Planting Decision)
If Lookup Table is choosen as the Decision Type, you must define a configuration table (as shown in Figure 6), which can be entered manually or imported using the Import button. This table is used to determine the Area and Underirrigation Factor for a given value of Available Water. Additionally, for values of Available Water that are not present in the table, linear interpolation is used to determine the other two parameters. For the example shown in Figure 6, if available resources in a RAS are 15000ML, the planting area will be 3000ha based on linear interpolation between (10000, 2000) and (20000, 4000). The available resources from water user (order debit type) is determined from the current account balances plus on farm storage available water, as at maximum travel time, released water in the river is zero.
Planting decisions are made based on the travel time in advance of the Plant Date. If a Lookup table is used, Available Water is actually the travel time before the Plant Date. For example, if the plant date is 1 OCtober, and max travel time to the supply point (ie, travel time to storage farthest away), decision date is 10 days before 1 October. The Crop area is based on water available at 10 days before 1 October.
Figure 6. Irrigation demand model (Planting Decision, Lookup table)
Target soil depletion
The amount of water in the rootzone is defined in terms of rootzone depletion, which describes the soil water deficit of the rootzone relative to field capacity. The target depletion can be specified as a pattern, a constant value, a time series, or as a function.
Three target depletions can be specified specified (as shown in Figure 17):
- A Regulated Target - the target at which Irrigators water and attempts to maintain soil depletion; or. It is shown as Target Soil Depletion in Figure 1 or Figure 7. For the pond crop such as Rice, it is displayed as Minimum Pond Level. Its inside parameter name (such as name in Scenario Input Sets) is Target Soil Moisture;
- An Opportunistic Target (optional - right click on Target Soil Depletion or Minimum Pond Level and then click on Enabled Opportunistic Target Depletion) - used to generate opportunistic requests. It is displayed as Opp target soil depletion in the User Interface. For the pond crop, it is displayed as Maximum Pond Level. Its inside parameter name (such as name in Scenario Input Sets) is Maximum Target Soil Moisture; or
- Refill Trigger (optional - right click on Target Soil Depletion or Minimum Pond Level and then click on Enable Refill Trigger) - May allow better representation of irrigation scheduling for individual properties as irrigation does not commence until the forecasted soil depletion reaches the specified refill trigger (assuming the trigger depletion is greater than the target).
Note that if ponding if ponding is required a negative soil moisture target should be specified. . Also, the modelled soil depletion in the recorder is called Soli Depletion and it is not Initial Depletion, which is an input parameter and does not appear in the parameter recorder tree.
Figure 7. Irrigator demand model (Target soil depletion)
Runoff
This specifies the percentage The Spill From System parameter defines the amount of applied irrigation and rainfall that becomes deep percolation and drains below the rootzone. Thewater that becomes runoff. A value of 0 results in no irrigation runoff; 10% indicates that 10% of the applied irrigation water becomes runoff. By default, both are set to 0 and do not need to be configured
The Return Efficiency parameter is used to maximise return flow set efficiency to 100. You must also specify a return efficiency, which means that the proportion of runoff that is returned to the water user, which can be stored in the farm storage or returned to the river. The configuration window is similar to that shown in Figure 78.
Deep Percolation
The Spill From System parameter defines the amount This specifies the percentage of applied irrigation water that becomes runoff. A value of 0 results in no irrigation runoff; 10% indicates that 10% of the applied irrigation water becomes runoff. By default, both are set to 0 and do not need to be configured. and rainfall that becomes deep percolation and drains below the rootzone. The configuration of Deep Percolation is the same as that for Runoff. The configuration window is shown in Figure 78.
A 10% supply escape efficiency would indicate that 10% of the applied water becomes runoff.
Figure 7Figure 8. Irrigator demand model (Deep Percolation)
Economics
You can configure some simple economic considerations in Irrigator, as shown in Figure 89. To enable economic values to be configured for a crop, right click on the crop and choose Enable Economics. A simple, linear crop water production function is used to predict the reduction in crop yield resulting from water stress. Irrigator records the relative yield as a daily time series. The following parameters must be specified as a function:
- Yield factor - represents the Yield response factor, as expressed in equation 90 of FAO56. This parameter defines how yield is reduced as a result of water stress. It is used in the calculation of the relative yield daily time series (one of the outputs of the demand model). Note that in IrrigationIrrigator, the yield response factor is entered as a percentage rather than as a fraction;
- Expected Usage - this is a depth measured in mm (note that 100mm is equivalent to 1ML/ha); and
- Productivity - allows you to multiply this is the same as the Maximum Yield number in the FAO33 calculations and allows the calculation of socio-economic outputs when the relative yield by a and productivity term are multiplied together (eg. $/ha or tonnes/ha) to calculate socio-economic outputs.
For more information consult the Irrigator Demand Model page of the Source Scientific Reference Guide.