- 02 May, 2012 1 commit
-
-
Tiago Peixoto authored
-
- 29 Apr, 2012 1 commit
-
-
Tiago Peixoto authored
-
- 21 Mar, 2012 1 commit
-
-
Tiago Peixoto authored
This works around a regression introduced in boost 1.48, relating to the edge descriptors of reversed graphs. See: https://svn.boost.org/trac/boost/ticket/6391
-
- 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.
-
- 04 Dec, 2010 1 commit
-
-
Tiago Peixoto authored
Now, whenever GraphWrap is being used, the property maps are always in "checked" mode.
-
- 13 Nov, 2010 1 commit
-
-
Tiago Peixoto authored
-
- 09 Aug, 2010 1 commit
-
-
Tiago Peixoto authored
This avoid a namespace clash when using run_action.inline().
-
- 07 Mar, 2010 1 commit
-
-
Tiago Peixoto authored
-
- 06 Sep, 2009 1 commit
-
-
Tiago Peixoto authored
-
- 25 Apr, 2009 1 commit
-
-
Tiago Peixoto authored
-
- 10 Mar, 2009 1 commit
-
-
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)
-
- 14 Feb, 2009 1 commit
-
-
Tiago Peixoto authored
This makes the naming more sensible.
-
- 10 Feb, 2009 1 commit
-
-
Tiago Peixoto authored
It now does not implies automatically "always_directed".
-
- 06 Feb, 2009 2 commits
-
-
Tiago Peixoto authored
Now all symbols are exported by default, except those strictly marked as hidden.
-
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.
-
- 21 Jul, 2008 1 commit
-
-
Tiago Peixoto authored
Also, get rid of g.underlying_graph(), and rely on "private" variable g._Graph__graph instead.
-
- 14 Apr, 2008 1 commit
-
-
Tiago Peixoto authored
GCC 4.3 complains when a typedef overrides the meaning of another type.
-
- 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
-
- 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.
-
- 07 Oct, 2007 1 commit
-
-
Tiago Peixoto authored
Complete overhaul of command line parsing, and support for loading graph-tool as whole as a python module The command line parsing was completely rewritten. It now supports better parsing of sub-options, with type checking and grouping support. Error reporting was also significantly improved, and it now warns of invalid options and option values, before the option is executed. Some syntax has changed, such as range filtering: --[vertex|edge]-range-filter was replaced by --exclude-[vertex|edge]-range and --keep-[vertex|edge]-range, which should have a clearer meaning. Ranges can also be specified now by comparison operators (>,<,>=,<=,=), such as ">=10", to indicate a range of (10, inf). In addition, ranges can now be easily open or closed at either end, by suffixing the specific end with '*', to indicate it is closed, ex: "10 700*" means (10,700]. The graph-tool script can now be loaded as a python module (it must be renamed first to 'something.py'). All the command line options (except 'for' and 'history' which become irrelevant) are available as functions, with full description and optional parameter support. In addition, pure function objects can be given as parameters where expressions are asked, instead of strings and files, which enables convenient extension of graph-tool.
-
- 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.
-
- 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
-
- 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
-
- 18 May, 2007 1 commit
-
-
Tiago Peixoto authored
* src/graph/graph_clustering.cc * src/graph/graph_distance.cc * src/graph/graph_extended_clustering.cc * src/graph/graph_distance_sampled.cc * fixed "jacknife" variance bug in src/graph/graph_clustering.cc git-svn-id: https://svn.forked.de/graph-tool/trunk@97 d4600afd-f417-0410-95de-beed9576f240
-
- 30 Jan, 2007 1 commit
-
-
Tiago Peixoto authored
git-svn-id: https://svn.forked.de/graph-tool/trunk@72 d4600afd-f417-0410-95de-beed9576f240
-
- 29 Jan, 2007 1 commit
-
-
Tiago Peixoto authored
* accept external files for property editing routines * include in_PROP() andd out_PROP() functions to be used in python filtering/property editing routines. git-svn-id: https://svn.forked.de/graph-tool/trunk@71 d4600afd-f417-0410-95de-beed9576f240
-
- 25 Jan, 2007 1 commit
-
-
Tiago Peixoto authored
included option to disable python and range filtering during compilation, thus reducing compile-time memory requirements git-svn-id: https://svn.forked.de/graph-tool/trunk@64 d4600afd-f417-0410-95de-beed9576f240
-
- 15 Nov, 2006 1 commit
-
-
Tiago Peixoto authored
git-svn-id: https://svn.forked.de/graph-tool/trunk@59 d4600afd-f417-0410-95de-beed9576f240
-
- 14 Nov, 2006 1 commit
-
-
Tiago Peixoto authored
git-svn-id: https://svn.forked.de/graph-tool/trunk@58 d4600afd-f417-0410-95de-beed9576f240
-
- 04 Sep, 2006 1 commit
-
-
Tiago Peixoto authored
* Range filters now support all kinds of scalar properties without falling back to python code git-svn-id: https://svn.forked.de/graph-tool/trunk@46 d4600afd-f417-0410-95de-beed9576f240
-
- 17 Aug, 2006 1 commit
-
-
Tiago Peixoto authored
* cleanup src/graph/graph_python_filtering.hh git-svn-id: https://svn.forked.de/graph-tool/trunk@39 d4600afd-f417-0410-95de-beed9576f240
-
- 16 Aug, 2006 1 commit
-
-
Tiago Peixoto authored
* add GetSampledDistanceHistogram (in src/graph/graph_distance_sampled.cc) * fix BFS initialization bug in src/graph/graph_extended_clustering.cc git-svn-id: https://svn.forked.de/graph-tool/trunk@38 d4600afd-f417-0410-95de-beed9576f240
-
- 15 Aug, 2006 1 commit
-
-
Tiago Peixoto authored
* separated graphml code into graphml.hpp and graphml.cpp, and added support for default property values * added HashedDescriptorMap with automatic memory management git-svn-id: https://svn.forked.de/graph-tool/trunk@36 d4600afd-f417-0410-95de-beed9576f240
-