SWAT+ categorizes plants into seven different types: warm season annual legume, cold season annual legume, perennial legume, warm season annual, cold season annual, perennial and trees. The differences between the different plant types, as modeled by SWAT+, are as follows:
1. warm season annual legume:
-simulate nitrogen fixation
-root depth varies during growing season due to root growth
2. cold season annual legume:
-simulate nitrogen fixation
-root depth varies during growing season due to root growth
-fall-planted land covers will go dormant when daylength is less than
the threshold daylength
3.perennial legume:
-simulate nitrogen fixation
-root depth always equal to the maximum allowed for the plant species and soil
-plant goes dormant when daylength is less than the threshold daylength
4.warm season annual:
-root depth varies during growing season due to root growth
5.cold season annual:
-root depth varies during growing season due to root growth
-fall-planted land covers will go dormant when daylength is less than the threshold
daylength
6.perennial:
-root depth always equal to the maximum allowed for the plant species and soil
-plant goes dormant when daylength is less than the threshold daylength
7. trees:
-root depth always equal to the maximum allowed for the plant species and soil
-partitions new growth between leaves/needles and woody growth
-growth in a given year will vary depending on the age of the tree relative to the
number of years required for the tree to full development/maturity
-plant goes dormant when daylength is less than the threshold daylength
Table 5:1-3: SWAT+ input variables that pertain to plant type.
Temperature is one of the most important factors governing plant growth. Each plant has its own temperature range, i.e. its minimum, optimum, and maximum for growth. For any plant, a minimum or base temperature must be reached before any growth will take place. Above the base temperature, the higher the temperature the more rapid the growth rate of the plant. Once the optimum temperature is exceeded the growth rate will begin to slow until a maximum temperature is reached at which growth ceases.
In the 1920s and 1930s, canning factories were searching for ways to time the planting of sweet peas so that there would be a steady flow of peas at the peak of perfection to the factory. Crops planted at weekly intervals in the early spring would sometimes come to maturity with only a 1- or 2-day differential while at other times there was a 6- to 8-day differential (Boswell, 1926; 1929). A heat unit theory was suggested (Boswell, 1926; Magoon and Culpepper, 1932) that was revised and successfully applied (Barnard, 1948; Phillips, 1950) by canning companies to determine when plantings should be made to ensure a steady harvest of peas with no “bunching” or “breaks”.
The heat unit theory postulates that plants have heat requirements that can be quantified and linked to time to maturity. Because a plant will not grow when the mean temperature falls below its base temperature, the only portion of the mean daily temperature that contributes towards the plant’s development is the amount that exceeds the base temperature. To measure the total heat requirements of a plant, the accumulation of daily mean air temperatures above the plant’s base temperature is recorded over the period of the plant’s growth and expressed in terms of heat units. For example, assume sweet peas are growing with a base temperature of 5°C. If the mean temperature on a given day is 20°C, the heat units accumulated on that day are 20 – 5 = 15 heat units. Knowing the planting date, maturity date, base temperature and mean daily temperatures, the total number of heat units required to bring a crop to maturity can be calculated.
The heat index used by SWAT+ is a direct summation index. Each degree of the daily mean temperature above the base temperature is one heat unit. This method assumes that the rate of growth is directly proportional to the increase in temperature. It is important to keep in mind that the heat unit theory without a high temperature cutoff does not account for the impact of harmful high temperatures. SWAT+ assumes that all heat above the base temperature accelerates crop growth and development.
The mean daily temperature during 1992 for Greenfield, Indiana is plotted in Figure 5:1-1 along with the base temperature for corn (8°C). Crop growth will only occur on those days where the mean daily temperature exceeds the base temperature. The heat unit accumulation for a given day is calculated with the equation:
When calculating the potential heat units for a plant, the number of days to reach maturity must be known. For most crops, these numbers have been quantified and are easily accessible. For other plants, such as forest or range, the time that the plants begin to develop buds should be used as the beginning of the growing season and the time that the plant seeds reach maturation is the end of the growing season. For the Greenfield Indiana example, a 120 day corn hybrid was planted on May 15. Summing daily heat unit values, the total heat units required to bring the corn to maturity was 1456.
As the heat unit theory was proven to be a reliable predictor of harvest dates for all types of crops, it was adapted by researchers for prediction of the timing of other plant development stages such as flowering (Cross and Zuber, 1972). The successful adaptation of heat units to predict the timing of plant stages has subsequently led to the use of heat units to schedule management operations.
SWAT+ allows management operations to be scheduled by day or by fraction of potential heat units. For each operation the model checks to see if a month and day has been specified for timing of the operation. If this information is provided, SWAT+ will perform the operation on that month and day. If the month and day are not specified, the model requires a fraction of potential heat units to be specified. As a general rule, if exact dates are available for scheduling operations, these dates should be used.
Scheduling by heat units allows the model to time operations as a function of temperature. This method of timing is useful for several situations. When very large watersheds are being simulated where the climate in one portion of the watershed is different enough from the climate in another section of the watershed to affect timing of operations, heat unit scheduling may be beneficial. By using heat unit scheduling, only one generic management file has to be made for a given land use. This generic set of operations can then be used wherever the land use is found in the watershed. Also, in areas where the climate can vary greatly from year to year, heat unit scheduling will allow the model to adjust the timing of operations to the weather conditions for each year.
While scheduling by heat units is convenient, there are some negatives to using this type of scheduling that users need to take into consideration. In the real world, applications of fertilizer or pesticide are generally not scheduled on a rainy day. However when applications are scheduled by heat units, the user has no knowledge of whether or not the heat unit fraction that triggers the application will occur on a day with rainfall or not. If they do coincide, there will be a significant amount of the applied material transported with surface runoff (assuming runoff is generated on that day), much higher than if the application took place even one day prior to the rainfall event.
To schedule by heat units, the timing of the operations are expressed as fractions of the potential heat units for the plant or fraction of maturity. Let us use the following example for corn in Indiana.
As stated previously, SWAT+ always keeps track of base zero heat units. The base zero heat unit scheduling is used any time there are no plants growing in the HRU (before and including the plant operation and after the kill operation). Once plant growth is initiated, the model switches to plant heat unit scheduling until the plant is killed.
The following heat unit fractions have been found to provide reasonable timings for the specified operations:
Table 5:1-1: SWAT+ input variables that pertain to heat units.
SWAT+ assumes trees, perennials and cool season annuals can go dormant as the daylength nears the shortest or minimum daylength for the year. During dormancy, plants do not grow.
The beginning and end of dormancy are defined by a threshold daylength. The threshold daylength is calculated:
5:1.2.1
where is the threshold daylength to initiate dormancy (hrs), is the minimum daylength for the watershed during the year (hrs), and tdorm is the dormancy threshold (hrs). When the daylength becomes shorter than in the fall, plants other than warm season annuals that are growing in the watershed will enter dormancy. The plants come out of dormancy once the daylength exceeds in the spring.
The dormancy threshold, , varies with latitude.
if 40 º N or S 5:1.2.2
if 20 º N or S 40 º N or S 5:1.2.3
if 20 º N or S 5:1.2.4
where is the dormancy threshold used to compare actual daylength to minimum daylength (hrs) and is the latitude expressed as a positive value (degrees).
At the beginning of the dormant period for trees, a fraction of the biomass is converted to residue and the leaf area index for the tree species is set to the minimum value allowed (both the fraction of the biomass converted to residue and the minimum LAI are defined in the plant growth database). At the beginning of the dormant period for perennials, 10% of the biomass is converted to residue and the leaf area index for the species is set to the minimum value allowed. For cool season annuals, none of the biomass is converted to residue.
Table 5:1-2: SWAT+ input variables that pertain to dormancy.
Variable Name | Definition | Input File |
---|
Variable Name | Definition | Input File |
---|---|---|
when 5:1.1.1
where is the number of heat units accumulated on a given day (heat units), is the mean daily temperature (°C), and is the plant’s base or minimum temperature for growth (°C). The total number of heat units required for a plant to reach maturity is calculated:
5:1.1.2
where is the total heat units required for plant maturity (heat units), is the number of heat units accumulated on day where on the day of planting and is the number of days required for a plant to reach maturity. is also referred to as potential heat units.
The number of heat units accumulated for the different operation timings is calculated by summing the heat units for every day starting with the planting date (May 15) and ending with the day the operation takes place. To calculate the fraction of at which the operation takes place, the heat units accumulated is divided by the for the crop (1456).
Note that the fraction of for the harvest operation is 1.16. The fraction is greater than 1.0 because corn is allowed to dry down prior to harvesting. The model will simulate plant growth until the crop reaches maturity (where maturity is defined as = 1456). From that point on, plants will not transpire or take up nutrients and water. They will stand in the HRU until converted to residue or harvested.
While the operations after planting have been scheduled by fraction of , operations—including planting—which occur during periods when no crop is growing must still be scheduled. To schedule these operations, SWAT+ keeps track of a second heat index where heat units are summed over the entire year using = 0°C. This heat index is solely a function of the climate and is termed the base zero heat index. For the base zero index, the heat units accumulated on a given day are:
when 0°C 5:1.1.3
where is the number of base zero heat units accumulated on a given day (heat units), and is the mean daily temperature (°C). The total number of heat units for the year is calculated:
5:1.1.4
where is the total base zero heat units (heat units), is the number of base zero heat units accumulated on day where on January 1 and 365 on December 31. Unlike the plant which must be provided by the user, is the average calculated by SWAT+ using long-term weather data provided in the .wgn file.
For the example watershed in Indiana, = 4050. The heat unit fractions for the remaining operations are calculated using this value for potential heat units.
Variable Name | Definition | Input File |
---|---|---|
PHU
PHU: potential heat units for plant that is growing at the beginning of the simulation in an HRU
.mgt
HEAT UNITS
: potential heat units for plant whose growth is initiated with a planting operation.
.mgt
HUSC
Fraction of potential heat units at which operation takes place.
.mgt
T_BASE
: Minimum temperature for plant growth (°C)
crop.dat
IDC
Land cover/plant classification: 1.warm season annual legume 2.cold season annual legume 3.perennial legume 4.warm season annual 5.cold season annual 6.perennial 7.trees
crop.dat
The growth cycle of a plant is controlled by plant attributes summarized in the plant growth database and by the timing of operations listed in the management file. This chapter reviews the heat unit theory used to regulate the growth cycle of plants. Chapter 6:1 focuses on the impact of user inputs in management operations on the growth and development of plants.
SUB_LAT | : Latitude of the subbasin (degrees). | .sub |
IDC | Land cover/plant classification: 1.warm season annual legume 2.cold season annual legume 3.perennial legume 4.warm season annual 5.cold season annual 6.perennial 7.trees | crop.dat |
ALAI_MIN | Minimum leaf area index for plant during dormant period (m/m) | crop.dat |
BIO_LEAF | Fraction of tree biomass accumulated each year that is converted to residue during dormancy | crop.dat |