doc/groups.dox
author ladanyi
Fri, 12 Oct 2007 22:19:03 +0000
changeset 2494 839c74eeba84
parent 2489 48dddc283cfc
child 2500 9d9855af1de1
permissions -rw-r--r--
Makefile fix.
alpar@2391
     1
/* -*- C++ -*-
alpar@2391
     2
 *
alpar@2391
     3
 * This file is a part of LEMON, a generic C++ optimization library
alpar@2391
     4
 *
alpar@2391
     5
 * Copyright (C) 2003-2007
alpar@2391
     6
 * Egervary Jeno Kombinatorikus Optimalizalasi Kutatocsoport
alpar@2391
     7
 * (Egervary Research Group on Combinatorial Optimization, EGRES).
alpar@2391
     8
 *
alpar@2391
     9
 * Permission to use, modify and distribute this software is granted
alpar@2391
    10
 * provided that this copyright notice appears in all copies. For
alpar@2391
    11
 * precise terms see the accompanying LICENSE file.
alpar@2391
    12
 *
alpar@2391
    13
 * This software is provided "AS IS" with no warranty of any kind,
alpar@2391
    14
 * express or implied, and with no claim as to its suitability for any
alpar@2391
    15
 * purpose.
alpar@2391
    16
 *
alpar@2391
    17
 */
alpar@814
    18
alpar@678
    19
/**
alpar@678
    20
@defgroup datas Data Structures
alpar@921
    21
This group describes the several graph structures implemented in LEMON.
alpar@678
    22
*/
alpar@430
    23
alpar@678
    24
/**
alpar@678
    25
@defgroup graphs Graph Structures
alpar@678
    26
@ingroup datas
alpar@921
    27
\brief Graph structures implemented in LEMON.
alpar@430
    28
marci@1172
    29
The implementation of combinatorial algorithms heavily relies on 
marci@1172
    30
efficient graph implementations. LEMON offers data structures which are 
marci@1172
    31
planned to be easily used in an experimental phase of implementation studies, 
marci@1172
    32
and thereafter the program code can be made efficient by small modifications. 
alpar@430
    33
deba@2084
    34
The most efficient implementation of diverse applications require the
deba@2084
    35
usage of different physical graph implementations. These differences
deba@2084
    36
appear in the size of graph we require to handle, memory or time usage
deba@2084
    37
limitations or in the set of operations through which the graph can be
deba@2084
    38
accessed.  LEMON provides several physical graph structures to meet
deba@2084
    39
the diverging requirements of the possible users.  In order to save on
deba@2084
    40
running time or on memory usage, some structures may fail to provide
deba@2084
    41
some graph features like edge or node deletion.
marci@1172
    42
marci@1172
    43
Alteration of standard containers need a very limited number of 
marci@1172
    44
operations, these together satisfy the everyday requirements. 
alpar@2117
    45
In the case of graph structures, different operations are needed which do 
alpar@2006
    46
not alter the physical graph, but gives another view. If some nodes or 
marci@1172
    47
edges have to be hidden or the reverse oriented graph have to be used, then 
alpar@2117
    48
this is the case. It also may happen that in a flow implementation 
alpar@2006
    49
the residual graph can be accessed by another algorithm, or a node-set 
alpar@2006
    50
is to be shrunk for another algorithm. 
marci@1172
    51
LEMON also provides a variety of graphs for these requirements called 
alpar@1401
    52
\ref graph_adaptors "graph adaptors". Adaptors cannot be used alone but only 
marci@1172
    53
in conjunction with other graph representation. 
alpar@430
    54
alpar@678
    55
You are free to use the graph structure that fit your requirements
alpar@678
    56
the best, most graph algorithms and auxiliary data structures can be used
marci@1172
    57
with any graph structures. 
alpar@678
    58
*/
alpar@430
    59
alpar@678
    60
/**
deba@1866
    61
@defgroup semi_adaptors Semi-Adaptors Classes for Graphs
deba@1866
    62
@ingroup graphs
deba@1866
    63
\brief Graph types between real graphs and graph adaptors.
deba@1866
    64
alpar@2117
    65
Graph types between real graphs and graph adaptors. These classes wrap
alpar@2117
    66
graphs to give new functionality as the adaptors do it. On the other
alpar@2117
    67
hand they are not light-weight structures as the adaptors.
deba@1866
    68
*/
deba@1866
    69
