<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: 19 Versions and Whadda You Get</title>
	<atom:link href="http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/feed/" rel="self" type="application/rss+xml" />
	<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/</link>
	<description>by Steve McIntyre</description>
	<lastBuildDate>Tue, 21 May 2013 15:32:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Adjustments to GISS, pre-Y2K, post-Y2k and current - US Message Board - Political Discussion Forum</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-242551</link>
		<dc:creator><![CDATA[Adjustments to GISS, pre-Y2K, post-Y2k and current - US Message Board - Political Discussion Forum]]></dc:creator>
		<pubDate>Mon, 04 Oct 2010 17:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-242551</guid>
		<description><![CDATA[[...] to GISS, pre-Y2K, post-Y2k and current    from 19 Versions and Whadda You Get Climate Audit      Quote: Pre-Y2K: As of mid-2007, prior to the identification of the Y2K error, NASA used the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] to GISS, pre-Y2K, post-Y2k and current    from 19 Versions and Whadda You Get Climate Audit      Quote: Pre-Y2K: As of mid-2007, prior to the identification of the Y2K error, NASA used the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Urbinto</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138585</link>
		<dc:creator><![CDATA[Sam Urbinto]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 16:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138585</guid>
		<description><![CDATA[How about a reading at the top of every two hours at two locations (or 1 location for two consecutive days) starting at midnight:

12 45 50
02 50 51
04 50 52
06 50 53
08 55 54
10 55 55
12 50 56
14 50 57
16 55 58
18 55 59
20 60 60
22 60 45

So both days are a mean of 57.5

But what does that really tell you?]]></description>
		<content:encoded><![CDATA[<p>How about a reading at the top of every two hours at two locations (or 1 location for two consecutive days) starting at midnight:</p>
<p>12 45 50<br />
02 50 51<br />
04 50 52<br />
06 50 53<br />
08 55 54<br />
10 55 55<br />
12 50 56<br />
14 50 57<br />
16 55 58<br />
18 55 59<br />
20 60 60<br />
22 60 45</p>
<p>So both days are a mean of 57.5</p>
<p>But what does that really tell you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ChrisZ</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138584</link>
		<dc:creator><![CDATA[ChrisZ]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 16:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138584</guid>
		<description><![CDATA[I have been lurking and reading here for quite some time, and the ongoing TOB discussion is the one that puzzles me most - both because I still can&#039;t figure out how such a bias should come to exist at all due to the changes you describe (except maybe a one-off outlier on the very day the observation time is changed because one Tmin or Tmax is counted twice or not at all), and because it should be ridiculously easy to end the discussion by either showing the non-existence or determining the amount of the effect. Let me explain:

If I&#039;m not very mistaken, there exist hourly or even by-the-minute temperature data for certain places and periods. Take one month or so of these and hack it into 24-hour slices - first at 0:00, then (with the same source data) at 1:00, 2:00, and so on. To shorten the procedure, start by cutting your 24-hour periods at the two times of day  noted as &quot;most critical&quot; above, namely 5PM and 7AM. For each set of 24-hour data slices, find Tmin and Tmax and calculate Tmean. Compare the two sets of Tmax/Tmean/Tmin etc. found. I have a strong feeling the two sets at worst have an offset by a day against each other, but certainly NOT by so-and-so-many degrees Celsius (as the one-day offset can obviously give both positive and negative temp differences depending on the slope of the curve at any point, but they will be negligible when looking at whole months, years, or even decades).

Back to lurk mode (unless someone point me to the kind of data I am talking about so that I may make the experiment myself...)]]></description>
		<content:encoded><![CDATA[<p>I have been lurking and reading here for quite some time, and the ongoing TOB discussion is the one that puzzles me most &#8211; both because I still can&#8217;t figure out how such a bias should come to exist at all due to the changes you describe (except maybe a one-off outlier on the very day the observation time is changed because one Tmin or Tmax is counted twice or not at all), and because it should be ridiculously easy to end the discussion by either showing the non-existence or determining the amount of the effect. Let me explain:</p>
<p>If I&#8217;m not very mistaken, there exist hourly or even by-the-minute temperature data for certain places and periods. Take one month or so of these and hack it into 24-hour slices &#8211; first at 0:00, then (with the same source data) at 1:00, 2:00, and so on. To shorten the procedure, start by cutting your 24-hour periods at the two times of day  noted as &#8220;most critical&#8221; above, namely 5PM and 7AM. For each set of 24-hour data slices, find Tmin and Tmax and calculate Tmean. Compare the two sets of Tmax/Tmean/Tmin etc. found. I have a strong feeling the two sets at worst have an offset by a day against each other, but certainly NOT by so-and-so-many degrees Celsius (as the one-day offset can obviously give both positive and negative temp differences depending on the slope of the curve at any point, but they will be negligible when looking at whole months, years, or even decades).</p>
<p>Back to lurk mode (unless someone point me to the kind of data I am talking about so that I may make the experiment myself&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hu McCulloch</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138583</link>
		<dc:creator><![CDATA[Hu McCulloch]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 14:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138583</guid>
		<description><![CDATA[Re Geoff Sherrington, #236, I think you are wrongly assuming that we know when Max and Min  occurred.  In fact, for most stations all we know is the time of observation and what the min and max tmeperatures were since the last reading and resetting of the thermometers or MMTS.  It would be trivial to wire a thermistor to a 15-year-old PC to integrate temperature over a 24 hour period to get the true daily mean, but even the &quot;modern&quot; MMTS are read manually once a day for 24-hour max and min, just like the old liquid-in-glass models.

Even if NWS went to a computer-age technology, we would still be stuck with over a century of historical data to compare the present to.  In the TOBS thread, I argued that the best time to measure, in terms of avoiding the double counting bias and wild card, would be around 9AM or 9PM.  The most popular times have been 5PM or 7AM, but 7AM is too close to the overnight min, and 5PM too close to the daily high.  Switching from 5PM to 7AM is going to generate a big drop in mean tmeperature, that requires an offsetting upward adjustment.  Eyeballing Karl&#039;s Figure 8, it looks like about +.9 dC would be justified.]]></description>
		<content:encoded><![CDATA[<p>Re Geoff Sherrington, #236, I think you are wrongly assuming that we know when Max and Min  occurred.  In fact, for most stations all we know is the time of observation and what the min and max tmeperatures were since the last reading and resetting of the thermometers or MMTS.  It would be trivial to wire a thermistor to a 15-year-old PC to integrate temperature over a 24 hour period to get the true daily mean, but even the &#8220;modern&#8221; MMTS are read manually once a day for 24-hour max and min, just like the old liquid-in-glass models.</p>
<p>Even if NWS went to a computer-age technology, we would still be stuck with over a century of historical data to compare the present to.  In the TOBS thread, I argued that the best time to measure, in terms of avoiding the double counting bias and wild card, would be around 9AM or 9PM.  The most popular times have been 5PM or 7AM, but 7AM is too close to the overnight min, and 5PM too close to the daily high.  Switching from 5PM to 7AM is going to generate a big drop in mean tmeperature, that requires an offsetting upward adjustment.  Eyeballing Karl&#8217;s Figure 8, it looks like about +.9 dC would be justified.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Sherrington</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138582</link>
		<dc:creator><![CDATA[Geoff Sherrington]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 11:29:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138582</guid>
		<description><![CDATA[Lights - some thoughts

Satellites measure lights as Mosh and others described above. However, the probability that a light detector at whatever frequency precisely captures a town&#039;s lights, completely from N to S and E to W as it sweeps along is just an accident of geometry on a given pass. If the PM tube sees just the edge of town it will report a small lights. If it traverses the centre, it will report larger. If it makes a number of passes and these are combined, then you have to know the maths of how they are combined and the associated errors. In particular, the positional errors are so large that a combination of say 10 images is unlikely to aggregate to more than a blob which has little to do with the true shape of the town - or the location of the climate station.

How this blob relates to Google maps etc is a further source of error, large enough to cause me severe disinterest in the topic.

If you too had spent years trying to find radiometric and magnetic anomalies from an aircraft, then going bush to find them on the ground, you&#039;d have a better appreciation of what I mean. And the aircraft typically flew 80-100 meters above terrain, not several hundred km like a satellite does.

I&#039;d really be giving the whole concept of lights a big miss. It&#039;s got classic signs of being promotional with spin, not hard science.]]></description>
		<content:encoded><![CDATA[<p>Lights &#8211; some thoughts</p>
<p>Satellites measure lights as Mosh and others described above. However, the probability that a light detector at whatever frequency precisely captures a town&#8217;s lights, completely from N to S and E to W as it sweeps along is just an accident of geometry on a given pass. If the PM tube sees just the edge of town it will report a small lights. If it traverses the centre, it will report larger. If it makes a number of passes and these are combined, then you have to know the maths of how they are combined and the associated errors. In particular, the positional errors are so large that a combination of say 10 images is unlikely to aggregate to more than a blob which has little to do with the true shape of the town &#8211; or the location of the climate station.</p>
<p>How this blob relates to Google maps etc is a further source of error, large enough to cause me severe disinterest in the topic.</p>
<p>If you too had spent years trying to find radiometric and magnetic anomalies from an aircraft, then going bush to find them on the ground, you&#8217;d have a better appreciation of what I mean. And the aircraft typically flew 80-100 meters above terrain, not several hundred km like a satellite does.</p>
<p>I&#8217;d really be giving the whole concept of lights a big miss. It&#8217;s got classic signs of being promotional with spin, not hard science.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Sherrington</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138581</link>
		<dc:creator><![CDATA[Geoff Sherrington]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 11:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138581</guid>
		<description><![CDATA[TOBS again

It&#039;s 1.25 am in California now and that makes for easy typing in Australia since most of USA is asleep. And it&#039;s a cool evening as the last day of Feb 2008 ends. The Bureau of Meteorology reported that -

&lt;blockquote&gt;Victoria has experienced a relatively cool summer with maximum and minimum temperatures typically 1 to 3 degrees below average across the State, the coolest since 1995 in some areas.&lt;/blockquote&gt;

That was a historical snippet for year 2002, just to get you going.

For year 2008, Feb Tmax averaged 25.8 and Tmin averaged 14.5. The long-term Feb averages, years 1855-2007 are Tmax 25.1 and Tmin 15.9. Look at the difference in Tmin for this month!!

One swallow does not a summer make, but we are taught that CO2 causes global wrming everywhere, relentlessly, increasingly, with settled science.....

Back to Time of Observation Bias as adjusted for thermometers which record a daily Tmax and a daily Tmin. The TOBS adjustment became an issue because you could do simple sums that showed that if you read the instruments at different times of day, you could get yesterday&#039;s max or min instead of today&#039;s. So I&#039;ve just re-read Karl for the nth time.

The problem seems to be that the accepted methodolgy is to adjust the temperature axis, usually graphed as Y. The mistake occurs in time, on the X-axis. So why not adjust time instead of temperature?

Here is a quick, imperfect attempt at a flowsheet to correct for time.

Read time of observation. Select the preceding 24 hours. If Tmax and Tmin are both present, (and we assume this for this simple model) one is right. Review the past month. Calculate the time of day when the maximum is most often reached - say 2 pm. If the time of observation is before this, use the immediately prior Tmin as correct and go back to the high before it and record that as the Tmax for the day. (If the time of observation is after the monthly Tmax average time, reverse the labelling and accept the prior Tmax on the day as correct and search for the Tmin in the day preceding it, then accept it as the correct Tmin for that day.)

The main objection occurs when a station reading has been historically taken close to the daily max or min. This can be the case where (say) 7 am readings are taken and the daily Tmin has or has not been registered. Historically, it is less common to take readings when close to monthly Tmax, say sometime between noon and 4 pm.

Of course, written station records override these assumptions when available.

If this method is used, in the majority of cases by far, either Tmax or Tmin will be correct and should not need adjustment. If one of them relates to the previous day, it could be higher or lower, but will usually be much the same if there has not been an extreme change in the critical part of the day.

Tmean (which I dislike) can then be taken arithmetically for each day (including an occasional wrong value up or down) and can then be averaged to get monthly obs.

The advantages of this approach are that few temperature changes will be needed and when adjustments are made, they will be close to the preceding day and usually rare, and usually cancelling pos with neg over the long term.

Now shoot me down please.]]></description>
		<content:encoded><![CDATA[<p>TOBS again</p>
<p>It&#8217;s 1.25 am in California now and that makes for easy typing in Australia since most of USA is asleep. And it&#8217;s a cool evening as the last day of Feb 2008 ends. The Bureau of Meteorology reported that -</p>
<blockquote><p>Victoria has experienced a relatively cool summer with maximum and minimum temperatures typically 1 to 3 degrees below average across the State, the coolest since 1995 in some areas.</p></blockquote>
<p>That was a historical snippet for year 2002, just to get you going.</p>
<p>For year 2008, Feb Tmax averaged 25.8 and Tmin averaged 14.5. The long-term Feb averages, years 1855-2007 are Tmax 25.1 and Tmin 15.9. Look at the difference in Tmin for this month!!</p>
<p>One swallow does not a summer make, but we are taught that CO2 causes global wrming everywhere, relentlessly, increasingly, with settled science&#8230;..</p>
<p>Back to Time of Observation Bias as adjusted for thermometers which record a daily Tmax and a daily Tmin. The TOBS adjustment became an issue because you could do simple sums that showed that if you read the instruments at different times of day, you could get yesterday&#8217;s max or min instead of today&#8217;s. So I&#8217;ve just re-read Karl for the nth time.</p>
<p>The problem seems to be that the accepted methodolgy is to adjust the temperature axis, usually graphed as Y. The mistake occurs in time, on the X-axis. So why not adjust time instead of temperature?</p>
<p>Here is a quick, imperfect attempt at a flowsheet to correct for time.</p>
<p>Read time of observation. Select the preceding 24 hours. If Tmax and Tmin are both present, (and we assume this for this simple model) one is right. Review the past month. Calculate the time of day when the maximum is most often reached &#8211; say 2 pm. If the time of observation is before this, use the immediately prior Tmin as correct and go back to the high before it and record that as the Tmax for the day. (If the time of observation is after the monthly Tmax average time, reverse the labelling and accept the prior Tmax on the day as correct and search for the Tmin in the day preceding it, then accept it as the correct Tmin for that day.)</p>
<p>The main objection occurs when a station reading has been historically taken close to the daily max or min. This can be the case where (say) 7 am readings are taken and the daily Tmin has or has not been registered. Historically, it is less common to take readings when close to monthly Tmax, say sometime between noon and 4 pm.</p>
<p>Of course, written station records override these assumptions when available.</p>
<p>If this method is used, in the majority of cases by far, either Tmax or Tmin will be correct and should not need adjustment. If one of them relates to the previous day, it could be higher or lower, but will usually be much the same if there has not been an extreme change in the critical part of the day.</p>
<p>Tmean (which I dislike) can then be taken arithmetically for each day (including an occasional wrong value up or down) and can then be averaged to get monthly obs.</p>
<p>The advantages of this approach are that few temperature changes will be needed and when adjustments are made, they will be close to the preceding day and usually rare, and usually cancelling pos with neg over the long term.</p>
<p>Now shoot me down please.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarkW</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138580</link>
		<dc:creator><![CDATA[MarkW]]></dc:creator>
		<pubDate>Mon, 25 Feb 2008 17:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138580</guid>
		<description><![CDATA[Heat from electricity is only one aspect of UHI, and not a major one at that.  The biggest are the amount of paved surface, and the amount of vegetation removed.  Most 2nd and third world cities have very high population densities.  This will be a major source of heat, even without electric lights.]]></description>
		<content:encoded><![CDATA[<p>Heat from electricity is only one aspect of UHI, and not a major one at that.  The biggest are the amount of paved surface, and the amount of vegetation removed.  Most 2nd and third world cities have very high population densities.  This will be a major source of heat, even without electric lights.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BarryW</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138579</link>
		<dc:creator><![CDATA[BarryW]]></dc:creator>
		<pubDate>Mon, 25 Feb 2008 16:22:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138579</guid>
		<description><![CDATA[Re &lt;a href=&quot;http://www.climateaudit.org/?p=2746#comment-216508&quot; rel=&quot;nofollow&quot;&gt;232&lt;/a&gt;

Yes but the amount of energy generated (i.e., heat) is much less per person.  I&#039;d have to believe that in equivalently populated  cities the UHIE for N. Korea is much less that in S. Korea.]]></description>
		<content:encoded><![CDATA[<p>Re <a href="http://www.climateaudit.org/?p=2746#comment-216508" rel="nofollow">232</a></p>
<p>Yes but the amount of energy generated (i.e., heat) is much less per person.  I&#8217;d have to believe that in equivalently populated  cities the UHIE for N. Korea is much less that in S. Korea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Mosher</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138578</link>
		<dc:creator><![CDATA[Steven Mosher]]></dc:creator>
		<pubDate>Mon, 25 Feb 2008 13:41:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138578</guid>
		<description><![CDATA[re 230. will do, ive been working on other stuff]]></description>
		<content:encoded><![CDATA[<p>re 230. will do, ive been working on other stuff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarkW</title>
		<link>http://climateaudit.org/2008/02/20/19-versions-and-whadda-you-get/#comment-138577</link>
		<dc:creator><![CDATA[MarkW]]></dc:creator>
		<pubDate>Mon, 25 Feb 2008 13:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=2746#comment-138577</guid>
		<description><![CDATA[BarryW,

The second and third world is a lot less electrified than the US.  The ratio of lights to people is a lot lower.  As an extreme example, have you seen the nightlights picture of the Korean pennisula?  It&#039;s real easy to tell where S. Korea ends and N. Korea starts.]]></description>
		<content:encoded><![CDATA[<p>BarryW,</p>
<p>The second and third world is a lot less electrified than the US.  The ratio of lights to people is a lot lower.  As an extreme example, have you seen the nightlights picture of the Korean pennisula?  It&#8217;s real easy to tell where S. Korea ends and N. Korea starts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
