Total Pageviews

Monday, November 25, 2019

ClimateGate 10 Year Anniversary: Chapter One -- The stunning "Harry Read Me" files

Based on the hacked
Climategate emails 
released in 2009, 2011 
and 2013:

The British Climatic 
Research Unit
included 
Mr. Ian “Harry” Harris,
who worked 
for four years 
to de-bug and 
properly 
document 
a CRU data base 
“TS 2.1” 
of many global 
weather station's 
recorded monthly 
temperature data.

It seems like
the database
had a lot 
of problems,
although perhaps
good enough for 
goobermint work


You should
read Harry's 
notes and 
come to 
your own
conclusion. 

One national input,
from the Australian 
Bureau of Meteorology, 
had frequent adjustments, 
that resulted in a greater 
warming trend.

Below are 
"Harry’s" comments, 
from a 200-page 
logging of his notes
(reformatted for easier reading):


Concerning Australia 
temperature data:
"What a bloody mess. 

Now looking at the dates
… something bad 
has happened, hasn’t it. 

COBAR AIRPORT AWS 
[data from an Australian 
weather station] cannot 
start in 1962, it didn’t open 
until 1993! 

… getting seriously fed up 
with the state of the 
Australian data. 

So many new stations 
have been introduced, 
so many false references 
… so many changes 
that aren’t documented
 … I am very sorry to report 
that the rest of the databases 
seem to be in nearly as poor 
a state as Australia was
…Aarrggghhh! 

There truly is no end in sight…!"



Harry Harris also wrote,
concerning temperature
data in general:
OH  F**K  THIS. 

It’s Sunday evening, 
I’ve worked all weekend, 
and just when I thought 
it was done, I’m hitting 
yet another problem 
that’s based on the 
hopeless state 
of our databases

 … Bear in mind
that there is no 
working synthetic 
method for cloud, 
because Mark New 
lost the coefficients file 
and never found it again 
(despite searching 
on tape archives at UEA) 
and never recreated it

 … This whole project 
is SUCH A MESS. 

No wonder I needed therapy!!

 … So, uhhhh 
what in tarnation
 s going on? 

Just how off-beam 
are these datasets?!!

 … Unbelievable 
— even here the conventions 
have not been followed. 

It’s botch after botch after botch 

…Where is 
the documentation 
to explain all this?! 

… It’s halfway through April 
and I’m still working on it. 

This surely is 
the worst project 
I’ve ever attempted. 

Eeeek … Oh bugger. 

What the HELL is going on?!.. 

Oh GOD if I could start this 
project again and actually 
argue the case for junking 
the inherited program suite!! 

.,. Am I the first person 
to attempt to get the CRU 
databases in working order?!! 

… So, we can have 
a proper result, 
but only by including
 a load of garbage …


Who added 
those two 
series together? 

When? 

Why? 

Untraceable, 
except anecdotally. 


It’s the same story 
for many other 
Russian stations, 
unfortunately 
— meaning that
 (probably) there was 
a full Russian 
update that did  
no data integrity 
checking at all. 

I just hope 
it’s restricted 
to Russia!! 



… What the hell 
is supposed to 
happen here? 

Oh yeah – there is
no ‘supposed’, 
I can make it up. 

So (we) will allow 
bad databases 
to pass unnoticed, 
and good databases 
to become bad, 
but I really don’t think 
people care enough 
to fix ’em, 
and it’s the main reason 
the project is nearly
a year late.”