07c BackTracking

More on Stacks and Queues and Backtracking
A.R. Hadaegh Dr. Ahmad R. Hadaegh California State University San Marcos (CSUSM) Page 1
As we mentioned before, two common introductory Abstract Data Type (ADT) that worth studying are Stack and Queue Many problems (or parts of problems) can be thought of as stack problems, queue problems, or other problems that can be solved with the help of another (perhaps user-defined) ADT
You need to decide what ADTs you need, build them, test them, then tackle your larger problem
A.R. Hadaegh Dr. Ahmad R. Hadaegh
California State University San Marcos (CSUSM)
Page
Stack ADT
A stack is an ADT with specific properties and operations Stack properties are: Only one item can be accessed at a time Always the last item inserted is the first to come out (LIFO)
New items must be inserted at the top

The size of the stack is dynamic
The stack must be able to grow and shrink

Normally, items stored on the stack are homogeneous (i. e. they are all integers or all are string, etc
Stack Operations
Stack operations are: Push: Puts a new item on the top of the stack. Cant push into a full stack Pop: Removes the top item from stack. Cant pop an empty stack Top: Examine top item without modifying stack. Cant top an empty stack Init: Set existing stack to empty Full: Returns true if the stack is full Empty: Returns true if the stack is empty
Problem Solving Using Stack: Bracket Checking

Many problems can be solved using stacks Given a mathematical expression with 3 types of brackets ( ) [ ] { }, we want to determine if the brackets are properly matched For example, bracketing in the following expression is CORRECT { 5 * (8-2) } / { [4 * (3+2)] + [5 * 6] } However, the bracketing in the following two expressions are INCORRECT { (A+C) * D [A + {B+C} )
This problem is easily solved with a stack

Algorithm: Scan expression from left to right Each time a left bracket is encountered, push it onto the stack When a right bracket is encountered, compare it to the top item on the stack If its a match, pop the stack If not, report illegal bracketing If the stack is prematurely empty, report illegal bracketing If there are items left on the stack after the expression has been scanned, report illegal bracketing
This program assumes bool BracketMaching (string expression) that we have the { following routines char curr, temp; available Stack bracket_stack; for (int i=0; i< stg.size(); i++) bool empty (); { push (item); curr = stg[i]; char top (); if (curr == ( || curr == [ || curr == {) bracket_stack.push (curr); else if (curr == ) || curr == ] || curr == }) if (bracket_stack.empty() ) then return false; else if (bracket_stack.pop() does not match with curr) return false; end if end if } // for loop
return true; }
Problem Solving Using Stack: Evaluation of An Expression

Consider the problem of evaluating an arithmetic expression using a stack Traditionally, when we write an arithmetic expression as follows: 2 + 3 * (6 - 5) This is known as infix notation Operators are in-between the operands When computing arithmetic expressions, its sometimes useful to represent them using postfix (operator after) or prefix (operator before) notation
Prefix -61 *+432 /+23-94
Infix 6-1 (4 + 3) * 2 (2 + 3) / (9 - 4)
Postfix 6143+2* 23+94-/
Its easy to evaluate postfix and prefix expressions using a stack in part because no brackets are necessary
Page
prefix *+432 evaluate 4 7 + 3 2 * 14 2 Push 2 Push 3 Push 4 Pop 4 Pop 3 Apply + and get 7 Push 7 Pop 7 Pop 2 Apply * and get 14 Push 14
postfix
43+2*
3 2 * 14 4 + 7 push 4 push 3 Pop 3 Pop 4 Apply addition and get 7 Push 7 Push 2 Pop 2 Pop 7 Apply * and get 14 Push 14
Page 10
Algorithm for evaluating postfix: Parse expression from left to right When an operand is encountered, push it onto the stack
When an operator is encountered, pop the top two operands, apply the operator, and push the result onto the stack
When the expression is completely scanned, the final result will be on the stack What if we want to convert an expression from infix to postfix? For example: 2 + 3 * [(5 - 6) / 2] becomes 2356-2/*+
Use the following algorithm to change infix to postfix:
Scan infix string from left to right

Each time an operand is encountered, copy it to the output When a bracket is encountered, check its orientation. Push left brackets onto the stack If its a right bracket, pop all operators out of the stack and copy them to output until a matching left bracket is encountered. Discard the left bracket. When an operator is encountered, check the top item of the stack. If the priority is >= the current operator, pop the top operator and copy it to output Continue until an operator of lesser priority is encountered or until stack is empty Assume left brackets have lowest priority Finally, push current operator onto the stack When the end of the expression is reached, copy the remaining stack contents to output in the order popped
Consider the following example that is scanned from left to right Expression: 2+3*[(56)/2]
Stack
Output:
2 is placed on the output line because it is an operand Expression: 2+3*[(56)/2] Stack
Output:
+ is an operator and it is placed in the stack. Note there is no operator on the top of the stack with priority >= the + operator
Page 13
Expression: 2+3*[(56)/2]
Stack
Output:
23
3 is placed on the output line because it is an operand
Stack
Output:
23
* +
* is an operator and it is placed in the stack without taking anything out of the stack. Note that * has higher priority than +
Page 14
Stack
Output:
23
[ * +
Left brackets, no matter what type of bracket it is, it is placed in the stack
Stack ( [ * +
Output:
23
Again another left encountered and it is placed in the stack
Page 15
Stack
Output:
235
( [ * +
Stack Output: 235 ( Minus sign (-) is placed in the [ stack. Note that the top of the * stack is not an operator to + compare minus sign with it
Page 16
Stack Output: 2356 ( [ 6 is placed on the output line * because it is an operand +
Stack
Output:
2356-
[ * +
( is a closing round bracket. Keep on popping from the stack till we you find the matching opening round bracket. DO NOT COPY THE OPEN ROUND BRACKET TO THE OUTPUT
Page 17
Stack / [ * +
Output:
2356-
Division (/) is placed in the stack. Note that the top of the stack is not an operator to compare division sign with it
Stack / [ * +
Output:
2356-2
Page 18
Stack
Output:
2356-2/
* + Stack
] is a closing square bracket. Keep on popping from the stack till we you find the matching opening square bracket. DO NOT COPY THE OPEN SQUARE BRACKET TO THE OUTPUT
Output:
23562/*+
We are done. So keep popping from the stack and place the characters to the output line
What we have on the output line is the corresponding postfix expression

Problem Solving Using Stack: Adding large numbers using stack

Another example of stack application is adding two large numbers together. Note that the largest magnitude of integers are limited so we are not able to normally add numbers like: 243678489505654679857465758598595950949463535 + 462668435748955758056548577946 Since the integer variables cannot hold such a big numbers we can use other tools to add these numbers together The next slide shows the algorithm of adding two numbers together using stack
Algorithm for adding two numbers

Read the numerals of the first number and store the numbers corresponding to them on the stack; Read the numerals of the second number and store them in another stack; Let R = 0; While at least one stack is not empty Pop a number from each stack and add them to R; Push the unit part of R on the result stack; Store carry part of R in R overwriting the old value; Push R on the result stack if it is not zero Pop numbers from the result stack and display them
592 + 3784 4376
2 +4 6
9 +8 17
1 5 +7 13
1 +3 4
2 Stack 1 9 5
9 5
+ =6
4 Stack 2 8 7 3 8 7 3
+ =17
7 3
+ =13
+ =4
Result Stack
7 6
3 7 6
4 3 7 6
Page 22
Problem Solving Using Stack: Exiting A Maze

Consider the problem of a trapped mouse that tries to find its way to an exit in a maze The mouse systematically moves and if it hits a wall, it backtracks and tries another path. The maze is implemented as a two dimensional character array in which passages are marked with o and walls are marked with 1.
When a cell is visited, it is marked with . so that the mouse does not try that again.
In general, the mouse always takes right cell first, if it cannot succeed, it takes left and if it still fails, it takes down and finally it tries the upper cell to reach its destination. As long as it finds a space it moves in that path and tries its best to find the exit door. We represent the mouse with M and exit door with E
In order to ensure that the mouse does not fall off the maze, we create a wall around the maze.
Thus the mouse will be trapped in the maze until it finds the door.
If the mouse tries all the possible solutions and still cannot find the exit door, we report a failure; otherwise, we report a success.
The algorithm is:
Initialize stack, exitCell, entryCell, currentCell = entryCell; Create a wall of 1s around the maze While currentCell is not exitCell Mark currentCell as visited; Push onto the stack the unvisited neighbors of current Cell in the order of up, down left and right If stack is empty Report failure Else Pop off a cell from the stack and make it currentCell success
0 1 2 3 4 5
Start with the following maze where the mouse is at position (3, 3) and the exit door is at (2, 4)
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1 1 o o o E 1 1 o o M 1 1 1 1 1 1 1 1
0 1 2 3 4 5
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1 1 o o o E 1 1 o o M 1 1 1 1 1 1 1 1
Push the Up and Left cell into stack
Make the current position visited (.) Pop the first element of the stack Move the mouse to that position
(3, 2) (2, 3)
Page 25
0 1 2 3 4 5
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1
Push the Up and Left cells into stack
1 o o o E 1
1 o M . 1 1 1 1 1 1 1 1
(3, 1) (2, 2) (2, 3)
0 1 2 3 4 5
Push the Up cell into stack
Make the current position visited (.)

Pop the first element of the stack Move the mouse to that position
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1 1 o o o E 1 1 M . . 1 1 1 1 1 1 1 1
(2, 1) (2, 2) (2, 3)
Page 26
0 1 2 3 4 5
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1
Push the Right cell into stack
1 M o o E 1
1 . . . 1 1 1 1 1 1 1 1
(2, 2) (2, 2) (2, 3)
0 1 2 3 4 5
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1 1 . 1 . M o E 1 . . 1 1
Push the Right cell into stack
Make the current position visited (.)

Pop the first element of the stack Move the mouse to that position
(2, 3) (2, 2) (2, 3)
1 1 1 1 1 1
Page 27
0 1 2 3 4 5
0 1 2 3 4
1 1 1 1 1 1 1 1 1 o o 1
Push the UP and Right cell into stack
1 .
1 .
.
.
M E 1
. 1 1
1 1 1 1 1 1
(2, 4) (1, 3) (2, 2) (2, 3)
0 1 2 3 4 5
0 1 2 3 4
1 1 1 1 1 1 1 o 1 . 1 . . . . .
1 o 1 1
1 1 1 1
Push the UP cell into stack
E/M 1
1 1 1 1
(1, 3) (2, 2) (2, 3)
The exit door is found
Page 28

07c BackTracking

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

07c BackTracking

Uploaded by

Copyright:

Available Formats

More on Stacks and Queues and Backtracking

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

New items must be inserted at the top

The stack must be able to grow and shrink

Problem Solving Using Stack: Bracket Checking

This problem is easily solved with a stack

Problem Solving Using Stack: Evaluation of An Expression

Prefix -61 *+432 /+23-94

Postfix 6143+2* 23+94-/

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

California State University San Marcos (CSUSM)

Use the following algorithm to change infix to postfix:

Scan infix string from left to right

2 is placed on the output line because it is an operand Expression: 2+3*[(56)/2] Stack

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

3 is placed on the output line because it is an operand

California State University San Marcos (CSUSM)

Again another left encountered and it is placed in the stack

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

5 is placed on the output line because it is an operand

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

Stack Output: 2356 ( [ 6 is placed on the output line * because it is an operand +

California State University San Marcos (CSUSM)

2 is placed on the output line because it is an operand

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

What we have on the output line is the corresponding postfix expression

Problem Solving Using Stack: Adding large numbers using stack

Algorithm for adding two numbers

592 + 3784 4376

California State University San Marcos (CSUSM)

Problem Solving Using Stack: Exiting A Maze

Push the Up and Left cell into stack

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

Push the Up and Left cells into stack

(3, 1) (2, 2) (2, 3)

Push the Up cell into stack

Make the current position visited (.)

(2, 1) (2, 2) (2, 3)

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

Push the Right cell into stack

(2, 2) (2, 2) (2, 3)

Push the Right cell into stack

Make the current position visited (.)

(2, 3) (2, 2) (2, 3)

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

Push the UP and Right cell into stack

(2, 4) (1, 3) (2, 2) (2, 3)

Push the UP cell into stack

(1, 3) (2, 2) (2, 3)

The exit door is found

A.R. Hadaegh Dr. Ahmad R. Hadaegh

California State University San Marcos (CSUSM)

You might also like