如何针对两个节点之间的单个最短路径优化 Dijkstra 算法?
我试图理解Dijkstra算法的这个实现在C中同时修改它,以便只找到2个特定节点(源和目的地)之间的最短路径。
但是,我不知道到底要做什么。在我看来,没有什么可做的,我似乎无法更改 d[]
或 prev[]
因为这些数组在最短的时间内聚合了一些重要数据路径计算。
我唯一能想到的是在找到路径时停止算法,也就是说,当 mini = destination
被标记为已访问时,打破循环。
我还能做些什么来让它变得更好吗?或者这样就足够了吗?
编辑:
虽然我很欣赏给我的建议,但人们仍然无法准确回答我的问题。我想知道的是如何优化算法以仅搜索2个节点之间的最短路径。目前我对所有其他一般优化不感兴趣。我的意思是,在查找从节点 X 到所有其他节点的所有最短路径的算法中,如何优化它以仅搜索特定路径?
PS:我刚刚注意到for
循环从1
开始直到<=
,为什么不能从0<开始/code> 直到
<
?
I was trying to understand this implementation in C of the Dijkstra algorithm and at the same time modify it so that only the shortest path between 2 specific nodes (source and destination) is found.
However, I don't know exactly what do to. The way I see it, there's nothing much to do, I can't seem to change d[]
or prev[]
cause those arrays aggregate some important data for the shortest path calculation.
The only thing I can think of is stopping the algorithm when the path is found, that is, break the cycle when mini = destination
when it's being marked as visited.
Is there anything else I could do to make it better or is that enough?
EDIT:
While I appreciate the suggestions given to me, people still fail to answer exactly what I questioned. All I want to know is how to optimize the algorithm to only search the shortest path between 2 nodes. I'm not interested, for now, in all other general optimizations. What I'm saying is, in an algorithm that finds all shortest paths from a node X to all other nodes, how do I optimize it to only search for a specific path?
P.S: I just noticed that the for
loops start at 1
until <=
, why can't it start at 0
and go until <
?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
您问题中的实现使用相邻矩阵,这导致 O(n^2) 实现。考虑到现实世界中的图通常是稀疏的,即节点数n通常很大,但边的数量却远远少于n^2。
您最好查看基于堆的 dijkstra 实现。
顺便说一句,单对最短路径的求解速度不能比特定节点的最短路径更快。
The implementation in your question uses a adjacent matrix, which leads O(n^2) implementation. Considering that the graphs in the real world are usually sparse, i.e. the number of nodes n is usually very big, however, the number of edges is far less from n^2.
You'd better look at a heap-based dijkstra implementation.
BTW, single pair shortest path cannot be solved faster than shortest path from a specific node.
您也许可以通过维护一个单独的打开和关闭列表(已访问和未访问)来有所改进,它可能会稍微缩短查找时间。
当前,您搜索与源距离最小的未访问节点。
1)您可以维护一个单独的“开放”列表,随着您的迭代,该列表会变得越来越小,从而使您的搜索空间逐渐变小。
2)如果您维护一个“封闭”列表(您访问过的那些节点),您可以仅检查这些节点的距离。这将逐渐增加您的搜索空间,但您不必每次迭代都检查所有节点。对尚未访问过的节点进行距离检查没有任何意义。
另外:在选择要评估的下一个节点时,也许可以考虑遵循图表:在“闭合”列表上,您可以寻找最小距离,然后在其连接中搜索“开放”节点。 (如果该节点的连接中没有开放节点,您可以将其从关闭列表中删除;死胡同)。
您甚至可以使用此连接来形成打开列表,这也有助于处理岛屿(如果您的图形有岛屿,您的代码当前将崩溃)。
您还可以预先构建一个更有效的连接图,而不是包含所有可能的节点组合的交叉表(例如,带有 neighbours[] 节点列表的 Node 结构)。这将消除检查 dist[][] 数组中每个节点的所有节点的麻烦,
而不是将所有节点距离初始化为无穷大,您可以将它们初始化为到目标的“最小可能乐观距离”,并基于该距离有利于节点处理(这里你的可能性有所不同,如果节点位于 2D 平面上,你可以使用鸟类距离)。有关启发式,请参阅 A* 描述。我曾经围绕队列实现过这个,但不完全确定如何将它集成到这段代码中(没有队列)。
You could perhaps improve somewhat by maintaining a separate open and closed list (visited and unvisited) it may improve seek times a little.
Currently you search for an unvisited node with the smallest distance to source.
1) You could maintain a separate 'open' list that will get smaller and smaller as you iterate and thus making your search space progressively smaller.
2) If you maintain a 'closed' list (those nodes you visited) you can check the distance against only those nodes. This will progressively increasing your search space but you don't have to check all nodes each iteration. The distance check against nodes that have not been visited yet holds no purpose.
Also: perhaps consider following the graph when picking the next node to evaluate: On the 'closed' list you could seek the smallest distance and then search an 'open' node among it's connections. (if the node turns out to have no open nodes in it's connections you can remove it from the closed list; dead end).
You can even use this connectivity to form your open list, this would help with islands also (your code will currently crash if you graph has islands).
You could also pre-build a more efficient connection graph instead of a cross table containing all possible node combinations (eg. a Node struct with a neighbours[] node list). This would remove having to check all nodes for each node in the dist[][] array
Instead of initializing all node distances to infinity you could initialize them to the 'smallest possible optimistic distance' to the target and favor node processing based on that (your possibilities differ here, if the nodes are on a 2D plane you could use bird-distance). See A* descriptions for the heuristic. I once implemented this around a queue, not entirely sure how I would integrate it in this code (without a queue that is).
您可以对 Dijkstra 进行的最大改进是使用 A* 代替。当然,这需要你有启发式功能。
The biggest improvement you can make over Dijkstra is using A* instead. Of course, this requires that you have a heuristic function.