| [797] | 1 | NOTE: The information in this file might not yet include the changes introduced with the switch to the autotools. |
|---|
| 2 | |
|---|
| [2] | 3 | To build Clp see INSTALL file |
|---|
| 4 | |
|---|
| [225] | 5 | To use Clp you need the Clp and Coin libraries |
|---|
| [2] | 6 | |
|---|
| [1088] | 7 | To make standalone executable do 'make Clp' in the Clp directory. |
|---|
| 8 | This creates an executable clp in Clp/src. |
|---|
| [2] | 9 | |
|---|
| [1088] | 10 | To run unitTest do 'make unitTest' in the Clp directory. This will |
|---|
| 11 | do some minimal testing. |
|---|
| [2] | 12 | |
|---|
| [1088] | 13 | To run clp on all netlib problems do 'make unitTest NETLIBDIR=<dirname>' |
|---|
| 14 | dirname should be the path to the directory containing all the |
|---|
| 15 | netlib files. If you have compiled Clp without zlib support then the |
|---|
| 16 | files must be uncompressed. |
|---|
| 17 | |
|---|
| [349] | 18 | Running clp gives you some hints. It can do a unit test (clp -unitTest) and solve netlib |
|---|
| 19 | problems (-netlib or -netlibp using primal). It can also solve problems and set tolerances etc. Just do |
|---|
| [2] | 20 | |
|---|
| [349] | 21 | clp |
|---|
| [64] | 22 | |
|---|
| 23 | and then try ? or setting various stuff. |
|---|
| 24 | |
|---|
| [349] | 25 | clp filename reads file, does presolve and dual algorithm |
|---|
| 26 | clp filename -primalsimplex would use primal instead |
|---|
| [2] | 27 | |
|---|
| [349] | 28 | On Linux clp can do file completion and line editing if it can find history, readline and termcap.. |
|---|
| 29 | |
|---|
| [64] | 30 | If you want to stress the code you can set various stuff e.g. dantzig pricing |
|---|
| 31 | and then go into netlib testing. I do not guarantee that it will solve all |
|---|
| [102] | 32 | netlib if you get too creative. For instance using presolve makes netlib |
|---|
| 33 | solve faster - but pilot87 prefers a large infeasibility weight. So |
|---|
| [2] | 34 | |
|---|
| [102] | 35 | clp -presolve on -dualbound 1.0e10 -netlib |
|---|
| 36 | |
|---|
| 37 | works well. |
|---|
| 38 | |
|---|
| [349] | 39 | There are samples in ./Samples. To create an executable - testit do |
|---|
| [2] | 40 | |
|---|
| [349] | 41 | make DRIVER=minimum to use minimum.cpp |
|---|
| [64] | 42 | |
|---|
| [349] | 43 | or whichever driver you want. A list is in Makefile. |
|---|
| 44 | |
|---|
| 45 | Three useful samples are: |
|---|
| 46 | |
|---|
| [64] | 47 | minimum.cpp This is the simplest possible program to read an mps file. |
|---|
| [102] | 48 | |
|---|
| [64] | 49 | defaults.cpp. This does not do much more, but it does it in much more |
|---|
| 50 | complicated way by specifically setting defaults so it does give more |
|---|
| 51 | useful information. It also prints a solution in a format "similar" to that |
|---|
| 52 | of MPSX. |
|---|
| [102] | 53 | |
|---|
| 54 | presolve.cpp. This is a good driver for larger problems. |
|---|
| [349] | 55 | |
|---|
| 56 | Other ones can get complicated so start simple and work your way up. |
|---|
