### 1996 Canadian Computing Competition, Stage 2

## Day 2, Problem 3: Hoppers

Hoppers are people on a jump stick who can jump from one square to the other, without touching the squares in between (a bit like a knight in chess). They can pick up speed and make bigger hops, but their acceleration per move is limited, and they also have a maximum speed. The game of Hoppers is played on a rectangular grid, where each square on the grid is either empty or occupied. While hoppers can fly over any square, they can only land on empty squares. At any point in time, a hopper has a velocity (x,y), where x and y are the speed (in squares) parallel to the grid. Thus, a speed of (2,1) corresponds to a knight jump, (as does (-2,1) and 6 other speeds).

To determine the hops a hopper can make, we need to know how much speed a hopper can pick up or lose: either -1, 0, or 1 square in either or both directions. Thus, while having speed (2,1), the hopper can change to speeds (1,0), (1,1), (1,2), (2,0), (2,1), (2,2), (3,0), (3,1) and (3,2). It is impossible for the hopper to obtain a velocity of 4 in either direction, so the x and y component will stay between -3 and 3 inclusive.

The goal of Hoppers is to get from start to finish as quickly as possible (i.e. in the least number of hops), without landing on occupied squares. You are to write a program which, given a rectangular grid, a start point S, and a finish point F, determines the least number of hops in which you can get from S to F. A hopper starts with initial speed (0,0) and does not care about the speed when arriving at F.

### Input specification

The first line contains the number of test cases (`N`) your program has to process.

Each test case consists of a first line containing the width `X` (1 ≤ `X` ≤ 16) and height `Y` (1 ≤ `Y` ≤ 16) of the grid.

Next is a line containing four integers separated by blanks, of which the first two indicate the start point (x1, y1) and the last two indicate the end point (x2, y2), where the start and end point are valid points on the grid (that is, 0 ≤ x1, x2 < `X`, and 0 ≤ y1, y2 < `Y`).

The third line of each test case contains an integer P indicating the number of obstacles in the grid.

Finally, the test case consists of P lines, each specifying an obstacle.

Each obstacle consists of four integers: x1, x2, y1 and y2, (0 ≤ x1 ≤ x2 < `X`, and 0 ≤ y1 ≤ y2 < `Y`), meaning that all squares (x, y) with x1 ≤ x ≤ x2 and y1 ≤ y ≤ y2 are occupied. Neither the start point nor the finish point will ever be occupied.

### Output specification

The string '`No solution.`

' if there is no way the hopper can reach the finish point from the start point without hopping on an occupied square. Otherwise, the text '`Optimal solution takes `

', where `N` hop(s).`N` is the number of hops needed to get from start to finish point.

### Sample input

2 5 5 4 0 4 4 1 1 4 2 3 3 3 0 0 2 2 2 1 1 0 2 0 2 1 1

### Sample output

Optimal solution takes 7 hop(s). No solution.

### Illustration of sample input

The example input can be illustrated as follows. Let `#`

denote an occupied square, `S`

denote the start point, `F`

denote the finish point, and `*`

denote the boundary of the grid. Then the sample input can also be given as follows.

2 5 5 ******* * F* * ####* * ####* * * * S* ******* 3 3 ***** * #F* *###* *S# * *****

All Submissions

Best Solutions

**Point Value:** 15

**Time Limit:** 2.00s

**Memory Limit:** 16M

**Added:** Jun 26, 2013

**Languages Allowed:**

C++03, PAS, C, HASK, ASM, RUBY, PYTH2, JAVA, PHP, SCM, CAML, PERL, C#, C++11, PYTH3

## Comments (Search)

jeffreyxiaoon Sep 04, 2014 - 3:09:39 am UTC Sample inputAlexon Sep 04, 2014 - 4:02:41 am UTC Re: Sample inputEdit: Whoops, I made the same mistake as Jeffrey, so unfixed.

awaykenedon Dec 26, 2014 - 5:47:51 pm UTC Re: Sample inputcorrect me if i'm wrong but,

the obstacle should cover (1,2) --> (4,3)

when currently in the diagram it covers (1,1) --> (4,2)

jeffreyxiaoon Dec 27, 2014 - 12:32:21 am UTC Re: Sample inputImbaCalvinon Sep 22, 2013 - 1:24:23 pm UTC Title error...Alexon Sep 22, 2013 - 5:11:21 pm UTC Re: Title error...