
3.3 Reasoning Behind the Growing DegreeDay Approximation
Given accurate and complete local daily temperature readings, we can predict insect development (for example, codling moth) without relying on other observations (except, possibly, the first presence of adults at biofix). To be able to do this, we must magically approximate Growing DegreeDays using just the daily maximum and minimum temperature. This is an examination of the behavior of the growing degreeday approximation, using realworld temperature data. It does not validate the codling moth development model against actual codling moth development over the years, but others have done so (U. C. Agriculture and Natural Resources, Research Models and Coop's DegreeDay Models). 3.3.1 Raw DataData consists of hourly automated instrumental temperature observations from the Sheboygan County, Wisconsin, Memorial Airport (KSBM) between 19960831 18:53 and 20181108 17:53. The precision appears to be about one degree Fahrenheit (ASOSAWOSMETAR Data Download). The numbers of observations are: 2694 (1996), 7954 (1997), 8587 (1998), 8207 (1999), 11094 (2000), 8657 (2001), 7915 (2002), 10969 (2003), 11563 (2004), 11181 (2005), 10946 (2006), 11401 (2007), 11942 (2008), 11578 (2009), 11368 (2010), 11581 (2011), 11155 (2012), 11786 (2013), 11714 (2014), 11334 (2015), 11709 (2016), 11456 (2017), and 9742 (2018). There are several gaps of more than 5 hours. Many observations fall into these gaps and are not recorded. Some are recorded as missing. The numbers of gaps are: 4 (1996), 14 (1997), 4 (1998), 24 (1999), 18 (2000), 9 (2001), 12 (2002), 12 (2003), 10 (2004), 2 (2005), 19 (2006), 2 (2007), 3 (2008), 4 (2009), 1 (2010), 5 (2011), 2 (2013), 7 (2014), 4 (2015), 3 (2017), and 4 (2018). Taken together, these gaps cover many hours out of the years: 27 (1996), 140 (1997), 68 (1998), 427 (1999), 363 (2000), 99 (2001), 847 (2002), 249 (2003), 171 (2004), 13 (2005), 424 (2006), 17 (2007), 22 (2008), 32 (2009), 9 (2010), 110 (2011), 12 (2013), 110 (2014), 29 (2015), 95 (2017), and 111 (2018). Now and then, there are runs of (at least 5) consecutive observations of identical temperature (in at least 5 hours), which I consider implausible. These represent malfunctions probably of hardware and more certainly of software and may be interpreted as attempts to "clean" the data by plugging in readings to conceal missing or outofrange observations. I have taken the liberty of removing the days that such runs span: 19960913, 19960914, 19960926, 19961024, 19961120, 19961203, 19961205, 19961207, 19961208, 19961211, 19961212, 19961216, 19961217, 19970101, 19970102, 19970131, 19970201, 19970204, 19970205, 19970206, 19970220, 19970221, 19970301, 19970324, 19970412, 19970817, 19970823, 19970824, 19970913, 19970914, 19971024, 19971104, 19971105, 19971203, 19971204, 19971205, 19971206, 19971207, 19971209, 19971210, 19971225, 19980104, 19980105, 19980106, 19980107, 19980108, 19980117, 19980121, 19980122, 19980123, 19980125, 19980126, 19980127, 19980128, 19980129, 19980130, 19980201, 19980202, 19980205, 19980217, 19980218, 19980223, 19980224, 19980303, 19980304, 19980305, 19980308, 19980309, 19980318, 19980319, 19980320, 19980331, 19980415, 19980609, 19980610, 19980707, 19980708, 19980805, 19980806, 19980914, 19980915, 19981030, 19981031, 19981119, 19981120, 19990102, 19990122, 19990123, 19990124, 19990128, 19990205, 19990207, 19990226, 19990227, 19990228, 19990305, 19990404, 19990405, 19990422, 19990506, 19990512, 19990513, 19990927, 19991119, 19991120, 19991124, 19991214, 19991215, 20000112, 20000209, 20000212, 20000320, 20000718, 20000719, 20000821, 20000822, 20001031, 20001110, 20001116, 20001117, 20001129, 20010112, 20010113, 20010114, 20010115, 20010129, 20010130, 20010201, 20010202, 20010204, 20010205, 20010206, 20010208, 20010212, 20010213, 20010215, 20010228, 20010315, 20010316, 20010402, 20010812, 20010813, 20011025, 20011026, 20011027, 20011031, 20011129, 20011130, 20011201, 20011202, 20011216, 20011217, 20020107, 20020129, 20020130, 20020210, 20020214, 20020219, 20020220, 20020402, 20020407, 20020421, 20020422, 20020427, 20020428, 20020429, 20020501, 20020502, 20020614, 20020814, 20020823, 20020824, 20021007, 20021008, 20021025, 20021026, 20021101, 20021102, 20021111, 20021112, 20021121, 20021130, 20021217, 20021222, 20021224, 20021225, 20021226, 20021227, 20021228, 20030102, 20030105, 20030131, 20030203, 20030312, 20030511, 20030512, 20030912, 20030913, 20031114, 20031115, 20031122, 20040222, 20040308, 20040309, 20040314, 20040513, 20040823, 20040824, 20041017, 20041018, 20041027, 20041102, 20041103, 20041130, 20041207, 20041215, 20041216, 20050101, 20050124, 20050125, 20050130, 20050131, 20050201, 20051130, 20051201, 20051225, 20051229, 20051230, 20060105, 20060204, 20060306, 20060824, 20061112, 20061113, 20061114, 20061221, 20061222, 20061225, 20061226, 20061227, 20070225, 20070227, 20070228, 20070408, 20070409, 20070702, 20070703, 20070820, 20071027, 20071123, 20071124, 20071203, 20071220, 20071221, 20080130, 20080131, 20080203, 20080204, 20081102, 20081116, 20081117, 20081208, 20081209, 20090217, 20090218, 20090331, 20090527, 20090528, 20090925, 20090926, 20091031, 20091126, 20091127, 20091204, 20091205, 20091213, 20100104, 20100105, 20100106, 20100114, 20100115, 20100214, 20100221, 20100228, 20100312, 20100804, 20100911, 20101218, 20101219, 20110119, 20110127, 20110128, 20110301, 20110309, 20110503, 20111127, 20111216, 20120330, 20120331, 20120419, 20120420, 20121014, 20121029, 20121030, 20121109, 20121110, 20121130, 20121212, 20121226, 20121227, 20121228, 20130103, 20130116, 20130201, 20130209, 20130323, 20130324, 20130605, 20130606, 20130702, 20130703, 20130718, 20130719, 20131003, 20131004, 20131127, 20131128, 20131203, 20131204, 20131220, 20131221, 20131230, 20131231, 20140109, 20140110, 20140111, 20140120, 20140130, 20140217, 20140319, 20140403, 20140423, 20140424, 20140610, 20140821, 20140822, 20140823, 20140824, 20140911, 20140912, 20140913, 20141014, 20141015, 20141020, 20141021, 20141031, 20141101, 20141105, 20141208, 20141209, 20141210, 20141212, 20141213, 20141220, 20141221, 20141224, 20141225, 20141231, 20150112, 20150113, 20150114, 20150115, 20150120, 20150127, 20150204, 20150208, 20150216, 20150217, 20150325, 20150326, 20150825, 20150826, 20151003, 20151004, 20151005, 20151006, 20151127, 20151130, 20151221, 20151222, 20151226, 20151230, 20160103, 20160106, 20160107, 20160121, 20160125, 20160204, 20160214, 20160218, 20160219, 20160221, 20160222, 20160225, 20160321, 20160510, 20160511, 20160704, 20160705, 20160720, 20160721, 20160807, 20160812, 20160813, 20160907, 20161001, 20161002, 20161026, 20161116, 20161117, 20161123, 20161125, 20161130, 20161201, 20161202, 20161203, 20161204, 20161210, 20161217, 20161224, 20170102, 20170103, 20170105, 20170106, 20170117, 20170118, 20170124, 20170126, 20170127, 20170211, 20170212, 20170224, 20170304, 20170305, 20170324, 20170325, 20170326, 20170330, 20170331, 20170417, 20170418, 20170502, 20170806, 20170807, 20171012, 20171013, 20171014, 20171104, 20171105, 20171111, 20171115, 20171116, 20171118, 20171205, 20171206, 20171207, 20171210, 20171212, 20171213, 20171216, 20171217, 20171218, 20171228, 20180117, 20180118, 20180122, 20180124, 20180207, 20180222, 20180308, 20180403, 20180408, 20180409, 20180413, 20180414, 20180519, 20180920, 20180928, 20181013, 20181014, 20181106. The days in boldfaced text occur within months that contain (at least 3) corrupt days.
Because I plan to use this data to conduct sensitivity analysis of the model for codling moth development, I need to have fairly complete summer records. Accordingly, I have removed some years altogether that contain corrupt summer months: 2013, 2014, 2016. I searched for discontinuities in the data that remains with a moving window of (5) observations. I tried to predict the next observation by running a trend line through the window. I examined each discontinuity where my prediction differed from the actual by more than 20°F. Upon inspection, many of these discontinuities appeared plausible. Others appeared after data gaps. I took the liberty of eliminating a number observations that appeared implausible: 4 on 19961001, 4 on 19970501, 5 on 19971201, 6 on 19980101, 6 on 19981201, 6 on 19990101, 6 on 19990301, 6 on 19990501, 6 on 19991101, 2 on 20001103, and 1 on 20010731. That these rejected observations were taken on the first day of the month in many cases is curious.The numbers of discontinuities remaining are: 3 (1996), 17 (1997), 13 (1998), 20 (1999), 13 (2000), 9 (2001), 11 (2002), 8 (2003), 12 (2004), 5 (2005), 7 (2006), 5 (2007), 4 (2008), 4 (2009), 8 (2010), 6 (2011), 4 (2012), 7 (2015), 13 (2017), and 11 (2018). 3.3.2 Daily Average TemperatureThe first thing to do is show what average temperatures look like over 24 hours during the summer. Here is a spaghetti plot where each thread is a day in July and August. Fig. A The belief that temperature is a continuous phenomenon is compelling, and the lacy appearance of the spaghetti plot shown in Fig. A is disturbing because it shows that temperatures are clustered. This is because temperature is recorded in whole degrees Fahrenheit and on hourly intervals; nevertheless, because the underlying phenomenon must be continuous, there should be no particular intellectual difficulty in making the statistical leap of faith that we can treat the discrete measurements as though they are, too. Thus, the curve highlighted in light blue can be said fairly to represent the average from hour to hour of summer temperatures. Note that it is skewed slightly toward the afternoon. The next step is to idealize this curve. Here is the same spaghetti plot overlaid by an ideal sine wave. Fig. B This ideal curve shown in Fig. B closely matches the actual shown in Fig. A except for the skew and will be the basis for arguments that follow. By characterizing hourly temperatures during a day as a sine wave, the temperature at any hour does not have to be measured and recorded. Instead, an approximation can be calculated, given the maximum and minimum temperatures for that day. Also, the sine has pleasant mathematical properties that make some of the anticipated calculations fairly easy to do. ... so what should we do with this ideal curve? Plot growing DegreeDays, of course. Fig. C Fig. C shows how the temperature may vary during a chilly day. The daily maximum temperature is below the threshold temperature at which insect development begins, so there can be no Growing DegreeDays accrued at all for this day. Fig. D Fig. D shows a warmer day when the daily maximum temperature crosses the threshold temperature for a portion of the day. On a day such as this, we would record a small amount of Growing DegreeDays (GDD). Fig. E Fig. E shows a still warmer day when not only the daily maximum temperature crosses the threshold but also the daily average temperature is above the threshold. On a day like this, we would record a larger amount of Growing DegreeDays, shown in yellow and green. Also, the conventional way of calculating DegreeDays (DD), which is the difference shown in green and blue between the average temperature and the threshold, is positive but not so large as the Growing DegreeDays. The average temperature is assumed to be: \begin{equation} TAvg = (TMax + TMin) / 2.0 \end{equation}\begin{equation} \label{dd} DD = TAvg  TThreshold \end{equation} ... where \(TMax\) is maximum daily temperature and \(TMin\) is minimum daily temperature. For this reason the conventional DD calculation is sometimes called the maxmin method. Note that both DD and GDD are constrained not to be negative. Fig. F Fig. F shows a succession of warm nights when the daily minimum temperatures are above the threshold. Over a 24hour period such as this, the Growing DegreeDays, shown in yellow and green, is identical to the conventional DegreeDays, shown in green and blue. The rationale for using the sine wave instead of the maxmin average is this: By using the sine wave, we can capture more days on which there is a small contribution to insect development even though the average temperature is below the threshold. Fig. G Returning to the actual data for Sheboygan, Fig. G shows the average daily maximum and minimum temperatures recorded. Also shown are the conventional DegreeDays (DD) and the growing degree_days (GDD). Yellow highlights the days when daily minimum is above the threshold. On these days, DD and GDD track together. Orange highlights the days when DD and GDD diverge. Red highlights the days when only GDD is accrued. Thus, in Sheboygan the accrual of GDD begins earlier and thus outruns the accrual of DD for a period of six weeks in the spring. Fig. H Fig. H shows a spaghetti plot of the cumulative GDD in Sheboygan where each thread is a different year. 2012 was the warmest. 1997 was the coldest.
3.3.3 Variability
Fig. H shows a spaghetti plot of the cumulative GDD in Sheboygan along with the two prominent horizons of codling moth development: the first and second flight. For a given year, the time of a flight is predicted by when the cumulative GDD curve crosses the respective horizon. From the warmest (earliest) year to the coolest (latest) year, the difference between the dates of the first flight can be as much as five weeks and the same for the second flight. Two successive chemical treatments ten days apart will suppress larval activity for at most three weeks. Thus, chemical control cannot span the natural variability in the dates of codling moth development. For this reason it is better not to rely on a calendar for timing codling moth treatment. That is what the ancient Egyptians did who tried to predict the snow melt on the Mountains of the Moon. For timing codling moth treatment it is better to rely on tracking cumulative Growing DegreeDays using the methods proposed by Baskerville and Emin. 3.3.4 Methods of CalculationFig. H shows a spaghetti plot of the cumulative GDD in Sheboygan along with the average cumulative GDD and the average cumulative conventional DD. The Growing DegreeDays (GDD) calculated by Baskerville and Emin's single sine horizontal cutoff method outruns the conventional DegreeDays (DD) calculated by the maxmin method by about a week. Thus, for timing codling moth treatment, the method used to calculate DegreeDays is significant, and methods calculating Growing DegreeDays rather than conventional DegreeDays are preferred. There are other methods of estimating Growing DegreeDays besides single sine. U. C. Agriculture and Natural Resources (UCANR) publishes on their Web site a discussion of "DegreeDays," which describes similar methods. Also, they publish an "Evaluation of Several DegreeDay Estimation Methods in California Climates," which reviews performance of single sine, double sine, single triangle, and double triangle methods (among others) against hourly summation and concludes that all methods yield similar results during the spring and summer and that there is no particular advantage of the doubled methods that treat morning and afternoon separately. "The single triangle and single sine methods estimate DegreeDays relativity well," they say. While single triangle may be superior during the fall and winter (for daily temperature patterns experienced in California), use of single sine is still customary for studies of insect development.
Much of the research validating insect development against Growing DegreeDays recommends single sine methods (UCANR, "Research Models"), but many papers apparently do not specify the method by which their authors arrived at Growing DegreeDays. This leads one to conclude that any of the practical methods for estimating Growing DegreeDays are probably adequate. 3.3.4.1 Single SineCoop presents a computer algorithm for calculating Growing DegreeDays. Here's how it works. Temperatures are assumed to follow an idealized sine wave throughout the hours of each day. The sine wave is clipped horizontally from below by the threshold temperature. Growing DegreeDays for each day is proportional to the area under the curve above the threshold, which thus depends on the threshold and the maximum and minimum temperatures for each day. The algebra, trigonometry, and Integral Calculus involved are apparently not too exotic but are fairly obscure. Here follows my reconstruction. If the threshold temperature is below the daily minimum temperature, the answer we must give is the conventional one. See Formula \(\ref{dd}\), above. This is because the curve is not clipped. Below, we're going to use the following ¨simplifying¨ expression, so I suppose I ought to define it here. \begin{align} Let \quad D2& = 2 * DD\\ & = 2 * TThreshold  (TMax + TMin) \end{align} Consider a sine wave from \(\pi/2\) to \(3\pi/2\) radians with its peak at high noon (\(\pi/2\) radians). If the threshold temp is above the daily minimum temp, we need to integrate over a portion of the curve. The essential magic is to discover the angle \(\Theta\) where the sine wave, scaled and offset to the average temperature, crosses this threshold. Then we can cast away the area below the threshold along with the tails of the curve. Because the sine wave is symmetric about \(\pi/2\), we need to integrate only between \(\pi/2\) and \(\pi/2\). The definite integral of the sine wave from \(\pi/2\) and \(+\pi/2\) is zero because half of it is negative, so that doesn't do us much good. We'll have to choose a different function. How about \(\sin + 1\)? \begin{align} \int_{\pi/2}^{+\pi/2}{(\sin(t) + 1)}dt& = \cos(\pi/2)  (\cos(\pi/2)) + \pi/2  (\pi/2)\\ & = \pi \end{align} This is the area under the curve. To normalize the calculations to follow, we have to multiply by this: \begin{equation} DownscaleFactor = 1 / \pi \end{equation} When \(TThreshold == TMin\) and \(\Theta == \pi/2\), the answer we must give is \(DD\) as in Formula \(\ref{dd}\). This becomes our upscale_factor: \begin{align} UpscaleFactor& = ((TMax + TTMin) / 2)  TThreshold\\ & = (TMax + TMin  2 * TThreshold) / 2\\ & = (TMax + TMin  2 * TMin) / 2\\ & = (TMax  TMin) / 2 \end{align} The following formula is similar to that given by Baskerville and Emin in their Fig. 1.B: \begin{equation} GDD = DownscaleFactor * (UpscaleFactor * WholeArea  ClippedArea))\\ \end{equation} where: \begin{align} WholeArea& = \int_{\Theta}^{\pi/2}{(sin(t) + 1)}dt\\ & = \cos(\pi/2)  (\cos(\Theta)) + (\pi/2  \Theta)\\ & = \cos(\Theta) + (\pi/2  \Theta) \end{align} \begin{align} ClippedArea& = \int_{\Theta}^{\pi/2}{(TThreshold  TMin)}dt\\ & = (TThreshold  TMin) * (\pi/2  \Theta) \end{align} thus: \begin{multline} GDD = DownscaleFactor * (UpscaleFactor * (\cos(\Theta)\\ + (\pi/2  \Theta)))  (TThreshold  TMin) * (\pi/2  \Theta) \end{multline}\begin{multline} \quad = (1 / \pi) * (((TMax  TMin) * (\cos(\Theta)\\ + (\pi/2  \Theta)) / 2)  ((TThreshold  TMin) * (\pi/2  \Theta))) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * (\cos(\Theta)\\ + (\pi/2  \Theta))  2 * (TThreshold  TMin) * (\pi/2  \Theta)) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * \cos(\Theta)\\ + (TMax  TMin) * (\pi/2  \Theta)  2 * (TThreshold  TMin) * (\pi/2  \Theta)) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * \cos(\Theta)\\ + ((TMax  TMin)  2 * (TThreshold  TMin)) * (\pi/2  \Theta)) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * \cos(\Theta)\\ + (TMax  TMin  2 * TThreshold + 2 * TMin) * (\pi/2  \Theta)) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * \cos(\Theta)\\ + (TMax  2 * TThreshold + TMin) * (\pi/2  \Theta)) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * \cos(\Theta)\\  (2 * TThreshold  (TMax + TMin)) * (\pi/2  \Theta)) \end{multline}\begin{multline} \quad = (1 / 2\pi) * ((TMax  TMin) * \cos(\Theta)  D2 * (\pi/2  \Theta)) \end{multline} ... which is the formula that Coop uses to calculate GDD. ===== Now, for the essential magic we need to compute: \begin{equation} \label{arcsin} \Theta = \arcsin(UnitBase) \end{equation} ... where \(UnitBase\) is the threshold temperature scaled to the sine wave (not \(\sin + 1\)): \begin{multline} UnitBase = 2 * (TThreshold  TMin) / (TMax  TMin)  1 \end{multline}\begin{multline} \quad = (2 * (TThreshold  TMin)  (TMax  TMin)) / (TMax  TMin) \end{multline}\begin{multline} \quad = (2 * TThreshold  2 * TMin  TMax + TMin) / (TMax  TMin) \end{multline}\begin{multline} \quad = (2 * TThreshold  TMin  TMax) / (TMax  TMin) \end{multline}\begin{multline} \quad = (2 * TThreshold  (TMax + TMin)) / (TMax  TMin) \end{multline}\begin{multline} \quad = D2 / (TMax  TMin) \end{multline} But there's a fly in this ointment. We want to have pretty good computational accuracy where \(UnitBase\) is pretty close to \(\pm1\), which should yield an \(\arcsin\) result pretty close to \(\pm\pi/2\), but that is just where the accuracy of realworld \(\arcsin\) implementations falls down due to inherent granularity of simulating mathematics of continuous functions on binary machines, which can handle only discrete values. Maybe it would be better to calculate \(\Theta\) using the \(\arctan\), instead. I think it's just this easy: \(\sin(\Theta) = a / c\) where the sides of the right triangle are: \((a * a) + (b * b) = (c * c)\) and, using the same angle: \(\tan(\Theta) = a / b = a / \sqrt{c^2  a^2}\) \begin{equation} Now \quad \Theta = \arcsin(a / c) \end{equation} and by Formula \(\ref{arcsin}\) this means that: \begin{align} a& = UnitBase\\ and \quad c& = 1 \end{align} Then, the same angle would be: \begin{align} \Theta& = \arctan(a / \sqrt{c^2  a^2})\\ & = \arctan(UnitBase / \sqrt{(1 * 1)  (UnitBase * UnitBase)})\\ & = \arctan((D2 / (TMax  TMin)) / \sqrt{1  (D2 / (TMax  TMin))^2})\\ & = \arctan(D2 / \sqrt{(TMax  TMin) * (TMax  TMin)  D2 * D2}) \end{align} ... which, if I have not deluded myself, is the formula for \(\Theta\) used by Coop. (In practice however, using the \(\arcsin\) yields identical results rounded to the nearest integer.) Nowadays, we are accustomed to enjoying the fruits of highspeed computing and think nothing of writing little programs to churn through thousands of such calculations that would have been extremely tedious, time consuming, and error prone to work out with a slide rule. The ease with which it is done causes us to imagine that, however minuscule the improvement in timing insect treatments, the effort is small and will surely be repaid. 3.3.4.2 CutoffFig. I Fig. I shows Growing DegreeDays without any cutoff. The lower threshold is implicit in the single sine method. Obviously insect development slows in cooler weather. The lower threshold preserves the proportionality of insect development with Growing DegreeDays by introducing nonlinearity between temperature and Growing DegreeDays. It is to be expected that some kind of upper cutoff is required, as well. Baskerville and Emin demonstrate two approaches. Fig. J Fig. J shows the horizontal cutoff typical of the codling moth model and other insect models. In warm weather, insect development is not constrained by temperature, which is to say it is constrained by other things and no longer dependent on temperature. To preserve proportionality of insect development with Growing DegreeDays, it is necessary to introduce nonlinearity between temperature and Growing DegreeDays at warmer temperatures. One way to achieve this is with a horizontal cutoff. Once we are able to characterize the formula for Growing DegreeDays without any cutoff in terms of just \(TMax\), \(TMin\), and \(TThreshold\), it is trivial to characterize the area to be "cutoff" with the same formula in terms of just \(TMax\), \(TMin\), and \(TCutoff\). Fig. K Fig. K shows a vertical cutoff, which is not typical of the model for codling moth although it is typical of other insects such as Spotted Tentiform Leafminer (Phyllonorycter blancardella). In warm weather, insect development may be slowed or stopped just as it is in cool weather. Another way to introduce nonlinearity between temperature and Growing DegreeDays at warmer temperatures is with a vertical cutoff, We can characterize the area to be "cutoff" as the same as the horizontal cutoff plus the rectangle beneath it. Fig. L Fig. L shows a cutoff intermediate between a horizontal and a vertical cutoff. The intermediate cutoff has been validated for Blue Alfalfa Aphid (Acyrthosiphon kondoi). The intermediate cutoff was not demonstrated by Baskerville and Emin, but it is easily implemented. It is double the area of the horizontal cutoff. Fig. M Fig. M compares the behavior of the three kinds of cutoff against temperature. All of the sine methods show a flattening of Growing DegreeDays with decreasing temperature at the threshold. The same is to be expected at the cutoff. Without a cutoff, Growing DegreeDays and insect development would increase indefinitely with increasing temperature, and this is implausible. The horizontal cutoff gives the same kind of flattening at the cutoff temperature that all methods exhibit at the threshold temperature. Thus, it is useful for modeling the insects whose development plateaus in warm weather. The vertical cutoff is for insects that show an abrupt decrease in development at the cutoff temperature, and the intermediate cutoff is better for insects that show a more graceful decline. Naturally, the reader is encouraged to seek out research that validates growing degreeday models for the insect species to be treated. (See, for example, the list of insect "Research Models" published by U. C. Agriculture and Natural Resources, and please refer to Coop's "Library of DegreeDay Models," as well.) The reader should expect to gain an inkling of the calculation method and kind of cutoff used by the researchers. In the absence of these, it is not unreasonable to choose single sine with horizontal cutoff. More importantly, the research ought to indicate the threshold and cutoff temperatures that govern the development of the species to be treated. 