107 .arcMap("length", length) |
107 .arcMap("length", length) |
108 .node("source", src) |
108 .node("source", src) |
109 .attribute("caption", title) |
109 .attribute("caption", title) |
110 .run(); |
110 .run(); |
111 \endcode |
111 \endcode |
|
112 |
|
113 Undirected graphs can be stored in LGF format in almost the same way. |
|
114 The <tt>\@arcs</tt> section can also be called <tt>\@edges</tt>, they are |
|
115 identical. The only speciality is that arc maps can be distinguished from |
|
116 edge maps using a \c + or \c - prefix before the name of the map. |
|
117 For example, |
|
118 |
|
119 \code |
|
120 @edges |
|
121 label +length -length |
|
122 0 1 0 10 20 |
|
123 ... |
|
124 \endcode |
|
125 |
|
126 In conjunction with undirected graphs, the classes \ref GraphReader and |
|
127 \ref GraphWriter can be used. |
112 |
128 |
113 Apart from LGF, the library can also handle other graph |
129 For more information, see the \ref lgf-format "description of the LGF format" |
|
130 and the \ref io_group module in the reference manual. |
|
131 For a working example, see \ref lgf_demo.cc in the demo directory |
|
132 of the LEMON source. |
|
133 |
|
134 \note Apart from LGF, the library can also handle other graph |
114 formats, such as the well-known DIMACS format. |
135 formats, such as the well-known DIMACS format. |
115 |
|
116 For more information, see a more detailed \ref lgf-format |
|
117 "description of the LGF format" and the \ref io_group module |
|
118 in the reference manual. |
|
119 |
136 |
120 [TRAILER] |
137 [TRAILER] |
121 */ |
138 */ |
122 } |
139 } |