Answer: Debug the Robot #150

Here’s the bug

A Forward step is missing. It should come after step 5. Without it, Beep turns too early.

Did you find a different fix that also gets Beep to the battery? That counts too! There is often more than one way to fix a bug. The important thing is that you tested it step by step.

The fixed program, with Beep's route to the battery drawn as an orange line.
With the bug fixed, Beep reaches the battery.

The fixed program

  1. Turn left
  2. Turn left
  3. Forward
  4. Turn left
  5. Forward
  6. Forward
  7. Forward

What the buggy program did

Here is what happens if Beep follows the program with the bug, step by step. Beep doesn’t bump into anything, but ends up in the wrong square.

StepCommandBeep is now atFacingNote
1Turn leftcolumn 5, row 1up
2Turn leftcolumn 5, row 1left
3Forwardcolumn 4, row 1left
4Turn leftcolumn 4, row 1down
5Forwardcolumn 4, row 2down
6Forwardcolumn 4, row 3down

Check it with Python

This Python program pretends to be Beep. It follows the fixed program and checks for walls on the way. In Python, squares are counted from 0, so column 1, row 1 is (0, 0).

program = "LLFLFFF"
walls = [(0, 0), (0, 4), (1, 3), (2, 4), (4, 3)]
width, height = 5, 5
x, y, facing = 4, 0, "right"

moves = {"up": (0, -1), "right": (1, 0), "down": (0, 1), "left": (-1, 0)}
turn_left = {"up": "left", "left": "down", "down": "right", "right": "up"}
turn_right = {"up": "right", "right": "down", "down": "left", "left": "up"}

for step in program:
    if step == "F":
        dx, dy = moves[facing]
        if (x + dx, y + dy) in walls or not (0 <= x + dx < width and 0 <= y + dy < height):
            print("Bump! Beep hit a wall at", (x, y))
            break
        x, y = x + dx, y + dy
    elif step == "L":
        facing = turn_left[facing]
    elif step == "R":
        facing = turn_right[facing]

print("Beep finished at", (x, y), "facing", facing)

When you run it, it prints:

Beep finished at (3, 3) facing down

The battery is at (3, 3) in Python’s counting, so Beep made it! Try putting the buggy program, "LLFLFF", back in and see what Python says.