Running (limping?)

[Nick Barnes]

I've got ccc-gistemp running again, matching the current GISTEMP semantics.  This includes using GHCN-M 3.1.0, and generating reports for the mid-latitude zones.  There is some cleaning-up to do, but this should allow us to produce whatever intermediate results Jeremy can use for his visualisation tool.

The next thing I'm intending to do is to split the parameters.py file, which has become somewhat laden down with experimental bits and pieces, and retains stuff which is irrelevant to the newer GISTEMP semantics.  I'm planning to make a parameters/ directory, containing:

  standard.py : parameters currently used in GISTEMP;
  obsolete.py : parameters which were once used in GISTEMP, and which we still support, or which allow us to turn on obsolete features (e.g. USHCN munging);
  extension.py: parameters controlling useful features which we have added, beyond the GISTEMP functionality.

Comments?

I'm also mulling over the possibility of moving code which is 'obsolete' - which performs functions no longer in GISTEMP - out to a separate directory, and doing something magic in tool/run.py, controlled by something in parameters/obsolete.py, to turn it on.  This would include a lot of steps 0 and 1.
--
Nick Barnes, Climate Code Foundation, http://climatecode.org/

[Nick Barnes]

On Sat, May 26, 2012 at 6:38 PM, Nick Barnes <n...@climatecode.org> wrote:

The next thing I'm intending to do is to split the parameters.py file, which has become somewhat laden down with experimental bits and pieces, and retains stuff which is irrelevant to the newer GISTEMP semantics.  I'm planning to make a parameters/ directory, containing:

  standard.py : parameters currently used in GISTEMP;
  obsolete.py : parameters which were once used in GISTEMP, and which we still support, or which allow us to turn on obsolete features (e.g. USHCN munging);
  extension.py: parameters controlling useful features which we have added, beyond the GISTEMP functionality.

Done.

I'm also mulling over the possibility of moving code which is 'obsolete' - which performs functions no longer in GISTEMP - out to a separate directory, and doing something magic in tool/run.py, controlled by something in parameters/obsolete.py, to turn it on.  This would include a lot of steps 0 and 1.

Done, for step 0 and step 1.  See extension/step0.py and extension/step1.py.

This means that code/step0.py and code/step1.py are now both really short.

I was in two minds about where to put this, since it's not new functionality, so maybe I ought to follow the same pattern as parameters/ and have a directory called obsolete/ or similar.  Comments would be very welcome.