deba@1866
    70
/**
alpar@1043
    71
@defgroup maps Maps 
alpar@1043
    72
@ingroup datas
alpar@1043
    73
\brief Some special purpose map to make life easier.
alpar@1043
    74
alpar@1043
    75
LEMON provides several special maps that e.g. combine
alpar@1043
    76
new maps from existing ones.
alpar@1043
    77
*/
alpar@1043
    78
alpar@1402
    79
/**
alpar@1402
    80
@defgroup graph_maps Graph Maps 
alpar@1402
    81
@ingroup maps
alpar@1402
    82
\brief Special Graph-Related Maps.
alpar@1402
    83
alpar@1402
    84
These maps are specifically designed to assign values to the nodes and edges of
alpar@1402
    85
graphs.
alpar@1402
    86
*/
alpar@1402
    87
alpar@1402
    88
alpar@1402
    89
/**
alpar@1402
    90
\defgroup map_adaptors Map Adaptors
alpar@1402
    91
\ingroup maps
alpar@1402
    92
\brief Tools to create new maps from existing ones
alpar@1402
    93
alpar@1402
    94
Map adaptors are used to create "implicit" maps from other maps.
alpar@1402
    95
alpar@2260
    96
Most of them are \ref lemon::concepts::ReadMap "ReadMap"s. They can
alpar@2117
    97
make arithmetic operations between one or two maps (negation, scaling,
alpar@1402
    98
addition, multiplication etc.) or e.g. convert a map to another one
alpar@1402
    99
of different Value type.
deba@2489
   100
deba@2489
   101
The typical usage of this classes is the passing implicit maps to
deba@2489
   102
algorithms.  If a function type algorithm is called then the function
deba@2489
   103
type map adaptors can be used comfortable. For example let's see the
deba@2489
   104
usage of map adaptors with the \c graphToEps() function:
deba@2489
   105
\code
deba@2489
   106
  Color nodeColor(int deg) {
deba@2489
   107
    if (deg >= 2) {
deba@2489
   108
      return Color(0.5, 0.0, 0.5);
deba@2489
   109
    } else if (deg == 1) {
deba@2489
   110
      return Color(1.0, 0.5, 1.0);
deba@2489
   111
    } else {
deba@2489
   112
      return Color(0.0, 0.0, 0.0);
deba@2489
   113
    }
deba@2489
   114
  }
deba@2489
   115
  
deba@2489
   116
  Graph::NodeMap<int> degree_map(graph);
deba@2489
   117
  
deba@2489
   118
  graphToEps(graph, "graph.eps")
deba@2489
   119
    .coords(coords).scaleToA4().undirected()
deba@2489
   120
    .nodeColors(composeMap(functorMap(nodeColor), degree_map)) 
deba@2489
   121
    .run();
deba@2489
   122
\endcode 
deba@2489
   123
The \c functorMap() function makes an \c int to \c Color map from the
deba@2489
   124
\e nodeColor() function. The \c composeMap() compose the \e degree_map
deba@2489
   125
and the previous created map. The composed map is proper function to
deba@2489
   126
get color of each node.
deba@2489
   127
deba@2489
   128
The usage with class type algorithms is little bit harder. In this
deba@2489
   129
case the function type map adaptors can not be used, because the
deba@2489
   130
function map adaptors give back temporarly objects.
deba@2489
   131
\code
deba@2489
   132
  Graph graph;
deba@2489
   133
  
deba@2489
   134
  typedef Graph::EdgeMap<double> DoubleEdgeMap;
deba@2489
   135
  DoubleEdgeMap length(graph);
deba@2489
   136
  DoubleEdgeMap speed(graph);
deba@2489
   137
  
deba@2489
   138
  typedef DivMap<DoubleEdgeMap, DoubleEdgeMap> TimeMap;
deba@2489
   139
  
deba@2489
   140
  TimeMap time(length, speed);
deba@2489
   141
  
deba@2489
   142
  Dijkstra<Graph, TimeMap> dijkstra(graph, time);
deba@2489
   143
  dijkstra.run(source, target);
deba@2489
   144
\endcode
deba@2489
   145
deba@2489
   146
We have a length map and a maximum speed map on a graph. The minimum
deba@2489
   147
time to pass the edge can be calculated as the division of the two
deba@2489
   148
maps which can be done implicitly with the \c DivMap template
deba@2489
   149
class. We use the implicit minimum time map as the length map of the
deba@2489
   150
\c Dijkstra algorithm.
alpar@1402
   151
*/
alpar@1402
   152
