• You have to understand what you have done
• Others should be able to reproduce what you have done

• Put in results directory
• Entries dated
• Entries relatively verbose
• Link to data and code (including versions)
• Embedded images or tables showing results of analysis done
• Observations, Conclusions, and ideas for future work
• Also document analysis that doesn't work, so that it can be understood why you choose a particular way of doing the analysis in the end

• Paper Notebook
• Word processor program / Text files
• Electronic Lab Notebooks
• 'Interactive' Electronic Notebooks
  • e.g. jupyther, R Notebooks in RStudio
  • Plain text - work well with version control

• RStudio (New File… -> R Notebook)
• Documentation: http://rmarkdown.rstudio.com/r_notebooks.html
• Write in R Markdown
  • Documentation: http://rmarkdown.rstudio.com/lesson-1.html
  • Cheatsheet: https://www.rstudio.com/wp-content/uploads/2016/03/rmarkdown-cheatsheet-2.0.pdf
  • also Help->Cheatsheets->R Markdown Cheat Sheet in RStudio)
• Embed R and execute code (or bash, Python, SQL, etc)

• YAML Header

---
title: "R Notebook"
output: html_notebook
---

• Text content
  • Markdown

• Inline code

• 'Knit' to different output formats
  • html, pdf, word