Changeset 349 for trunk/README


Ignore:
Timestamp:
Apr 9, 2004 9:38:34 AM (16 years ago)
Author:
forrest
Message:

For JP

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/README

    r225 r349  
    55To make the unitTest and standalone executable do
    66
    7 make unitTest in this directory.  This creates an executable clp.
     7make unitTest in the Clp directory (or make in Clp/test).  This creates an executable clp.in Clp
    88
    9 Running clp gives you some hints.  It can do a unit test and solve netlib
    10 problems.  It can also solve problems and set tolerances etc.  Just do
     9Running clp gives you some hints.  It can do a unit test (clp -unitTest) and solve netlib
     10problems (-netlib or -netlibp using primal).  It can also solve problems and set tolerances etc.  Just do
    1111
    12 clp -
     12clp
    1313 
    1414and then try ? or setting various stuff.
    1515
    16 On Linux clp can do file completion and line editing. 
     16clp filename   reads file, does presolve and dual algorithm
     17clp filename -primalsimplex would use primal instead
     18
     19On Linux clp can do file completion and line editing if it can find history, readline and termcap.. 
    1720
    1821If you want to stress the code you can set various stuff e.g. dantzig pricing
     
    2528works well.
    2629
    27 There are samples in ./Samples.  Use the corresponding Makefile to
    28 create an executable - testit.  For later ones do "make DRIVER=sprint" etc.
     30There are samples in ./Samples.  To create an executable - testit do
    2931
    30 At present there are only three useful samples.
     32make DRIVER=minimum to use minimum.cpp
     33
     34or whichever driver you want.  A list is in Makefile.
     35
     36Three useful samples are:
    3137
    3238minimum.cpp  This is the simplest possible program to read an mps file.
     
    3844
    3945presolve.cpp.  This is a good driver for larger problems.
     46
     47Other ones can get complicated so start simple and work your way up.
Note: See TracChangeset for help on using the changeset viewer.