Every user with a COR@L account can access the machines listed here using her/his username and password. However, if you are outside Lehigh’s network, then you need to connect to Lehigh VPN Concentrator or use the Lehigh Linux Jumphost - ssh.lehigh.edu. Please reference the Lehigh VPN Wiki page for guidance. Once you are on the VPN or connected to the Jumphost you can connect to cluster directly from your host (vpn) or jumphost. The only host you should be connecting to for cluster work is polyps.ie.lehigh.edu

Linux users

If you are a Linux user, then logging into COR@L is straightforward. The following command uses ssh, which is typically available on standard Linux distributions:

ssh username@machinename.ie.lehigh.edu

Your COR@L username and password are the same for all machines. COR@L uses NIS to manage passwords, so passwords can be at most 8 characters long. Any extra characters will be ignored. If you wish to change your password, then do not use the passwd command. Use yppasswd instead.

Windows users

If you are using Windows and want to sign into a COR@L machine, then you need to install an ssh client first. There are several free software options. You can check Wikipedia for more information about your choices. A common free ssh client is PuTTY, which can be downloaded here. This ssh client is easy to use and it is well documented here. Another commonly used client is MobaXterm.

Back

Below is a list of the tools available for supporting optimization research at COR@L.

Solvers:

COIN-OR
CPLEX
EXPRESS
GLPK
GUROBI
MOSEK

Modeling:

AMPL
GAMS
PULP

Back

This is a description of the steps followed to install coin-or on a OS X Mountain Lion using macports:

Install macports, there is a nice installation guide in this link
Install gcc47: To do this open a terminal and type “sudo port install gcc47″.
Install subversion: “sudo port install subversion”.
Download coin-all: svn co https://projects.coin-or.org/svn/CoinBinary/CoinAll/stable/1.6 coin-all
Move to directory coin-all and do “mkdir buildmac”
Download all the Third Party sources. Got to the ThirdParty folder and run the get script for: ASL, Blas, Lapack, Mumps, Metis, Glpk
Move to the directory buildmac
Run the configure script (This command is taken from link):
../configure –disable-shared F77=gfortran-mp-4.7 FFLAGS=”-fexceptions -m64 -fbackslash” CFLAGS=”-fno-common -no-cpp-precomp -fexceptions -m64″ CXXFLAGS=”-fno-common -no-cpp-precomp -fexceptions -m64″
make tests (the DyLP test fails, rename the folder DyLP/test to DyLP/test.back if you want to run the other tests)
make install, remember that you need to use the option -prefix=/path/to/install if you want to specify a particular path to install the binaries

To submit a job to the condor pool you need a condor.sub file similar to this one:
################################################################################# # This line is important to get the license variables of mosek, cplex and others # This line is needed only once in the file getenv = TRUE # This is the standard universe, this should work fine with most of the tasks # This line is needed only once in the file Universe = vanilla # This is where you specify the executable you want to use # Advice: absolute paths will ensure that you are using the file you want Executable = mosek # This is where you put the arguments for the executable arguments = -into r12c15k5i10.sol r12c15k5i10.mps # This tells condor where to place the outputs it can generate, they are really useful to identify # if there are problems with the job you are trying to run Output = r12c15k5i10.out Error = r12c15k5i10.err Log = r12c15k5i10.log # This instruct condor to put the job in the queue queue # You can put as many jobs as you need repeating the same lines with different information # Notice that you don’t need to specify the executable again, unless you want to use a different # file
arguments = -into r12c15k5i15.sol r12c15k5i15.mps Output = r12c15k5i10.out Error = r12c15k5i10.err Log = r12c15k5i10.log queue #######################################################################################################
Once you have your condor file you can send it to the pool with the command “condor_submit condor.sub”
To check the status of the job you run “condor_q -global” and your username will appear under the column owner for the jobs you are currently running
To kill a job you use the command “condor_rm ID”, where ID is the number in the ID column of the output of condor_q associated with the job you want to remove. You can remove only those jobs you are the owner.