doc/graphs.dox
author deba
Fri, 04 Mar 2005 17:12:36 +0000
changeset 1189 9203a299ce4e
parent 1043 52a2201a88e9
child 1200 ae69f556b429
permissions -rw-r--r--
Bug fix
     1 /*!
     2 
     3 \page graphs How to use graphs
     4 
     5 The primary data structures of LEMON are the graph classes. They all
     6 provide a node list - edge list interface, i.e. they have
     7 functionalities to list the nodes and the edges of the graph as well
     8 as  incoming and outgoing edges of a given node. 
     9 
    10 
    11 Each graph should meet the
    12 \ref lemon::concept::StaticGraph "StaticGraph" concept.
    13 This concept does not
    14 make it possible to change the graph (i.e. it is not possible to add
    15 or delete edges or nodes). Most of the graph algorithms will run on
    16 these graphs.
    17 
    18 The graphs meeting the
    19 \ref lemon::concept::ExtendableGraph "ExtendableGraph"
    20 concept allow node and
    21 edge addition. You can also "clear" such a graph (i.e. erase all edges and nodes ).
    22 
    23 In case of graphs meeting the full feature
    24 \ref lemon::concept::ErasableGraph "ErasableGraph"
    25 concept
    26 you can also erase individual edges and nodes in arbitrary order.
    27 
    28 The implemented graph structures are the following.
    29 \li \ref lemon::ListGraph "ListGraph" is the most versatile graph class. It meets
    30 the \ref lemon::concept::ErasableGraph "ErasableGraph" concept
    31 and it also has some convenient extra features.
    32 \li \ref lemon::SmartGraph "SmartGraph" is a more memory
    33 efficient version of \ref lemon::ListGraph "ListGraph". The
    34 price of this is that it only meets the
    35 \ref lemon::concept::ExtendableGraph "ExtendableGraph" concept,
    36 so you cannot delete individual edges or nodes.
    37 \li \ref lemon::SymListGraph "SymListGraph" and
    38 \ref lemon::SymSmartGraph "SymSmartGraph" classes are very similar to
    39 \ref lemon::ListGraph "ListGraph" and \ref lemon::SmartGraph "SmartGraph".
    40 The difference is that whenever you add a
    41 new edge to the graph, it actually adds a pair of oppositely directed edges.
    42 They are linked together so it is possible to access the counterpart of an
    43 edge. An even more important feature is that using these classes you can also
    44 attach data to the edges in such a way that the stored data
    45 are shared by the edge pairs. 
    46 \li \ref lemon::FullGraph "FullGraph"
    47 implements a complete graph. It is a \ref lemon::concept::StaticGraph, so you cannot
    48 change the number of nodes once it is constructed. It is extremely memory
    49 efficient: it uses constant amount of memory independently from the number of
    50 the nodes of the graph. Of course, the size of the \ref maps-page "NodeMap"'s and
    51 \ref maps-page "EdgeMap"'s will depend on the number of nodes.
    52 
    53 \li \ref lemon::NodeSet "NodeSet" implements a graph with no edges. This class
    54 can be used as a base class of \ref lemon::EdgeSet "EdgeSet".
    55 \li \ref lemon::EdgeSet "EdgeSet" can be used to create a new graph on
    56 the node set of another graph. The base graph can be an arbitrary graph and it
    57 is possible to attach several \ref lemon::EdgeSet "EdgeSet"'s to a base graph.
    58 
    59 \todo Don't we need SmartNodeSet and SmartEdgeSet?
    60 \todo Some cross-refs are wrong.
    61 
    62 The graph structures themselves can not store data attached
    63 to the edges and nodes. However they all provide
    64 \ref maps-page "map classes"
    65 to dynamically attach data the to graph components.
    66 
    67 The following program demonstrates the basic features of LEMON's graph
    68 structures.
    69 
    70 \code
    71 #include <iostream>
    72 #include <lemon/list_graph.h>
    73 
    74 using namespace lemon;
    75 
    76 int main()
    77 {
    78   typedef ListGraph Graph;
    79 \endcode
    80 
    81 ListGraph is one of LEMON's graph classes. It is based on linked lists,
    82 therefore iterating throuh its edges and nodes is fast.
    83 
    84 \code
    85   typedef Graph::Edge Edge;
    86   typedef Graph::InEdgeIt InEdgeIt;
    87   typedef Graph::OutEdgeIt OutEdgeIt;
    88   typedef Graph::EdgeIt EdgeIt;
    89   typedef Graph::Node Node;
    90   typedef Graph::NodeIt NodeIt;
    91 
    92   Graph g;
    93   
    94   for (int i = 0; i < 3; i++)
    95     g.addNode();
    96   
    97   for (NodeIt i(g); i!=INVALID; ++i)
    98     for (NodeIt j(g); j!=INVALID; ++j)
    99       if (i != j) g.addEdge(i, j);
   100 \endcode
   101 
   102 After some convenient typedefs we create a graph and add three nodes to it.
   103 Then we add edges to it to form a complete graph.
   104 
   105 \code
   106   std::cout << "Nodes:";
   107   for (NodeIt i(g); i!=INVALID; ++i)
   108     std::cout << " " << g.id(i);
   109   std::cout << std::endl;
   110 \endcode
   111 
   112 Here we iterate through all nodes of the graph. We use a constructor of the
   113 node iterator to initialize it to the first node. The operator++ is used to
   114 step to the next node. Using operator++ on the iterator pointing to the last
   115 node invalidates the iterator i.e. sets its value to
   116 \ref lemon::INVALID "INVALID". This is what we exploit in the stop condition.
   117 
   118 The previous code fragment prints out the following:
   119 
   120 \code
   121 Nodes: 2 1 0
   122 \endcode
   123 
   124 \code
   125   std::cout << "Edges:";
   126   for (EdgeIt i(g); i!=INVALID; ++i)
   127     std::cout << " (" << g.id(g.source(i)) << "," << g.id(g.target(i)) << ")";
   128   std::cout << std::endl;
   129 \endcode
   130 
   131 \code
   132 Edges: (0,2) (1,2) (0,1) (2,1) (1,0) (2,0)
   133 \endcode
   134 
   135 We can also iterate through all edges of the graph very similarly. The 
   136 \c target and
   137 \c source member functions can be used to access the endpoints of an edge.
   138 
   139 \code
   140   NodeIt first_node(g);
   141 
   142   std::cout << "Out-edges of node " << g.id(first_node) << ":";
   143   for (OutEdgeIt i(g, first_node); i!=INVALID; ++i)
   144     std::cout << " (" << g.id(g.source(i)) << "," << g.id(g.target(i)) << ")"; 
   145   std::cout << std::endl;
   146 
   147   std::cout << "In-edges of node " << g.id(first_node) << ":";
   148   for (InEdgeIt i(g, first_node); i!=INVALID; ++i)
   149     std::cout << " (" << g.id(g.source(i)) << "," << g.id(g.target(i)) << ")"; 
   150   std::cout << std::endl;
   151 \endcode
   152 
   153 \code
   154 Out-edges of node 2: (2,0) (2,1)
   155 In-edges of node 2: (0,2) (1,2)
   156 \endcode
   157 
   158 We can also iterate through the in and out-edges of a node. In the above
   159 example we print out the in and out-edges of the first node of the graph.
   160 
   161 \code
   162   Graph::EdgeMap<int> m(g);
   163 
   164   for (EdgeIt e(g); e!=INVALID; ++e)
   165     m.set(e, 10 - g.id(e));
   166   
   167   std::cout << "Id Edge  Value" << std::endl;
   168   for (EdgeIt e(g); e!=INVALID; ++e)
   169     std::cout << g.id(e) << "  (" << g.id(g.source(e)) << "," << g.id(g.target(e))
   170       << ") " << m[e] << std::endl;
   171 \endcode
   172 
   173 \code
   174 Id Edge  Value
   175 4  (0,2) 6
   176 2  (1,2) 8
   177 5  (0,1) 5
   178 0  (2,1) 10
   179 3  (1,0) 7
   180 1  (2,0) 9
   181 \endcode
   182 
   183 As we mentioned above, graphs are not containers rather
   184 incidence structures which are iterable in many ways. LEMON introduces
   185 concepts that allow us to attach containers to graphs. These containers are
   186 called maps.
   187 
   188 In the example above we create an EdgeMap which assigns an integer value to all
   189 edges of the graph. We use the set member function of the map to write values
   190 into the map and the operator[] to retrieve them.
   191 
   192 Here we used the maps provided by the ListGraph class, but you can also write
   193 your own maps. You can read more about using maps \ref maps-page "here".
   194 
   195 */