From HARRY-READ-ME text:
As you read the programmer's comments below, remember, this is only a fraction of what he says [in the HARRY_READ_Me.txt file]. These
presumably precise data are the backbone of climate science. Reading "HARRY_READ_Me.txt" it's clear the CRU's files were a mess. ... [And
yet] the CRU at East Anglia University is considered by many as the world's leading climate research agency. ...
-- Back to the gridding. I am seriously worried that our flagship gridded data product is produced by Delaunay triangulation - apparently
linear as well. As far as I can see, this renders the station counts totally meaningless. It also means that we cannot say exactly
how the gridded data is arrived at from a statistical perspective ... Of course, it's too late for me to fix it too. Meh.
-- But what are all those monthly files? DON'T KNOW, UNDOCUMENTED. Wherever I look, there are data files, no info about what they are
other than their names. And that's useless ...
-- It's botch after botch after botch.
-- This surely is the worst project I've ever attempted. Eeeek.
-- Oh, GOD, if I could start this project again and actually argue the case for junking the inherited program suite.
-- ... this should all have been rewritten from scratch a year ago!
-- Well, dtr2cld is not the world's most complicated program. Wheras cloudreg is, and I immediately found a mistake! ... a loop that, for
completely unfathomable reasons, didn't include months!
-- Am I the first person to attempt to get the CRU databases in working order?!!
-- As far as I can see, this renders the (weather) station counts totally meaningless.
-- 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.
-- 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.
-- What the hell is supposed to happen here? Oh yeah -- there is no 'supposed,' I can make it up. So I have : - )
-- You can't imagine what this has cost me -- to actually allow the operator to assign false WMO (World Meteorological
Organization) codes!! But what else is there in such situations? Especially when dealing with a 'Master' database of dubious provenance ...
-- So with a somewhat cynical shrug, I added the nuclear option -- to match every WMO possible, and turn the rest into new stations ... In
other words what CRU usually do. It will allow bad databases to pass unnoticed, and good databases to become bad ...
-- OH FUCK 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.
-- This whole project is SUCH A MESS. No wonder I needed therapy!! ... I am seriously close to giving up, again.
-- Right, time to stop pussyfooting around the niceties of Tim's labyrinthine software suites - let's have a go at producing CRU TS 3.0! since failing
to do that will be the definitive failure of the entire project..