Closed sjspielman closed 2 years ago
So, there's a lot of merges in my history here which I don't think is a problem, but there was mysteriously a draft file I made in 2019 that made it onto this branch which I just created today. I purged it, but it's in the history.
Can purge this whole history and do new PR without that weird file if preferred!
Purpose/implementation Section
What was your approach?
Include an Rmarkdown
param
, with default ofrelease-v21-20210820
, to ensure flexibility of this notebook moving forward.What GitHub issue does your pull request address?
1218
Directions for reviewers. Tell potential reviewers what kind of feedback you are soliciting.
Which areas should receive a particularly close look?
release-v21-20210820
orv21-20210820
with "release-" string added in?!
to a.
, but enthusiasm is maintained.Is there anything that you want to discuss further?
Nope
Is the analysis in a mature enough form that the resulting figure(s) and/or table(s) are ready for review?
Yes
Results
N/A
Reproducibility Checklist
Documentation Checklist
README
and it is up to date.analyses/README.md
and the entry is up to date.