You have a finite amount of keystrokes in your life. Automating repetitive steps is one of the great benefits of knowing a bit about coding, even if the code is just a simple shell script. That’s why I set up an example project on Github using a Makefile and sample article (inspired by Rob Hyndman). This post explains the structure of that project and explains how to modify it for your own purposes.
Running the Makefile with the example article in an otherwise-empty project directory will create:
- a setup.R file for clearing the workspace, setting paths, and loading libraries
- a data directory for storing files (csv, rda, etc)
- a drafts directory for LaTeX, including a generic starter article
- a graphics library for storing plots and figures to include in your article
- an rcode directory for your R scripts
It also supplies some starter code for the setup.R file in the main directory and a start.R file in the rcode directory. This takes the current user and sets relative paths to the project directories with simple variable references in R. For example, after running setup.R in your analysis file you can switch to the data directory with
setwd(pathData), then create a plot and save it after running
setwd(pathGraphics). Because of the way the setup.R file works, you could have multiple users working on the same project and not need to change any of the other scripts.
If you want to change this structure, there are two main ways to do it. You can add more (or fewer) directories by modifying the
mkdir lines in the Makefile. You can add (or remove) text in the R files by changing the
If you decide to make major customizations to this file or already have your own structure for projects like this, leave a link in the comments for other readers.
H/T to Josh Cutler for encouraging me to write a post about my project structure and automation efforts. As a final note, this is the second New Year’s Eve in a row that I have posted a tech tip. Maybe it will become a YSPR tradition!