clearclimatecode.org

By stoat on September 15, 2008.

clearclimatecode.org is a project of Nick Barnes, who occasionally comments here. Its an attempt to re-write the byzantine GISS historical record processing software into something that won't disgrace the 21st century, namely Python (boo hiss, but mt will be happy).

So the bugfixes are nice and clearly described, and are things like "STEP 0 of the GISTEMP code is in FORTRAN. This makes it unclear to the public." :-)

The aim is to re-implement the GISS algorithms, but in clearer code and in a more portable way, ideally producing identical results except for bug-fixes.

They have found one real bug so far: "GISTEMP STEP0 discards the final digit of every USHCN datum". Before anyone gets overexcited, GISS already know, have fixed it, and it makes no noticeable difference to the overall result.

Someone else, I think, was doing an open data averaging project, but I forget where. [Update: www.opentemp.org by John Van Vliet (thanks IH). Not sure if that is still active -W]

Tags
climate science

More like this

clearclimatecode.org
If you believe in climate related software being open, or even if you only believe in the ultimate triumph of Python over Fortran (personally I'm a Perlista when not rooting for embedded C, though I have respectable colleagues who adhere to the Python heresy, and who may convert me in time), then…
surfacetemperatures.org
surfacetemperatures.org/ is a bit odd - perhaps rather rushed. Braod aspects to be covered will be... suggests that they haven't even had time to spell check it. That they don't mention clearclimatecode.org/ makes me think this is going to be officious ponderous we-need-our-own-wheel stuff. Still,…
Figure 4 time (the data strikes back)
I thought I'd expand a bit more on why Svensmarks figure 4 is unacceptable (fig 4 of arXiv; fig 6 in Cosmoclimatology: a new theory emerges). Bear in mind that there is more wrong in the article than just this, though! The fig is: I'm arguing about the lower line, which purports to be a 90-64S…
Why is climate modelling stuck?
Why is climate modelling stuck? asked mt, and Bryan weighs in too. So I don't see why I shouldn't too. This is no kind of comprehensive list or manifesto, the way mt's is. Just some random thoughts. First of all, there are too many GCMs, and some of them are cr*p, so much so that they should simply…

bad link to ccc.

[Thanks. Fixed now, I hope -W]

Thank you for this link.
clearclimatecode.org will one day have a mailing list, some online data visualisation, and maybe a blog, but I have a day job and have spent the last couple of weeks getting CCC ready for our presentation at PyconUK yesterday. So for now and for a while to come there's just a big tarball to download, and the PNGs of our Pycon presentation. Email comments (and especially offers of help) to staff@clearclimatecode.org.

By Nick Barnes (not verified) on 15 Sep 2008 #permalink

My little OpenTemp program was built to do an independent analysis of the USA48 temperatures. I put it together in response to the SurfaceStations survey and suggestions by some that GISTEMP was wildly inaccurate.

I was able to show that the GISTEMP historical trends for the USA48 very closely matched a temperature history derived from only the "best" stations (as determined by SurfaceStations). Good times.

I haven't touched the code for about 10 months, but it's still available if anyone's interested. I'd like to resurrect and extend it but real life has been getting in the way.