如何复制 boost::property_map?
Posted
技术标签:
【中文标题】如何复制 boost::property_map?【英文标题】:How to copy boost::property_map? 【发布时间】:2016-01-12 23:11:01 【问题描述】:我想从 one 图获得 两组 最短路径(一对多),定义为 adjacency_list
并具有内部属性(相反捆绑)
理论上我可以在两个参考节点n1
和n2
上运行dijkstra_shortest_paths
。如果我创建两个property_maps
并将它们按顺序传递给dijkstra_...
,我会得到同一张地图的两个视图。两者都指向上次运行 dijkstra_shortest_paths
的结果,因此旧的结果消失了。我应该怎么做才能达到预期的效果?
// Define some property maps
property_map<ugraph_t,edge_weight_t>::type Weight=get(edge_weight,G);
property_map<ugraph_t,vertex_distance_t>::type Dist1=get(vertex_distance,G);
// One line later, I expect this to be mapped to the SPs w.r.t n1
// Run SP on the first node
dijkstra_shortest_paths(G,n1,predecessor_map(Prev1).distance_map(Dist1).weight_map(Weight));
// New property maps
property_map<ugraph_t,vertex_distance_t>::type Dist2(Dist1); // And now to the second set
property_map<ugraph_t,vertex_predecessor_t>::type Prev2(Prev1); // But no two sets will result...
// Run SP on the second node
// This will run fine, but I will lose the first SP set (with or without a copy constructor above)
dijkstra_shortest_paths(G,n2,predecessor_map(Prev2).distance_map(Dist2).weight_map(Weight));
结论:如果我没记错的话,property_map
可以被认为是带有迭代器的接口,因此复制 property_map
s 没有任何意义。解决方案是传递一个动态构建的自定义容器。该解决方案在下面@sehe 的答案中有详细说明,我非常感谢!
注意:这仅适用于顶点容器类型为vecS
。使用listS
,必须“手动”逐个顶点复制。
【问题讨论】:
【参考方案1】:距离图不应该是内部属性。 前任地图也是如此。
它们不是图表的逻辑属性。它们是查询的结果。因此,它们是查询参数组合的属性,包括图形、起始节点等。
如果您想保存内部属性的值,只需以您通常会使用的任何方式保存它:
std::vector<double> saved_distances(num_vertices(G));
BGL_FORALL_VERTICES(v, G, ugraph_t)
saved_distances.push_back(Dist1[v]);
解决方法
复制地图的解决方法:
Live On Coliru
#include <boost/graph/adjacency_list.hpp>
#include <boost/graph/properties.hpp>
#include <boost/graph/dijkstra_shortest_paths.hpp>
#include <boost/graph/iteration_macros.hpp>
using namespace boost;
using ugraph_traits = graph_traits<adjacency_list<vecS, vecS, directedS> >;
using ugraph_t = adjacency_list<
vecS, vecS, directedS,
property<vertex_distance_t, double,
property<vertex_predecessor_t, ugraph_traits::vertex_descriptor>
>,
property<edge_weight_t, double>
>;
int main()
ugraph_t G(10);
ugraph_t::vertex_descriptor n1 = 0, n2 = 1, v;
(void) n1;
(void) n2;
// ...
property_map<ugraph_t, edge_weight_t>::type Weight = get(edge_weight,G);
property_map<ugraph_t, vertex_distance_t>::type Dist1 = get(vertex_distance,G);
property_map<ugraph_t, vertex_predecessor_t>::type Prev1 = get(vertex_predecessor,G);
dijkstra_shortest_paths(G, n1,
predecessor_map(Prev1)
.distance_map(Dist1)
.weight_map(Weight)
);
std::vector<double> saved_distances(num_vertices(G));
std::vector<ugraph_t::vertex_descriptor> saved_predecessors(num_vertices(G));
BGL_FORALL_VERTICES(v, G, ugraph_t)
saved_distances.push_back(Dist1[v]);
saved_predecessors.push_back(Prev1[v]);
/*
* // C++11 style
* for(auto v : make_iterator_range(vertices(G)))
* saved_distances[v] = Dist1[v];
*/
// Run SP on the second node
dijkstra_shortest_paths(G,n2,predecessor_map(Prev1).distance_map(Dist1).weight_map(Weight));
建议
我建议将结果映射制作成单独的容器,只留下边缘权重内部:
Live On Coliru
Better Yet:重构以删除重复代码
这样就变成了
Live On Coliru
#include <boost/graph/adjacency_list.hpp>
#include <boost/graph/dijkstra_shortest_paths.hpp>
using namespace boost;
using ugraph_t = adjacency_list<vecS, vecS, directedS, no_property, property<edge_weight_t, double> >;
using Vertex = ugraph_t::vertex_descriptor;
struct ShortestPaths
ShortestPaths(size_t num_vertices);
std::vector<double> distances;
std::vector<Vertex> predecessors;
;
ShortestPaths GetShortestPaths(ugraph_t const& G, Vertex start);
int main()
ugraph_t G(10);
Vertex n1 = 0, n2 = 1;
ShortestPaths sp1 = GetShortestPaths(G, n1);
ShortestPaths sp2 = GetShortestPaths(G, n2);
// some other cpp file...:
ShortestPaths::ShortestPaths(size_t num_vertices)
: distances(num_vertices), predecessors(num_vertices)
ShortestPaths GetShortestPaths(ugraph_t const& G, Vertex start)
ShortestPaths result(num_vertices(G));
dijkstra_shortest_paths(G, start,
predecessor_map(make_container_vertex_map(result.predecessors, G))
.distance_map (make_container_vertex_map(result.distances, G))
.weight_map (get(edge_weight, G))
);
return result;
请注意,不再需要复制结果。事实上,您甚至不需要保留图表来保留查询结果。
【讨论】:
用listS
替换vecS
打破了你的榜样。你能解决这个问题吗?我原来的 typedef 使用列表:typedef adjacency_list <listS,listS,undirectedS, property<vertex_index_t, size_t, property<vertex_name_t, std::string, property<vertex_distance_t, float, property<vertex_predecessor_t, ugraph_vertex_descriptor> > > >, property<edge_weight_t, float> > ugraph_t;
当然会破坏它。您的问题与listS
无关。我总是强调展示完整的、独立的代码(即使你没有)。我选择了vecS
,因为它是唯一可能与所示代码一起工作的东西。在创建顶点属性映射以及调用算法函数时,您需要维护和使用显式 vertex_index_map
。
A little demo 以防万一以上是关于如何复制 boost::property_map?的主要内容,如果未能解决你的问题,请参考以下文章