<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reproducibility on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/tag/reproducibility/</link><description>Recent content in Reproducibility on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/tag/reproducibility/index.xml" rel="self" type="application/rss+xml"/><item><title>Cookie Cutter</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/02/cookie-cutter/</link><pubDate>Tue, 10 Feb 2015 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/02/cookie-cutter/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 I was first introduced to William Stafford Noble's paper
 "&lt;a href="http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424">A Quick Guide to Organizing Computational Biology Projects&lt;/a>"
 when Ivan Gonzalez and I taught Harvard last November. Noble describes
 how scientists in Computational Biology should set up their
 project folders so code, results, outputs, figures, and papers are
 all in easily understandable locations. He also writes about how
 one should run experiments (using driver scripts) to make workflows
 reproducible, readable, and understandable to others (and your
 future self).
&lt;/p></description></item></channel></rss>