RhodeCode

 * This software is provided "AS IS" with no warranty of any kind,

 * express or implied, and with no claim as to its suitability for any

 * purpose.

 *

 */

/**

@defgroup datas Data Structures

*/

/**

@defgroup graphs Graph Structures

@ingroup datas

\brief Graph structures implemented in LEMON.

The implementation of combinatorial algorithms heavily relies on 

In the case of graph structures, different operations are needed which do 

not alter the physical graph, but gives another view. If some nodes or 

edges have to be hidden or the reverse oriented graph have to be used, then 

this is the case. It also may happen that in a flow implementation 

the residual graph can be accessed by another algorithm, or a node-set 

is to be shrunk for another algorithm. 

LEMON also provides a variety of graphs for these requirements called 

\ref graph_adaptors "graph adaptors". Adaptors cannot be used alone but only 

You are free to use the graph structure that fit your requirements

the best, most graph algorithms and auxiliary data structures can be used

with any graph structures. 

*/

/**

@ingroup graphs

\brief Graph types between real graphs and graph adaptors.

*/

/**

@defgroup maps Maps 

@ingroup datas

new maps from existing ones.

*/

/**

@defgroup graph_maps Graph Maps 

@ingroup maps

\brief Special Graph-Related Maps.

*/

/**

\defgroup map_adaptors Map Adaptors

\ingroup maps

\brief Tools to create new maps from existing ones

Most of them are \ref lemon::concepts::ReadMap "ReadMap"s. They can

make arithmetic operations between one or two maps (negation, scaling,

addition, multiplication etc.) or e.g. convert a map to another one

of different Value type.

algorithms.  If a function type algorithm is called then the function

type map adaptors can be used comfortable. For example let's see the

usage of map adaptors with the \c graphToEps() function:

\code

  Color nodeColor(int deg) {

    if (deg >= 2) {

      return Color(0.5, 0.0, 0.5);

    } else if (deg == 1) {

\endcode 

The \c functorMap() function makes an \c int to \c Color map from the

\e nodeColor() function. The \c composeMap() compose the \e degree_map

and the previous created map. The composed map is proper function to

get color of each node.

The usage with class type algorithms is little bit harder. In this

case the function type map adaptors can not be used, because the

\code

  Graph graph;

  typedef Graph::EdgeMap<double> DoubleEdgeMap;

  DoubleEdgeMap length(graph);

  DoubleEdgeMap speed(graph);

  typedef DivMap<DoubleEdgeMap, DoubleEdgeMap> TimeMap;

maps which can be done implicitly with the \c DivMap template

class. We use the implicit minimum time map as the length map of the

\c Dijkstra algorithm.

*/

/**

@defgroup matrices Matrices 

@ingroup datas

*/

/**

@defgroup paths Path Structures

@ingroup datas

\brief Path structures implemented in LEMON.

efficient to have e.g. the Dijkstra algorithm to store its result in

any kind of path structure.

\sa lemon::concepts::Path

*/

/**

@defgroup auxdat Auxiliary Data Structures

@ingroup datas

order to make it easier to implement combinatorial algorithms.

*/

/**

@defgroup algs Algorithms

\brief This group describes the several algorithms

implemented in LEMON.

This group describes the several algorithms

implemented in LEMON.

*/

/**

@defgroup search Graph Search

@ingroup algs

*/

/**

@defgroup shortest_path Shortest Path algorithms

@ingroup algs

*/

/** 

@defgroup max_flow Maximum Flow algorithms 

@ingroup algs 

This group describes the algorithms for finding maximum flows and

feasible circulations.

directed graph, an \f$c_a:A\rightarrow\mathbf{R}^+_0\f$ capacity

function and given \f$s, t \in V\f$ source and target node. The

\f[ 0 \le f_a \le c_a \f]

\f[ \max \sum_{v\in\delta^{+}(s)}f_{uv} - \sum_{v\in\delta^{-}(s)}f_{vu}\f]

- \ref lemon::EdmondsKarp "Edmonds-Karp" 

- \ref lemon::Preflow "Goldberg's Preflow algorithm"

- \ref lemon::GoldbergTarjan "Preflow algorithm with dynamic trees"

fastest method to compute the maximum flow. All impelementations

*/

/**

@defgroup min_cost_flow Minimum Cost Flow algorithms

@ingroup algs

This group describes the algorithms for finding minimum cost flows and

circulations.  

*/

