- 07 Aug, 2009 1 commit
-
-
Tiago Peixoto authored
When using undirected graphs, the implicit direction of each edge was not properly handled, and the correlated case would not work. Now, in this case, the direction is always checked, and the edge is inverted if necessary.
-
- 04 Aug, 2009 1 commit
-
-
Tiago Peixoto authored
-
- 02 Jun, 2009 2 commits
-
-
Ale Abdo authored
-
Tiago Peixoto authored
-
- 23 May, 2009 1 commit
-
-
Tiago Peixoto authored
The generators from boost::random seem to have a bug which causes them to be biased. The generators from tr1::random seem to be in better shape. See: http://thread.gmane.org/gmane.comp.lib.boost.user/48006
-
- 10 Mar, 2009 2 commits
-
-
Tiago Peixoto authored
This finally fixes in the bug addressed by commit 309ddbbd, where parallel edges could be erroneously created. In fact, the bug was more serious: The source and target edge lists always pointed to the same list (in the uncorrelated case, but could occasionally happen for the correlated case also) which got shuffled during iteration. Since the shuffling of one list interfered with the shuffling of the other, some combinations of source and target edges could simply never be considered... This commit forces both lists to always be independent.
-
Tiago Peixoto authored
Thins changes the graph filtering code slightly to wrap graph types with GraphWrap, which automatically updates the edge index list when edges are removed and added to the graph. This also changes how graphs are passed to algorithms, which is now by reference instead of pointer. (hence this touches lots of code, but changes are trivial)
-
- 10 Feb, 2009 1 commit
-
-
Tiago Peixoto authored
In some circumstances, the test for parallel edges would fail to detect one, if it involved another "new" edge and one of the current ones being rewired. This commit also removes the requirement that edge indexes be continuous in the range [0, num_edges(g)), which is not in general the case.
-
- 06 Feb, 2009 1 commit
-
-
Tiago Peixoto authored
This includes a new vector property map type (fast_vector_property_map) which has optional disabling of bounds checking, through its associate map type (unchecked_fast_vector_property_map). This should improve performance on algorithms which depend on tight loops which access property maps. Bounds checking is only disabled locally just before the algorithms run, and proper care is taken for bounds checking _beforehand_. The property maps exposed to python still have internal bounds checking.
-
- 23 Oct, 2008 2 commits
-
-
Tiago Peixoto authored
Unnecessary dynamic polymorphism is replaced by static polymorphism, in the definitions of the rewiring strategies.
-
Tiago Peixoto authored
This also creates the misc sub-module. This may be re-organized in the future.
-
- 21 Oct, 2008 1 commit
-
-
Tiago Peixoto authored
Restructure the rewiring code, introducing further abstraction through class inheritance. Both uncorrelated and correlated cases draw edges directly. This has actually proven faster than drawing vertices for the correlated case, since realizing that indexes could be stored instead of edges. Doing so avoids changes in the pool of candidate edges, which in turn removes the need to rebuild it for each edge to rewire. Consequently, it also makes the uncorrelated case a lot quicker. In the uncorrelated undirected case, the new code also fixes a serious bug: when building the edge pool, only one end of each edge was looked at, because the "edges" vector is not equivalent to drawing all out_edges from all vertices, as is done now.
-
- 17 Feb, 2008 1 commit
-
-
Tiago Peixoto authored
This commit splits libraph_tool into different libraries: - libgraph_tool_core - libgraph_tool_clustering (*) - libgraph_tool_community (*) - libgraph_tool_correlations (*) - libgraph_tool_distance (*) - libgraph_tool_generation (*) - libgraph_tool_layout (*) - libgraph_tool_misc (*) - libgraph_tool_stats (*) It also adds the python sub-module 'test', which provides extensive unit testing of the core functionality. The core library is fully functional and all test pass successfully. (*) -> module needs to be ported to new refactoring, and does not yet build
-
- 10 Feb, 2008 1 commit
-
-
Tiago Peixoto authored
This is a huge commit which completely refactors the metaprogramming engine which generates and selects (at run time) the graph view type and the desired algorithm implementation (template instantiation) that runs on it. Things are laid out now as following. There exists a main underlying graph type (GraphInterface::multigraph_t) and several other template classes that mask it some way or another, in a hierarchic fashion: multigraph_t -> filtered_graph (edges only, vertices only, both) | | | | | | | | |-------(reversed_graph)--------|-----------|-----------| | | | | \------(UndirectedAdaptor)------------------------------/ The filtered_graph filters out edges and/or vertices from the graph based on some scalar boolean property. The reversed_graph reversed the direction of the edges and, finally, the UndirectedAdaptor treats the original directed graphs as undirected, transversing the in- and out-edges of each vertex indifferently. Thus, the total number of graph view types is 12. (The option --disable-graph-filtering can be passed to the configure script, which will disable graph filtering altogether and bring the total number down to 3, to reduce compile time and memory usage) In general, some specific algorithm, implemented as a template function object, needs to be instantiated for each of those types. Furthermore, the algorithm may also depend on other types, such as specific property_maps. Thus, the following scheme is used: struct my_algorithm // algorithm to be implemented { template <class Graph, class PropertyMap> void operator()(Graph *g, PropertyMap p, double& result) const { // ... } }; // in order for the above code to be instantiated at compile time // and selected at run time, the run_action template function object // is used from a member function of the GraphInterface class: double GraphInterface::MyAlgorithm(string prop_name) { double result; boost::any vprop = prop(property, _vertex_index, _properties); run_action<>()(*this, bind<void>(my_algorithm(), _1, _2, var(result)), vertex_scalar_properties())(vprop); return result; } The whole code was changed to reflect this scheme, but now things are more centralized and less ad-hoc code needed to be written. Unfortunately, due to GCC's high memory usage during template instantiations, some of the code (namely all the degree correlation things) had to be split in multiple compilation units... Maybe this will change in the future if GCC gets optimized. This commit also touches other parts of code. More specifically, the way filtering gets done is very different. Now we only filter on boolean properties, and with the above scheme, the desired implementation runs with the correct chosen type, and no implicit type conversions should ever happen, which would have a bad impact on performance.
-
- 13 Dec, 2007 1 commit
-
-
Tiago Peixoto authored
-
- 03 Dec, 2007 3 commits
-
-
Tiago Peixoto authored
Move remaining parallelism check out of the outer/inner loops and into the parallel_check() function.
-
Ale Abdo authored
3) missing parallel edge check in uncorrelated strategy 2) "_in()" for target and source of "target swap edge" 1) order of arguments of swap_edge_triad::parallel_check melodrama time... "premature optimization is the root of all evil" "careless abstraction are the fruits of its tree"
-
Tiago Peixoto authored
The check for parallel edges was cleaned up and abstracted into a function, and other minor things were changed. Code comments were added to places where it might have been hard to understand.
-
- 28 Nov, 2007 1 commit
-
-
Ale Abdo authored
Major changes to both correlated and uncorrelated rewiring code. Both cases are now functional and use iterative shuffling. Uncorrelated picks edges to rewire directly, correlated picks vertices in order to choose edges.
-
- 05 Nov, 2007 1 commit
-
-
Ale Abdo authored
Several changes in the random rewiring code, making it fully functional for the correlated case. The reshuffling operations lag in efficiency, even though already the algorithm runs in little time.
-
- 23 Oct, 2007 1 commit
-
- 07 Oct, 2007 1 commit
-
-
Tiago Peixoto authored
Remove graph rewiring for now, since it's quite buggy. It will be re-commited when ready.
-
- 12 Sep, 2007 1 commit
-
-
Tiago Peixoto authored
-
- 30 Jul, 2007 1 commit
-
-
Tiago Peixoto authored
* src/Makefile.am: removed 'boost_workaround' dist files * src/graph/graph_rewiring.cc: deleted blank lines. git-svn-id: https://svn.forked.de/graph-tool/trunk@116 d4600afd-f417-0410-95de-beed9576f240
-
- 11 Jul, 2007 1 commit
-
-
Tiago Peixoto authored
* ChangeLog: updated ChangeLog file with svn history * src/graph/graph_filtering.hh: added add_edge() and remove_edge() functions for filtered graphs * src/graph/shared_map.hh: included SharedContainer * src/graph/graph_rewiring.cc: initial support for random graph rewiring git-svn-id: https://svn.forked.de/graph-tool/trunk@114 d4600afd-f417-0410-95de-beed9576f240
-