-
Notifications
You must be signed in to change notification settings - Fork 0
Writing the Manuscript
Robbie Richards edited this page Jan 11, 2018
·
21 revisions
In an effort to make all of the research process as transparent and reproducible as possible, we try to integrate our code and results into our manuscript writing in an automated process.
R Markdown allows you both to save and execute code and to generate reports and manuscripts with embedded code and figures in a single document. These .Rmd files are the most common way that we practice reproducibility here in the Drake Lab.
Check out this helpful manual for more information. What resource do we want to link?
Here's a good cheat sheet as well.
Because research is collaborative now, it is best to use a text editing software that allows you collaborate with others, incorporate edits, and track changes.
Pros | Cons | |
---|---|---|
Google docs | version control, easy editing, accessible anywhere, not OS specific | cannot insert citations, must convert to other format(.doc, .tex) for journal submission |
LateX/Overleaf | easy citation formatting and control, precise formatting, Overleaf allows online collaboration | not everyone knows LaTex, steep learning curve |
Word (and other word processors) | WYSIWYG, more widely used, allows edits via track changes | doesn't work across OS, formatting can be a pain |
- John's Fifteen Steps to writing a manuscript
- LaTeX cover letter template
- CARS method of introductions
- journal-club doc
- google-sites lab manual
- index of all Drake-lab google sites
- lab-meeting--minutes doc Contact John if you are having trouble accessing google docs or websites.
- repository of public domain images