/**

@defgroup min_cut Minimum Cut algorithms 

@ingroup algs 

This group describes the algorithms for finding minimum cut in graphs.

The minimum cut problem is to find a non-empty and non-complete

\f$X\f$ subset of the vertices with minimum overall capacity on

outgoing arcs. Formally, there is \f$G=(V,A)\f$ directed graph, an

\f$c_a:A\rightarrow\mathbf{R}^+_0\f$ capacity function. The minimum

\f[ \min_{X \subset V, X\not\in \{\emptyset, V\}}\sum_{uv\in A, u\in X, v\not\in X}c_{uv}\f]

  in directed graphs  

  calculate minimum cut in undirected graphs

  pairs minimum cut in undirected graphs

If you want to find minimum cut just between two distinict nodes,

please see the \ref max_flow "Maximum Flow page".

*/

/**

@defgroup graph_prop Connectivity and other graph properties

@ingroup algs

\image html edge_biconnected_components.png

\image latex edge_biconnected_components.eps "bi-edge-connected components" width=\textwidth

*/

/**

@defgroup planar Planarity embedding and drawing

@ingroup algs

\image html planar.png

\image latex planar.eps "Plane graph" width=\textwidth

*/

/**

@defgroup matching Matching algorithms 

@ingroup algs

matchings in graphs and bipartite graphs. The general matching problem is

finding a subset of the edges which does not shares common endpoints.

There are several different algorithms for calculate matchings in

graphs.  The matching problems in bipartite graphs are generally

easier than in general graphs. The goal of the matching optimization

can be the finding maximum cardinality, maximum weight or minimum cost

matching. The search can be constrained to find perfect or

\image html bipartite_matching.png

\image latex bipartite_matching.eps "Bipartite Matching" width=\textwidth

*/

/**

@defgroup spantree Minimum Spanning Tree algorithms

@ingroup algs

tree in a graph

*/

/**

@defgroup auxalg Auxiliary algorithms

@ingroup algs

*/

/**

@defgroup approx Approximation algorithms

*/

/**

@defgroup gen_opt_group General Optimization Tools

\brief This group describes some general optimization frameworks

implemented in LEMON.

This group describes some general optimization frameworks

various LP solvers could be used in the same manner with this

interface.

*/

/** 

@defgroup lp_utils Tools for Lp and Mip solvers 

@ingroup lp_group

This group adds some helper tools to general optimization framework

implemented in LEMON.

*/

/**

@defgroup metah Metaheuristics

@ingroup gen_opt_group

\brief Metaheuristics for LEMON library.

*/

/**

@defgroup utils Tools and Utilities 

*/

/**

@defgroup gutils Basic Graph Utilities

@ingroup utils

This group describes some simple basic graph utilities.

*/

/**

@defgroup misc Miscellaneous Tools

@ingroup utils

debugging and testing.

*/

/**

@defgroup timecount Time measuring and Counting

@ingroup misc

of algorithms.

*/

/**

@defgroup graphbits Tools for Graph Implementation

@ingroup utils

the maps that dynamically update with the graph changes.

*/

/**

@defgroup exceptions Exceptions

@ingroup utils

*/

/**

@defgroup io_group Input-Output

and graph related data. Now it supports the LEMON format, the

*/

/**

@defgroup lemon_io Lemon Input-Output

@ingroup io_group

\brief Reading and writing LEMON format

tutorial pages.

*/

/**

@defgroup section_io Section readers and writers

@ingroup lemon_io

\brief Section readers and writers for lemon Input-Output.

*/

/**

@defgroup item_io Item Readers and Writers

@ingroup lemon_io

\brief Item readers and writers for lemon Input-Output.

The Input-Output classes can handle more data type by example

read some way. The module make possible to do this.  

*/

/**

@defgroup eps_io Postscript exporting

@ingroup io_group

\brief General \c EPS drawer and graph exporter

graph exporting tools. 

*/

/**

@defgroup concept Concepts

\brief Skeleton classes and concept checking classes

  without implementations and real data structures behind the

  interface. On the other hand they should provide nothing else. All

  the algorithms working on a data structure meeting a certain concept

  should compile with these classes. (Though it will not run properly,

  of course.) In this way it is easily to check if an algorithm

  doesn't use any extra feature of a certain implementation.

- The concept descriptor classes also provide a <em>checker class</em>

  concept indeed provides all the required features.

- Finally, They can serve as a skeleton of a new implementation of a concept.

*/

/**

@defgroup graph_concepts Graph Structure Concepts

@ingroup concept

\brief Skeleton and concept checking classes for graph structures

graph structures and helper classes used to implement these.

*/

/* --- Unused group

@defgroup experimental Experimental Structures and Algorithms

The stuff here is subject to change.

*/

/**

\anchor demoprograms

@defgroup demos Demo programs

Some demo programs are listed here. Their full source codes can be found in

the \c demo subdirectory of the source tree.

It order to compile them, use <tt>--enable-demo</tt> configure option when

build the library.

*/

/**

@defgroup tools Standalone utility applications

Some utility applications are listed here. 

The standard compilation procedure (<tt>./configure;make</tt>) will compile

them, as well. 

*/