<?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 for Climate Code Foundation</title>
	<atom:link href="http://climatecode.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://climatecode.org</link>
	<description></description>
	<lastBuildDate>Thu, 10 Nov 2011 14:45:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Homogenization report by Peter Thorne</title>
		<link>http://climatecode.org/blog/2011/09/homogenization-report/#comment-2873</link>
		<dc:creator>Peter Thorne</dc:creator>
		<pubDate>Thu, 10 Nov 2011 14:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=583#comment-2873</guid>
		<description>&lt;a href=&quot;http://surfacetemperatures.blogspot.com/2011/11/ghcn-m-v310-showing-value-of-engaging.html&quot; rel=&quot;nofollow&quot;&gt;http://surfacetemperatures.blogspot.com/2011/11/ghcn-m-v310-showing-value-of-engaging.html&lt;/a&gt; provides some degree of update of demonstrable outcomes of this work for you.

Peter</description>
		<content:encoded><![CDATA[<p><a href="http://surfacetemperatures.blogspot.com/2011/11/ghcn-m-v310-showing-value-of-engaging.html" rel="nofollow">http://surfacetemperatures.blogspot.com/2011/11/ghcn-m-v310-showing-value-of-engaging.html</a> provides some degree of update of demonstrable outcomes of this work for you.</p>
<p>Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Science Code Manifesto by Alexander Atkins</title>
		<link>http://climatecode.org/blog/2011/10/science-code-manifesto/#comment-2755</link>
		<dc:creator>Alexander Atkins</dc:creator>
		<pubDate>Sun, 30 Oct 2011 13:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=595#comment-2755</guid>
		<description>Rhys, that section of the Discussion document is about citation. All open source licences require citation.</description>
		<content:encoded><![CDATA[<p>Rhys, that section of the Discussion document is about citation. All open source licences require citation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Science Code Manifesto by Larry</title>
		<link>http://climatecode.org/blog/2011/10/science-code-manifesto/#comment-2557</link>
		<dc:creator>Larry</dc:creator>
		<pubDate>Fri, 14 Oct 2011 20:56:34 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=595#comment-2557</guid>
		<description>I like this manifesto and I think it expresses a lot of my concerns with science and software.  I want to contemplate it a little more before I choose to endorse it.

One thing I would like to know from the foundation that created the manifesto is which articles of publication,  development or software have met the standards of the manifesto and which have not.  That could be a very telling list and set an interesting competition among publishers.</description>
		<content:encoded><![CDATA[<p>I like this manifesto and I think it expresses a lot of my concerns with science and software.  I want to contemplate it a little more before I choose to endorse it.</p>
<p>One thing I would like to know from the foundation that created the manifesto is which articles of publication,  development or software have met the standards of the manifesto and which have not.  That could be a very telling list and set an interesting competition among publishers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Science Code Manifesto by Rhys Ulerich</title>
		<link>http://climatecode.org/blog/2011/10/science-code-manifesto/#comment-2550</link>
		<dc:creator>Rhys Ulerich</dc:creator>
		<pubDate>Fri, 14 Oct 2011 14:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=595#comment-2550</guid>
		<description>In the Discussion page (http://sciencecodemanifesto.org/discussion) it states &quot;Adapting someone else’s code without permission and citation is plagiarism&quot; to which I&#039;d add that &quot;permission&quot; may inherently be granted by software licensing terms (e.g. FOSS or free-for-non-commercial situations).</description>
		<content:encoded><![CDATA[<p>In the Discussion page (<a href="http://sciencecodemanifesto.org/discussion" rel="nofollow">http://sciencecodemanifesto.org/discussion</a>) it states &#8220;Adapting someone else’s code without permission and citation is plagiarism&#8221; to which I&#8217;d add that &#8220;permission&#8221; may inherently be granted by software licensing terms (e.g. FOSS or free-for-non-commercial situations).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why publish code: a case study by Paul Coombes</title>
		<link>http://climatecode.org/blog/2011/03/why-publish-code-a-case-study/#comment-373</link>
		<dc:creator>Paul Coombes</dc:creator>
		<pubDate>Sat, 05 Mar 2011 09:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=295#comment-373</guid>
		<description>I write code for a living. Late last year I was talking to an engineering lecturer friend of mine and was horrified to learn that the Fortran programs he writes and uses are neither subject to testing or publication. I have never, in over twenty years in the software industry, encountered a program that doesn&#039;t have bugs. So, for me, you are pushing at an open door, I wish you the best in persuading people that code publication is important. You might also want to consider educating people in the benefits of code testing and, as you state above, configuration control. I do, however, feel that you are going to have a struggle as, in my experience, people become very proprietorial about their coding efforts.</description>
		<content:encoded><![CDATA[<p>I write code for a living. Late last year I was talking to an engineering lecturer friend of mine and was horrified to learn that the Fortran programs he writes and uses are neither subject to testing or publication. I have never, in over twenty years in the software industry, encountered a program that doesn&#8217;t have bugs. So, for me, you are pushing at an open door, I wish you the best in persuading people that code publication is important. You might also want to consider educating people in the benefits of code testing and, as you state above, configuration control. I do, however, feel that you are going to have a struggle as, in my experience, people become very proprietorial about their coding efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Summer of Code by Summer Program on Climate Software &#171; Azimuth</title>
		<link>http://climatecode.org/blog/2011/02/google-summer-of-code/#comment-363</link>
		<dc:creator>Summer Program on Climate Software &#171; Azimuth</dc:creator>
		<pubDate>Thu, 03 Mar 2011 12:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=288#comment-363</guid>
		<description>[...] &#8226; Climate Code Foundation, Google Summer of Code. [...]</description>
		<content:encoded><![CDATA[<p>[...] &bull; Climate Code Foundation, Google Summer of Code. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why publish code: a case study by Nic Lewis</title>
		<link>http://climatecode.org/blog/2011/03/why-publish-code-a-case-study/#comment-357</link>
		<dc:creator>Nic Lewis</dc:creator>
		<pubDate>Wed, 02 Mar 2011 15:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=295#comment-357</guid>
		<description>Congratulations and thanks to everyone involved in setting up and running the Climate Code Foundation.  I very much support your aims.  Best wishes for success.  

I have been myself pressing in a modest way for full code (and data) used in published climate science papers to be made freely available.  I have just made a submission to a UK Parliament science committee inquiry into peer review,  covering this issue in the context of the limits of peer review.  (See http://www.parliament.uk/business/committees/committees-a-z/commons-select/science-and-technology-committee/news/110127-new-inquiry---peer-review/ - you might want to make a submission on behalf of the CCF.

In case you are not already aware of a recently published climate science paper  that I co-authored and for which complete turnkey code was archived at the time of publication, may I draw your attention to it?  The paper concerned  is &quot;Improved methods for PCA-based reconstructions:  case study using the Steig et al. (2009) Antarctic temperature reconstruction&quot; by Ryan O’Donnell, Nicholas Lewis, Steve McIntyre and Jeff Condon, published by Journal of Climate in December 2010 (Early Online Release version).  The code (written by Ryan) is available at http://www.climateaudit.info/data/odonnell/ along with the required data.  As it happens, our paper criticised a paper published in Nature, in respect of which some but not all the code used was archived.

Although you are concentrating on code availability, please do not lose sight of the importance also of all data used being archived and made publicly available.  In many cases, climate science papers use data that is not publicly available (and/or only available if one knew exactly where to find it), making the studies impossible to replicate or to investigate sensitivities to particular elements of the data even where full code is provided.  And even where data is publicly available, it is often subsequently revised, again making replication impossible if the actual data used has not been publicly archived.</description>
		<content:encoded><![CDATA[<p>Congratulations and thanks to everyone involved in setting up and running the Climate Code Foundation.  I very much support your aims.  Best wishes for success.  </p>
<p>I have been myself pressing in a modest way for full code (and data) used in published climate science papers to be made freely available.  I have just made a submission to a UK Parliament science committee inquiry into peer review,  covering this issue in the context of the limits of peer review.  (See <a href="http://www.parliament.uk/business/committees/committees-a-z/commons-select/science-and-technology-committee/news/110127-new-inquiry---peer-review/" rel="nofollow">http://www.parliament.uk/business/committees/committees-a-z/commons-select/science-and-technology-committee/news/110127-new-inquiry&#8212;peer-review/</a> &#8211; you might want to make a submission on behalf of the CCF.</p>
<p>In case you are not already aware of a recently published climate science paper  that I co-authored and for which complete turnkey code was archived at the time of publication, may I draw your attention to it?  The paper concerned  is &#8220;Improved methods for PCA-based reconstructions:  case study using the Steig et al. (2009) Antarctic temperature reconstruction&#8221; by Ryan O’Donnell, Nicholas Lewis, Steve McIntyre and Jeff Condon, published by Journal of Climate in December 2010 (Early Online Release version).  The code (written by Ryan) is available at <a href="http://www.climateaudit.info/data/odonnell/" rel="nofollow">http://www.climateaudit.info/data/odonnell/</a> along with the required data.  As it happens, our paper criticised a paper published in Nature, in respect of which some but not all the code used was archived.</p>
<p>Although you are concentrating on code availability, please do not lose sight of the importance also of all data used being archived and made publicly available.  In many cases, climate science papers use data that is not publicly available (and/or only available if one knew exactly where to find it), making the studies impossible to replicate or to investigate sensitivities to particular elements of the data even where full code is provided.  And even where data is publicly available, it is often subsequently revised, again making replication impossible if the actual data used has not been publicly archived.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why publish code: a case study by Shub</title>
		<link>http://climatecode.org/blog/2011/03/why-publish-code-a-case-study/#comment-356</link>
		<dc:creator>Shub</dc:creator>
		<pubDate>Wed, 02 Mar 2011 14:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=295#comment-356</guid>
		<description>A related article here:

&lt;a href=&quot;http://nigguraths.wordpress.com/2011/02/27/nature-code-availability/&quot; rel=&quot;nofollow&quot;&gt;The code of Nature: Making authors part with their programs&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>A related article here:</p>
<p><a href="http://nigguraths.wordpress.com/2011/02/27/nature-code-availability/" rel="nofollow">The code of Nature: Making authors part with their programs</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why publish code: a case study by Mike Edwards</title>
		<link>http://climatecode.org/blog/2011/03/why-publish-code-a-case-study/#comment-355</link>
		<dc:creator>Mike Edwards</dc:creator>
		<pubDate>Wed, 02 Mar 2011 13:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=295#comment-355</guid>
		<description>In my opinion, any science research that is funded by public funds should be &lt;i&gt;required&lt;/i&gt; to release all of the computer software written during the project as Open Source code using a suitable open source repository.

This has a number of positive effects, including visibility of the code for validation and debugging purposes, availability of the code for use by others and/or for extension and expansion by others.  If it also embarrasses the writers of the code into making the code cleaner and better tested, so much the better.</description>
		<content:encoded><![CDATA[<p>In my opinion, any science research that is funded by public funds should be <i>required</i> to release all of the computer software written during the project as Open Source code using a suitable open source repository.</p>
<p>This has a number of positive effects, including visibility of the code for validation and debugging purposes, availability of the code for use by others and/or for extension and expansion by others.  If it also embarrasses the writers of the code into making the code cleaner and better tested, so much the better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why publish code: a case study by tolkein</title>
		<link>http://climatecode.org/blog/2011/03/why-publish-code-a-case-study/#comment-352</link>
		<dc:creator>tolkein</dc:creator>
		<pubDate>Wed, 02 Mar 2011 12:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://climatecode.org/?p=295#comment-352</guid>
		<description>Excellent!

Many problems would have been avoided if publication of code in climate science was mandatory. We could then focus on the implications of the research rather than arguing about whether the analysis in the research was or was not worthless.</description>
		<content:encoded><![CDATA[<p>Excellent!</p>
<p>Many problems would have been avoided if publication of code in climate science was mandatory. We could then focus on the implications of the research rather than arguing about whether the analysis in the research was or was not worthless.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

