Rat in a Maze Problem in DSA C++ - Time & Space Complexity
We want to understand how the time needed to solve the Rat in a Maze problem changes as the maze size grows.
How does the number of steps the algorithm takes grow when the maze gets bigger?
Analyze the time complexity of the following code snippet.
bool solveMaze(int maze[N][N], int x, int y, int sol[N][N]) {
if (x == N-1 && y == N-1) {
sol[x][y] = 1;
return true;
}
if (isSafe(maze, x, y)) {
sol[x][y] = 1;
if (solveMaze(maze, x+1, y, sol)) return true;
if (solveMaze(maze, x, y+1, sol)) return true;
sol[x][y] = 0; // backtrack
}
return false;
}
This code tries to find a path from the top-left to the bottom-right of a maze using backtracking.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Recursive calls exploring possible paths in the maze.
- How many times: Potentially, each cell is visited multiple times as the algorithm tries different paths.
As the maze size grows, the number of possible paths grows very fast because the rat can move right or down at each step.
| Input Size (n) | Approx. Operations |
|---|---|
| 2 | Up to 22+2 = 16 tries |
| 4 | Up to 24+4 = 256 tries |
| 8 | Up to 28+8 = 65,536 tries |
Pattern observation: The number of operations grows exponentially as the maze size increases.
Time Complexity: O(2^{2n}) = O(4^{n})
This means the time needed can grow very fast, doubling many times as the maze gets bigger.
[X] Wrong: "The algorithm only checks each cell once, so it runs in linear time."
[OK] Correct: The algorithm tries many paths and can visit the same cell multiple times in different paths, causing exponential growth.
Understanding this problem helps build skills in recursion and backtracking, which are useful for many puzzles and pathfinding tasks.
"What if we added memoization to remember visited paths? How would the time complexity change?"
Practice
Rat in a Maze Problem in Data Structures & Algorithms?Solution
Step 1: Understand the problem context
The Rat in a Maze problem involves navigating a maze represented by a grid to find a path from the start cell to the destination cell.Step 2: Identify the main objective
The main objective is to find a valid path through open cells (usually marked as 1) from the start to the end point.Final Answer:
Find a path from the start to the destination in a maze -> Option AQuick Check:
Goal = Find path [OK]
- Confusing pathfinding with counting walls
- Thinking it's about sorting cells
- Assuming it's about shortest distance always
Solution
Step 1: Recall C++ array declaration syntax
In C++, a 2D array is declared using square brackets for each dimension, likeint maze[4][4];.Step 2: Analyze each option
int maze[4][4]; uses correct syntax. int maze(4,4); uses parentheses which is invalid for arrays. int maze[4,4]; uses comma inside brackets which is incorrect. int maze{4,4}; uses braces which is invalid for declaration.Final Answer:
int maze[4][4]; -> Option AQuick Check:
2D array = int maze[4][4]; [OK]
- Using parentheses instead of brackets
- Using commas inside brackets
- Using braces for declaration
int maze[2][2] = {{1, 0}, {1, 1}};
bool solveMaze(int maze[2][2], int x, int y) {
if (x == 1 && y == 1) return true;
if (x < 0 || y < 0 || x >= 2 || y >= 2 || maze[x][y] == 0) return false;
if (solveMaze(maze, x + 1, y)) return true;
if (solveMaze(maze, x, y + 1)) return true;
return false;
}
int main() {
bool result = solveMaze(maze, 0, 0);
std::cout << (result ? "Path Found" : "No Path") << std::endl;
return 0;
}
What will be the output when this program runs?Solution
Step 1: Trace the recursive calls starting at (0,0)
At (0,0), maze[0][0] = 1 (open). Try moving down to (1,0): maze[1][0] = 1 (open). From (1,0), try moving down to (2,0) invalid, then right to (1,1): maze[1][1] = 1 (open) and is destination.Step 2: Confirm path existence
Since (1,1) is reached, function returns true and prints "Path Found".Final Answer:
Path Found -> Option DQuick Check:
Valid path exists = Path Found [OK]
- Ignoring boundary checks
- Assuming no path due to blocked cell
- Confusing indices order
bool solveMaze(int maze[3][3], int x, int y) {
if (x == 2 && y == 2) return true;
if (x > 2 || y > 2 || maze[x][y] == 0) return false;
if (solveMaze(maze, x + 1, y)) return true;
if (solveMaze(maze, x, y + 1)) return true;
return false;
}
What is the bug in this code?Solution
Step 1: Analyze boundary and base case checks
The code checks if x or y are greater than 2 and if the cell is blocked. It returns true if destination (2,2) is reached.Step 2: Identify missing visited check
There is no mechanism to mark visited cells, so the recursion can revisit the same cells repeatedly, causing infinite recursion or stack overflow.Final Answer:
No check for visited cells causing infinite recursion -> Option CQuick Check:
Visited check missing = Infinite recursion [OK]
- Ignoring visited cells check
- Assuming boundary checks cover all cases
- Confusing base case with boundary
int maze[4][4] = {
{1, 0, 0, 0},
{1, 1, 0, 1},
{0, 1, 0, 0},
{1, 1, 1, 1}
};
Write a function to find one path from (0,0) to (3,3) moving only right or down. Which of the following describes the correct approach?Solution
Step 1: Understand movement constraints and maze structure
The rat can move only right or down. The maze has blocked cells (0) and open cells (1). We need to find a path from top-left to bottom-right.Step 2: Choose correct algorithm approach
Backtracking explores all possible paths by moving right or down, marking visited cells to avoid revisiting and infinite loops. Greedy or BFS without visited checks can fail or loop.Final Answer:
Use backtracking to explore right and down moves, marking visited cells to avoid cycles -> Option BQuick Check:
Backtracking + visited = Correct approach [OK]
- Using greedy without backtracking
- Ignoring visited cells causing loops
- Moving in wrong directions
Ready to prove it?
Pass the test and this pattern moves unknown
