Changes in / [715:ece80147fb08:712:6d5f547e5bfb] in lemon-main
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/groups.dox
r715 r710 281 281 282 282 /** 283 @defgroup geomdat Geometric Data Structures284 @ingroup auxdat285 \brief Geometric data structures implemented in LEMON.286 287 This group contains geometric data structures implemented in LEMON.288 289 - \ref lemon::dim2::Point "dim2::Point" implements a two dimensional290 vector with the usual operations.291 - \ref lemon::dim2::Box "dim2::Box" can be used to determine the292 rectangular bounding box of a set of \ref lemon::dim2::Point293 "dim2::Point"'s.294 */295 296 /**297 @defgroup matrices Matrices298 @ingroup auxdat299 \brief Two dimensional data storages implemented in LEMON.300 301 This group contains two dimensional data storages implemented in LEMON.302 */303 304 /**305 283 @defgroup algs Algorithms 306 284 \brief This group contains the several algorithms … … 342 320 343 321 /** 344 @defgroup spantree Minimum Spanning Tree Algorithms345 @ingroup algs346 \brief Algorithms for finding minimum cost spanning trees and arborescences.347 348 This group contains the algorithms for finding minimum cost spanning349 trees and arborescences.350 */351 352 /**353 322 @defgroup max_flow Maximum Flow Algorithms 354 323 @ingroup algs … … 428 397 429 398 \f[ \min_{X \subset V, X\not\in \{\emptyset, V\}} 430 \sum_{uv\in A :u\in X, v\not\in X}cap(uv) \f]399 \sum_{uv\in A, u\in X, v\not\in X}cap(uv) \f] 431 400 432 401 LEMON contains several algorithms related to minimum cut problems: … … 441 410 If you want to find minimum cut just between two distinict nodes, 442 411 see the \ref max_flow "maximum flow problem". 412 */ 413 414 /** 415 @defgroup graph_properties Connectivity and Other Graph Properties 416 @ingroup algs 417 \brief Algorithms for discovering the graph properties 418 419 This group contains the algorithms for discovering the graph properties 420 like connectivity, bipartiteness, euler property, simplicity etc. 421 422 \image html edge_biconnected_components.png 423 \image latex edge_biconnected_components.eps "bi-edge-connected components" width=\textwidth 424 */ 425 426 /** 427 @defgroup planar Planarity Embedding and Drawing 428 @ingroup algs 429 \brief Algorithms for planarity checking, embedding and drawing 430 431 This group contains the algorithms for planarity checking, 432 embedding and drawing. 433 434 \image html planar.png 435 \image latex planar.eps "Plane graph" width=\textwidth 443 436 */ 444 437 … … 484 477 485 478 /** 486 @defgroup graph_properties Connectivity and Other Graph Properties 487 @ingroup algs 488 \brief Algorithms for discovering the graph properties 489 490 This group contains the algorithms for discovering the graph properties 491 like connectivity, bipartiteness, euler property, simplicity etc. 492 493 \image html connected_components.png 494 \image latex connected_components.eps "Connected components" width=\textwidth 495 */ 496 497 /** 498 @defgroup planar Planarity Embedding and Drawing 499 @ingroup algs 500 \brief Algorithms for planarity checking, embedding and drawing 501 502 This group contains the algorithms for planarity checking, 503 embedding and drawing. 504 505 \image html planar.png 506 \image latex planar.eps "Plane graph" width=\textwidth 479 @defgroup spantree Minimum Spanning Tree Algorithms 480 @ingroup algs 481 \brief Algorithms for finding minimum cost spanning trees and arborescences. 482 483 This group contains the algorithms for finding minimum cost spanning 484 trees and arborescences. 485 */ 486 487 /** 488 @defgroup auxalg Auxiliary Algorithms 489 @ingroup algs 490 \brief Auxiliary algorithms implemented in LEMON. 491 492 This group contains some algorithms implemented in LEMON 493 in order to make it easier to implement complex algorithms. 507 494 */ 508 495 … … 514 501 This group contains the approximation and heuristic algorithms 515 502 implemented in LEMON. 516 */517 518 /**519 @defgroup auxalg Auxiliary Algorithms520 @ingroup algs521 \brief Auxiliary algorithms implemented in LEMON.522 523 This group contains some algorithms implemented in LEMON524 in order to make it easier to implement complex algorithms.525 503 */ 526 504 … … 631 609 632 610 /** 633 @defgroup dimacs_group DIMACS Format611 @defgroup dimacs_group DIMACS format 634 612 @ingroup io_group 635 613 \brief Read and write files in DIMACS format … … 693 671 694 672 /** 673 \anchor demoprograms 674 675 @defgroup demos Demo Programs 676 677 Some demo programs are listed here. Their full source codes can be found in 678 the \c demo subdirectory of the source tree. 679 680 In order to compile them, use the <tt>make demo</tt> or the 681 <tt>make check</tt> commands. 682 */ 683 684 /** 695 685 @defgroup tools Standalone Utility Applications 696 686 … … 701 691 */ 702 692 703 /**704 \anchor demoprograms705 706 @defgroup demos Demo Programs707 708 Some demo programs are listed here. Their full source codes can be found in709 the \c demo subdirectory of the source tree.710 711 In order to compile them, use the <tt>make demo</tt> or the712 <tt>make check</tt> commands.713 */714 715 693 } -
lemon/bfs.h
r713 r503 414 414 ///The simplest way to execute the BFS algorithm is to use one of the 415 415 ///member functions called \ref run(Node) "run()".\n 416 ///If you need better control on the execution,you have to call417 ///\ref init() first, then you can add several source nodes with416 ///If you need more control on the execution, first you have to call 417 ///\ref init(), then you can add several source nodes with 418 418 ///\ref addSource(). Finally the actual path computation can be 419 419 ///performed with one of the \ref start() functions. … … 1426 1426 /// The simplest way to execute the BFS algorithm is to use one of the 1427 1427 /// member functions called \ref run(Node) "run()".\n 1428 /// If you need better control on the execution,you have to call1429 /// \ref init() first, then you can add several source nodes with1428 /// If you need more control on the execution, first you have to call 1429 /// \ref init(), then you can add several source nodes with 1430 1430 /// \ref addSource(). Finally the actual path computation can be 1431 1431 /// performed with one of the \ref start() functions. -
lemon/circulation.h
r715 r689 73 73 /// It must conform to the \ref concepts::ReadWriteMap "ReadWriteMap" 74 74 /// concept. 75 #ifdef DOXYGEN76 typedef GR::ArcMap<Value> FlowMap;77 #else78 75 typedef typename Digraph::template ArcMap<Value> FlowMap; 79 #endif80 76 81 77 /// \brief Instantiates a FlowMap. … … 92 88 /// The elevator type used by the algorithm. 93 89 /// 94 /// \sa Elevator, LinkedElevator 95 #ifdef DOXYGEN 96 typedef lemon::Elevator<GR, GR::Node> Elevator; 97 #else 90 /// \sa Elevator 91 /// \sa LinkedElevator 98 92 typedef lemon::Elevator<Digraph, typename Digraph::Node> Elevator; 99 #endif100 93 101 94 /// \brief Instantiates an Elevator. … … 477 470 /// \name Execution Control 478 471 /// The simplest way to execute the algorithm is to call \ref run().\n 479 /// If you need bettercontrol on the initial solution or the execution,480 /// you have to call one of the \ref init() functions first, then472 /// If you need more control on the initial solution or the execution, 473 /// first you have to call one of the \ref init() functions, then 481 474 /// the \ref start() function. 482 475 -
lemon/dfs.h
r713 r584 412 412 ///The simplest way to execute the DFS algorithm is to use one of the 413 413 ///member functions called \ref run(Node) "run()".\n 414 ///If you need better control on the execution,you have to call415 ///\ref init() first, then you can add a source node with \ref addSource()414 ///If you need more control on the execution, first you have to call 415 ///\ref init(), then you can add a source node with \ref addSource() 416 416 ///and perform the actual computation with \ref start(). 417 417 ///This procedure can be repeated if there are nodes that have not … … 1370 1370 /// The simplest way to execute the DFS algorithm is to use one of the 1371 1371 /// member functions called \ref run(Node) "run()".\n 1372 /// If you need better control on the execution,you have to call1373 /// \ref init() first, then you can add a source node with \ref addSource()1372 /// If you need more control on the execution, first you have to call 1373 /// \ref init(), then you can add a source node with \ref addSource() 1374 1374 /// and perform the actual computation with \ref start(). 1375 1375 /// This procedure can be repeated if there are nodes that have not -
lemon/dijkstra.h
r713 r584 585 585 ///The simplest way to execute the %Dijkstra algorithm is to use 586 586 ///one of the member functions called \ref run(Node) "run()".\n 587 ///If you need better control on the execution,you have to call588 ///\ref init() first, then you can add several source nodes with587 ///If you need more control on the execution, first you have to call 588 ///\ref init(), then you can add several source nodes with 589 589 ///\ref addSource(). Finally the actual path computation can be 590 590 ///performed with one of the \ref start() functions. -
lemon/dim2.h
r714 r440 22 22 #include <iostream> 23 23 24 ///\ingroup geomdat24 ///\ingroup misc 25 25 ///\file 26 26 ///\brief A simple two dimensional vector and a bounding box implementation 27 /// 28 /// The class \ref lemon::dim2::Point "dim2::Point" implements 29 /// a two dimensional vector with the usual operations. 30 /// 31 /// The class \ref lemon::dim2::Box "dim2::Box" can be used to determine 32 /// the rectangular bounding box of a set of 33 /// \ref lemon::dim2::Point "dim2::Point"'s. 27 34 28 35 namespace lemon { … … 34 41 namespace dim2 { 35 42 36 /// \addtogroup geomdat43 /// \addtogroup misc 37 44 /// @{ 38 45 -
lemon/gomory_hu.h
r713 r596 360 360 /// \c t. 361 361 /// \code 362 /// Gomor yHu<Graph> gom(g, capacities);362 /// GomoruHu<Graph> gom(g, capacities); 363 363 /// gom.run(); 364 364 /// int cnt=0; 365 /// for(Gomor yHu<Graph>::MinCutNodeIt n(gom,s,t); n!=INVALID; ++n) ++cnt;365 /// for(GomoruHu<Graph>::MinCutNodeIt n(gom,s,t); n!=INVALID; ++n) ++cnt; 366 366 /// \endcode 367 367 class MinCutNodeIt … … 457 457 /// \c t. 458 458 /// \code 459 /// Gomor yHu<Graph> gom(g, capacities);459 /// GomoruHu<Graph> gom(g, capacities); 460 460 /// gom.run(); 461 461 /// int value=0; 462 /// for(Gomor yHu<Graph>::MinCutEdgeIt e(gom,s,t); e!=INVALID; ++e)462 /// for(GomoruHu<Graph>::MinCutEdgeIt e(gom,s,t); e!=INVALID; ++e) 463 463 /// value+=capacities[e]; 464 464 /// \endcode -
lemon/min_cost_arborescence.h
r713 r625 489 489 /// The simplest way to execute the algorithm is to use 490 490 /// one of the member functions called \c run(...). \n 491 /// If you need bettercontrol on the execution,492 /// you have to call \ref init() first, then you can add several491 /// If you need more control on the execution, 492 /// first you must call \ref init(), then you can add several 493 493 /// source nodes with \ref addSource(). 494 494 /// Finally \ref start() will perform the arborescence -
lemon/preflow.h
r715 r689 53 53 /// The type of the map that stores the flow values. 54 54 /// It must meet the \ref concepts::ReadWriteMap "ReadWriteMap" concept. 55 #ifdef DOXYGEN56 typedef GR::ArcMap<Value> FlowMap;57 #else58 55 typedef typename Digraph::template ArcMap<Value> FlowMap; 59 #endif60 56 61 57 /// \brief Instantiates a FlowMap. … … 72 68 /// The elevator type used by Preflow algorithm. 73 69 /// 74 /// \sa Elevator, LinkedElevator 75 #ifdef DOXYGEN 76 typedef lemon::Elevator<GR, GR::Node> Elevator; 77 #else 78 typedef lemon::Elevator<Digraph, typename Digraph::Node> Elevator; 79 #endif 70 /// \sa Elevator 71 /// \sa LinkedElevator 72 typedef LinkedElevator<Digraph, typename Digraph::Node> Elevator; 80 73 81 74 /// \brief Instantiates an Elevator. … … 399 392 /// The simplest way to execute the preflow algorithm is to use 400 393 /// \ref run() or \ref runMinCut().\n 401 /// If you need bettercontrol on the initial solution or the execution,402 /// you have to call one of the \ref init() functions first, then394 /// If you need more control on the initial solution or the execution, 395 /// first you have to call one of the \ref init() functions, then 403 396 /// \ref startFirstPhase() and if you need it \ref startSecondPhase(). 404 397
Note: See TracChangeset
for help on using the changeset viewer.