Code chunks and output in R Programming - Time & Space Complexity

Time Complexity: Code chunks and output

O(n)

Understanding Time Complexity

We want to see how the time to run code chunks grows as we add more lines or commands.

How does the number of code chunks affect the total work done?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

# Print numbers from 1 to n
print_numbers <- function(n) {
  for (i in 1:n) {
    print(i)
  }
}

print_numbers(5)
    

This code prints numbers from 1 up to n, one by one.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that prints each number.
• How many times: Exactly n times, once for each number.

How Execution Grows With Input

As n grows, the number of print operations grows the same way.

Input Size (n)	Approx. Operations
10	10 prints
100	100 prints
1000	1000 prints

Pattern observation: The work grows directly with n, so doubling n doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the number of items printed.

Common Mistake

[X] Wrong: "The code runs instantly no matter how big n is."

[OK] Correct: Each number must be printed one by one, so more numbers mean more time.

Interview Connect

Understanding how loops affect time helps you explain code efficiency clearly and confidently.

Self-Check

"What if we changed the loop to print only every second number? How would the time complexity change?"

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