<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Make on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/make/</link>
    <description>Recent content in Make on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 23 Jul 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/make/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Can {drake} RAP?</title>
      <link>https://www.rostrum.blog/2019/07/23/can-drake-rap/</link>
      <pubDate>Tue, 23 Jul 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/07/23/can-drake-rap/</guid>
      <description>tl;dr The {drake} package records file interdependecies in your analysis. When files are changed, {drake} only re-runs the parts that need to be re-run. This saves time and reduces error.
This could be useful for Reproducible Analytical Pipelines (RAP), an automated approach to producing UK government statistics that minimises error and speeds production.
 Make it to make it Analysis projects can become complicated as multiple inputs, script files and outputs build up.</description>
    </item>
    
  </channel>
</rss>