alpar@1043
   153
/**
alpar@2072
   154
@defgroup matrices Matrices 
alpar@2072
   155
@ingroup datas
alpar@2072
   156
\brief Two dimensional data storages.
alpar@2072
   157
deba@2084
   158
Two dimensional data storages.
alpar@2072
   159
*/
alpar@2072
   160
deba@2084
   161
/**
deba@2084
   162
@defgroup paths Path Structures
deba@2084
   163
@ingroup datas
deba@2084
   164
\brief Path structures implemented in LEMON.
deba@2084
   165
deba@2084
   166
LEMON provides flexible data structures
deba@2084
   167
to work with paths.
deba@2084
   168
deba@2489
   169
All of them have similar interfaces, and it can be copied easily with
deba@2489
   170
assignment operator and copy constructor. This make it easy and
deba@2489
   171
efficient to have e.g. the Dijkstra algorithm to store its result in
deba@2489
   172
any kind of path structure.
deba@2084
   173
alpar@2260
   174
\sa lemon::concepts::Path
deba@2084
   175
deba@2084
   176
*/
alpar@2072
   177
alpar@2072
   178
/**
alpar@678
   179
@defgroup auxdat Auxiliary Data Structures
alpar@678
   180
@ingroup datas
alpar@921
   181
\brief Some data structures implemented in LEMON.
alpar@406
   182
alpar@921
   183
This group describes the data structures implemented in LEMON in
alpar@678
   184
order to make it easier to implement combinatorial algorithms.
alpar@678
   185
*/
alpar@406
   186
alpar@785
   187
alpar@785
   188
/**
deba@2084
   189
@defgroup algs Algorithms
deba@2084
   190
\brief This group describes the several algorithms
alpar@921
   191
implemented in LEMON.
alpar@947
   192
deba@2084
   193
This group describes the several algorithms
alpar@947
   194
implemented in LEMON.
alpar@947
   195
*/
alpar@947
   196
alpar@947
   197
/**
deba@2376
   198
@defgroup search Graph Search
deba@2084
   199
@ingroup algs
deba@2376
   200
\brief This group contains the common graph
deba@2376
   201
search algorithms.
alpar@947
   202
deba@2376
   203
This group contains the common graph
deba@2376
   204
search algorithms like Bfs and Dfs.
alpar@678
   205
*/
alpar@678
   206
alpar@678
   207
/**
deba@2376
   208
@defgroup shortest_path Shortest Path algorithms
deba@2084
   209
@ingroup algs
alpar@758
   210
\brief This group describes the algorithms
deba@2376
   211
for finding shortest paths.
deba@2060
   212
deba@2376
   213
This group describes the algorithms for finding shortest paths in
deba@2376
   214
graphs.
deba@2376
   215
deba@2376
   216
*/
deba@2376
   217
deba@2376
   218
/** 
deba@2376
   219
@defgroup max_flow Maximum Flow algorithms 
deba@2376
   220
@ingroup algs 
deba@2376
   221
\brief This group describes the algorithms for finding maximum flows.
deba@2376
   222
deba@2377
   223
This group describes the algorithms for finding maximum flows and
deba@2377
   224
feasible circulations.
deba@2060
   225
deba@2060
   226
\image html flow.png
deba@2060
   227
\image latex flow.eps "Graph flow" width=\textwidth
alpar@678
   228
*/
alpar@678
   229
alpar@678
   230
/**
deba@2376
   231
@defgroup min_cost_flow Minimum Cost Flow algorithms
deba@2376
   232
@ingroup algs
deba@2376
   233
deba@2376
   234
\brief This group describes the algorithms
deba@2376
   235
for finding minimum cost flows and circulations.
deba@2376
   236
deba@2376
   237
This group describes the algorithms for finding minimum cost flows and
deba@2376
   238
circulations.  
deba@2376
   239
*/
deba@2376
   240
