Problems with the satellite record, as previously reported by DenialDepot
Over at WattsUpWithThat, a blog that poaches all my best commenters, the maps of UAH global temperature for the year 2009 have been posted and discussed without a hint of due skepticism.
DenialDepot has documented multiple instances of serious problems and causes of concern regarding the satellite record data. These problems remain unanswered.
One of the scientists involved in the satellite records posted an explaination of how the records are produced, which raises more questions than answers. The part that interested me the most was the acknowledgement that the satellite data is adjusted by FORTRAN programs:
POST-PROCESSING OF DATA AT UAH
The millions of calibrated brightness temperature measurements are averaged in space and time, for instance monthly averages in 2.5 degree latitude bands. I have FORTRAN programs I have written to do this. I then pass the averages to John Christy, who inter-calibrates the different satellites’ AMSUs during periods when two or more satellites are operating (which is always the case).
This is what I don't get. Other blogs have found errors in the satellite records and then have attempted to investigate the errors by comparing adjusted data. Ridiculous. All blog scientists should know the best way to find errors is to get hold of the source code! Why aren't these other blogs demanding the UAH satellite source code be released? If necessary use FOI requests!
So I am left to pick up the slack. I shot off a quick email to Roy Spencer:
I was very interested to read your latest article about how the satellite records are adjusted.
I am a blog scientist. Me and my commenters are interested in determining why the satellite records show too much warming over the last 30 years. You mention you adjust the raw data using some FORTRAN programs. Is this source code available online so we might replicate this process?
And by replicate I of course meant audit