Moving right along since the problem with Harry was identified on Super Bowl Sunday, BAS reports:
This is a list of corrections that have been made to the AWS data tables and a link to the table before the corrections were applied, any suspected errors should be reported to Steve Colwell
(2/2/09)The AWS data for Harry have been corrected after is was reported by Gavin Schmidt that data from Gill had been added where data for Harry did not exist. The incorrect data file for Harry temperatures can be accessed here
(4/2/09)The AWS data for Racer Rock since April 2004 have been removed from the READER website as the values appear to come from a different station even though they were transmitted on the GTS (Global Telecommunications System) as 89261 which the WMO (World Meteorological Organization) still list as being Racer Rock. The incorrect data file for Racer Rock temperatures can be accessed here
(4/2/09)The AWS data for Penguin Point since January 2007 have been removed from the READER website as the values received on the GTS appear to come from a different station and this AWS is reported as being removed at the start of 2007. The incorrect data file for Penguin Point temperatures can be accessed here
(4/2/09)The AWS data for Clean Air since January 2005 have been removed from the READER website as the values received on the GTS appear to come from a different station and this AWS is reported as being removed at the start of 2005. The incorrect data file for Clean Air temperatures can be accessed here
I compliment British Antarctic Survey for being professional in dealing with the situation. Clean Air is in Steig Table S1, Harry in Steig Table S2. Penguin Point and Racer Rock are in neither table. But it seems not beyond imagination that the exclusion of bad data might make them eligible for Table S1 or S2 – whatever the eligibility criteria (and I don’t pretend to have any idea how eligibility for these exclusive clubs is determined.) So the mere fact that they did not contribute to the present recon, if they didn’t, doesn’t mean that they shouldn’t have – once the records are corrected. Time will tell.
While Steig has asserted that I should know the impact of these various errors, I don’t. Maybe they’re negligible, maybe not. We’ll find out. In Steig’s shoes, as I’ve mentioned before, I would deal with present situation by placing end-to-end source code online so interested parties can readily assess the impact of these errors for themselves. If he’s certain that the errors “don’t matter”, that’s the best way to extinguish speculation.
Being stubborn about this is going to be unsustainable and he might as well get it over with.
Just my opinion.
Update: See here for a list of 6 surface (nor AWS) stations where problems of one sort or another are pending.