deba@2376
   241
/**
deba@2376
   242
@defgroup min_cut Minimum Cut algorithms
deba@2376
   243
@ingroup algs
deba@2376
   244
\brief This group describes the algorithms
deba@2376
   245
for finding minimum cut in graphs.
deba@2376
   246
deba@2376
   247
This group describes the algorithms
deba@2376
   248
for finding minimum cut in graphs.
deba@2376
   249
*/
deba@2376
   250
deba@2376
   251
/**
deba@2429
   252
@defgroup graph_prop Connectivity and other graph properties
deba@2084
   253
@ingroup algs
deba@1750
   254
\brief This group describes the algorithms
deba@2429
   255
for discover the graph properties
deba@2060
   256
deba@2429
   257
This group describes the algorithms for discover the graph properties
deba@2429
   258
like connectivity, bipartiteness, euler property, simplicity, etc...
deba@2060
   259
deba@2060
   260
\image html edge_biconnected_components.png
deba@2060
   261
\image latex edge_biconnected_components.eps "bi-edge-connected components" width=\textwidth
deba@1750
   262
*/
deba@1750
   263
deba@1750
   264
/**
deba@2376
   265
@defgroup matching Matching algorithms 
deba@2084
   266
@ingroup algs
deba@2042
   267
\brief This group describes the algorithms
deba@2042
   268
for find matchings in graphs and bipartite graphs.
deba@2060
   269
deba@2060
   270
This group provides some algorithm objects and function
deba@2060
   271
to calculate matchings in graphs and bipartite graphs.
deba@2060
   272
deba@2060
   273
\image html bipartite_matching.png
deba@2060
   274
\image latex bipartite_matching.eps "Bipartite Matching" width=\textwidth
deba@2060
   275
deba@2042
   276
*/
deba@2042
   277
deba@2042
   278
/**
deba@2376
   279
@defgroup spantree Minimum Spanning Tree algorithms
deba@2084
   280
@ingroup algs
alpar@2117
   281
\brief This group contains the algorithms for finding a minimum cost spanning
deba@2084
   282
tree in a graph
deba@2084
   283
alpar@2117
   284
This group contains the algorithms for finding a minimum cost spanning
deba@2084
   285
tree in a graph
deba@2084
   286
*/
deba@2084
   287
deba@2084
   288
deba@2084
   289
/**
deba@2376
   290
@defgroup auxalg Auxiliary algorithms
deba@2084
   291
@ingroup algs
deba@2084
   292
\brief Some algorithms implemented in LEMON.
deba@2084
   293
deba@2084
   294
This group describes the algorithms in LEMON in order to make 
deba@2084
   295
it easier to implement complex algorithms.
deba@2376
   296
*/
deba@2084
   297
deba@2376
   298
/**
deba@2376
   299
@defgroup approx Approximation algorithms
deba@2376
   300
\brief Approximation algorithms
deba@2376
   301
deba@2376
   302
Approximation and heuristic algorithms
deba@2084
   303
*/
deba@2084
   304
deba@2084
   305
/**
deba@2084
   306
@defgroup gen_opt_group General Optimization Tools
deba@2084
   307
\brief This group describes some general optimization frameworks
deba@2084
   308
implemented in LEMON.
deba@2084
   309
deba@2084
   310
This group describes some general optimization frameworks
deba@2084
   311
implemented in LEMON.
deba@2084
   312
alpar@1151
   313
*/
alpar@1151
   314
deba@2370
   315
/**
deba@2371
   316
@defgroup lp_group Lp and Mip solvers
deba@2370
   317
@ingroup gen_opt_group
deba@2370
   318
\brief Lp and Mip solver interfaces for LEMON.
deba@2370
   319
deba@2370
   320
This group describes Lp and Mip solver interfaces for LEMON. The
deba@2370
   321
various LP solvers could be used in the same manner with this
deba@2370
   322
interface.
deba@2370
   323
deba@2370
   324
*/
deba@2370
   325
deba@2368
   326
