-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathPractical.Rmd
More file actions
47 lines (35 loc) · 1.36 KB
/
Copy pathPractical.Rmd
File metadata and controls
47 lines (35 loc) · 1.36 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
---
title: "Practical"
author: "Emma Cliffe"
date: "2025-10-13"
output:
word_document: default
html_document: default
pdf_document: default
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
```
```{r message=FALSE, warning=FALSE, include=FALSE}
#A library I want to use but I don't want this in the document
library(psych)
```
## Todo
Have a look at the GitHub course repository issue. The work below should be done as part of a GitHub repository.
1. Download, read through and knit the attached R markdown file (R_Rstudio_Rmarkdown.Rmd) to pdf. This is to ensure you are able to output pdfs, which you will need to submit your final report.
2. Create a new R markdown file.
3. Create at least two code chunks in between your text. (It can be any text and any code, it doesn't need to be meaningful.)
4. In your text, add section headers, and at least one numbered list and one unordered list.
Remember to tick off each item on the course repository issue as you complete them!
That is the numbered list done, since I copied and pasted it and had to add the numbers back! I've added a section header already. Here are two code blocks (though I added the one above too).
```{r cars}
summary(cars)
describe(cars)
```
A very quick visual...
```{r carsplot, echo=FALSE}
plot(cars)
```
### Have I finished?
* Now I have...
* Once it is published on github, anyway