It is generally said that A* is the best algorithm to solve pathfinding problems.
Is there any situation when A* is not the best algorithm to find solution?
How good is A* compared to BFS, DFS, UCS, etc?
It is generally said that A* is the best algorithm to solve pathfinding problems.
Is there any situation when A* is not the best algorithm to find solution?
How good is A* compared to BFS, DFS, UCS, etc?
The short answer is yes, there are situations in which A* is not the best algorithm to solve a problem. However, there are a number of ways to assess what constitutes the best algorithm for finding a solution.
If you are considering best in terms of performance of multiple searches from a single source to many destinations, then you should consider using a more suitable approach (Dijkstra's algorithm).
If you are considering best in terms of performance, then in some special cases DFS and BFS will significantly outperform A*. From past experience, this occurs for very small, almost trivial graphs, but would require careful testing and profiling to make a stronger statement.
If you are considering best in terms of path-length, that is how long the final path produced by the algorithm is, then A* is equivalent to any other optimal search algorithm.
If you are considering best in terms of completeness, that is, will the algorithm always find a path to the goal if such a path exists. If so, then A* is equivalent to any other complete algorithm (for example, breadth-first-search).
If you are considering best in cases where some of the weights in the graph are negative, then you will need to use a special algorithm to solve those problems (for example bellman-ford)
If you are considering best in cases where the no heuristic is available then you must fall back on h(x,y)=0 forall states x and y
. In this case A* is equivalent to best first search.
If you are considering best in cases related to motion planning in continuous configuration spaces, then A* may work adequately in low dimensions, but storage of the search graph starts to become impractical at high dimensions, and the need to use probabilistically complete algorithms increases (for example RRT, Bi-RRT, RDT)
If you are considering best in cases where the graph is partially observable, you only know a subset of all the possible vertices and edges within the graph at any time, and you need to change state to observe more of the graph, then you need an alternative algorithm designed for this (for example, Keonig's Lifelong Planning A*, LPA*, does exactly this).
If you are considering best in cases where the graph changes over time, which occurs frequently in robotics when you incorporate moving obstacles, then you need an algorithm which is designed for this (for example Stentz's D* or Koenig & Likhachev's D*-Lite).
A* is special because can be morphed into other path-finding algorithms by playing with how it evaluates nodes and the heuristics it uses. You can do this to simulate Djikstra's, best-first-search, breadth-first-search, and depth-first-search.
Furthermore, it's often easy to speed it up. For instance, if you multiply an admissible heuristic by a constant, c, you can guarantee that the cost of the resulting sequence of nodes is no more than c times the optimal result.
For instance, take this awesome paper by Ian Davis (written for Star Trek Armada). A* is used with a hierarchical set of waypoints, which results in a rough path. THEN, in order to smooth the path, they run A* again on a new, generated graph containing the nodes on the path and those nearby to get a more reasonable path. Finally, they run rubber-banding to remove redundant nodes.
So, A* isn't the solution to everything, but it's a very versatile tool.
An extremely simple alternative (no wrangling with heuristics) is Collaborative Diffusion. It works superbly when you need to target one target or any member of a group, indiscriminately, and in this case can be faster than A*. It mimics the game "You're Getting Warmer/Colder".
Collaborative diffusion creates one heatmap per "group" you wish to target... if you want to track a specific target, treat it as it's own group by creating a heatmap just for that target; Collaborative Diffusion's domain is games like football (where both teams of agents track the ball and goalposts specifically, leading to just 3 influence maps) or Pacman (similar, multiple agents tracking Pac) or army games where there is one combined heatmap representing the body (aggregate) of each army as determined from each agent in that army, so that one army can approach "the other army" rather than "specific units within the other army". This generality may afford increased performance.
Walking consists of hill-climbing (going from the current cell to a warmer neighbour cell) until we reach the destination (hottest point). The approach implicitly deals with moving obstacles i.e. other agents.
It is best suited where maps are fairly densely populated with many, moving units, thus justifying the extensive diffusion which must occur across the entire search space on each update. It is clear how a well-tuned A* approach can be an order of magnitude cheaper in a large, sparse map where we have just one unit targeting just one other unit, because with A* in this case you are only working on a fraction of map tiles between the seeker and the target; whereas with Collaborative Diffusion, you are instead diffusing across the entire map just to do the same thing, making it far more costly.
I see question is old but probably this practical solution will be useful for someone. Recently I found very nice open source code written in python
code contains next pathfinding algorithms:
changing the matrix size and values allows to feel difference between different path finding algorithms. As it is mentioned on Wikipedia: "A* is complete and will always find a solution if one exists"