---
# System prepended metadata

title: RaukR improvements

---

# RaukR improvements

Here, we can put our thoughts and ideas regarding improving RaukR. Include anything from suggestions for new topics, technical improvements or suggestions regarding the lecture/lab contents.

## Day 1

### General improvements

External speakers should have direct line of communication with us. Invite them to the slack for example, so we can message them.

### Module 1 -- Introduction

### Module 2 -- Reproducible Research

#### Lecture

#### Lab

### Module 3 -- R Style Coding Guidelines

#### Lecture

#### Lab

### Module 4 -- Functions and Scripts

#### Lecture

#### Lab

## Day 2

### General improvements

### Module 5 -- Code debugging, optimization and profiling
Perhaps a bit odd to talk about parallelisation and things here and also the day after in another session. Should be together?

### Module 6 -- R packages
People are having a hard time knowing when something should be in the script, in the terminal, or in the R console. Perhaps colorcode the instructions to make it easier to know what goes where?
Make Rcpp even clearer, some people had issues getting it working.

## Day 3

### Module  -- Parallelisation

I need to update the language in the labs to be more coherent. Not use "resolved" in one place and "evaluated" in another.
I need to update presenters notes.

Add resampling as a good example for parallel processing.

## Day 4

## ggplot2

Add few slides of basics

## Day 5

## shiny

Better example for reactivity
