r4ds/rmarkdown-workflow.Rmd

63 lines
3.7 KiB
Plaintext
Raw Normal View History

2016-08-23 05:08:16 +08:00
# R Markdown workflow
2016-08-22 22:31:17 +08:00
Earlier, we discussed a basic workflow for capturing your R code where you work interactively in the _console_, then capture what works in the _script editor_. R Markdown effectively puts the console and the script editor in same place, blurring the lines between interactive exploration and long-term code capture. You can rapidly iterate within a chunk, editing and re-executing with Cmd/Ctrl + Shift + Enter. When you're happy, you move on and start a new chunk.
2016-08-24 05:40:35 +08:00
R Markdown is also important because it so tightly integrates prose and code. This makes it a great __analysis notebook__ because it lets you develop code and record your thoughts. An analysis notebook shares many of the same goals as a classic lab notebook in the physical sciences:
2016-08-24 05:40:35 +08:00
* Record what you did and why you did it. Regardless of how great your
memory is, if you don't record what you do, there will come a time when
2016-08-24 05:40:35 +08:00
you have forgotten important details. Write them down so you don't forget!
* To support rigorous thinking. You are more likely to come up with a strong
analysis if you record your thoughts as you go, and continue to reflect
on them. This also saves you time when you eventually write up your
2016-08-24 05:40:35 +08:00
analysis to share with others.
* To help others understand your work. It is rare to do data analysis by
yourself, and you'll often be working as part of a team. A lab notebook
helps you share not only what you've done, but why you did it with your
colleagues or lab mates.
2016-08-24 05:40:35 +08:00
Much of the good advice about using lab notebooks effectively can also be translated to analysis notebooks. I've drawn on my own experiences and Colin Purrington's advice on lab notebooks <http://colinpurrington.com/tips/lab-notebooks> to come up with the following list of tips:
2016-08-24 05:40:35 +08:00
* Ensure each notebook has a descriptive title, an evocative filename, and a
2016-08-24 05:40:35 +08:00
first paragraph that briefly describes the aims of the analysis.
* Use the YAML header date field to record the date you started working on the
2016-08-24 05:40:35 +08:00
notebook:
2016-08-24 05:40:35 +08:00
```yaml
date: 2016-08-23
```
Use ISO8601 YYYY-MM-DD format so that's there no ambiguity. Use it
even if you don't normally write dates that way!
* If you spend a lot of time on an analysis idea and it turns out to be a
dead end, don't delete it! Write up a brief note about why it failed and
leave it in the notebook. That will help you avoid going down the same
dead end when you come back to the analysis in the future.
2016-08-24 05:40:35 +08:00
* Generally, you're better off doing data entry outside of R. If you need
a small snippet of data, clearly lay it out using `tibble::tribble()`.
* If you discover an error in a data file, never modify it directly, but
2016-08-24 05:40:35 +08:00
instead write code to correct the value. Explain why you made the fix.
* Before you finish for the day, make sure you can compile the notebook
using knitr (aftering clearing caches if you're using them). That will
let you fix any problems while the code is still fresh in your mind.
* If you want your code to be reproducible in the long-run (i.e. so you can
come back to run it next month or next year), you'll need to track the
versions of the packages that your code uses. A rigorous approach is to use
2016-08-24 05:40:35 +08:00
__packrat__, <http://rstudio.github.io/packrat/>, which stores packages in
2016-08-25 21:20:35 +08:00
your project directory. A quick and dirty hack is to include a chunk that
2016-08-24 05:40:35 +08:00
runs `sessionInfo()` --- that won't let easily recreate your packages as
they are today, but at least you know what they were.
* You are going to create many, many, many analysis notebooks over the course
2016-08-24 05:40:35 +08:00
of your career. How are you going to organise them so you can find them
again in the future? I recommend storing them in individual projects,
and coming up with a good naming scheme.