Using rmarkdown and parameterised reports
summary
Uses parameterised rmarkdown with child documents and the Tidyverse to run the same analysis across three endpoints, embedding a YAML param named params$endpoint with a default and fixed choices and a boolean that toggles showing code for quantitative vs nonquantitative audiences. Knits via the IDE pop-up or render(params=...) from the command line, stores precompiled variants on RStudio Connect, catches failures with tryCatch, and requires days of setup that amortise over months or years.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:15TL;DR & Disclaimer
- 2:43Data analysis - THEORY
- 5:17Who is your audience?
- 6:23Notebooks / markdown vs scripts (for analysis)
- 7:17Rule of three
- 8:06YAML header parameters
- 9:30Render with parameters
- 12:48More parameterisation
related talks
10mHow to write a report using R Markdown
16mSometimes you just need words
20mUsing Quarto to Improve Formatting/Automate the Generation of Hundreds of Reports
12mFrom summarizing projects to setting tags, uses of parsing R files
21mCreating reproducible static reports
22mMotley Crews: Collaborating with Quarto
42mJSON data + RML template = PDF report
19mQuarto: A Multifaceted Publishing Powerhouse for Medical Researchers