Reaction time game in Raspberry Pi - Time & Space Complexity

Time Complexity: Reaction time game

O(1)

Understanding Time Complexity

We want to understand how the time it takes for the reaction time game code to run changes as the game runs longer or with more players.

Specifically, we ask: how does the number of steps the program does grow when the game runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

import time
import random

for i in range(5):
    wait = random.uniform(1, 3)
    time.sleep(wait)  # wait for random time
    start = time.time()
    input('Press Enter as fast as you can!')
    reaction = time.time() - start
    print(f'Reaction time: {reaction:.3f} seconds')

This code runs a simple reaction time game 5 times, waiting a random time before asking the player to press Enter and measuring how fast they respond.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that repeats the reaction test 5 times.
• How many times: Exactly 5 times, fixed and does not change with input size.

How Execution Grows With Input

Since the loop runs a fixed 5 times, the number of operations stays the same no matter what.

Input Size (n)	Approx. Operations
5	5 reaction tests
10	Still 5 reaction tests (fixed)
100	Still 5 reaction tests (fixed)

Pattern observation: The number of steps does not grow with input size because the loop count is fixed.

Final Time Complexity

Time Complexity: O(1)

This means the program runs in constant time, doing the same amount of work no matter how big the input or game length might be.

Common Mistake

[X] Wrong: "The time grows with the number of seconds the player waits before pressing Enter."

[OK] Correct: Waiting time is a pause, not extra steps the program does. The program only counts how many times it runs the loop, not how long the player takes to respond.

Interview Connect

Understanding how loops and fixed repetitions affect time helps you explain how programs behave as they run longer or handle more data. This skill is useful when designing games or interactive programs on devices like Raspberry Pi.

Self-Check

"What if we changed the loop to run for a variable number of rounds based on user input? How would the time complexity change?"

Practice

1. What is the main purpose of a reaction time game on a Raspberry Pi?

easy

A. To measure how quickly a player presses a button after an LED lights up

B. To count how many times a button is pressed in a minute

C. To display random colors on an LED strip

D. To control the brightness of an LED using a sensor

Solution

1. Step 1: Understand the game goal

   The reaction time game tests how fast a player reacts to a signal, usually an LED lighting up.

2. Step 2: Identify the key action

   The player must press a button as soon as the LED lights up to measure reaction speed.

3. Final Answer:

   To measure how quickly a player presses a button after an LED lights up -> Option A

4. Quick Check:

   Reaction time = button press speed after LED [OK]

Hint: Focus on measuring speed after LED signal [OK]

Common Mistakes:

• Confusing reaction time with counting presses
• Thinking the game controls LED brightness
• Assuming it displays colors randomly

2. Which Python code snippet correctly sets up GPIO pin 17 as an input for a button on Raspberry Pi?

easy

A. GPIO.setup(17, GPIO.OUT)

B. GPIO.setup(17, GPIO.IN)

C. GPIO.input(17, GPIO.IN)

D. GPIO.output(17, GPIO.IN)

Solution

1. Step 1: Recall GPIO setup syntax

   To set a pin as input, use GPIO.setup(pin_number, GPIO.IN).

2. Step 2: Match the correct option

   GPIO.setup(17, GPIO.IN) uses GPIO.setup(17, GPIO.IN), which is correct for input pin setup.

3. Final Answer:

   GPIO.setup(17, GPIO.IN) -> Option B

4. Quick Check:

   GPIO.setup(pin, GPIO.IN) sets input pin [OK]

Hint: Use GPIO.setup with GPIO.IN for input pins [OK]

Common Mistakes:

• Using GPIO.OUT instead of GPIO.IN for input
• Confusing GPIO.input() with GPIO.setup()
• Trying to use GPIO.output() on input pins

3. What will be the output of this code snippet in a reaction time game?

import time
start = time.time()
# LED lights up here
input('Press Enter as fast as you can!')
end = time.time()
print(f'Reaction time: {end - start:.2f} seconds')

medium

A. No output because input() is not called

B. Reaction time: 0.00 seconds

C. SyntaxError due to missing parentheses

D. Reaction time: time taken between prompt and Enter press

Solution

1. Step 1: Understand timing with time.time()

   The code records time before and after waiting for user input.

2. Step 2: Calculate reaction time

   The difference end - start measures how long the user took to press Enter after the prompt.

3. Final Answer:

   Reaction time: time taken between prompt and Enter press -> Option D

4. Quick Check:

   Reaction time = end - start after input [OK]

Hint: time.time() difference measures reaction delay [OK]

Common Mistakes:

• Assuming reaction time is always zero
• Confusing syntax errors with correct code
• Thinking input() is not called

4. Identify the error in this Raspberry Pi reaction game code snippet:

GPIO.setup(18, GPIO.OUT)
GPIO.setup(23, GPIO.IN)
GPIO.output(23, GPIO.HIGH)
# Wait for button press on pin 23

medium

A. Pin 23 should be set as GPIO.OUT

B. GPIO.setup() missing for pin 18

C. GPIO.output() used on input pin 23, which is incorrect

D. No error, code is correct

Solution

1. Step 1: Check pin setup

   Pin 23 is set as input with GPIO.setup(23, GPIO.IN).

2. Step 2: Identify incorrect usage

   GPIO.output() cannot be used on input pins; it is only for output pins.

3. Final Answer:

   GPIO.output() used on input pin 23, which is incorrect -> Option C

4. Quick Check:

   GPIO.output() only for output pins [OK]

Hint: Use GPIO.output only on output pins [OK]

Common Mistakes:

• Trying to write output on input pins
• Forgetting to setup pins before use
• Assuming no error when pin modes mismatch

5. You want to improve your Raspberry Pi reaction time game by adding a random delay before lighting the LED. Which code snippet correctly adds a random delay between 1 and 5 seconds before turning on the LED on pin 18?

hard

A. import random
import time
wait = random.randint(1, 5)
time.sleep(wait)
GPIO.output(18, GPIO.HIGH)

B. import random
wait = random.random(1, 5)
time.sleep(wait)
GPIO.output(18, GPIO.HIGH)

C. import random
wait = random.randint(1, 5)
GPIO.output(18, GPIO.HIGH)
time.sleep(wait)

D. import time
wait = random.randint(1, 5)
time.sleep(wait)
GPIO.output(18, GPIO.HIGH)

Solution

1. Step 1: Use random.randint for integer delay

   random.randint(1, 5) returns an integer between 1 and 5 seconds.

2. Step 2: Sleep before turning LED on

   time.sleep(wait) pauses the program before GPIO.output(18, GPIO.HIGH) lights the LED.

3. Final Answer:

   import random import time wait = random.randint(1, 5) time.sleep(wait) GPIO.output(18, GPIO.HIGH) -> Option A

4. Quick Check:

   random.randint + sleep before LED ON [OK]

Hint: Sleep before LED ON using random.randint delay [OK]

Common Mistakes:

• Using random.random with arguments (invalid)
• Sleeping after turning LED on
• Not importing random module