Skip to main content

ClimatePrediction.net

I'm back from SC06 and almost recovered from jetlag. We're in the middle of a workshop on Virtual Organisations, which I'll report on in due course. Right now I want to highlight another of the projects we demonstrated on the UK e-Science stand at SC06.

ClimatePrediction.net uses home enthusiasts to run climate models on their PCs, inspired by SETI@Home and similar projects. This has the advantage that it can run multiple versions of models with slightly varying parameters and look at the most likely results.

It's good and worthwhile science but what makes the project particularly worth noting is the work they've done with education and the media. They have created a schools pack so that the system can be used in school teaching (that's pre-college school in USA terms). As a result they have several schools running models on their IT labs.

The project has also been fortunate to attract the interest of the BBC, who included it in a documentary on climate change and invited viewers to join in by running their own models. We played this documentary on our stand. The BBC are producing another programme to present the results, to be broadcast early next year.

At SC06, Carl Christensen of ClimatePrediction.net and David Anderson of BOINC and SETI@home gave a good discussion of what's required to run a successful project of this kind. The social questions of how to get a good user base have to be addressed as well as the technological problems. Several techniques exist but getting the BBC on your side must count as a particular useful one.

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…