2.1. BlightPro Decision Support System and Field Trial Evaluation
BlightPro is an internet-based application available on the USAblight website (
http://usablight.org). It was developed provide crop protection strategies in order to manage late blight disease for tomato and potato crops throughout the growing season [
11,
13]. BlightPro recommends precise, timely fungicide applications in response to weather conditions, late blight pathogen type, host resistance, and fungicide characteristics and efficacy. It accesses weather data from the nearest weather station for a given field, and uses the current and forecasted weather information as an input to a late blight disease simulator and disease forecasting tools. BlightPro uses a specific disease severity index to trigger a fungicide application recommendation. The same index and trigger value is used for tomato and potato crops. An alert system notifies the user of impending critical thresholds for fungicide intervention via text or e-mail, when weather conditions are conducive for the development of late blight.
Tomato field trials were conducted in 2015 at the Mountain Horticultural Crops Research and Extension Center in Mills River, North Carolina. The trials were designed to evaluate the performance of BlightPro in managing tomato late blight disease. The data collected included the disease severity, the timing of applications, number of fungicide applications, and tomato yields for two tomato cultivars, with one susceptible cultivar (Mountain Fresh Plus) and one moderately resistant cultivar (Legend) to late blight. The trials used four replications in a randomized complete block design with split plots to accommodate the two cultivars used (see
Figure 1). Three treatments were used, namely: the calendar-based strategy (seven-day spray schedule), DSS-based strategy (BlightPro Decision Support System based strategy), and unsprayed control (no fungicide application). Each plot was 20′ long and 25′ wide, and was composed of two experimental rows bordered on both sides by one untreated ‘guard’ row to prevent fungicide drift. An additional guard row was included between the two cultivars of each plot. Ten feet separated the two experimental rows within a plot, and fifteen feet separated the experimental rows between each plot. Each experimental row contained 14 plants, at 18″ spacing in raised beds, covered with 1.5 millimeter polyethylene black plastic.
Four-week-old tomato seedlings were transplanted into fumigated soil on 9 June and a protectant fungicide with an active ingredient, chlorothalonil, was sprayed at starting on 12 June. Because of a miscommunication, both Mountain Fresh Plus and Legend were sprayed according to the BlightPro recommendations for Mountain Fresh Plus until late in the season. For this reason, the results for the Legend are not discussed in this paper, and all of the results are for Mountain Fresh Plus.
Thirteen foliar applications were made to the calendar-based strategy. Eleven foliar applications were made under the DSS-based strategy. The plots were harvested three times during the season and the total culled tomatoes and marketable tomatoes were measured by weight. One treatment (replicate II) for the calendar-based strategy was incorrectly planted with the wrong cultivar, and the associated data was disregarded for the trial and this analysis. In addition, multiple plants were removed because of bacterial wilt, and the harvest calculations (i.e., weight of culled and marketable tomatoes per acre) were adjusted accordingly.
Table 1 summarizes the area under the disease progress curve (AUDPC, a quantitative summary of disease severity of late blight over time), marketable weight, cull weight, and the total weight for the susceptible cultivar (Mountain Fresh Plus). The results show that using the DSS-based strategy improved the marketable tomato weight by 14.8% in 2015 for the susceptible cultivar (Mountain Fresh Plus), relative to the calendar-based strategy. These marketable weight data were used as a guide to motivate the sensitivity analysis with respect to tomato yields when conducting economic analyses. Ideally, a model that links the disease severity, weather conditions, and yield should be used to predict the tomato yield or tomato yield reductions. However, no such model exists in the literature. The interaction among several factors influencing the tomato yield increases the complexity in developing such a model. These factors include the influence of weather, the impact of disease severity, and the input usage on the tomato yield. To compensate for the fact that no such model exists, we conducted a sensitivity analysis for the tomato yield so as to examine the economic benefits of BlightPro for tomato growers. The sensitivity analysis assumed that the DSS-based strategy would improve the tomato yield by 0%, 5%, 10%, or 15%, relative to the calendar-based strategy.
2.2. Computer Smiluation Experiments and Economic Data
To estimate the economic benefits of the DSS-based strategy for tomato production, the distributions of the net return per acre need to be generated, which is the gross revenue minus the costs of fungicide and its application. These distributions are generated by first conducting computer simulation experiments, which use 14 years of meteorological data (2000–2013), recorded from 25 locations (13 locations in New York and 12 locations in North Carolina). The set of computer simulations used for the economic analysis is a subset of the data generated by Small et al. [
13]. The original computer simulated data set included 59 locations in the United States. This was reduced to 25 locations for inclusion in this study, because of a lack of availability of the tomato price and the yield information for the other locations.
Each year’s weather conditions at each location created a unique tomato growing environment. In total, 316 tomato growing environments were included after removing those years with more than 2% missing weather data during the growing season. The results were generated for three disease-resistance categories with a different susceptibility to late blight, as follows: susceptible, moderately susceptible, and moderately resistant. Each disease-resistance category includes several different tomato varieties. Three methods of fungicide scheduling throughout the production season were compared, including a calendar-based strategy (seven-day spray schedule), a DSS-based strategy (BlightPro Decision Support System based strategy), and a no spray strategy (no fungicide application). The initiation date of the late blight disease was assumed to initiate randomly during the growing season with a 0.001% disease severity (one lesion per 10 plants). This reflects the random nature of the late blight initiation over the course of a production season for a field that starts the season being disease-free, with tomato crops becoming infected by inoculum from external sources (e.g., infected farm/vegetable gardens) in the surrounding environment. In total, 2844 simulations (316 environments × three disease-resistance categories × three methods of fungicide scheduling) were used to compare the DSS-based strategy with the calendar-based strategy for tomato production. For a comprehensive discussion and illustration of the difference between the DSS-based strategy and the calendar-based strategy, see Small et al. [
13] and Liu et al. [
14].
Figure 2 illustrates that the process of the computer simulation experiments and the data generating process for the economic analysis. For a comprehensive discussion of the computer simulation experiments, see Small et al. [
13]. The following common parameters were used. The length of the season was 110 days (
Table 2). All diseases other than late blight, and the effects of other pests, weeds, nutrients, and heat or frost shock, were assumed to have an equal effect on the tomato production process among the calendar-based strategy and the DSS-based strategy. The growers were also assumed to be able to make fungicide applications according to both the DSS-based and calendar-based strategy. In reality, fungicide applications may be delayed as weather conditions, such as precipitation, may not allow for growers to get into the field to apply fungicides.
To estimate the economic benefits of the DSS-based strategy, the net return per acre, which is the gross revenue minus the costs of the fungicide and its application, was compared for each of the 25 locations within a 14-year period. The tomato yield is simulated to estimate gross return per acre. The tomato yields per acre from 2000 to 2013 were estimated using historical state-level average fresh market tomato yield data obtained from the USDA NASS database [
9]. The tomato yield per acre for the calendar-based strategy was assumed to be equal to the historical state-level average fresh market tomato yield from 2000 to 2013. The tomato yield per acre for the DSS-based strategy was calculated for each year,
, and each state,
, as follows:
From the 2015 tomato field trials, the tomato marketable weight improved by 14.8% on average for the DSS-based strategy when compared with the calendar-based strategy. The sensitivity analyses were conducted with the assumption that the DSS-based strategy could improve the tomato yield by 0%, 5%, 10%, or 15%, compared with the calendar-based strategy. For each year at a given location, the net return per acre for each disease-resistance category was equal to the gross revenue (price × yield) less the cost of the fungicide applications, including materials and other application costs. The net return per acre was computed as follows:
where
stands for each of the 25 sites;
stands for a specific year;
refers to the calendar-based or the DSS-based strategy; and
stands for the state (New York or North Carolina) in which the site,
l, is located. The fresh market tomato prices from 2000 to 2013 were obtained from USDA NASS [
9]. The average yield and price were assumed to be the same across the different cultivar resistance levels. A protectant fungicide with an active ingredient, chlorothalonil, was applied at 1.34 kg a.i./ha (equivalent to 1.5 pints per acre) for each application. The fungicide price was obtained from a local agricultural chemical distributor on Long Island, by Dr. M.T. McGrath in April 2013 [
15]. The fungicide cost per acre for each application in 2013 is
$8.63. The application cost (
$6.58/acre/application) comes from Lazarus [
16], which is the total cost per acre of a self-propelled boom sprayer, including fuel, lubricants, repairs and maintenance, labor, electricity, depreciation (depreciation is both time-related and use related), and overhead costs (interest, insurance, and housing). The USDA Prices Paid Indices (agricultural chemical and machinery indices) were used to adjust the fungicide price and application cost in 2013 to the nominal prices in previous years.
2.3. Stochastic Dominance and Stochastic Efficiency
The weather conditions in different years influence the risk for late blight infection, which results in uncertainties and volatility in the net returns for decision makers. Recognizing this, we incorporated the uncertainty and producers’ risk attitudes into the decision-making framework. Individual risk attitudes can be used to rank alternative decisions [
17]. Producers with different degrees of risk-aversion are likely to have different preferences among alternative strategies [
18]. In this research, we compared mutually exclusive decisions faced by tomato growers for alternative fungicide spray strategies (i.e., the calendar-based strategy or the DSS-based strategy). Stochastic dominance, stochastic dominance with respect to a function, and stochastic efficiency with respect to a function (SERF), were used to rank alternative fungicide application strategies, using net return per acre for each location. These methods can help farmers to better understand their risk preferences and choices under price, yield, or weather uncertainty.
Stochastic dominance methods [
19,
20,
21,
22] were used to identify the most risk efficient strategy among the DSS-based and calendar-based strategies. These methods compare the entire cumulative distribution function of the net return per acre for the DSS-based and calendar-based strategies under the different ranges of the risk aversion coefficient of a decision maker. First-degree stochastic dominance (FSD) compares the risky alternatives faced by decision makers who have positive marginal utility [
19], which implies that decision makers prefer more wealth (or net return in this case) to less. There is no restriction on the decision makers’ risk aversion coefficient [
19], which means that the risk aversion coefficient ranges from negative infinity to positive infinity. Second-degree stochastic dominance (SSD) assumes that decision makers are risk averse [
19]. Risk averse decision makers prefer a higher average income, lower variance, and less downside risk. The risk aversion coefficient for SSD ranges from zero to positive infinity. Stochastic dominance with respect to a function (SDRF) ranks risky alternatives based on assumed lower and upper bounds of decision makers’ absolute risk aversion levels [
23,
24]. It does not impose any restrictions on the width of the relevant absolute risk aversion interval [
24], which allows the lower and upper bounds on the absolute risk aversion interval to vary among studies [
24]. First- and second-degree stochastic dominance can be considered as special cases of SDRF [
24].
Information pertaining to the absolute risk aversion coefficients is required for SDRF analysis. According to Raskin and Cochran [
25], this information can be obtained by dividing the relative risk aversion coefficients by the location-specific average net return per acre. The relative risk aversion levels used for stochastic dominance with respect to a function, include slightly risk-averse (0–1.0), moderately risk-averse (1.0–3.0), and strongly risk-averse (3.0–4.0). The equation for the transformation of relative risk aversion and absolute risk aversion is as follows:
where
stands for the absolute risk aversion for a specific location,
stands for the relative risk aversion, and
stands for the average net return per acre for each location of both DSS-based and calendar-based strategies.
The stochastic efficiency with respect to a function [
26] was used to evaluate the economic benefits of adopting BlightPro under different risk aversion levels. Stochastic efficiency with respect to a function was first used to compute the certainty equivalents (CEs) of the net return per acre for each fungicide application strategy. The CE is the risk adjusted value of the net return per acre for each fungicide application strategy. It is also the guaranteed amount of money that a decision maker would be willing to accept instead of taking the risky alternative [
27]. Thus, risky alternatives with higher CEs are preferred to alternatives with lower CEs [
26,
28,
29]. Stochastic efficiency with respect to a function was also used to identify the utility weighted risk premium (RP), which can also be interpreted as the value of information provided by BlightPro. Given the risk aversion level, the utility weighted risk premium (RP) can be calculated using the following equation:
A positive RP means that a tomato grower should prefer to use BlightPro rather than the calendar-based strategy. The RP could also be viewed as the value of information provided by BlightPro for the tomato growers.
For the SERF analysis, a utility function needs to be specified. Schumann et al. [
30] found that the efficient set identified by different utility functions can be similar. In this study, the power utility function was used to calculate the CEs for the alternative fungicide application strategies. The functional form of the power utility is as follows:
. The power utility function is often referred to as the constant relative risk aversion utility function, which has been widely used for modeling the risk aversion of decision makers [
31]. In addition to the constant relative risk aversion, this utility function exhibits a decreasing absolute risk aversion as an individual’s wealth increases. Namely, as an individual’s wealth increases, that individual is willing to take more risks. It is a commonly assumed characteristic of people’s risk aversion. The relative risk aversion levels,
, used for stochastic efficiency with respect to a function, ranged from 0 (risk neutral) to 4 (strongly risk averse) [
32].
The stochastic dominance and stochastic efficiency methods can be adapted to a wide range of individual decision making processes [
19,
33]. These approaches have been applied to evaluate various alternative decisions, such as beef farm insurance policies [
27], contract options [
34], tillage options [
35], irrigation strategies [
23], growing-finishing swine diets [
36], cotton planting acreage [
37], crop rotation and weed control methods [
38], farming machinery selection [
39], postharvest marketing strategies [
40], policy impacts [
41], and integrated pest and disease management strategies [
3,
14,
42,
43,
44,
45].
The Simulation and Econometrics to Analyze Risk (SIMETAR) software was used to conduct the stochastic dominance and stochastic efficiency with respect to a function analysis. These analyses were conducted separately for each location, in an Excel file. Each Excel file summarized the location-specific distributions of the net return per acre for the DSS-based and calendar-based strategies. The net return per acre distributions between the DSS-based strategy and the calendar-based strategy were compared so as to identify the preferred strategy. The same analyses were repeated and conducted 300 times using 300 Excel files (25 locations × 3 disease-resistance categories × 4 yield improvement assumptions).