<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Orderly on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/orderly/</link>
    <description>Recent content in Orderly on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 31 Jan 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/orderly/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>{orderly} and {drake} at Bioinformatics London</title>
      <link>https://www.rostrum.blog/2020/01/31/reprobioinformatics/</link>
      <pubDate>Fri, 31 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/01/31/reprobioinformatics/</guid>
      <description>REPRODUCIBILITY 4 LYFE (via Bioinformatics London’s Meetup page)  tl;dr I spoke at the latest Bioinformatics London Meetup (event link, Twitter) about workflow reproducibility tools in R. I explained the benefits of Will Landau’s {drake} package for doing this.
 Order, order Rich FitzJohn opened proceedings with an excellent introduction to his {orderly} package (source) that is intended for ‘lightweight reproducible reporting’.
In short, the user declares inputs (anything, including things like SQL queries and CSV files) and artefacts (results) of their analysis.</description>
    </item>
    
  </channel>
</rss>