Path finding library
This library will contain standard path finding algorithms and return the resulting graph object. You can search for paths in a graph based or grid based structure.
Table of contents generated with markdown-toc
Currently supported:
- Construct graphs
- Graph operations
- Create grids
- Grid operations
- Create Minimum Spanning Tree (MST) from a graph
- Find path with Depth-First Search (DFS)
- With Breadth-First Search (BFS)
- With Bidirectional Breadth-First Search (BBFS)
- With the Dijkstra algorithm
- With the A* algorithm, with heuristic:
- Euclidean distance
- Manhattan distance
- TBC: with a Hierarchical Path-Finding A* (HPA*), with heuristic:
- Euclidean distance
- Manhattan distance
Download the crate: https://crates.io/crates/path-finding
How to use
At the moment, we have following major concepts:
- Edge
- Node
- Graph
- Position
- Grid
You only need to pass edges to the graph. The nodes are generated automatically. Each pathfinding method will accept a graph, and return a graph that only contains the edges and nodes of the result.
Alternatively, you can also create a graph if you provide an adjacency matrix. Edges and nodes will be generated automatically.
If you want to use the A* path-finding algorithm, please make sure to provide positional information for each node.
Additionally, we work on a support for each of those algorithms based on a 2D grid based structure.
Create Graph
- Create Edge
- Create Graph from edges
- Create Graph from adjacency matrix
Graph operations
You may want to get some information or mutate the graph in some way. Therefore, the graph currently supports three functions for convenience operations or to provide data for a heuristic function.
sorted_by_weight_asc
offer_positions
Create Grid
- Create Grid from cost matrix
In some cases, such as 2D games, a grid based structure is advantageous. The grid can be created by passing a cost
matrix to the construction function ::from
. At each entry of the matrix you provide an unsigned integer, indicating
the effort it takes
to move to this position from any neighbouring position. In the example below moving from position (0, 0)
to position
(0, 1)
will require an effort, or require a cost, of 2. Equivalently, moving from (2, 2)
to (1, 1)
will incur a
cost of 1. Based on this information, we want to provide a support for grid based structures in each path finding
algorithm.
Grid operations
outside
Check if a position is outside the grid. Pass a coordinate to the function below.
within
Check if a position is within the grid. Pass a coordinate to the function below.
node_id
Convert your coordinate to a node_id
cost
Retrieve the cost required to move to a provided node id
Minimum spanning tree
Depth-first search
For graphs
For grids
Breadth-first search
For graphs
For grids
Bidirectional breadth-first search
For graphs
For grids
Dijkstra path search
For graphs
For grids
A* path search
You can use the A* path-finding algorithm by providing either an existing heuristic function as shown below. Or you provide your own heuristic function. In case you use an existing heuristic function, make sure to provide the positional information for the nodes.
TBC: Hierarchical A* path search
Similar to the A* path-finding algorithm, you can provide either an existing heuristic function as shown in the previous section. Or you provide your own heuristic function. In case you use an existing heuristic function, make sure to provide the positional information for the nodes.
In addition to the functionality of A*, this algorithm will require you to pass the graph to the Hierarchical A* instance. The reason is simple, the algorithm will divide the graph into segments on creation and cache information required in the subsequent path-finding process.