/** 
deba@2370
   327
@defgroup lp_utils Tools for Lp and Mip solvers 
deba@2370
   328
@ingroup lp_group
deba@2370
   329
\brief This group adds some helper tools to the Lp and Mip solvers
deba@2370
   330
implemented in LEMON.
deba@2368
   331
deba@2368
   332
This group adds some helper tools to general optimization framework
deba@2368
   333
implemented in LEMON.
deba@2368
   334
*/
deba@2368
   335
alpar@1151
   336
/**
deba@2370
   337
@defgroup metah Metaheuristics
deba@2370
   338
@ingroup gen_opt_group
deba@2370
   339
\brief Metaheuristics for LEMON library.
deba@2370
   340
deba@2370
   341
This group contains some metaheuristic optimization tools.
deba@2370
   342
*/
deba@2370
   343
deba@2370
   344
/**
deba@2376
   345
@defgroup utils Tools and Utilities 
deba@2376
   346
\brief Tools and Utilities for Programming in LEMON
deba@2376
   347
deba@2376
   348
Tools and Utilities for Programming in LEMON
deba@2376
   349
*/
deba@2376
   350
deba@2376
   351
/**
deba@2376
   352
@defgroup gutils Basic Graph Utilities
deba@2376
   353
@ingroup utils
deba@2376
   354
\brief This group describes some simple basic graph utilities.
deba@2376
   355
deba@2376
   356
This group describes some simple basic graph utilities.
deba@2376
   357
*/
deba@2376
   358
deba@2376
   359
/**
alpar@678
   360
@defgroup misc Miscellaneous Tools
deba@2376
   361
@ingroup utils
alpar@678
   362
Here you can find several useful tools for development,
alpar@678
   363
debugging and testing.
alpar@678
   364
*/
alpar@678
   365
deba@2376
   366
alpar@678
   367
/**
alpar@1847
   368
@defgroup timecount Time measuring and Counting
alpar@1847
   369
@ingroup misc
alpar@1847
   370
Here you can find simple tools for measuring the performance
alpar@1847
   371
of algorithms.
alpar@1847
   372
*/
alpar@1847
   373
alpar@1847
   374
/**
deba@2376
   375
@defgroup graphbits Tools for Graph Implementation
deba@2376
   376
@ingroup utils
deba@2376
   377
\brief Tools to Make It Easier to Make Graphs.
deba@2376
   378
deba@2376
   379
This group describes the tools that makes it easier to make graphs and
deba@2376
   380
the maps that dynamically update with the graph changes.
deba@2376
   381
*/
deba@2376
   382
deba@2376
   383
/**
deba@2376
   384
@defgroup exceptions Exceptions
deba@2376
   385
@ingroup utils
deba@2376
   386
This group contains the exceptions thrown by LEMON library
deba@2376
   387
*/
deba@2376
   388
deba@2376
   389
/**
deba@2016
   390
@defgroup io_group Input-Output
deba@2084
   391
\brief Several Graph Input-Output methods
deba@2084
   392
deba@2084
   393
Here you can find tools for importing and exporting graphs 
deba@2084
   394
and graph related data. Now it supports the LEMON format, the
alpar@2117
   395
\c DIMACS format and the encapsulated postscript format.
deba@2084
   396
*/
deba@2084
   397
deba@2084
   398
/**
deba@2084
   399
@defgroup lemon_io Lemon Input-Output
deba@2084
   400
@ingroup io_group
deba@2084
   401
\brief Reading and writing LEMON format
deba@2084
   402
deba@2084
   403
Methods for reading and writing LEMON format. More about this
deba@2084
   404
format you can find on the \ref graph-io-page "Graph Input-Output"
deba@2084
   405
tutorial pages.
alpar@1287
   406
*/
alpar@1287
   407
alpar@1287
   408
/**
deba@2016
   409
@defgroup section_io Section readers and writers
deba@2084
   410
@ingroup lemon_io
deba@2016
   411
\brief Section readers and writers for lemon Input-Output.
deba@2016
   412
deba@2016
   413
Here you can find which section readers and writers can attach to
deba@2016
   414
the LemonReader and LemonWriter.
deba@2016
   415
*/
deba@2016
   416
deba@2016
   417
