[Note] This is a group project. Students may work in groups of 3 ~ 4 people. After completion, Every group member submits their solutions on Autograder individually.
In this project you will implement a Java program that places wires on a computer chip.
For purposes of this project, a computer chip will be abstractly represented as a grid of vertices, where each vertex is connected to the four neighboring vertices (in the directions north, south, east, and west). To complicate matters, parts of the chip are already allocated for other uses and may not be used for running wires. These already-in-use parts are called obstacles. Each obstacle is a rectangular region of the grid. You will be given a list of pairs of coordinates and your task is to connect each pair with a wire. A coordinate is a pair of integers, with the first being the row number, and the second being the column number. A wire is a list of grid points. Wires may not cross one another. In addition to connecting all the pairs, your goal is to minimize the aggregate lengths of all the wires and to minimize the execution time of your program.
The format of the input file is described as follows. The first line is the height (number of rows) of the grid, given as an integer. The second line is the width (number of columns) of the grid, also given as an integer. The third line is the number of obstacles $o$. The next $o$ lines are the obstacles. Each line has four integers, separated by spaces. The first two integers give the upper left coordinate of the obstacle and the second two integers give the lower right coordinate of the obstacle. After the obstacles, there is a line that gives the number of pairs that need to be connected. The remaining lines in the file are pairs of space-separated coordinates, where each coordinate is a pair of space-separated integers.
We have given you the code that reads the input file and creates the grid with obstacles laid out and the source and destination points specified. The obstacles are marked with grid cells with value -1. The start and end points of a wire/path are marked with a number assigned to that path. All the other cells contain the value 0.
Your function findPaths in the Routing class should use this grid
to connect a source and a destination with a path, avoiding points
that lie on an obstacle. You should mark the grid once a path has been
found for a pair of points, thus preventing overlapping of paths. That
is, mark all the points in a path with the same number as the start
and end point. The autograder checks these conditions to verify the
correctness of your solution.
Note that a path can have the same source and destination points.
.
├── src
│ ├── Board.java
│ ├── Coord.java
│ ├── Endpoints.java
│ ├── Routing.java // your code
│ └── Wire.java
├── test
│ ├── StudentTest.java // your tests
│ ├── Utilities.java
│ └── inputs // your test input files
│ └── wire0.in
└── wire-routing.iml
Routing.java and write-up file README.md to
link.We need you to implement the findPaths method. It takes the board
and the points to be connected (goals) as arguments and returns a list of
paths. The board represents the entire chip. Each path represents the
wire used to connect components represented by points. Each path
connects a pair of points in the points array; avoiding obstacles and
other paths while minimizing the total path length required to connect
all points. If two points cannot be connected, then the path should be
null. The findPaths method should update the board by marking the
grid. However, it must not mutate the goals array list.
Think of a simple way to minimize the path length. You can use the grid to mark the points that lie on a path. You might want to use auxiliary data structures to keep track of the intermediate points that lie on the path.
We recommend that you start by implementing an algorithm that uses breadth-first search (BFS), which will solve most of the tests of the autograder, but not all. Once that is complete, you can experiment with improvements to BFS or alternative algorithms.
For this assignment we are asking you to describe your solution in
the README.md file. A significant part of your grade
is based on how good your description is.
Things you should include in the description are:
In this README.md file, justify why your improvements are worth the
final points! Solving all the tests is one good justification,
but you may use other justifications.