Software Carpentry

Helping scientists make better software since 1997

Archive for June 2007

Two Studies of ASCI (and no, that’s not a typo)

After spending ten years helping scientists write programs for massively-parallel computers, I realized that what scientists really needed was to learn how to program, full stop. It took me another eight years to (a) get up to speed with the theory and practice of modern software engineering, (b) realize how big the gap between the two was, and (c) accept that the only people who are entitled to have an opinion about how we ought to be building software are the ones who are studying how well their favorite tools and practices actually work in the field. I no longer care what you’re pushing—formal methods and cleanroom development or agile adhocracy and pair programming—unless you’ve gone the extra mile and collected data to show what effect it’s actually having.

That’s why I was so pleased to come across these two papers:

  1. Post and Kendall: “Software Project Management and Quality Engineering Practices for Complex, Coupled Multiphysics, Massively Parallel Computational Simulations: Lessons Learned from ASCI”. Intl. Journal of High Performance Computing Applications, 18(4), Winter 2004, pp. 399-416.
  2. Carver, Kendall, Squires, and Post: “Software Development Environments for Scientific and Engineering Software: A Series of Case Studies”. Proc. ICSE 2007, May 2007, pp. 550-59, 0-7695-2828-7.

“ASCI” is the Accelerated Strategic Computing Initiative. Launched in the mid-1990s, its mission was to produce a new generation of software for the US nuclear weapons program. These are big pieces of code: millions of lines, with lifespans measured in decades, doing some of the most complicated math ever devised by human beings. Hundreds of millions of dollars have been spent, and thousands of programmer-years, so it’s worth asking, “How’s it going? And what could be done better?”

According to the authors of these papers, who have spent a lot of time studying the major projects within ASCI, the answers are “So-so” and “Lots” respectively. Some parts of ASCI are considered outright failures: the Blanca project, for example, was so much in love with funky technology like template metaprogramming that it never delivered the science it was supposed to. Other parts, though, have come through, though many have taken longer to do so than originally envisioned. As the authors point out, though, management was “aggressive” in setting ASCI’s specs, schedule, and resourcing levels, so it’s not surprising that mere mortals couldn’t live up to them.

A lot of what these papers say is standard project management dogma. For me, the most important point was, “Emphasize ‘best practices’ instead of ‘processes’.” Every successful development team I’ve ever seen worried more about “doing the right thing” than about following the steps in a flowchart. Knowing what the “right thing” is, now, that’s the tricky part, but it’s what I’d like most to impart to my students. If you come back in ten years and ask me how I’m doing, I ought to have some data for you.


Written by Greg Wilson

2007/06/27 at 21:40

Posted in Content, Research

Software Carpentry at LLNL

Titus Brown has posted about the first run of his Advanced Software Carpentry course at Lawrence Livermore National Laboratory.  It was a bit bumpy, but seems to have gone well overall, and he has put a ton of useful material on the web.

Written by Greg Wilson

2007/06/26 at 06:15

Posted in LLNL, Version 3

Software Carpentry Screencasts by Chris Lasher

Chris Lasher, a grad student at the University of Virginia Virginia Tech (sorry, sorry), has posted some screencasts about version control based on the Software Carpentry notes at; a second series about using the shell should be up shortly. It’s just plain cool to see the material picked up and carried forward in ways I wouldn’t even have thought of a couple of years ago.

Later: now there’s, the Journal of Visual Experiments, and others — the world moves on.

Written by Greg Wilson

2007/06/20 at 07:49

Posted in Content

Inspirational Videos

This, on scientific computing and visualization, is pretty fricken cool.

Written by Greg Wilson

2007/06/20 at 06:57

Posted in Noticed

Nature Precedings

Tim O’Reilly posted a note from Timo Hannay, of Nature magazine, about their new “Precedings“, which:

giv[es] researchers a place to post documents such as preprints and presentations in a way that makes them globally visible and citable. Submissions are filtered by a team of curators to weed out obviously inappropriate material, but there’s no peer-review so accepted contributions appear online very quickly — usually within a couple of hours.

Written by Greg Wilson

2007/06/18 at 14:16

Posted in Uncategorized

Praising the Good

I frequently gripe about how backward scientific software development is, so it’s only fair that I give praise where praise is due.  Steve Easterbrook pointed me at the UK Met Office’s Flexible Configuration Management system, which combines code management using Subversion and Trac with a GNU Make-based build and an extraction system that pulls data out of the repository and builds it for particular platforms.  This image shows how the three parts fit together; it ain’t rocket science, but it’s very professional, and a good model for others to follow.

Written by Greg Wilson

2007/06/11 at 08:51

Posted in Content