Code chunks and output in R Programming - Step-by-Step Execution

Concept Flow - Code chunks and output

Start R Markdown

↓

Write code chunk

↓

Run code chunk

↓

Execute R code

↓

Capture output

↓

Display output in document

↓

Repeat for next chunk or finish

This flow shows how R Markdown runs code chunks: write code, run it, capture output, and display it in the document.

Execution Sample

R Programming

```{r}
summary(c(1, 2, 3, 4, 5))
```

This code chunk calculates and shows a summary of the numbers 1 to 5.

Execution Table

Step	Action	Code Executed	Output Produced
1	Start code chunk execution	summary(c(1, 2, 3, 4, 5))	Calculates summary statistics
2	Calculate Min	Min = 1	Min: 1
3	Calculate 1st Qu.	1st Qu. = 2	1st Qu.: 2
4	Calculate Median	Median = 3	Median: 3
5	Calculate Mean	Mean = 3	Mean: 3
6	Calculate 3rd Qu.	3rd Qu. = 4	3rd Qu.: 4
7	Calculate Max	Max = 5	Max: 5
8	Display summary output	summary output shown	Min: 1 1st Qu.: 2 Median: 3 Mean: 3 3rd Qu.: 4 Max: 5
9	End code chunk execution	chunk finished	Output displayed in document

💡 All summary statistics calculated and output displayed

Variable Tracker

Variable	Start	After Min	After 1st Qu.	After Median	After Mean	After 3rd Qu.	After Max	Final
min	NA	1	1	1	1	1	1	1
1st Qu.	NA	NA	2	2	2	2	2	2
median	NA	NA	NA	3	3	3	3	3
mean	NA	NA	NA	NA	3	3	3	3
3rd Qu.	NA	NA	NA	NA	NA	4	4	4
max	NA	NA	NA	NA	NA	NA	5	5

Key Moments - 2 Insights

Why does the output show multiple statistics instead of just one number?

The summary() function calculates several statistics at once, as shown in the execution_table rows 2 to 7 where each statistic is computed step-by-step.

Does the code chunk run all at once or line by line?

The code chunk runs all at once, but internally R calculates each statistic step-by-step, as seen in the execution_table steps 2 to 7.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'median' after step 4?

A 3

B NA

C 4

D 2

💡 Hint

Check the variable_tracker table column 'After Median' and step 4 in execution_table

At which step does the output show the maximum value?

A Step 5

B Step 7

C Step 6

D Step 8

💡 Hint

Look at execution_table rows where 'Max' is calculated

If the input vector changed to c(10, 20, 30), how would the 'min' value in variable_tracker change?

A It would be 20

B It would be 1

C It would be 10

D It would be 30

💡 Hint

The 'min' is the smallest number in the input vector, see variable_tracker 'min' row

Concept Snapshot

R Markdown code chunks run R code inside backticks.
Output from code runs is captured and shown below the chunk.
Functions like summary() produce multiple outputs.
Each chunk runs fully before showing results.
This helps combine code and output in one document.

Full Transcript

This visual shows how R Markdown code chunks work. You write code inside special backticks. When you run the chunk, R executes the code and captures the output. For example, summary(c(1,2,3,4,5)) calculates several statistics like min, median, and max. Each statistic is computed step-by-step, then all results are displayed below the code chunk. This process repeats for each chunk, letting you mix code and results in one document.

Practice

1. What is the purpose of an R code chunk in an R Markdown document?

easy

A. To run R code and show its output inline with text

B. To write plain text without any code

C. To create a table of contents automatically

D. To add images to the document

Solution

1. Step 1: Understand R Markdown structure

   R Markdown uses code chunks to embed R code inside text documents.

2. Step 2: Purpose of code chunks

   Code chunks run R code and display results inline, mixing code and output.

3. Final Answer:

   To run R code and show its output inline with text -> Option A

4. Quick Check:

   Code chunk = run code + show output [OK]

Hint: Code chunks run code and show output together [OK]

Common Mistakes:

• Thinking code chunks only hold text
• Confusing code chunks with document sections
• Assuming code chunks add images automatically

2. Which of the following is the correct way to start an R code chunk in R Markdown?

easy

A. {r}```

B. ```r

C. ```{r}

D. {r}

Solution

1. Step 1: Recall R Markdown chunk syntax

   R code chunks start with three backticks followed by {r} exactly.

2. Step 2: Check each option

   Only ```{r} correctly starts a chunk; others are invalid syntax.

3. Final Answer:

   ```{r} -> Option C

4. Quick Check:

   Chunk start = ```{r} [OK]

Hint: Start chunks with three backticks and {r} [OK]

Common Mistakes:

• Omitting curly braces around r
• Using only two backticks
• Confusing HTML tags with chunk syntax

3. What will be the output of this R code chunk?

```{r}
x <- 5
x * 2
```

medium

A. [1] 10

B. 10

C. x * 2

D. Error: object 'x' not found

Solution

1. Step 1: Understand the code execution

   Variable x is assigned 5, then multiplied by 2, resulting in 10.

2. Step 2: R output format

   R prints numeric output with index [1] before the value.

3. Final Answer:

   [1] 10 -> Option A

4. Quick Check:

   5 * 2 = 10 with [1] prefix [OK]

Hint: R prints numeric output with [1] prefix [OK]

Common Mistakes:

• Ignoring the [1] prefix in output
• Expecting just '10' without index
• Thinking code prints the expression itself

4. Identify the error in this R code chunk:

```{r}
print("Hello)
```

medium

A. Missing closing curly brace for chunk

B. Missing closing quote in the string

C. Incorrect function name 'print'

D. No error, code runs fine

Solution

1. Step 1: Check the string syntax

   The string starts with a double quote but lacks the closing double quote.

2. Step 2: Consequence of missing quote

   This causes a syntax error because the string is not properly closed.

3. Final Answer:

   Missing closing quote in the string -> Option B

4. Quick Check:

   Unclosed string causes syntax error [OK]

Hint: Check all quotes are closed in strings [OK]

Common Mistakes:

• Assuming chunk braces cause error
• Thinking print is misspelled
• Ignoring missing quote errors

5. You want to run an R code chunk but hide the code and only show the output. Which chunk option should you use?

hard

A. ```{r, include=FALSE}

B. ```{r, eval=FALSE}

C. ```{r, message=FALSE}

D. ```{r, echo=FALSE}

Solution

1. Step 1: Understand chunk options

   echo=FALSE hides the code but runs it, showing output only.

2. Step 2: Compare other options

   eval=FALSE skips running code, include=FALSE hides both code and output, message=FALSE hides messages only.

3. Final Answer:

   ```{r, echo=FALSE} -> Option D

4. Quick Check:

   echo=FALSE hides code, shows output [OK]

Hint: Use echo=FALSE to hide code but show output [OK]

Common Mistakes:

• Using eval=FALSE hides output too
• Using include=FALSE hides everything
• Confusing message=FALSE with code hiding