From d18b728cb306de19b9d60d6226d5d27843ecc585 Mon Sep 17 00:00:00 2001
From: Sadeep Madurange
A graph is a finite set of vertices, and a subset of vertex pairs known as -edges. Edges can have weights.
- -In the case of vessel tracking, the route points can be modeled as a graph -with the distances between them as weights. For different reasons, people are -interested in minimizing (or maximizing) the weight of a path through a set of -vertices. For instance, we may want to find the shortest path between two -ports.
+edges. Edges can have weights. In the case of vessel tracking, the route points +can be modeled as a graph with the distances between them as weights. For +different reasons, people are interested in minimizing (or maximizing) the +weight of a path through a set of vertices. For instance, we may want to find +the shortest path between two ports.Dijkstra’s algorithm is one such algorithm that finds the shortest path between two vertices. The one drawback of this algorithm is that it computes all the @@ -345,10 +343,8 @@ public class ShortestPathAStar extends Algorithm<ShortestPathAStar> {
The heuristic function is domain-specific. If chosen wisely, it can significantly speed up the search. In our case, we achieved a 300x speedup, -enabling us to expand our search from 4,000 to 13,000 route points.
- -The Neo4J graph algorithms open-source project v3.4 shipped -with my implementation of the A* search algorithm.
+enabling us to expand our search from 4,000 to 13,000 route points. The v3.4.0 of the +Neo4J graph algorithms shipped with the A* search algorithm. -- cgit v1.2.3