<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Code</title>
	<atom:link href="http://clearclimatecode.org/code/feed/" rel="self" type="application/rss+xml" />
	<link>http://clearclimatecode.org</link>
	<description></description>
	<lastBuildDate>Mon, 19 Jul 2010 18:01:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jorge Kampmann</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-2825</link>
		<dc:creator>Jorge Kampmann</dc:creator>
		<pubDate>Mon, 19 Jul 2010 18:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-2825</guid>
		<description>gistemp 0.5.0 still has this strange behaviour ...:
kampmann@ibk-node14:~/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0&gt; python tool/run.py
MISSING: input/antarc1.list
MISSING: input/antarc1.txt
MISSING: input/antarc2.list
MISSING: input/antarc2.txt
MISSING: input/antarc3.list
MISSING: input/antarc3.txt
MISSING: input/t_hohenpeissenberg_200306.txt_as_received_July17_2003
MISSING: input/ushcn2.tbl
MISSING: input/ushcnV2_cmb.tbl
MISSING: input/mcdw.tbl
MISSING: input/ushcn2.tbl
MISSING: input/sumofday.tbl
MISSING: input/v2.inv
MISSING: input/oisstv2_mod4.clim.gz
MISSING: input/v2.mean
MISSING: input/ushcnv2
MISSING: input/SBBX.HadR2
Attempting to fetch missing files: antarc1.list antarc1.txt antarc2.list antarc2.txt antarc3.list antarc3.txt t_hohenpeissenberg_200306.txt_as_received_July17_2003 ushcn2.tbl ushcnV2_cmb.tbl mcdw.tbl ushcn2.tbl sumofday.tbl v2.inv oisstv2_mod4.clim.gz v2.mean ushcnv2 SBBX.HadR2
Extracting members from http://data.giss.nasa.gov/gistemp/sources/GISTEMP_sources.tar.gz ...
Traceback (most recent call last):
  File &quot;tool/run.py&quot;, line 225, in 
    sys.exit(main())
  File &quot;tool/run.py&quot;, line 172, in main
    preflight.checkit(sys.stderr)
  File &quot;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/preflight.py&quot;, line 103, in checkit
    fetch.main(argv=[&#039;fetch&#039;] + missing)
  File &quot;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&quot;, line 405, in main
    fetch(args)
  File &quot;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&quot;, line 219, in fetch
    handler[hname](group, prefix, output)
  File &quot;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&quot;, line 262, in fetch_tar
    compression_type=tar_compression_type)
  File &quot;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&quot;, line 348, in fetch_from_tar
    tar = tarfile.open(&#039;&#039;, mode=&#039;r&#124;%s&#039; % compression_type, fileobj=inp)
  File &quot;/usr/lib/python2.5/tarfile.py&quot;, line 1046, in open
    _Stream(name, filemode, comptype, fileobj, bufsize))
  File &quot;/usr/lib/python2.5/tarfile.py&quot;, line 352, in __init__
    self._init_read_gz()
  File &quot;/usr/lib/python2.5/tarfile.py&quot;, line 439, in _init_read_gz
    raise ReadError(&quot;not a gzip file&quot;)
tarfile.ReadError: not a gzip file
kampmann@ibk-node14:~/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0&gt;         

could you explain or help?
Thanks
Jörg</description>
		<content:encoded><![CDATA[<p>gistemp 0.5.0 still has this strange behaviour &#8230;:<br />
kampmann@ibk-node14:~/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0&gt; python tool/run.py<br />
MISSING: input/antarc1.list<br />
MISSING: input/antarc1.txt<br />
MISSING: input/antarc2.list<br />
MISSING: input/antarc2.txt<br />
MISSING: input/antarc3.list<br />
MISSING: input/antarc3.txt<br />
MISSING: input/t_hohenpeissenberg_200306.txt_as_received_July17_2003<br />
MISSING: input/ushcn2.tbl<br />
MISSING: input/ushcnV2_cmb.tbl<br />
MISSING: input/mcdw.tbl<br />
MISSING: input/ushcn2.tbl<br />
MISSING: input/sumofday.tbl<br />
MISSING: input/v2.inv<br />
MISSING: input/oisstv2_mod4.clim.gz<br />
MISSING: input/v2.mean<br />
MISSING: input/ushcnv2<br />
MISSING: input/SBBX.HadR2<br />
Attempting to fetch missing files: antarc1.list antarc1.txt antarc2.list antarc2.txt antarc3.list antarc3.txt t_hohenpeissenberg_200306.txt_as_received_July17_2003 ushcn2.tbl ushcnV2_cmb.tbl mcdw.tbl ushcn2.tbl sumofday.tbl v2.inv oisstv2_mod4.clim.gz v2.mean ushcnv2 SBBX.HadR2<br />
Extracting members from <a href="http://data.giss.nasa.gov/gistemp/sources/GISTEMP_sources.tar.gz" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/GISTEMP_sources.tar.gz</a> &#8230;<br />
Traceback (most recent call last):<br />
  File &#8220;tool/run.py&#8221;, line 225, in<br />
    sys.exit(main())<br />
  File &#8220;tool/run.py&#8221;, line 172, in main<br />
    preflight.checkit(sys.stderr)<br />
  File &#8220;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/preflight.py&#8221;, line 103, in checkit<br />
    fetch.main(argv=['fetch'] + missing)<br />
  File &#8220;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&#8221;, line 405, in main<br />
    fetch(args)<br />
  File &#8220;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&#8221;, line 219, in fetch<br />
    handler[hname](group, prefix, output)<br />
  File &#8220;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&#8221;, line 262, in fetch_tar<br />
    compression_type=tar_compression_type)<br />
  File &#8220;/home/kampmann/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0/tool/fetch.py&#8221;, line 348, in fetch_from_tar<br />
    tar = tarfile.open(&#8221;, mode=&#8217;r|%s&#8217; % compression_type, fileobj=inp)<br />
  File &#8220;/usr/lib/python2.5/tarfile.py&#8221;, line 1046, in open<br />
    _Stream(name, filemode, comptype, fileobj, bufsize))<br />
  File &#8220;/usr/lib/python2.5/tarfile.py&#8221;, line 352, in __init__<br />
    self._init_read_gz()<br />
  File &#8220;/usr/lib/python2.5/tarfile.py&#8221;, line 439, in _init_read_gz<br />
    raise ReadError(&#8220;not a gzip file&#8221;)<br />
tarfile.ReadError: not a gzip file<br />
kampmann@ibk-node14:~/Projekte/GlobalWarming/ccc-giss 0.5.0/ccc-gistemp-0.5.0&gt;         </p>
<p>could you explain or help?<br />
Thanks<br />
Jörg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick.Barnes</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-2233</link>
		<dc:creator>Nick.Barnes</dc:creator>
		<pubDate>Sat, 01 May 2010 11:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-2233</guid>
		<description>@Steven: We fetch the GISTEMP sources from 

http://data.giss.nasa.gov/gistemp/sources/GISTEMP_sources.tar.gz

Because that is the link given on the relevant web page:

http://data.giss.nasa.gov/gistemp/sources/

When we unpack this tarball, it used to make a directory called GISTEMP_sources.  Now it makes a directory called GISTEMP_sources_open.  Our preflight.py/fetch.py code is now independent of the name of this directory.

We&#039;ve never used the GISS_Obs_analysis link.</description>
		<content:encoded><![CDATA[<p>@Steven: We fetch the GISTEMP sources from </p>
<p><a href="http://data.giss.nasa.gov/gistemp/sources/GISTEMP_sources.tar.gz" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/GISTEMP_sources.tar.gz</a></p>
<p>Because that is the link given on the relevant web page:</p>
<p><a href="http://data.giss.nasa.gov/gistemp/sources/" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/</a></p>
<p>When we unpack this tarball, it used to make a directory called GISTEMP_sources.  Now it makes a directory called GISTEMP_sources_open.  Our preflight.py/fetch.py code is now independent of the name of this directory.</p>
<p>We&#8217;ve never used the GISS_Obs_analysis link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven mosher</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-2232</link>
		<dc:creator>Steven mosher</dc:creator>
		<pubDate>Fri, 30 Apr 2010 22:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-2232</guid>
		<description>hmm.

We fetch various files such as station metadata from the GISTEMP source
archive.  The top-level directory in this archive has changed name from
GISTEMP_sources to GISTEMP_sources_open.  Our preflight code fails as a
result.  We should be flexible about this: for instance, by using a regular
expression to match either old or new directory names.

Is that URL correct?

ftp://data.giss.nasa.gov/pub/gistemp/GISS_Obs_analysis/

Exists.

ftp://data.giss.nasa.gov/pub/gistemp/GISS_Obs_analysis/GISTEMP_sources/

Exists.

GISTEMP_sources_open    doesnt exist</description>
		<content:encoded><![CDATA[<p>hmm.</p>
<p>We fetch various files such as station metadata from the GISTEMP source<br />
archive.  The top-level directory in this archive has changed name from<br />
GISTEMP_sources to GISTEMP_sources_open.  Our preflight code fails as a<br />
result.  We should be flexible about this: for instance, by using a regular<br />
expression to match either old or new directory names.</p>
<p>Is that URL correct?</p>
<p><a href="ftp://data.giss.nasa.gov/pub/gistemp/GISS_Obs_analysis/" rel="nofollow">ftp://data.giss.nasa.gov/pub/gistemp/GISS_Obs_analysis/</a></p>
<p>Exists.</p>
<p><a href="ftp://data.giss.nasa.gov/pub/gistemp/GISS_Obs_analysis/GISTEMP_sources/" rel="nofollow">ftp://data.giss.nasa.gov/pub/gistemp/GISS_Obs_analysis/GISTEMP_sources/</a></p>
<p>Exists.</p>
<p>GISTEMP_sources_open    doesnt exist</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven mosher</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-2216</link>
		<dc:creator>steven mosher</dc:creator>
		<pubDate>Sun, 25 Apr 2010 15:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-2216</guid>
		<description>Cool, l have the 0.4.1. so I just got the files from one of the tar on your dowloands ( gisstemp test ) hit enter. went to bed and woke up to a successful run. about 2100 seconds on a MAC lap top. All the work files look to be in order. nice work. I&#039;ll check out your comment above.</description>
		<content:encoded><![CDATA[<p>Cool, l have the 0.4.1. so I just got the files from one of the tar on your dowloands ( gisstemp test ) hit enter. went to bed and woke up to a successful run. about 2100 seconds on a MAC lap top. All the work files look to be in order. nice work. I&#8217;ll check out your comment above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick.Barnes</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-2215</link>
		<dc:creator>Nick.Barnes</dc:creator>
		<pubDate>Sun, 25 Apr 2010 11:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-2215</guid>
		<description>@Steven: Yes, it changed a couple of weeks ago; I fixed our trunk sources to work either way.  See &lt;a href=&quot;http://code.google.com/p/ccc-gistemp/issues/detail?id=65&quot; rel=&quot;nofollow&quot;&gt;issue 65&lt;/a&gt; and &lt;a href=&quot;http://code.google.com/p/ccc-gistemp/source/detail?r=436&quot; rel=&quot;nofollow&quot;&gt;r436&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>@Steven: Yes, it changed a couple of weeks ago; I fixed our trunk sources to work either way.  See <a href="http://code.google.com/p/ccc-gistemp/issues/detail?id=65" rel="nofollow">issue 65</a> and <a href="http://code.google.com/p/ccc-gistemp/source/detail?r=436" rel="nofollow">r436</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven mosher</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-2214</link>
		<dc:creator>steven mosher</dc:creator>
		<pubDate>Sun, 25 Apr 2010 07:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-2214</guid>
		<description>hmm. did giss change names?

MISSING: input/ushcnV2_cmb.tbl
MISSING: input/mcdw.tbl
MISSING: input/ushcn2.tbl
MISSING: input/sumofday.tbl
MISSING: input/v2.inv
MISSING: input/oisstv2_mod4.clim.gz
PROBLEM: Tried fetching missing files but it didn&#039;t work.
====&gt; STEPS 0 to 5  ====
Traceback (most recent call last):
  File &quot;tool/run.py&quot;, line 225, in 
    sys.exit(main())
  File &quot;tool/run.py&quot;, line 206, in main
    data = step_fn[step](data)
  File &quot;tool/run.py&quot;, line 56, in run_step0
    data = giss_io.step0_input()
  File &quot;/Users/mosher/Downloads/ccc-gistemp-0.4.1/tool/giss_io.py&quot;, line 674, in step0_input
    input.ushcn_stations = read_USHCN_stations(&#039;input/ushcn2.tbl&#039;, &#039;input/ushcnV2_cmb.tbl&#039;)
  File &quot;/Users/mosher/Downloads/ccc-gistemp-0.4.1/tool/giss_io.py&quot;, line 609, in read_USHCN_stations
    for line in open(ushcn_v1_station_path):
IOError: [Errno 2] No such file or directory: &#039;input/ushcn2.tbl&#039;</description>
		<content:encoded><![CDATA[<p>hmm. did giss change names?</p>
<p>MISSING: input/ushcnV2_cmb.tbl<br />
MISSING: input/mcdw.tbl<br />
MISSING: input/ushcn2.tbl<br />
MISSING: input/sumofday.tbl<br />
MISSING: input/v2.inv<br />
MISSING: input/oisstv2_mod4.clim.gz<br />
PROBLEM: Tried fetching missing files but it didn&#8217;t work.<br />
====&gt; STEPS 0 to 5  ====<br />
Traceback (most recent call last):<br />
  File &#8220;tool/run.py&#8221;, line 225, in<br />
    sys.exit(main())<br />
  File &#8220;tool/run.py&#8221;, line 206, in main<br />
    data = step_fn[step](data)<br />
  File &#8220;tool/run.py&#8221;, line 56, in run_step0<br />
    data = giss_io.step0_input()<br />
  File &#8220;/Users/mosher/Downloads/ccc-gistemp-0.4.1/tool/giss_io.py&#8221;, line 674, in step0_input<br />
    input.ushcn_stations = read_USHCN_stations(&#8216;input/ushcn2.tbl&#8217;, &#8216;input/ushcnV2_cmb.tbl&#8217;)<br />
  File &#8220;/Users/mosher/Downloads/ccc-gistemp-0.4.1/tool/giss_io.py&#8221;, line 609, in read_USHCN_stations<br />
    for line in open(ushcn_v1_station_path):<br />
IOError: [Errno 2] No such file or directory: &#8216;input/ushcn2.tbl&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven mosher</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-974</link>
		<dc:creator>steven mosher</dc:creator>
		<pubDate>Fri, 02 Apr 2010 17:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-974</guid>
		<description>Understood nick,

 It struck me as notes one would write to oneself when deep into coding where you live and breath the code like it was your native tongue. But it was helpful to me to just get my feet back under me WRT gisstemp code. 

Part of this is I&#039;m putting together a bunch of metadata for any one to use, so I&#039;m painfully aware that I better get all the ids correct etc
so some of the id correction stuff was important, also learning R and trying to get the other data ( antartica ) into a GHCN format just as a R learning tool.</description>
		<content:encoded><![CDATA[<p>Understood nick,</p>
<p> It struck me as notes one would write to oneself when deep into coding where you live and breath the code like it was your native tongue. But it was helpful to me to just get my feet back under me WRT gisstemp code. </p>
<p>Part of this is I&#8217;m putting together a bunch of metadata for any one to use, so I&#8217;m painfully aware that I better get all the ids correct etc<br />
so some of the id correction stuff was important, also learning R and trying to get the other data ( antartica ) into a GHCN format just as a R learning tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick.Barnes</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-964</link>
		<dc:creator>Nick.Barnes</dc:creator>
		<pubDate>Fri, 02 Apr 2010 10:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-964</guid>
		<description>Oh, OK.  Yes, this should be documented better.  Release 0.5.0 will do much better at documentation in general.  But those -update-notes documents aren&#039;t gonig to be very helpful to anyone except an archaeologist.</description>
		<content:encoded><![CDATA[<p>Oh, OK.  Yes, this should be documented better.  Release 0.5.0 will do much better at documentation in general.  But those -update-notes documents aren&#8217;t gonig to be very helpful to anyone except an archaeologist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven mosher</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-955</link>
		<dc:creator>steven mosher</dc:creator>
		<pubDate>Fri, 02 Apr 2010 07:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-955</guid>
		<description>Shucks,

I was hoping for some clarification as Im trying to understand exactly what files gisstemp uses, what get added, what gets modified, what gets, disgarded, the various errors in station ids.

Let&#039;s say with Zeke&#039;s program its easy to understand. He uses GHCN. v2mean. 

Anyways, I&#039;m not being critical of the file or the operation I&#039;m just trying to understand it.

When I get some time, I&#039;ll try to come up with clearer questions.</description>
		<content:encoded><![CDATA[<p>Shucks,</p>
<p>I was hoping for some clarification as Im trying to understand exactly what files gisstemp uses, what get added, what gets modified, what gets, disgarded, the various errors in station ids.</p>
<p>Let&#8217;s say with Zeke&#8217;s program its easy to understand. He uses GHCN. v2mean. </p>
<p>Anyways, I&#8217;m not being critical of the file or the operation I&#8217;m just trying to understand it.</p>
<p>When I get some time, I&#8217;ll try to come up with clearer questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick.Barnes</title>
		<link>http://clearclimatecode.org/code/comment-page-1/#comment-907</link>
		<dc:creator>Nick.Barnes</dc:creator>
		<pubDate>Wed, 31 Mar 2010 20:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://clearclimatecode.org/?page_id=99#comment-907</guid>
		<description>Hi Steven.

That looks like a copy of most of the file doc/step0-update-notes, which I wrote in early 2009-12, as we were working towards ccc-gistemp release 0.2.0 - our first all-Python release, which we made on 2010-01-11.  There is a corresponding file doc/steps1-5-update-notes, which I wrote at the same time.  These files can be fetched with SVN or browsed, with revision history, &lt;a href=&quot;http://code.google.com/p/ccc-gistemp/source/browse/trunk/doc/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.

I wrote these documents to help myself to understand, and to communicate to ccc-gistemp people (mainly David Jones at the time), changes that GISS had made to GISTEMP over the preceding year or so.  I discarded these notes shortly after they were written, and haven&#039;t revisited them since.  So some of them may be terse, opaque, ambiguous, or downright wrong.  But the summary at the top of the file, which I will have written last, is probably both accurate and sufficient.

At the time, in 2009-12, we were working towards our first all-Python version of ccc-gistemp, release 0.2.0 which was actually released on 2010-01-11.  When we started ccc-gistemp, back in 2008, ccc-gistemp 0.1.0 was equivalent to GISTEMP in 2008-09 (the document says 2008-09-11, although I think the actual GISTEMP release may have been on 2008-09-10).  We wanted ccc-gistemp 0.2.0 to match current GISTEMP sources.  So I downloaded the GISTEMP sources released on 2009-12-03, ran diff over the two GISTEMP source trees, and spent a while pondering the results and writing these two documents (step0-update-notes and steps1-5-update-notes).

I emailed Reto Ruedy at GISS on 2009-12-17 to ask about the first version of these documents (I sent him a link to the SVN browser); his reply informed my next update (&lt;a href=&quot;http://code.google.com/p/ccc-gistemp/source/detail?r=102&quot; rel=&quot;nofollow&quot;&gt;r102&lt;/a&gt;).

So this document isn&#039;t really about versions of data (except inasmuch as the GISTEMP changes included a switch from USHCNv1 to USHCNv2, and some updates to SCAR data and metadata); it&#039;s about versions of code.</description>
		<content:encoded><![CDATA[<p>Hi Steven.</p>
<p>That looks like a copy of most of the file doc/step0-update-notes, which I wrote in early 2009-12, as we were working towards ccc-gistemp release 0.2.0 &#8211; our first all-Python release, which we made on 2010-01-11.  There is a corresponding file doc/steps1-5-update-notes, which I wrote at the same time.  These files can be fetched with SVN or browsed, with revision history, <a href="http://code.google.com/p/ccc-gistemp/source/browse/trunk/doc/" rel="nofollow">here</a>.</p>
<p>I wrote these documents to help myself to understand, and to communicate to ccc-gistemp people (mainly David Jones at the time), changes that GISS had made to GISTEMP over the preceding year or so.  I discarded these notes shortly after they were written, and haven&#8217;t revisited them since.  So some of them may be terse, opaque, ambiguous, or downright wrong.  But the summary at the top of the file, which I will have written last, is probably both accurate and sufficient.</p>
<p>At the time, in 2009-12, we were working towards our first all-Python version of ccc-gistemp, release 0.2.0 which was actually released on 2010-01-11.  When we started ccc-gistemp, back in 2008, ccc-gistemp 0.1.0 was equivalent to GISTEMP in 2008-09 (the document says 2008-09-11, although I think the actual GISTEMP release may have been on 2008-09-10).  We wanted ccc-gistemp 0.2.0 to match current GISTEMP sources.  So I downloaded the GISTEMP sources released on 2009-12-03, ran diff over the two GISTEMP source trees, and spent a while pondering the results and writing these two documents (step0-update-notes and steps1-5-update-notes).</p>
<p>I emailed Reto Ruedy at GISS on 2009-12-17 to ask about the first version of these documents (I sent him a link to the SVN browser); his reply informed my next update (<a href="http://code.google.com/p/ccc-gistemp/source/detail?r=102" rel="nofollow">r102</a>).</p>
<p>So this document isn&#8217;t really about versions of data (except inasmuch as the GISTEMP changes included a switch from USHCNv1 to USHCNv2, and some updates to SCAR data and metadata); it&#8217;s about versions of code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
