Changeset 557 for html/trunk/Cbc/ch06.html
 Timestamp:
 May 10, 2005 11:40:19 AM (16 years ago)
 File:

 1 edited
Legend:
 Unmodified
 Added
 Removed

html/trunk/Cbc/ch06.html
r554 r557 1 <html><head><meta httpequiv="ContentType" content="text/html; charset=ISO88591"><title>Chapter 6. 2 Messages 3 </title><meta name="generator" content="DocBook XSL Stylesheets V1.61.2"><link rel="home" href="index.html" title="CBC User Guide"><link rel="up" href="index.html" title="CBC User Guide"><link rel="previous" href="ch05.html" title="Chapter 5. 4 More Samples 5 "><link rel="next" href="apa.html" title="Appendix A. FAQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. 6 Messages 7 </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="messages"></a>Chapter 6. 8 Messages 9 </h2></div></div><div></div></div><p> 10 Some of the more common messages and codes passed by CLP are listed in the 11 tables below. This is list is not meant to exhaustive. The notation is as 12 for printf from "C": 13 </p><div class="itemizedlist"><ul type="disc"><li> 14 <tt class="computeroutput">%s</tt> is a string 15 </li><li> 16 <tt class="computeroutput">%d</tt> is an integer 17 </li><li> 18 <tt class="computeroutput">%g</tt> or <tt class="computeroutput">%f</tt> 19 is a floating point value 20 </li></ul></div><div class="table"><a name="id2904621"></a><p class="title"><b>Table 6.1. 21 COIN Messages passed at or above logging level 1 22 </b></p><table summary=" 23 COIN Messages passed at or above logging level 1 24 " border="0"><colgroup><col><col><col><col></colgroup><thead><tr><th align="center"> 25 Code 26 </th><th align="center"> 27 Area 28 </th><th> </th><th align="left"> 29 Text and notes 30 </th></tr></thead><tbody><tr><td align="left"> 31 1 32 </td><td align="center"> 33 MPSREAD 34 </td><td> </td><td align="left"><tt class="computeroutput">At line %d %s</tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 35 This just prints out NAME line, ROW line, etc 36 </p></td></tr><tr><td align="left"> 37 2 38 </td><td align="center"> 39 MPSREAD 40 </td><td> </td><td align="left"><tt class="computeroutput">Problem %s has %d rows, %d columns and %d elements 41 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 42 This gives statistics after reading an MPS file 43 </p></td></tr><tr><td align="left"> 44 8 45 </td><td align="center"> 46 MPSREAD 47 </td><td> </td><td align="left"><tt class="computeroutput">%s read with %d errors 48 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 49 This gives error statistics for file 50 </p></td></tr><tr><td align="left"> 51 505 52 </td><td align="center"> 53 PRESOLVE 54 </td><td> </td><td align="left"><tt class="computeroutput"> 55 Presolved poblem not optimal, resolve after postsolve 56 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 57 This could be because it was not feasible or because of maximum 58 iterations. If this message occurs then consider using primal clean up 59 </p></td></tr><tr><td align="left"> 60 506 61 </td><td align="center"> 62 PRESOLVE 63 </td><td> </td><td align="left"><tt class="computeroutput"> 64 Presolve %d (%d) rows, %d (%d) columns and %d (%d) elements 65 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 66 The first number is the number after presolve and the number 67 in parentheses is amount of reduction 68 </p></td></tr><tr><td align="left"> 69 510 70 </td><td align="center"> 71 PRESOLVE 72 </td><td> </td><td align="left"><tt class="computeroutput"> 73 Presolve is modifying %d integer bounds and represolving 74 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 75 If presolve determines at the end that an integer variable have its bounds 76 changed then it will repeat the entrire presolve 77 </p></td></tr><tr><td align="left"> 78 511 79 </td><td align="center"> 80 PRESOLVE 81 </td><td> </td><td align="left"><tt class="computeroutput"> 82 After Postsolve, objective %g, infeasibilities  dual %g (%d), 83 primal %g (%d) 84 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 85 This gives the state after postsolve  this gives the objective value 86 and the sum of dual and primal infeasibilities with the number of 87 infeasibilities in parentheses. Hopefully these should be zero 88 </p></td></tr><tr><td align="left"> 89 512 90 </td><td align="center"> 91 PRESOLVE 92 </td><td> </td><td align="left"><tt class="computeroutput"> 93 Presolved model was optimal, full model needs cleaning up 94 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 95 If the numbers in previous message (511) were large then maybe we need to 96 know, if small then that's life 97 </p></td></tr></tbody></table></div><div class="table"><a name="id2907202"></a><p class="title"><b>Table 6.2. 98 CLP Messages passed at or above logging level 1 99 </b></p><table summary=" 100 CLP Messages passed at or above logging level 1 101 " border="0"><colgroup><col><col><col><col></colgroup><thead><tr><th align="center"> 102 Code 103 </th><th align="center"> 104 Area 105 </th><th> </th><th align="left"> 106 Text and notes 107 </th></tr></thead><tbody><tr><td align="left"> 108 1 109 </td><td align="center"> 110 SIMPLEX 111 </td><td> </td><td align="left"><tt class="computeroutput"> 112 Primal infeasible  objective value %g 113 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 114 You may need to look at previous messages or use methods. Such as 115 sumPrimalInfeasibilities() to find cause 116 </p></td></tr><tr><td align="left"> 117 2 118 </td><td align="center"> 119 SIMPLEX 120 </td><td> </td><td align="left"><tt class="computeroutput"> 121 Dual infeasible  objective value %g 122 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 123 You may need to look at previous messages or use methods. Such as 124 sumDualInfeasibilities() to find cause 125 </p></td></tr><tr><td align="left"> 126 3 127 </td><td align="center"> 128 SIMPLEX 129 </td><td> </td><td align="left"><tt class="computeroutput"> 130 Stopped  objective value %g 131 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 132 The algorithm stopped as requested by the user. 133 </p></td></tr><tr><td align="left"> 134 4 135 </td><td align="center"> 136 SIMPLEX 137 </td><td> </td><td align="left"><tt class="computeroutput"> 138 Stopped due to errors  objective value %g 139 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 140 Switch on log level 2 to see information on size of elements etc. If they 141 look reasonable then maybe we need to know. 142 </p></td></tr><tr><td align="left"> 143 5 144 </td><td align="center"> 145 SIMPLEX 146 </td><td> </td><td align="left"><tt class="computeroutput"> 147 %d Obj %g Primal inf %g (%d) Dual inf %g (%d) 148 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 149 At each refactorization this gives the number of iterations and the value 150 of the objective function. If there are primal infeasibilities then the 151 sum and number are given and similarly for dual infeasibilities. 152 (This is a simplified form of message.) 153 </p></td></tr><tr><td align="left"> 154 14 155 </td><td align="center"> 156 SIMPLEX 157 </td><td> </td><td align="left"><tt class="computeroutput"> 158 Perturbing problem by %g % of %g 159 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 160 There is more to this message but if the user sees this then s/he has 161 chosen to perturb the problem or the algorithm has decided to do so. 162 If the numbers look too large the user may wish to think again. 163 </p></td></tr><tr><td align="left"> 164 19 165 </td><td align="center"> 166 SIMPLEX 167 </td><td> </td><td align="left"><tt class="computeroutput"> 168 %d variables/rows fixed as scaled bounds too close 169 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 170 If this occurs look carefully at your input data 171 </p></td></tr><tr><td align="left"> 172 24 173 </td><td align="center"> 174 SIMPLEX 175 </td><td> </td><td align="left"><tt class="computeroutput"> 176 Matrix will be packed to eliminate small elements 177 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 178 If this occurs the user should look carefully at data. 179 </p></td></tr><tr><td align="left"> 180 26 181 </td><td align="center"> 182 SIMPLEX 183 </td><td> </td><td align="left"><tt class="computeroutput"> 184 Matrix will be packed to eliminate %d duplicate elements 185 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 186 If this occurs the user should look carefully at data. 187 </p></td></tr><tr><td align="left"> 188 28 189 </td><td align="center"> 190 SIMPLEX 191 </td><td> </td><td align="left"><tt class="computeroutput"> 192 Crash put %d variables in basis, %d dual infeasibilities 193 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 194 195 </p></td></tr><tr><td align="left"> 196 29 197 </td><td align="center"> 198 SIMPLEX 199 </td><td> </td><td align="left"><tt class="computeroutput"> 200 End of values pass after %d iterations 201 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 202 ??? If primal(1) or dual(1) the a sweep through model is made and this 203 signals end of pass. 204 </p></td></tr></tbody></table></div><div class="table"><a name="id2908139"></a><p class="title"><b>Table 6.3. 205 COIN Messages passed at or above logging level 0 206 </b></p><table summary=" 207 COIN Messages passed at or above logging level 0 208 " border="0"><colgroup><col><col><col><col></colgroup><thead><tr><th align="center"> 209 Code 210 </th><th align="center"> 211 Area 212 </th><th> </th><th align="left"> 213 Text and notes 214 </th></tr></thead><tbody><tr><td align="left"> 215 3001 216 </td><td align="center"> 217 MPSREAD 218 </td><td> </td><td align="left"><tt class="computeroutput"> 219 Illegal value for %s of %g 220 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 221 String will be "infinity" if setInfinity passed bad value, 222 or "default integer bound" if setDefaultBound passed bad value. 223 </p></td></tr><tr><td align="left"> 224 3002 225 </td><td align="center"> 226 MPSREAD 227 </td><td> </td><td align="left"><tt class="computeroutput"> 228 Bad image at line %d < %s > 229 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 230 This gives line number and the offending line 231 </p></td></tr><tr><td align="left"> 232 3003 233 </td><td align="center"> 234 MPSREAD 235 </td><td> </td><td align="left"><tt class="computeroutput"> 236 Duplicate objective at line %d < %s > 237 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 238 An objective row appears twice in one column 239 </p></td></tr><tr><td align="left"> 240 3004 241 </td><td align="center"> 242 MPSREAD 243 </td><td> </td><td align="left"><tt class="computeroutput"> 244 Duplicate row %s at line %d %s 245 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 246 The named row appears twice in one column. 247 </p></td></tr><tr><td align="left"> 248 3005 249 </td><td align="center"> 250 MPSREAD 251 </td><td> </td><td align="left"><tt class="computeroutput"> 252 No match for row %s at line %d < %s > 253 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 254 The named row did not appear in ROWS section. 255 </p></td></tr><tr><td align="left"> 256 3006 257 </td><td align="center"> 258 MPSREAD 259 </td><td> </td><td align="left"><tt class="computeroutput"> 260 No match for column at line %d < %s > 261 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 262 The named column (in BOUNDS section) did not appear in COLUMNS section. 263 </p></td></tr><tr><td align="left"> 264 6001 265 </td><td align="center"> 266 MPSREAD 267 </td><td> </td><td align="left"><tt class="computeroutput"> 268 Unable to open mps input file %s 269 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 270 271 </p></td></tr><tr><td align="left"> 272 6002 273 </td><td align="center"> 274 MPSREAD 275 </td><td> </td><td align="left"><tt class="computeroutput"> 276 Unknown image %s at line %d of file %s 277 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 278 The Mps reader could not make sense of the image file specified. 279 </p></td></tr><tr><td align="left"> 280 6003 281 </td><td align="center"> 282 MPSREAD 283 </td><td> </td><td align="left"><tt class="computeroutput"> 284 Consider the possibility of a compressed file which zlib is unable to read. 285 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 286 Some .gz files can not be read by zlib. Using gunzip and then gzip 287 normally cures problem. 288 </p></td></tr><tr><td align="left"> 289 6004 290 </td><td align="center"> 291 MPSREAD 292 </td><td> </td><td align="left"><tt class="computeroutput"> 293 EOF on file %s 294 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 295 The Mps reader did not find expected section marker. 296 </p></td></tr><tr><td align="left"> 297 6005 298 </td><td align="center"> 299 MPSREAD 300 </td><td> </td><td align="left"><tt class="computeroutput"> 301 Returning as too many errors 302 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 303 The reader has put out 100 messages and is giving up. 304 </p></td></tr><tr><td align="left"> 305 507 306 </td><td align="center"> 307 PRESOLVE 308 </td><td> </td><td align="left"><tt class="computeroutput"> 309 Presolve determined that the problem is infeasible with tolerance of %g 310 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 311 If you want you can try with a larger tolerance 312 </p></td></tr><tr><td align="left"> 313 508 314 </td><td align="center"> 315 PRESOLVE 316 </td><td> </td><td align="left"><tt class="computeroutput"> 317 Presolve thinks problem is unbounded 318 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 319 Perhaps the user should maximize if initially minimizing or vice versa. 320 </p></td></tr><tr><td align="left"> 321 509 322 </td><td align="center"> 323 PRESOLVE 324 </td><td> </td><td align="left"><tt class="computeroutput"> 325 Presolve thinks problem is infeasible AND unbounded??? 326 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 327 If you get this message we want to know 328 </p></td></tr></tbody></table></div><div class="table"><a name="id2909208"></a><p class="title"><b>Table 6.4. 329 CLP Messages passed at or above logging level 0 330 </b></p><table summary=" 331 CLP Messages passed at or above logging level 0 332 " border="0"><colgroup><col><col><col><col></colgroup><thead><tr><th align="center"> 333 Code 334 </th><th align="center"> 335 Area 336 </th><th> </th><th align="left"> 337 Text and notes 338 </th></tr></thead><tbody><tr><td align="left"> 339 3002 340 </td><td align="center"> 341 SIMPLEX 342 </td><td> </td><td align="left"><tt class="computeroutput"> 343 Not solving empty problem  %d rows, %d columns and %d elements 344 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 345 Test problem size before solving. 346 </p></td></tr><tr><td align="left"> 347 6002 348 </td><td align="center"> 349 SIMPLEX 350 </td><td> </td><td align="left"><tt class="computeroutput"> 351 %d bad bound pairs or bad objectives were found 352 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 353 Either the value in the objective was too large or a lower bound was 354 greater than an upper bound. 355 </p></td></tr><tr><td align="left"> 356 6003 357 </td><td align="center"> 358 SIMPLEX 359 </td><td> </td><td align="left"><tt class="computeroutput"> 360 Matrix has %d large values, first at column %d, row %d is %g 361 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 362 Some of the values in matrix are ridiculous. 363 </p></td></tr><tr><td align="left"> 364 6004 365 </td><td align="center"> 366 SIMPLEX 367 </td><td> </td><td align="left"><tt class="computeroutput"> 368 Can't get out of loop ... 369 </tt></td></tr><tr><td colspan="3"> </td><td align="left"><p> 370 371 </p></td></tr></tbody></table></div><p> 372 There are also messages available at log level 2 (the most likely useful relate 373 to scaling), and will be addressed in a future version of this User Guide. 374 </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. 375 More Samples 376 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix A. FAQ</td></tr></table></div></body></html> 1 <?xml version="1.0" encoding="ISO88591" standalone="no"?> 2 <html xmlns="http://www.w3.org/1999/xhtml"><head><title>Chapter 6. Cutting planes</title><meta name="generator" content="DocBook XSL Stylesheets V1.61.2"/><link rel="home" href="index.html" title="CBC User Guide"/><link rel="up" href="index.html" title="CBC User Guide"/><link rel="previous" href="ch05s03.html" title="FollowOn Branching"/><link rel="next" href="ch07.html" title="Chapter 7. Advanced Solver Uses "/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Cutting planes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05s03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch07.html">Next</a></td></tr></table><hr/></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="CutsChap"/>Chapter 6. Cutting planes</h2></div></div><div/></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="ch06.html#cuts">Using Cut Generators with CBC</a></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="cuts"/>Using Cut Generators with CBC</h2></div></div><div/></div><p> 3 In the next version of this Guide, we need to have an example illustrating how to use COIN's CGL with CBC. Contribtions are welcome. 4 5 </p></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch05s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch07.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">FollowOn Branching </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. 6 Advanced Solver Uses 7 </td></tr></table></div></body></html>
Note: See TracChangeset
for help on using the changeset viewer.