post

Open source, open data, climate, energy and collaboration

Hard drive

James pointed me to a post yesterday about Transparency in energy usage – it made for interesting reading.

The article talks about the benefits of having open data in the energy arena. In this case, the post is specifically talking about the US Energy Information Administration‘s publishing of historical annual energy statistics for the entire US – included are data on total energy production, consumption, and trade; overviews of petroleum, natural gas, coal, electricity, nuclear energy, renewable energy, international energy, as well as financial and environmental indicators; and data unit conversion tables.

The data is downloadable in PDF, XLS and CSV formats, sliced and diced in any number of ways, or you can download it in its entirety. Amazing stuff.

By the way, if you don’t think open data can be made fascinating, you haven’t seen what Hans Rosling can do with the visualisation of statistics.

The article correctly points out though that the data, by itself, is not easily digestible. It is the combination of open data, along with the collaborative efforts of GOOD with hyperakt which makes this data far easier to digest.

And that’s key – we have seen the massive savings open source software has brought us (saving $60bn per annum, in direct costs). The other real benefits of open source though come from its crowd-sourced nature (rapid bug-fixing, security, mitigation of vendor collapse/product discontinuation, community, etc.).

Given the two recent controversies around climate science – a bit more crowd-sourcing of the data and methodologies in climate science should be welcomed by anyone seeking to add to climate science’s credibility.

With that in mind, it is great to see the Climate Code Foundation set up. The Climate Code Foundation say their goals are to promote public understanding of climate science:

  • by increasing the visibility and clarity of the software used in climate science, and by encouraging climate scientists to do the same
  • by encouraging good software development and management practices among climate scientists and
  • by encouraging the publication of climate science software as open source

The more openness and transparency there is in climate science (and every other science but especially climate science), the better for everyone (except perhaps the Lord Moncktons of the world).

You should follow me on Twitter here

Photo credit splorp

post

Clear Climate Code project needs your help

Climate record
Photo Credit vodstrup

I came across the Clear Climat Code project via a message from Sig.

Like all good ideas, this one is very simple –

The Clear Climate Code project writes and maintains software for climate modelling and analysis, with an emphasis on clarity and correctness.

The results of some climate-related software are used as the basis for important public policy decisions. If the software is not clearly correct, decision-making will be obscured by debates about it. The project goals are to clear away that obscurity, to increase the clarity and correctness of climate science software.

Ticks two of my favourite boxes straight away – open source and the climate!

The guys in Ravenbrook, who are coordinating this project took this task on themselves and they have decided to seek a little outside help in the process.

If you can program in Python and would like to help out, you can get in touch with Ravenbrook by email here