doc/quicktour.dox
author athos
Fri, 22 Jul 2005 15:03:23 +0000
changeset 1582 5fd89def7cbc
parent 1578 1d3a1bcbc874
child 1584 cf4bc8d477f4
permissions -rw-r--r--
File demoprograms.dox thrown away: demos module used instead.
athos@1169
     1
/**
athos@1169
     2
alpar@1170
     3
\page quicktour Quick Tour to LEMON
alpar@1170
     4
athos@1580
     5
Let us first answer the question <b>"What do I want to use LEMON for?"</b>. 
athos@1175
     6
LEMON is a C++ library, so you can use it if you want to write C++ 
athos@1175
     7
programs. What kind of tasks does the library LEMON help to solve? 
athos@1175
     8
It helps to write programs that solve optimization problems that arise
athos@1175
     9
frequently when <b>designing and testing certain networks</b>, for example
athos@1175
    10
in telecommunication, computer networks, and other areas that I cannot
athos@1175
    11
think of now. A very natural way of modelling these networks is by means
athos@1183
    12
of a <b> graph</b> (we will always mean a directed graph by that and say
athos@1183
    13
<b> undirected graph </b> otherwise). 
athos@1175
    14
So if you want to write a program that works with 
athos@1183
    15
graphs then you might find it useful to use our library LEMON. LEMON 
athos@1183
    16
defines various graph concepts depending on what you want to do with the 
athos@1183
    17
graph: a very good description can be found in the page
athos@1183
    18
about \ref graphs "graphs".
athos@1175
    19
athos@1514
    20
You will also want to assign data to the edges or nodes of the graph, for
athos@1514
    21
example a length or capacity function defined on the edges. You can do this in
athos@1514
    22
LEMON using so called \b maps. You can define a map on the nodes or on the edges of the graph and the value of the map (the range of the function) can be practically almost of any type. Read more about maps \ref maps-page "here".
athos@1175
    23
athos@1528
    24
In this quick tour we want to show you some facilities LEMON library can provide through examples (simple demo programs). The examples will only show part of the functionality, but links will always be given to reach complete details. 
athos@1528
    25
You will find links next to the code fragments that help to download full demo programs: save them on your computer and compile them according to the description in the page about \ref getstart "How to start using LEMON". 
athos@1528
    26
athos@1528
    27
Have fun!
athos@1175
    28
athos@1522
    29
<ul> <li> The first thing to discuss is the way one can create data structures
athos@1522
    30
like graphs and maps in a program using LEMON. 
athos@1522
    31
//There are more graph types
athos@1522
    32
//implemented in LEMON and you can implement your own graph type just as well:
athos@1522
    33
//read more about this in the already mentioned page on \ref graphs "graphs".
athos@1522
    34
athos@1522
    35
First we show how to add nodes and edges to a graph manually. We will also
athos@1522
    36
define a map on the edges of the graph. After this we show the way one can
athos@1522
    37
read a graph (and perhaps maps on it) from a stream (e.g. a file). Of course
athos@1522
    38
we also have routines that write a graph (and perhaps maps) to a stream
athos@1522
    39
(file): this will also be shown. LEMON supports the DIMACS file formats to
athos@1534
    40
read network optimization problems, but more importantly we also have our own
athos@1522
    41
file format that gives a more flexible way to store data related to network
athos@1522
    42
optimization.
athos@1522
    43
athos@1530
    44
<ol> <li>The following code shows how to build a graph from scratch
athos@1530
    45
and iterate on its nodes and edges.  This example also shows how to
athos@1530
    46
give a map on the edges of the graph.  The type Listgraph is one of
athos@1530
    47
the LEMON graph types: the typedefs in the beginning are for
athos@1530
    48
convenience and we will assume them later as well.
athos@1522
    49
athos@1530
    50
\include hello_lemon.cc
athos@1522
    51
athos@1530
    52
See the whole program in file \ref hello_lemon.cc in the \c demo subdir of
athos@1526
    53
LEMON package.
athos@1175
    54
athos@1526
    55
    If you want to read more on the LEMON graph structures and
athos@1526
    56
concepts, read the page about \ref graphs "graphs".
athos@1522
    57
athos@1530
    58
athos@1530
    59
<li>LEMON has an own file format for storing graphs, maps on edges/nodes and some other things. Instead of any explanation let us give a
athos@1530
    60
short example file in this format: read the detailed description of the LEMON
athos@1530
    61
graph file format and input-output routines here: \ref graph-io-page.
athos@1530
    62
athos@1530
    63
So here is a file describing a graph of 6 nodes (0 to 5), two nodemaps
athos@1530
    64
(called \c coordinates_x and \c coordinates_y), several edges, an edge map
athos@1530
    65
called \c capacity and two designated nodes (called \c source and \c target).
athos@1530
    66
athos@1541
    67
\verbatim
athos@1541
    68
@nodeset
athos@1541
    69
id      coordinates_x   coordinates_y
athos@1541
    70
5       796.398 208.035
athos@1541
    71
4       573.002 63.002
athos@1541
    72
3       568.549 401.748
athos@1541
    73
2       277.889 68.476
athos@1541
    74
1       288.248 397.327
athos@1541
    75
0       102.239 257.532
athos@1541
    76
@edgeset
athos@1541
    77
                id      capacity
athos@1541
    78
4       5       6       8
athos@1541
    79
3       5       5       8
athos@1541
    80
2       4       4       5
athos@1541
    81
1       4       3       8
athos@1541
    82
1       3       2       5
athos@1541
    83
0       2       1       10
athos@1541
    84
0       1       0       10
athos@1541
    85
#This is a comment here
athos@1541
    86
@nodes
athos@1541
    87
source 0
athos@1541
    88
target 5
athos@1541
    89
@edges 
athos@1541
    90
@attributes 
athos@1541
    91
author "Attila BERNATH"
athos@1541
    92
@end
athos@1541
    93
\endverbatim
athos@1530
    94
athos@1530
    95
Finally let us give a simple example that reads a graph from a file and writes
athos@1530
    96
it to the standard output.
athos@1530
    97
athos@1530
    98
\include reader_writer_demo.cc
athos@1530
    99
athos@1530
   100
See the whole program in file \ref reader_writer_demo.cc.
athos@1530
   101
athos@1526
   102
<li> The following code shows how to read a graph from a stream
athos@1526
   103
(e.g. a file) in the DIMACS file format (find the documentation of the
athos@1526
   104
DIMACS file formats on the web).
athos@1522
   105
athos@1181
   106
\code
athos@1181
   107
Graph g;
athos@1181
   108
std::ifstream f("graph.dim");
athos@1181
   109
readDimacs(f, g);
athos@1181
   110
\endcode
athos@1522
   111
athos@1526
   112
One can also store network (graph+capacity on the edges) instances and
athos@1526
   113
other things (minimum cost flow instances etc.) in DIMACS format and
athos@1534
   114
read these in LEMON: to see the details read the documentation of the
athos@1534
   115
\ref dimacs.h "Dimacs file format reader". 
athos@1522
   116
athos@1514
   117
</ol>
athos@1514
   118
<li> If you want to solve some transportation problems in a network then 
athos@1175
   119
you will want to find shortest paths between nodes of a graph. This is 
athos@1175
   120
usually solved using Dijkstra's algorithm. A utility
athos@1175
   121
that solves this is  the \ref lemon::Dijkstra "LEMON Dijkstra class".
athos@1522
   122
The following code is a simple program using the 
athos@1530
   123
\ref lemon::Dijkstra "LEMON Dijkstra class": it calculates the shortest path between node \c s and \c t in a graph \c g.
athos@1530
   124
We omit the part reading the graph  \c g and the length map \c len.
athos@1175
   125
athos@1528
   126
\dontinclude dijkstra_demo.cc
athos@1528
   127
\skip ListGraph
athos@1530
   128
\until Graph g
athos@1530
   129
...
athos@1530
   130
\skip Dijkstra algorithm
athos@1528
   131
\until std::cout << g.id(s)
athos@1175
   132
alpar@1287
   133
See the whole program in \ref dijkstra_demo.cc.
athos@1183
   134
athos@1530
   135
Some explanation: after instantiating a member of the Dijkstra class
athos@1530
   136
we run the Dijkstra algorithm from node \c s. After this we read some
athos@1530
   137
of the results.  You can do much more with the Dijkstra class, for
athos@1530
   138
example you can run it step by step and gain full control of the
athos@1530
   139
execution. For a detailed description, see the documentation of the
athos@1530
   140
\ref lemon::Dijkstra "LEMON Dijkstra class".
athos@1183
   141
athos@1183
   142
zsuzska@1578
   143
<li> If you want to design a network and want to minimize the total
zsuzska@1578
   144
length of wires then you might be looking for a <b>minimum spanning
zsuzska@1578
   145
tree</b> in an undirected graph. This can be found using the Kruskal
zsuzska@1578
   146
algorithm: the function \ref lemon::kruskal "LEMON Kruskal " does
zsuzska@1578
   147
this job for you.  After we had a graph \c g and a cost map \c
athos@1580
   148
edge_cost_map , the following code fragment shows an example how to get weight of the minmum spanning tree (in this first example the costs are uniform; this is of course not the case in real life applications):
athos@1175
   149
zsuzska@1578
   150
\dontinclude kruskal_demo.cc
zsuzska@1578
   151
\skip std::cout 
zsuzska@1578
   152
\until kruskal
zsuzska@1578
   153
athos@1580
   154
In the variable \c tree_map the function gives back an edge bool map, which contains the edges of the found tree.
athos@1580
   155
zsuzska@1578
   156
If the costs are non-uniform, for example  the cost is given by \c
athos@1580
   157
edge_cost_map_2 , or the edges of the tree  have to be given in a
zsuzska@1578
   158
vector, then we can give to the kruskal a vector \c tree_edge_vec , instead of
zsuzska@1578
   159
an edge bool map:
zsuzska@1578
   160
zsuzska@1578
   161
\skip edge_cost_map_2 
zsuzska@1578
   162
\until edge_cost_map_2, std::back_inserter
zsuzska@1578
   163
zsuzska@1578
   164
And finally the next fragment shows how to use the functions \c makeKruskalMapInput and \c makeKruskalSequenceOutPut:
zsuzska@1578
   165
zsuzska@1578
   166
\skip makeKruskalSequenceOutput
zsuzska@1578
   167
\until tree_edge_vec
zsuzska@1578
   168
zsuzska@1578
   169
See the whole program in \ref kruskal_demo.cc.
zsuzska@1578
   170
zsuzska@1578
   171
athos@1511
   172
athos@1517
   173
<li>Many problems in network optimization can be formalized by means
athos@1517
   174
of a linear programming problem (LP problem, for short). In our
athos@1517
   175
library we decided not to write an LP solver, since such packages are
athos@1517
   176
available in the commercial world just as well as in the open source
athos@1517
   177
world, and it is also a difficult task to compete these. Instead we
athos@1517
   178
decided to develop an interface that makes it easier to use these
athos@1517
   179
solvers together with LEMON. The advantage of this approach is
athos@1517
   180
twofold. Firstly our C++ interface is more comfortable than the
athos@1517
   181
solvers' native interface. Secondly, changing the underlying solver in
athos@1517
   182
a certain software using LEMON's LP interface needs zero effort. So,
athos@1517
   183
for example, one may try his idea using a free solver, demonstrate its
athos@1517
   184
usability for a customer and if it works well, but the performance
athos@1517
   185
should be improved, then one may decide to purchase and use a better
athos@1517
   186
commercial solver.
athos@1517
   187
athos@1517
   188
So far we have an
athos@1526
   189
interface for the commercial LP solver software \b CPLEX (developed by ILOG)
athos@1514
   190
and for the open source solver \b GLPK (a shorthand for Gnu Linear Programming
athos@1517
   191
Toolkit).
athos@1514
   192
athos@1514
   193
We will show two examples, the first one shows how simple it is to formalize
athos@1514
   194
and solve an LP problem in LEMON, while the second one shows how LEMON
athos@1514
   195
facilitates solving network optimization problems using LP solvers.
athos@1514
   196
athos@1514
   197
<ol>
athos@1514
   198
<li>The following code shows how to solve an LP problem using the LEMON lp
athos@1517
   199
interface. The code together with the comments is self-explanatory.
athos@1511
   200
athos@1530
   201
\dontinclude lp_demo.cc
athos@1530
   202
\skip A default solver is taken
athos@1530
   203
\until End of LEMON style code
athos@1175
   204
athos@1514
   205
See the whole code in \ref lp_demo.cc.
athos@1514
   206
athos@1517
   207
<li>The second example shows how easy it is to formalize a max-flow
athos@1517
   208
problem as an LP problem using the LEMON LP interface: we are looking
athos@1517
   209
for a real valued function defined on the edges of the digraph
athos@1517
   210
satisfying the nonnegativity-, the capacity constraints and the
athos@1517
   211
flow-conservation constraints and giving the largest flow value
athos@1517
   212
between to designated nodes.
athos@1517
   213
athos@1517
   214
In the following code we suppose that we already have the graph \c g,
athos@1517
   215
the capacity map \c cap, the source node \c s and the target node \c t
athos@1517
   216
in the memory. We will also omit the typedefs.
athos@1517
   217
athos@1530
   218
\dontinclude lp_maxflow_demo.cc
athos@1530
   219
\skip Define a map on the edges for the variables of the LP problem
athos@1530
   220
\until lp.max();
athos@1530
   221
\skip Solve with the underlying solver
athos@1530
   222
\until lp.solve();
athos@1517
   223
athos@1517
   224
athos@1517
   225
The complete program can be found in file \ref lp_maxflow_demo.cc. After compiling run it in the form:
athos@1517
   226
athos@1528
   227
<tt>./lp_maxflow_demo < sample.lgf</tt>
athos@1517
   228
athos@1528
   229
where sample.lgf is a file in the lemon format containing a maxflow instance (designated "source", "target" nodes and "capacity" map on the edges).
athos@1517
   230
athos@1517
   231
athos@1514
   232
athos@1514
   233
</ol>
athos@1514
   234
</ul>
athos@1175
   235
athos@1175
   236
*/