/*! \page Installation Installation Instructions. The compressed files \p DSDP5.X.tar.gz and \p DSDP5.X.zip contain an implementation of the dual-scaling algorithm for conic programming optimization problems. Create the \p DSDP5.X directory structure and enter it. For example, \verbatim gunzip DSDP5.X.tar.gz tar -xvf DSDP5.X.tar \endverbatim or \verbatim unzip DSDP5.X.zip \endverbatim Several executables may have been provided. If not, it will have to be compiled. DSDP is written in the C programming language. It has been tested using several different compilers and architectures. In particular, it has been tested using gcc-2.96 and gcc-3.2 (C and C++), Intel-6.0, Intel-7.1, Intel-8.0, and Microsoft Visual Studio 2003. It has been compiled on 32 bit and 64 bit architectures. \section Compile Compiling DSDP \subsection Make Using Make DSDP was developed using Make -- which is available on Linux and most Unix systems. To compile DSDP using Make - Go to the DSDP directory and edit the file \p make.include - Go to the DSDP directory \verbatim > cd DSDP5.X \endverbatim - Define the \p DSDPROOT variable as the full directory name. For example, \verbatim DSDPROOT = /home/benson/DSDP5.X \endverbatim For those using the GCC compilers, the default values for the remaining variables may suffice. - Edit the compiler flags \p CC and \p OPTFLAGS. For example, \verbatim CC = gcc \endverbatim - Edit the compiler optimization flag \verbatim OPTFLAGS = -O3 \endverbatim - Add timing flag. By default, timing routines are not implemented due to portability issues among architectures. However, DSDP can provide time profiles for several important operations by defining one of the following variables. \verbatim DSDPTIMER = NONE \endverbatim Users of the Microsoft compiler will probably need the flags \verbatim DSDPTIMER = DSDP_MS_TIME \endverbatim Users of the GCC and many other compilers should consider defining \verbatim DSDPTIMER = DSDP_TIME \endverbatim The routines that call these two timing utilities can be found in the file \p dsdptime.c and edited. - Add additional compiler flags. See the next section for more information about specific compiler flags. - If the Matlab interface is required, also check and edit the \p MEX flag. For example, \verbatim MEX = mex -O \endverbatim - In the same file, edit the location of the BLAS and LAPACK libraries and include any other libraries required to link to them such as \p -lg2c or \p -lm. For example, \verbatim LAPACKBLAS = -llapack -lblas -lg2c -lm \endverbatim Linking to a fast implementations of these libraries, such as ATLAS or Intel, will significantly improve performance. - Compile the source code to create the DSDP library and drivers. \verbatim > make all \endverbatim Alternatively, to compile just the DSDP Matlab routine: \verbatim > make dsdpmatlab \endverbatim Alternatively, to compile just the DSDP library and C examples: \verbatim > make dsdpapi \endverbatim If the DSDP Matlab mex function does not link with the library, try the next method of compilation. If problems persist, please send a copy of the compilation log to the developers. \subsection NoMake Without Make DSDP can also be compiled by copying all of the source and header files into another directory, compiled, and linked with a driver routine (such as one of the files in \p DSDPROOT/examples/ ). This process is demonstrated in the \p dsdpagain target in \p DSDPROOT/examples/Makefile. This method neglects the directory structure of the source code and the Makefile system, but it works fine. \section Flags Compiler Flags \subsection blas BLAS and LAPACK DSDP uses BLAS and LAPACK for many of the underlying operations and it must be linked to these libraries. Two of the eigenvalue routines require LAPACK version 3 or later. The routines in BLAS and LAPACK are called from the C programming language under the assumption that the routine names are lower case and end with an underscore. The most common linking problem occurs when these assumptions are not true. Several compiler flags can be defined to change these assumptions. Define - Define \p NOUNDERBLAS if no underscore is appended to the end of routine names. This flag was used to link DSDP to the reference BLAS available in Matlab using the Microsoft Compiler. - Define \p CAPSBLAS if the names of BLAS and LAPACK routine names use all capital letters. - Define \p __DSDP_NONAMEMANGLING if a C++ compiler is being used and the BLAS and LAPACK routine names should not be changed. See the makefiles in the distribution for examples of use of these terms. Those compiling in the Microsoft Windows Operating System usually need to define the \p NOUNDERBLAS flag. DSDP also assumes that the \p integer type in Fortran is the same size as a \p long \p int in C, and a \p double \p precision variable in Fortran is the same size as a \p double in C. If problems persist, the macros and type definitions in the file \p dsdplapack.h will have to be edited. \subsection matlab Matlab If the Matlab interface is be generated, one other flag may be of interest. - \p DSDPMATLAB enables the use of the memory allocation and additional print statements available from Matlab. The standard memory allocation and print statements will be used if this flag is not defined. \section testing Testing - Run the executables by switching to directory \p DSDPROOT/exec and test the examples. \verbatim > dsdp5 truss1.dat-s > maxcut graph1 > theta graph1 \endverbatim Compare the output with the files \p output.truss1 , \p output.maxcut , and \p output.theta . If the output from any of the tests differs significantly from the files, please report it to the developers. - DSDP can be called from Matlab version 6.0 and higher. Run the sample problems by starting Matlab in the \p DSDPROOT/matlab directory and test the solver \verbatim > check; \endverbatim Compare the output with the output in \p check.out . For help using the package, type \verbatim > help dsdp; \endverbatim Several example Matlab files have been provided in \p DSDPROOT/matlab that create example problems, read data files, and verify solutions. \section Help For help with installation, please send a copy of the compilation log to the developers. */