les <- 9 knitr::opts_chunk$set(echo = TRUE, class.source="Rchunk", class.output="Rout")
knitr::opts_chunk$set( echo = TRUE, warning = FALSE, message = FALSE, error = FALSE )
## Packages library(utils) library(tidyverse) library(tools) library(glue) library(readxl) library(httr) library(zoo) #library(blscrapeR)
rmarkdown::render()
to render one or multiple parameterized reportsNote that class time this week will be mostly spend on the practice job interviews.
As we saw previously, RMarkdown is R's answer to doing reproducible research. In this lesson we take the next step in customization of RMardown reports. We will see that RMarkdown can be used for a number of semi- and fully automated reporting work flows.
This is a much shorter lesson than the previous ones, as we will have the portfolio presentations today. The lesson consists mainly of a number of exercises.
By now you must have a clear idea on the possibilities of writing a reproducible static
analysis report in RMarkdown. It is time to make it a bit more flexible and robust.
Most of the time an analysis will depend on several parameters that you might want to vary for an analysis. We can think of the following things (this list is not exclusive):
Maak nu opdracht 8 van de portfolio-opdrachten.
CC BY-NC-SA 4.0 This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Unless it was borrowed (there will be a link), in which case, please use their license.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.