/**
deba@2016
   418
@defgroup item_io Item Readers and Writers
deba@2084
   419
@ingroup lemon_io
deba@2016
   420
\brief Item readers and writers for lemon Input-Output.
deba@2016
   421
deba@2016
   422
The Input-Output classes can handle more data type by example
deba@2016
   423
as map or attribute value. Each of these should be written and
deba@2016
   424
read some way. The module make possible to do this.  
deba@2016
   425
*/
deba@2016
   426
deba@2016
   427
/**
deba@2084
   428
@defgroup eps_io Postscript exporting
deba@2084
   429
@ingroup io_group
alpar@2117
   430
\brief General \c EPS drawer and graph exporter
deba@2084
   431
alpar@2117
   432
This group contains general \c EPS drawing methods and special
deba@2084
   433
graph exporting tools. 
deba@2084
   434
*/
deba@2084
   435
deba@2084
   436
deba@2084
   437
/**
klao@1030
   438
@defgroup concept Concepts
klao@959
   439
\brief Skeleton classes and concept checking classes
alpar@794
   440
klao@959
   441
This group describes the data/algorithm skeletons and concept checking
klao@1030
   442
classes implemented in LEMON.
klao@1030
   443
alpar@2117
   444
The purpose of the classes in this group is fourfold.
alpar@2117
   445
 
alpar@2117
   446
- These classes contain the documentations of the concepts. In order
alpar@2117
   447
  to avoid document multiplications, an implementation of a concept
alpar@2117
   448
  simply refers to the corresponding concept class.
klao@1030
   449
alpar@2233
   450
- These classes declare every functions, <tt>typedef</tt>s etc. an
alpar@2117
   451
  implementation of the concepts should provide, however completely
alpar@2117
   452
  without implementations and real data structures behind the
alpar@2117
   453
  interface. On the other hand they should provide nothing else. All
alpar@2117
   454
  the algorithms working on a data structure meeting a certain concept
alpar@2117
   455
  should compile with these classes. (Though it will not run properly,
alpar@2117
   456
  of course.) In this way it is easily to check if an algorithm
alpar@2117
   457
  doesn't use any extra feature of a certain implementation.
alpar@2117
   458
alpar@2233
   459
- The concept descriptor classes also provide a <em>checker class</em>
alpar@2117
   460
  that makes it possible check whether a certain implementation of a
alpar@2117
   461
  concept indeed provides all the required features.
alpar@2117
   462
alpar@2117
   463
- Finally, They can serve as a skeleton of a new implementation of a concept.
klao@1030
   464
alpar@794
   465
*/
alpar@794
   466
deba@2084
   467
klao@1030
   468
/**
klao@1030
   469
@defgroup graph_concepts Graph Structure Concepts
klao@1030
   470
@ingroup concept
klao@1030
   471
\brief Skeleton and concept checking classes for graph structures
klao@1030
   472
klao@1030
   473
This group contains the skeletons and concept checking classes of LEMON's
klao@1030
   474
graph structures and helper classes used to implement these.
klao@1030
   475
*/
alpar@794
   476
alpar@1587
   477
/* --- Unused group
alpar@678
   478
@defgroup experimental Experimental Structures and Algorithms
alpar@678
   479
This group contains some Experimental structures and algorithms.
alpar@678
   480
The stuff here is subject to change.
alpar@678
   481
*/
alpar@1151
   482
alpar@1558
   483
/**
athos@1582
   484
\anchor demoprograms
athos@1582
   485
alpar@1558
   486
@defgroup demos Demo programs
alpar@1558
   487
alpar@1559
   488
Some demo programs are listed here. Their full source codes can be found in
alpar@1558
   489
the \c demo subdirectory of the source tree.
alpar@1558
   490
ladanyi@1639
   491
The standard compilation procedure (<tt>./configure;make</tt>) will compile
ladanyi@1639
   492
them, as well. 
alpar@1558
   493
alpar@1558
   494
*/
alpar@1558
   495
deba@2491
   496
/**
deba@2491
   497
@defgroup tools Standalone utility applications
deba@2491
   498
deba@2491
   499
Some utility applications are listed here. 
deba@2491
   500
deba@2491
   501
The standard compilation procedure (<tt>./configure;make</tt>) will compile
deba@2491
   502
them, as well. 
deba@2491
   503
deba@2491
   504
*/
deba@2491
   505