Skip to content

Documentation

Scott Large edited this page Sep 25, 2019 · 1 revision

Overview

Documentation is important both for writing up the paper and for reviewers and also so that we are efficient and don't follow the same rabbit holes.

As an example (links are not meaningful):
The problem I was trying to solve was X

  1. I went through and universally raised all growth rates (see issue Y) and associated commit.
    • The outcome of this change was Z, see figure 1 and 2 from the .rmd from Sarah's evaluation script.