0
22
0
2
2
2
2
10
10
| ... | ... |
@@ -80,3 +80,3 @@ |
| 80 | 80 |
- For all \f$u\in V\f$ nodes: |
| 81 |
- \f$\pi(u) |
|
| 81 |
- \f$\pi(u)\leq 0\f$; |
|
| 82 | 82 |
- if \f$\sum_{uv\in A} f(uv) - \sum_{vu\in A} f(vu) \neq sup(u)\f$,
|
| ... | ... |
@@ -147,3 +147,3 @@ |
| 147 | 147 |
- For all \f$u\in V\f$ nodes: |
| 148 |
- \f$\pi(u) |
|
| 148 |
- \f$\pi(u)\geq 0\f$; |
|
| 149 | 149 |
- if \f$\sum_{uv\in A} f(uv) - \sum_{vu\in A} f(vu) \neq sup(u)\f$,
|
| ... | ... |
@@ -302,3 +302,3 @@ |
| 302 | 302 |
/// \c OperationTraits type. |
| 303 |
/// For more information see \ref BellmanFordDefaultOperationTraits. |
|
| 303 |
/// For more information, see \ref BellmanFordDefaultOperationTraits. |
|
| 304 | 304 |
template <class T> |
| ... | ... |
@@ -720,3 +720,3 @@ |
| 720 | 720 |
/// The shortest path tree used here is equal to the shortest path |
| 721 |
/// tree used in \ref predNode() and \predMap(). |
|
| 721 |
/// tree used in \ref predNode() and \ref predMap(). |
|
| 722 | 722 |
/// |
| ... | ... |
@@ -735,3 +735,3 @@ |
| 735 | 735 |
/// The shortest path tree used here is equal to the shortest path |
| 736 |
/// tree used in \ref predArc() and \predMap(). |
|
| 736 |
/// tree used in \ref predArc() and \ref predMap(). |
|
| 737 | 737 |
/// |
| ... | ... |
@@ -65,3 +65,3 @@ |
| 65 | 65 |
///It must conform to the \ref concepts::WriteMap "WriteMap" concept. |
| 66 |
///By default it is a NullMap. |
|
| 66 |
///By default, it is a NullMap. |
|
| 67 | 67 |
typedef NullMap<typename Digraph::Node,bool> ProcessedMap; |
| ... | ... |
@@ -850,3 +850,3 @@ |
| 850 | 850 |
///It must conform to the \ref concepts::WriteMap "WriteMap" concept. |
| 851 |
///By default it is a NullMap. |
|
| 851 |
///By default, it is a NullMap. |
|
| 852 | 852 |
typedef NullMap<typename Digraph::Node,bool> ProcessedMap; |
| ... | ... |
@@ -308,3 +308,3 @@ |
| 308 | 308 |
/// digraph and the maximum level should be passed to it). |
| 309 |
/// However an external elevator object could also be passed to the |
|
| 309 |
/// However, an external elevator object could also be passed to the |
|
| 310 | 310 |
/// algorithm with the \ref elevator(Elevator&) "elevator()" function |
| ... | ... |
@@ -109,3 +109,3 @@ |
| 109 | 109 |
/// This iterator goes through each node of the digraph. |
| 110 |
/// Its usage is quite simple, for example you can count the number |
|
| 110 |
/// Its usage is quite simple, for example, you can count the number |
|
| 111 | 111 |
/// of nodes in a digraph \c g of type \c %Digraph like this: |
| ... | ... |
@@ -198,3 +198,3 @@ |
| 198 | 198 |
/// of a digraph. |
| 199 |
/// Its usage is quite simple, for example you can count the number |
|
| 199 |
/// Its usage is quite simple, for example, you can count the number |
|
| 200 | 200 |
/// of outgoing arcs of a node \c n |
| ... | ... |
@@ -243,3 +243,3 @@ |
| 243 | 243 |
/// of a digraph. |
| 244 |
/// Its usage is quite simple, for example you can count the number |
|
| 244 |
/// Its usage is quite simple, for example, you can count the number |
|
| 245 | 245 |
/// of incoming arcs of a node \c n |
| ... | ... |
@@ -287,3 +287,3 @@ |
| 287 | 287 |
/// This iterator goes through each arc of the digraph. |
| 288 |
/// Its usage is quite simple, for example you can count the number |
|
| 288 |
/// Its usage is quite simple, for example, you can count the number |
|
| 289 | 289 |
/// of arcs in a digraph \c g of type \c %Digraph as follows: |
| ... | ... |
@@ -142,3 +142,3 @@ |
| 142 | 142 |
/// This iterator goes through each node of the graph. |
| 143 |
/// Its usage is quite simple, for example you can count the number |
|
| 143 |
/// Its usage is quite simple, for example, you can count the number |
|
| 144 | 144 |
/// of nodes in a graph \c g of type \c %Graph like this: |
| ... | ... |
@@ -230,3 +230,3 @@ |
| 230 | 230 |
/// This iterator goes through each edge of the graph. |
| 231 |
/// Its usage is quite simple, for example you can count the number |
|
| 231 |
/// Its usage is quite simple, for example, you can count the number |
|
| 232 | 232 |
/// of edges in a graph \c g of type \c %Graph as follows: |
| ... | ... |
@@ -274,3 +274,3 @@ |
| 274 | 274 |
/// of a certain node of a graph. |
| 275 |
/// Its usage is quite simple, for example you can compute the |
|
| 275 |
/// Its usage is quite simple, for example, you can compute the |
|
| 276 | 276 |
/// degree (i.e. the number of incident edges) of a node \c n |
| ... | ... |
@@ -371,3 +371,3 @@ |
| 371 | 371 |
/// This iterator goes through each directed arc of the graph. |
| 372 |
/// Its usage is quite simple, for example you can count the number |
|
| 372 |
/// Its usage is quite simple, for example, you can count the number |
|
| 373 | 373 |
/// of arcs in a graph \c g of type \c %Graph as follows: |
| ... | ... |
@@ -415,3 +415,3 @@ |
| 415 | 415 |
/// certain node of a graph. |
| 416 |
/// Its usage is quite simple, for example you can count the number |
|
| 416 |
/// Its usage is quite simple, for example, you can count the number |
|
| 417 | 417 |
/// of outgoing arcs of a node \c n |
| ... | ... |
@@ -463,3 +463,3 @@ |
| 463 | 463 |
/// certain node of a graph. |
| 464 |
/// Its usage is quite simple, for example you can count the number |
|
| 464 |
/// Its usage is quite simple, for example, you can count the number |
|
| 465 | 465 |
/// of incoming arcs of a node \c n |
| ... | ... |
@@ -589,3 +589,3 @@ |
| 589 | 589 |
/// |
| 590 |
/// Edges don't have source and target nodes, however methods |
|
| 590 |
/// Edges don't have source and target nodes, however, methods |
|
| 591 | 591 |
/// u() and v() are used to query the two end-nodes of an edge. |
| ... | ... |
@@ -602,3 +602,3 @@ |
| 602 | 602 |
/// |
| 603 |
/// Edges don't have source and target nodes, however methods |
|
| 603 |
/// Edges don't have source and target nodes, however, methods |
|
| 604 | 604 |
/// u() and v() are used to query the two end-nodes of an edge. |
| ... | ... |
@@ -20,3 +20,3 @@ |
| 20 | 20 |
///\file |
| 21 |
///\brief |
|
| 21 |
///\brief The concept of paths |
|
| 22 | 22 |
/// |
| ... | ... |
@@ -40,9 +40,18 @@ |
| 40 | 40 |
/// digraph. |
| 41 |
/// In a sense, a path can be treated as a list of arcs. |
|
| 42 |
/// LEMON path types just store this list. As a consequence, they cannot |
|
| 43 |
/// enumerate the nodes on the path directly and a zero length path |
|
| 44 |
/// cannot store its source node. |
|
| 45 |
/// |
|
| 46 |
/// The arcs of a path should be stored in the order of their directions, |
|
| 47 |
/// i.e. the target node of each arc should be the same as the source |
|
| 48 |
/// node of the next arc. This consistency could be checked using |
|
| 49 |
/// \ref checkPath(). |
|
| 50 |
/// The source and target nodes of a (consistent) path can be obtained |
|
| 51 |
/// using \ref pathSource() and \ref pathTarget(). |
|
| 52 |
/// |
|
| 53 |
/// A path can be constructed from another path of any type using the |
|
| 54 |
/// copy constructor or the assignment operator. |
|
| 55 |
/// |
|
| 41 | 56 |
/// \tparam GR The digraph type in which the path is. |
| 42 |
/// |
|
| 43 |
/// In a sense, the path can be treated as a list of arcs. The |
|
| 44 |
/// lemon path type stores just this list. As a consequence it |
|
| 45 |
/// cannot enumerate the nodes in the path and the zero length |
|
| 46 |
/// paths cannot store the source. |
|
| 47 |
/// |
|
| 48 | 57 |
template <typename GR> |
| ... | ... |
@@ -61,3 +70,3 @@ |
| 61 | 70 |
|
| 62 |
/// \brief Template constructor |
|
| 71 |
/// \brief Template copy constructor |
|
| 63 | 72 |
template <typename CPath> |
| ... | ... |
@@ -65,3 +74,3 @@ |
| 65 | 74 |
|
| 66 |
/// \brief Template assigment |
|
| 75 |
/// \brief Template assigment operator |
|
| 67 | 76 |
template <typename CPath> |
| ... | ... |
@@ -72,3 +81,3 @@ |
| 72 | 81 |
|
| 73 |
/// Length of the path |
|
| 82 |
/// Length of the path, i.e. the number of arcs on the path. |
|
| 74 | 83 |
int length() const { return 0;}
|
| ... | ... |
@@ -81,5 +90,5 @@ |
| 81 | 90 |
|
| 82 |
/// \brief LEMON style iterator for |
|
| 91 |
/// \brief LEMON style iterator for enumerating the arcs of a path. |
|
| 83 | 92 |
/// |
| 84 |
/// |
|
| 93 |
/// LEMON style iterator class for enumerating the arcs of a path. |
|
| 85 | 94 |
class ArcIt {
|
| ... | ... |
@@ -90,6 +99,6 @@ |
| 90 | 99 |
ArcIt(Invalid) {}
|
| 91 |
/// |
|
| 100 |
/// Sets the iterator to the first arc of the given path |
|
| 92 | 101 |
ArcIt(const Path &) {}
|
| 93 | 102 |
|
| 94 |
/// Conversion to Arc |
|
| 103 |
/// Conversion to \c Arc |
|
| 95 | 104 |
operator Arc() const { return INVALID; }
|
| ... | ... |
@@ -194,14 +203,11 @@ |
| 194 | 203 |
/// A skeleton structure for path dumpers. The path dumpers are |
| 195 |
/// the generalization of the paths. The path dumpers can |
|
| 196 |
/// enumerate the arcs of the path wheter in forward or in |
|
| 197 |
/// backward order. In most time these classes are not used |
|
| 198 |
/// directly rather it used to assign a dumped class to a real |
|
| 199 |
/// |
|
| 204 |
/// the generalization of the paths, they can enumerate the arcs |
|
| 205 |
/// of the path either in forward or in backward order. |
|
| 206 |
/// These classes are typically not used directly, they are rather |
|
| 207 |
/// used to be assigned to a real path type. |
|
| 200 | 208 |
/// |
| 201 | 209 |
/// The main purpose of this concept is that the shortest path |
| 202 |
/// algorithms can enumerate easily the arcs in reverse order. |
|
| 203 |
/// If we would like to give back a real path from these |
|
| 204 |
/// algorithms then we should create a temporarly path object. In |
|
| 205 |
/// LEMON such algorithms gives back a path dumper what can |
|
| 206 |
/// |
|
| 210 |
/// algorithms can enumerate the arcs easily in reverse order. |
|
| 211 |
/// In LEMON, such algorithms give back a (reverse) path dumper that |
|
| 212 |
/// can be assigned to a real path. The dumpers can be implemented as |
|
| 207 | 213 |
/// an adaptor class to the predecessor map. |
| ... | ... |
@@ -209,5 +215,2 @@ |
| 209 | 215 |
/// \tparam GR The digraph type in which the path is. |
| 210 |
/// |
|
| 211 |
/// The paths can be constructed from any path type by a |
|
| 212 |
/// template constructor or a template assignment operator. |
|
| 213 | 216 |
template <typename GR> |
| ... | ... |
@@ -221,3 +224,3 @@ |
| 221 | 224 |
|
| 222 |
/// Length of the path |
|
| 225 |
/// Length of the path, i.e. the number of arcs on the path. |
|
| 223 | 226 |
int length() const { return 0;}
|
| ... | ... |
@@ -229,11 +232,10 @@ |
| 229 | 232 |
/// |
| 230 |
/// If the RevPathTag is defined and true then reverse dumping |
|
| 231 |
/// is provided in the path dumper. In this case instead of the |
|
| 232 |
/// ArcIt the RevArcIt iterator should be implemented in the |
|
| 233 |
/// dumper. |
|
| 233 |
/// If this tag is defined to be \c True, then reverse dumping |
|
| 234 |
/// is provided in the path dumper. In this case, \c RevArcIt |
|
| 235 |
/// iterator should be implemented instead of \c ArcIt iterator. |
|
| 234 | 236 |
typedef False RevPathTag; |
| 235 | 237 |
|
| 236 |
/// \brief LEMON style iterator for |
|
| 238 |
/// \brief LEMON style iterator for enumerating the arcs of a path. |
|
| 237 | 239 |
/// |
| 238 |
/// |
|
| 240 |
/// LEMON style iterator class for enumerating the arcs of a path. |
|
| 239 | 241 |
class ArcIt {
|
| ... | ... |
@@ -244,6 +246,6 @@ |
| 244 | 246 |
ArcIt(Invalid) {}
|
| 245 |
/// |
|
| 247 |
/// Sets the iterator to the first arc of the given path |
|
| 246 | 248 |
ArcIt(const PathDumper&) {}
|
| 247 | 249 |
|
| 248 |
/// Conversion to Arc |
|
| 250 |
/// Conversion to \c Arc |
|
| 249 | 251 |
operator Arc() const { return INVALID; }
|
| ... | ... |
@@ -262,6 +264,7 @@ |
| 262 | 264 |
|
| 263 |
/// \brief LEMON style iterator for |
|
| 265 |
/// \brief LEMON style iterator for enumerating the arcs of a path |
|
| 266 |
/// in reverse direction. |
|
| 264 | 267 |
/// |
| 265 |
/// This class is used to iterate on the arcs of the paths in |
|
| 266 |
/// reverse direction. |
|
| 268 |
/// LEMON style iterator class for enumerating the arcs of a path |
|
| 269 |
/// in reverse direction. |
|
| 267 | 270 |
class RevArcIt {
|
| ... | ... |
@@ -272,6 +275,6 @@ |
| 272 | 275 |
RevArcIt(Invalid) {}
|
| 273 |
/// |
|
| 276 |
/// Sets the iterator to the last arc of the given path |
|
| 274 | 277 |
RevArcIt(const PathDumper &) {}
|
| 275 | 278 |
|
| 276 |
/// Conversion to Arc |
|
| 279 |
/// Conversion to \c Arc |
|
| 277 | 280 |
operator Arc() const { return INVALID; }
|
| ... | ... |
@@ -65,3 +65,3 @@ |
| 65 | 65 |
///It must conform to the \ref concepts::WriteMap "WriteMap" concept. |
| 66 |
///By default it is a NullMap. |
|
| 66 |
///By default, it is a NullMap. |
|
| 67 | 67 |
typedef NullMap<typename Digraph::Node,bool> ProcessedMap; |
| ... | ... |
@@ -780,3 +780,3 @@ |
| 780 | 780 |
///It must conform to the \ref concepts::WriteMap "WriteMap" concept. |
| 781 |
///By default it is a NullMap. |
|
| 781 |
///By default, it is a NullMap. |
|
| 782 | 782 |
typedef NullMap<typename Digraph::Node,bool> ProcessedMap; |
| ... | ... |
@@ -134,3 +134,3 @@ |
| 134 | 134 |
///It must conform to the \ref concepts::WriteMap "WriteMap" concept. |
| 135 |
///By default it is a NullMap. |
|
| 135 |
///By default, it is a NullMap. |
|
| 136 | 136 |
typedef NullMap<typename Digraph::Node,bool> ProcessedMap; |
| ... | ... |
@@ -428,3 +428,3 @@ |
| 428 | 428 |
///reference should be passed to the constructor of the heap). |
| 429 |
///However external heap and cross reference objects could also be |
|
| 429 |
///However, external heap and cross reference objects could also be |
|
| 430 | 430 |
///passed to the algorithm using the \ref heap() function before |
| ... | ... |
@@ -449,3 +449,3 @@ |
| 449 | 449 |
///\c OperationTraits type. |
| 450 |
/// For more information see \ref DijkstraDefaultOperationTraits. |
|
| 450 |
/// For more information, see \ref DijkstraDefaultOperationTraits. |
|
| 451 | 451 |
template <class T> |
| ... | ... |
@@ -998,3 +998,3 @@ |
| 998 | 998 |
///It must conform to the \ref concepts::WriteMap "WriteMap" concept. |
| 999 |
///By default it is a NullMap. |
|
| 999 |
///By default, it is a NullMap. |
|
| 1000 | 1000 |
typedef NullMap<typename Digraph::Node,bool> ProcessedMap; |
| ... | ... |
@@ -296,7 +296,5 @@ |
| 296 | 296 |
template <typename CutMap> |
| 297 |
Value minCutMap(const Node& s, |
|
| 297 |
Value minCutMap(const Node& s, |
|
| 298 | 298 |
const Node& t, |
| 299 |
///< |
|
| 300 | 299 |
CutMap& cutMap |
| 301 |
///< |
|
| 302 | 300 |
) const {
|
| ... | ... |
@@ -396,3 +394,3 @@ |
| 396 | 394 |
/// does not necessarily give the same set of nodes. |
| 397 |
/// However it is ensured that |
|
| 395 |
/// However, it is ensured that |
|
| 398 | 396 |
/// \code |
| ... | ... |
@@ -144,3 +144,3 @@ |
| 144 | 144 |
///\param ost Reference to the output stream. |
| 145 |
///By default it is <tt>std::cout</tt>. |
|
| 145 |
///By default, it is <tt>std::cout</tt>. |
|
| 146 | 146 |
///\param pros If it is \c true, then the \c ostream referenced by \c os |
| ... | ... |
@@ -514,3 +514,3 @@ |
| 514 | 514 |
|
| 515 |
///By default graphToEps() rescales the whole image in order to avoid |
|
| 515 |
///By default, graphToEps() rescales the whole image in order to avoid |
|
| 516 | 516 |
///very big or very small bounding boxes. |
| ... | ... |
@@ -1116,3 +1116,3 @@ |
| 1116 | 1116 |
///\param os Reference to the output stream. |
| 1117 |
///By default it is <tt>std::cout</tt>. |
|
| 1117 |
///By default, it is <tt>std::cout</tt>. |
|
| 1118 | 1118 |
/// |
| ... | ... |
@@ -1128,3 +1128,3 @@ |
| 1128 | 1128 |
/// |
| 1129 |
///For more detailed examples see the \ref graph_to_eps_demo.cc demo file. |
|
| 1129 |
///For more detailed examples, see the \ref graph_to_eps_demo.cc demo file. |
|
| 1130 | 1130 |
/// |
| ... | ... |
@@ -289,3 +289,3 @@ |
| 289 | 289 |
/// This class is completely static and it needs constant memory space. |
| 290 |
/// Thus you can neither add nor delete nodes or edges, however |
|
| 290 |
/// Thus you can neither add nor delete nodes or edges, however, |
|
| 291 | 291 |
/// the structure can be resized using resize(). |
| ... | ... |
@@ -429,3 +429,3 @@ |
| 429 | 429 |
/// |
| 430 |
/// By default the reader uses the first section in the file of the |
|
| 430 |
/// By default, the reader uses the first section in the file of the |
|
| 431 | 431 |
/// proper type. If a section has an optional name, then it can be |
| ... | ... |
@@ -2223,3 +2223,3 @@ |
| 2223 | 2223 |
/// |
| 2224 |
/// For example let's see a section, which contain several |
|
| 2224 |
/// For example, let's see a section, which contain several |
|
| 2225 | 2225 |
/// integers, which should be inserted into a vector. |
| ... | ... |
@@ -402,3 +402,3 @@ |
| 402 | 402 |
///\note \c ArcIt and \c OutArcIt iterators referencing the changed |
| 403 |
///arc remain valid, |
|
| 403 |
///arc remain valid, but \c InArcIt iterators are invalidated. |
|
| 404 | 404 |
/// |
| ... | ... |
@@ -414,3 +414,3 @@ |
| 414 | 414 |
///\note \c InArcIt iterators referencing the changed arc remain |
| 415 |
///valid, |
|
| 415 |
///valid, but \c ArcIt and \c OutArcIt iterators are invalidated. |
|
| 416 | 416 |
/// |
| ... | ... |
@@ -561,3 +561,3 @@ |
| 561 | 561 |
/// restored. These events invalidate the snapshot. |
| 562 |
/// However the arcs and nodes that were added to the digraph after |
|
| 562 |
/// However, the arcs and nodes that were added to the digraph after |
|
| 563 | 563 |
/// making the current snapshot can be removed without invalidating it. |
| ... | ... |
@@ -1288,3 +1288,3 @@ |
| 1288 | 1288 |
///\note \c EdgeIt iterators referencing the changed edge remain |
| 1289 |
///valid, |
|
| 1289 |
///valid, but \c ArcIt iterators referencing the changed edge and |
|
| 1290 | 1290 |
///all other iterators whose base node is the changed node are also |
| ... | ... |
@@ -1373,3 +1373,3 @@ |
| 1373 | 1373 |
/// cannot be restored. These events invalidate the snapshot. |
| 1374 |
/// However the edges and nodes that were added to the graph after |
|
| 1374 |
/// However, the edges and nodes that were added to the graph after |
|
| 1375 | 1375 |
/// making the current snapshot can be removed without invalidating it. |
| ... | ... |
@@ -148,3 +148,3 @@ |
| 148 | 148 |
|
| 149 |
/// Its usage is quite simple, for example you can count the number |
|
| 149 |
/// Its usage is quite simple, for example, you can count the number |
|
| 150 | 150 |
/// of columns in an LP \c lp: |
| ... | ... |
@@ -243,3 +243,3 @@ |
| 243 | 243 |
|
| 244 |
/// Its usage is quite simple, for example you can count the number |
|
| 244 |
/// Its usage is quite simple, for example, you can count the number |
|
| 245 | 245 |
/// of rows in an LP \c lp: |
| ... | ... |
@@ -232,6 +232,6 @@ |
| 232 | 232 |
/// values to integer keys from the range <tt>[0..size-1]</tt>. |
| 233 |
/// It can be used with some data structures, for example |
|
| 234 |
/// \c UnionFind, \c BinHeap, when the used items are small |
|
| 233 |
/// It can be used together with some data structures, e.g. |
|
| 234 |
/// heap types and \c UnionFind, when the used items are small |
|
| 235 | 235 |
/// integers. This map conforms to the \ref concepts::ReferenceMap |
| 236 |
/// "ReferenceMap" concept. |
|
| 236 |
/// "ReferenceMap" concept. |
|
| 237 | 237 |
/// |
| ... | ... |
@@ -350,5 +350,5 @@ |
| 350 | 350 |
/// |
| 351 |
/// Apart form that this map can be used in many other cases since it |
|
| 351 |
/// Apart form that, this map can be used in many other cases since it |
|
| 352 | 352 |
/// is based on \c std::map, which is a general associative container. |
| 353 |
/// However keep in mind that it is usually not as efficient as other |
|
| 353 |
/// However, keep in mind that it is usually not as efficient as other |
|
| 354 | 354 |
/// maps. |
| ... | ... |
@@ -1787,3 +1787,3 @@ |
| 1787 | 1787 |
/// that were marked \c true by an algorithm. |
| 1788 |
/// For example it makes easier to store the nodes in the processing |
|
| 1788 |
/// For example, it makes easier to store the nodes in the processing |
|
| 1789 | 1789 |
/// order of Dfs algorithm, as the following examples show. |
| ... | ... |
@@ -1802,3 +1802,3 @@ |
| 1802 | 1802 |
/// \note LoggerBoolMap is just \ref concepts::WriteMap "writable", so |
| 1803 |
/// it cannot be used when a readable map is needed, for example as |
|
| 1803 |
/// it cannot be used when a readable map is needed, for example, as |
|
| 1804 | 1804 |
/// \c ReachedMap for \c Bfs, \c Dfs and \c Dijkstra algorithms. |
| ... | ... |
@@ -1924,3 +1924,3 @@ |
| 1924 | 1924 |
/// suitable and more efficient for such cases. It provides iterators |
| 1925 |
/// to traverse the items with the same associated value, |
|
| 1925 |
/// to traverse the items with the same associated value, but |
|
| 1926 | 1926 |
/// it does not have \c InverseMap. |
| ... | ... |
@@ -3468,3 +3468,3 @@ |
| 3468 | 3468 |
/// The correct behavior of InDegMap is not guarantied if these additional |
| 3469 |
/// features are used. For example the functions |
|
| 3469 |
/// features are used. For example, the functions |
|
| 3470 | 3470 |
/// \ref ListDigraph::changeSource() "changeSource()", |
| ... | ... |
@@ -3598,3 +3598,3 @@ |
| 3598 | 3598 |
/// The correct behavior of OutDegMap is not guarantied if these additional |
| 3599 |
/// features are used. For example the functions |
|
| 3599 |
/// features are used. For example, the functions |
|
| 3600 | 3600 |
/// \ref ListDigraph::changeSource() "changeSource()", |
| ... | ... |
@@ -52,3 +52,3 @@ |
| 52 | 52 |
/// Moreover it supports both directions of the supply/demand inequality |
| 53 |
/// constraints. For more information see \ref SupplyType. |
|
| 53 |
/// constraints. For more information, see \ref SupplyType. |
|
| 54 | 54 |
/// |
| ... | ... |
@@ -61,5 +61,5 @@ |
| 61 | 61 |
/// \tparam V The value type used for flow amounts, capacity bounds |
| 62 |
/// and supply values in the algorithm. By default it is \c int. |
|
| 62 |
/// and supply values in the algorithm. By default, it is \c int. |
|
| 63 | 63 |
/// \tparam C The value type used for costs and potentials in the |
| 64 |
/// algorithm. By default it is the same as \c V. |
|
| 64 |
/// algorithm. By default, it is the same as \c V. |
|
| 65 | 65 |
/// |
| ... | ... |
@@ -70,3 +70,3 @@ |
| 70 | 70 |
/// implementations, from which the most efficient one is used |
| 71 |
/// by default. For more information see \ref PivotRule. |
|
| 71 |
/// by default. For more information, see \ref PivotRule. |
|
| 72 | 72 |
template <typename GR, typename V = int, typename C = V> |
| ... | ... |
@@ -126,6 +126,6 @@ |
| 126 | 126 |
/// of the algorithm. |
| 127 |
/// By default \ref BLOCK_SEARCH "Block Search" is used, which |
|
| 127 |
/// By default, \ref BLOCK_SEARCH "Block Search" is used, which |
|
| 128 | 128 |
/// proved to be the most efficient and the most robust on various |
| 129 | 129 |
/// test inputs according to our benchmark tests. |
| 130 |
/// However another pivot rule can be selected using the \ref run() |
|
| 130 |
/// However, another pivot rule can be selected using the \ref run() |
|
| 131 | 131 |
/// function with the proper parameter. |
| ... | ... |
@@ -133,3 +133,3 @@ |
| 133 | 133 |
|
| 134 |
/// The First Eligible pivot rule. |
|
| 134 |
/// The \e First \e Eligible pivot rule. |
|
| 135 | 135 |
/// The next eligible arc is selected in a wraparound fashion |
| ... | ... |
@@ -138,3 +138,3 @@ |
| 138 | 138 |
|
| 139 |
/// The Best Eligible pivot rule. |
|
| 139 |
/// The \e Best \e Eligible pivot rule. |
|
| 140 | 140 |
/// The best eligible arc is selected in every iteration. |
| ... | ... |
@@ -142,3 +142,3 @@ |
| 142 | 142 |
|
| 143 |
/// The Block Search pivot rule. |
|
| 143 |
/// The \e Block \e Search pivot rule. |
|
| 144 | 144 |
/// A specified number of arcs are examined in every iteration |
| ... | ... |
@@ -148,3 +148,3 @@ |
| 148 | 148 |
|
| 149 |
/// The Candidate List pivot rule. |
|
| 149 |
/// The \e Candidate \e List pivot rule. |
|
| 150 | 150 |
/// In a major iteration a candidate list is built from eligible arcs |
| ... | ... |
@@ -154,3 +154,3 @@ |
| 154 | 154 |
|
| 155 |
/// The Altering Candidate List pivot rule. |
|
| 155 |
/// The \e Altering \e Candidate \e List pivot rule. |
|
| 156 | 156 |
/// It is a modified version of the Candidate List method. |
| ... | ... |
@@ -814,3 +814,3 @@ |
| 814 | 814 |
/// |
| 815 |
/// For more information see \ref SupplyType. |
|
| 815 |
/// For more information, see \ref SupplyType. |
|
| 816 | 816 |
/// |
| ... | ... |
@@ -846,3 +846,3 @@ |
| 846 | 846 |
/// have to be set again. See \ref reset() for examples. |
| 847 |
/// However the underlying digraph must not be modified after this |
|
| 847 |
/// However, the underlying digraph must not be modified after this |
|
| 848 | 848 |
/// class have been constructed, since it copies and extends the graph. |
| ... | ... |
@@ -850,3 +850,3 @@ |
| 850 | 850 |
/// \param pivot_rule The pivot rule that will be used during the |
| 851 |
/// algorithm. For more information see \ref PivotRule. |
|
| 851 |
/// algorithm. For more information, see \ref PivotRule. |
|
| 852 | 852 |
/// |
| ... | ... |
@@ -875,3 +875,3 @@ |
| 875 | 875 |
/// \ref run() call. |
| 876 |
/// However the underlying digraph must not be modified after this |
|
| 876 |
/// However, the underlying digraph must not be modified after this |
|
| 877 | 877 |
/// class have been constructed, since it copies and extends the graph. |
| ... | ... |
@@ -267,3 +267,3 @@ |
| 267 | 267 |
/// digraph and the maximum level should be passed to it). |
| 268 |
/// However an external elevator object could also be passed to the |
|
| 268 |
/// However, an external elevator object could also be passed to the |
|
| 269 | 269 |
/// algorithm with the \ref elevator(Elevator&) "elevator()" function |
0 comments (0 inline)