layout: post title: “On blog tone” toc: true image: https://source.unsplash.com/OfMq2hIbWMQ tags: - carnivalesque
The main problem with the approach I outlined was how to get those nicely updated paragraphs into the document you are sharing with colleagues.
Medicine, in particular, seems wed to Microsoft Word documents for manuscripts. Word does not have a great way to include text from arbitrary files, forcing the physician-scientist to manually copy and paste those beautifully automated paragraphs. As I struggled with this, I thought (here cue Raymond Hettinger), “There must be a better way.“
Turns out that better way exists, and it is R Markdown.
Though I was at first resistant to learning about R Markdown, mostly because I am proficient in Python and thought the opportunity cost for learning R at this point would be too high, as soon as I saw it demoed I changed my tune. Here's why.
#just specifies a header - you can decide how you want the headers to look later, and that styling will automatically be applied).
R Markdown, as the name implies, can also run R code. Any analysis you can dream of in R can be included in your document, and you can choose whether you want to show the code and its output, the output alone, or the code alone. People will think you went through all the work of making that figure, editing it in PowerPoint, screenshotting it to a .png, then dropping that .png file into your manuscript, but the truth is… you scripted all of that, so the manuscript itself made the .png and included it where it needed to go.
R Markdown is by no means restricted to R code.
This is the killer app that won me over.
Simply by specifying that a given code block is Python,
and installing a little tool (
reticulate) that allows R to interface with Python,
I can run arbitrary Python code within the document and capture the output however I want.
That results paragraph? Sure.
Fancy images of predictions from my machine learning model? But of course.
If you don't want to use any R code ever, that's fine. R Markdown doesn't mind. Use SAS, MATLAB (via Octave), heck, even bash scripts - the range of language support is fantastic.
R Markdown can be compiled to pretty much any format you can dream of. My current setup simultaneously puts out an HTML document (that can be opened in any web browser), a PDF (because I love PDFs), and (AND!) a .docx Word file, all beautifully formatted, on demand, whenever I hit my keyboard shortcut. I can preview the PDF or HTML as I write, have a .docx to send to my PI, and life is good.
Also, because you can write in any programming language, you can easily collaborate between researchers that are comfortable in different paradigms. You can pass data back and forth between your chosen languages (for me, R and Python), either directly or by saving intermediate data to a format that both languages can read.
Many analyses and their manuscripts, especially if they use similar techniques (e.g. survival modeling), are rather formulaic. Many researchers have scripts they keep around and tweak for new analyses revolving around the same basic subject matter or approach. With R Markdown, your entire manuscript becomes a runnable program, further automating the boring parts of getting research out into the open.
One of the first introductions I had to R Markdown shared the remarkable idea of setting the file to run on a regular basis, generating a report based on any updated data, and then sending this report to all the interested parties automatically. While much academic work could not be so fully automated, parts of it certainly can be.
Perhaps your team is building a database for outcomes in a given disease, and has specified the analysis in great detail beforehand. One of my mentors gives the advice that in any project proposal you should go as far as to mock up the results section, including all figures, so you make sure you are collecting the right data. If this was done in an R Markdown document rather than a simple Word document, you could have large parts of the template manuscript become the real manuscript as the database fleshes out over time. Then when it's done, look over the data, make additions and subtractions as needed, write the discussion sections, and send it in.