Skip to main content

Met Office and CRU argue for open data and open code

Regular readers of this blog will recall that back in 2009 I looked at data released by the Met Office and CRU and found some errors and software bugs in the land surface temperature record known as CRUTEM3.

That experience led to a collaboration between myself and two professors and a joint paper in Nature entitled The Case for Open Computer Programs which used my experience with the closed Met Office code as one example. Our paper argued for the open release of data and code with all academic papers.

Today comes the news of a new paper from the Met Office and CRU describing an update to CRUTEM3 (called CRUTEM4). The paper is Hemispheric and large-scale land surface air temperature variations: An extensive revision and an update to 2010. It contains a couple of pleasing, if slightly surprising, paragraphs (my emphasis):
Given the importance of the CRUTEM land temperature analysis for monitoring climate change (e.g. Trenberth et al. 2007), our preference is that the underlying station data, and software to produce the gridded data, be made openly available. This will enhance transparency, and also allow more rapid identification of possible errors or improvements that might be necessary (see e.g. the earlier discussion of homogeneity adjustments in the SH).
and
As a result of these efforts, we are able to make the station data for all the series in the CRUTEM4 network freely available, together with software to produce the gridded data (http://www.cru.uea.ac.uk/cru/data/temperature/ and http://www.metoffice.gov.uk/hadobs/).
The Met Office site says the following of the code release:
The code required to produce the CRUTEM4 fields and timeseries will soon be made available. Note that code previously released for CRUTEM3 cannot be used to exactly reproduce CRUTEM4 temperature series due to changes in processing methodology.
Hurrah!

Let's hope that this becomes a trend in science.

Comments

Francis Turner said…
Hurray indeed. If anyone in the future should ask what good came of "Climategate" then this will be one clear answer. And if it helps make other climatescientists do the same then even better.

But it's all somewhat ironic. If they'd done this 5 years ago then there might not have been a Climategate because it seems like at least one of the drivers for that leak was the persistent stonewalling of FOIA requests to get precisely this information.
Paul Matthews said…
It is good to see all the data for CRUTEM4 released.

The change of attitude is not really surprising if you are familiar with the recent history.
The people to be thanked for this are Jonathan Jones and Don Keiller, who put in requests for CRU data and continued to appeal after CRU's refusals, and the information commissioner who in June last year over-ruled CRU's objections and ordered them to release the data within 35 days.

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it:


Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name.

There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly.

What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message:

Our system is unable to process last names that contain non-letters, please replace them with spaces.

Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your last name …

All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands. They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0image by Shinji
I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring):



The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30).
The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {
    float m = (360-30*float(h))*2/13;
    int s = round(60*(m-floor(m)));
    int col = h%6;
    int row = floor(h/6);
    draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1), r, h, floor(m…

Importing an existing SSL key/certificate pair into a Java keystore

I'm writing this blog post in case anyone else has to Google that. In Java 6 keytool has been improved so that it now becomes possible to import an existing key and certificate (say one you generated outside of the Java world) into a keystore.

You need: Java 6 and openssl.

1. Suppose you have a certificate and key in PEM format. The key is named host.key and the certificate host.crt.

2. The first step is to convert them into a single PKCS12 file using the command: openssl pkcs12 -export -in host.crt -inkey host.key > host.p12. You will be asked for various passwords (the password to access the key (if set) and then the password for the PKCS12 file being created).

3. Then import the PKCS12 file into a keystore using the command: keytool -importkeystore -srckeystore host.p12 -destkeystore host.jks -srcstoretype pkcs12. You now have a keystore named host.jks containing the certificate/key you need.

For the sake of completeness here's the output of a full session I performe…