- 01 Jan, 2015 1 commit
-
-
Tiago Peixoto authored
-
- 28 Jul, 2014 1 commit
-
-
Tiago Peixoto authored
-
- 09 Jun, 2014 1 commit
-
-
Tiago Peixoto authored
This also implements direct manipulation of OpenMP settings (schedule and number of threads) via python.
-
- 02 Jan, 2014 1 commit
-
-
Tiago Peixoto authored
-
- 10 Nov, 2013 1 commit
-
-
Tiago Peixoto authored
-
- 18 Oct, 2013 1 commit
-
-
Tiago Peixoto authored
The filtered array returned now also reflects the vertex filtering, so that it corresponds only to actually visible edges in the graph, not only those explicitly selected via an edge filter.
-
- 20 Mar, 2013 1 commit
-
-
Tiago Peixoto authored
This fixes ticket #131, and includes a 'fast' O(k) option, which changes the vertex index ordering.
-
- 11 Feb, 2013 1 commit
-
-
Tiago Peixoto authored
Dumping boost::adjacency_list<> improves memory usage by a factor of two, and also slightly improves performance in some cases.
-
- 10 Jan, 2013 1 commit
-
-
Tiago Peixoto authored
This enables the inclusion of the non-boost tr1 headers if a recent enough version of libstdc++ is detected. This als fixes a bug with clang when sparsehash pulls unwanted tr1 headers.
-
- 06 Jan, 2013 1 commit
-
-
Tiago Peixoto authored
-
- 21 Nov, 2012 1 commit
-
-
Tiago Peixoto authored
-
- 27 Oct, 2012 1 commit
-
-
Tiago Peixoto authored
-
- 02 May, 2012 1 commit
-
-
Tiago Peixoto authored
-
- 11 Apr, 2012 5 commits
-
-
Tiago Peixoto authored
This avoids copying property values when not necessary, if the index remains the same after purging
-
Tiago Peixoto authored
-
Tiago Peixoto authored
-
Tiago Peixoto authored
After the removal of filtered vertices via Graph.purge_vertices(), the values of known property maps are now kept consistent with the unmodified graph.
-
Tiago Peixoto authored
-
- 10 Feb, 2011 1 commit
-
-
Tiago Peixoto authored
-
- 02 Feb, 2011 1 commit
-
-
Tiago Peixoto authored
This implements a GraphView class which allows for convenient, independent filtering graphs.
-
- 13 Nov, 2010 1 commit
-
-
Tiago Peixoto authored
-
- 07 Mar, 2010 1 commit
-
-
Tiago Peixoto authored
-
- 03 Sep, 2009 1 commit
-
-
Tiago Peixoto authored
These functions group several scalar properties into one vector properties, and ungroup a vector property into several scalar properties.
-
- 21 Aug, 2009 1 commit
-
-
Tiago Peixoto authored
This is a large commit which replaces lambda::bind with boost::bind in most parts of the code. This improves compilation time, and slightly decreases compilation memory usage in some cases.
-
- 17 Jun, 2008 1 commit
-
-
Tiago Peixoto authored
This commit removes the internal property maps from the GraphInterface class, and makes all property maps external by default. The internal property maps were moved to the python layer.
-
- 10 Apr, 2008 1 commit
-
-
Tiago Peixoto authored
The whole histogram code has been redone, and the code has been simplified. The three-point vertex-edge-vertex correlation has been scrapped, since it's not frequently used, and would make compilation even more expensive. This also adds some missing files to the generation routine.
-
- 27 Mar, 2008 1 commit
-
-
Tiago Peixoto authored
Now graphml files properly contain all the supported value types, which are all perfectly preserved when read (floating point data is now saved in hexadecimal format). Several other improvements were made, such as the ability to read and write to python file-like objects. It is also now possible to have arbitrary python object properties, and store them persistently (which is done internally with the pickling interface). vector<bool> was totally abolished, since its implementation is quite broken. See: http://www.gotw.ca/publications/N1211.pdf and http://www.gotw.ca/publications/N1185.pdf Now a uint8_t (aka. char) is used in graph properties instead of a bool. Graph types can now be fully pickled (this may not be feasible memory-wise if the graph is too large, since the whole XML representation is dumped to a string before it is saved on disc).
-
- 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
-
- 06 Dec, 2007 1 commit
-
-
Tiago Peixoto authored
The graph object passed to the edit function is now a instance of the Graph class which wraps GraphInterface, not a GraphInterface instance.
-
- 30 Nov, 2007 1 commit
-
-
Tiago Peixoto authored
Property maps can now be obtained as such: weight = g.edge_properties['weight'] print weight[v] # v is a Vertex object weight[v] = 2.0 # and so on... The list of properties is obtained from g.vertex_properties, g.edge_properties and g.graph_properties, which can be read as dictionaries. The last can be set also, as such: g.graph_properties = {foo:"bar", baz:42} Functions to add and remove vertices or adges were also added (add_{vertex|edge}, remove_{vertex|edgge}). Vertex and Edge types can also now be printed for convenience, as such: for v in g.vertices(): print v for e in g.edges(): print e which results, for example, in: 0 1 2 3 4 5 6 (0,1) (1,2) (2,6) (3,4) (4,5) (4,2) (5,6) (6,1) (this also adds the forgotten graph_tool.py file, which was previously on .gitignore)
-
- 26 Nov, 2007 1 commit
-
-
Tiago Peixoto authored
Vertices and edges can be accessed from the graph class, as such: import graph_tool g = graph_tool.Graph() for v in g.vertices(): for e in v.out_edges(): # do something... Additionally, the --edit-{vertex|edge|graph}-property was ported to the new interface, and is working again, as it used to. The Vertex and Edge class no longer have the 'get_property' and 'set_property' method. They'll be replaced by a new method of accessing property maps.
-
- 04 Nov, 2007 1 commit
-
-
Tiago Peixoto authored
Line breaks at column 80 were added, and all trailing whitespace was deleted. Code comments were modified and some more were added.
-
- 11 Oct, 2007 1 commit
-
-
Tiago Peixoto authored
-
- 04 Oct, 2007 1 commit
-
-
Tiago Peixoto authored
Simplify range filtering, and definitely remove python filtering Simplify range filtering of vertices and edges, by always filtering both at once, even if all vertices or edges are being considered. This severely reduces compilation time and memory, at a small potential cost in run-time speed, which will probably be overshadowed by other things, such as dynamic_map look-ups ("premature optimization is the root of all evil"). Also, remove python-filtering, since, in the end, it is just code bloat, since it is quite slow for most uses and can be replaced, generally, by python property editing + range filtering.
-
- 09 Aug, 2007 1 commit
-
-
Tiago Peixoto authored
* src/boost-workaround/boost/graph/kamada_kawai_spring_layout.hpp: annotated code with openmp constructs. * src/graph/graph_adaptor.hh: graph_type should be a typedef to the original graph. * src/graph/graph_properties.hh, src/graph/graph_properties.cc: added pos_t type. * src/boost-workaround/boost/graph/fruchterman_reingold.hpp: annotated code with openmp constructs. * src/graph/graph_layout.cc: new file with graph layout routines. * src/graph/graph.cc: removed graph layout routines. * src/graph/graph_community_network.cc (struct get_community_network): fixed inversion of directedness test. * src/graph/graph.cc (GraphInterface::LabelComponents): use vector_property_map instead of HashedDescriptor. Don't use a static map! * src/graph/graph_adaptor.hh: fixed edge descriptor equality comparison, which must rely on underlying edge, regardless of whether it's inverted or not. git-svn-id: https://svn.forked.de/graph-tool/trunk@121 d4600afd-f417-0410-95de-beed9576f240
-
- 01 Aug, 2007 1 commit
-
-
Tiago Peixoto authored
* src/graph/graph.cc (GraphInterface::LabelParallelEdges): use long instead of size_t for parallel edges property. * src/graph/graph_properties.cc: call size_t by "size_t" not "long", since those are not the same type. This removes a bug where it is impossible to create/edit properties with type long. * src/graph/graph.cc (GraphInterface::LabelParallelEdges): use vector_property_map instead of HashedDescriptorMap. git-svn-id: https://svn.forked.de/graph-tool/trunk@120 d4600afd-f417-0410-95de-beed9576f240
-
- 30 Jun, 2007 2 commits
-
-
Tiago Peixoto authored
* change from HashedDescriptorMap to vector_property_map in several algorithms to save memory and increase speed in the most common case, where the graph is unfiltered. git-svn-id: https://svn.forked.de/graph-tool/trunk@102 d4600afd-f417-0410-95de-beed9576f240
-
Tiago Peixoto authored
git-svn-id: https://svn.forked.de/graph-tool/trunk@101 d4600afd-f417-0410-95de-beed9576f240
-