http://interval.louisiana.edu/GlobSol/install.html and also
file://<Globsol root directory>/install.html

Steps for Installing GlobSol

New: Two-step automatic self-contained installation on a native Windows system.

The following steps are contained on this page. (On some systems, some
of these steps are done automatically. Read this entire page for details.)

This page also contains the following information, that is not usually needed during an initial installation.

A thorough test of GlobSol (not usually necessary during installation)

Configuration and additional capabilities of GlobSol

Some notes on specific installations

Some reported difficulties

1. Familiarize yourself with GlobSol's components

This may be done by examining the page http://interval.louisiana.edu/GlobSol/download_GlobSol.html

2. Obtain GlobSol.zip

Obtain a copy of GlobSol.zip from the URL http://interval.louisiana.edu/GlobSol/download_GlobSol.html and put it in the installation
directory.

3. Use the "unpack" routine for your system

If your system is:

SunOS with the Sun compiler, THEN

Obtain the file unpack_sun_sun from the URL http://interval.louisiana.edu/GlobSol/unpack_sun_sun
store it in the file unpack_sun_sun in the root directory where you want to install GlobSol
set the permission of the csh script unpack_sun_sun to executable, then run unpack_sun_sun.
Go to step 6.

Microsoft Windows: Follow these special instructions
No longer supported SunOS with the NAG compiler
No longer supported SGI with the MIPS compiler
MS OS (DOS/Windows flavors) with the DEC compiler and Salford's "mk32", THEN

Obtain the file unpack_dos_dec.bat from the URL http://interval.louisiana.edu/GlobSol/unpack_dos_dec.bat
store it in the file unpack_dos_dec_mk32.bat
Check unpack_dos_dec.bat. It uses the WinZip command line utility "wzunzip", available from http://www.winzip.com/. If you do not have this, then you should change the commands to "unzip" or "pkunzip" as appropriate. Be sure the options are so directory structure in the zip file is preserved when the files are extracted.
Run unpack_dos_dec_mk32.bat.
Go to step 6.

No longer supported MS OS (DOS/Windows flavors) with the NAG/Salford compiler

4. Identify the zip file most nearly appropriate for your system

(Only do this step if your system is not one of those listed in step 3.)

The system-dependent routines are:

makefile
fmake (or fmake.bat or unix_fmake)
globsol (or globsol.bat)
glob0 (or glob0.bat)
make_f77 (or make_f77.bat)
unix_make_library (or GlobSol_objects.txt or linkfile_dos_NAG.txt)
sun_stubs.f90
dsecnd.f90

The file system_dependent.generic.zip contains only the files sun_stubs.generic.f90 and dsecnd.generic.f90.

5. Extract the appropriate archive

(Only do this step if your system is not one of those listed in step 3.) On Unix systems, be sure to use "unzip" with the "-a" option to make sure ASCII files have lines that end properly.

Rename each of the five system-dependent files to the above names. For example, makefile.sun should be renamed makefile.

6. Edit makefile

Edit the macros in makefile as indicated in the comments therein. (Only (a) below is usually required on SUN systems.)
(On Unix-based systems, the "unpack" macro may have already done part of this for you.)

IMPORTANT: One symbol that MUST be changed is ROOT. That variable should be set to the path to which the GlobSol.zip file and this install.html file are placed. (Note: The unix-based unpack scripts should automatically set this variable to the directory where the unpack script is being run, but it is wise to check it.) Other important symbols are F90, that contains the command for compiling a single subroutine with the Fortran 90 compiler (without producing executable code), and the variable LNK, that contains the command for linking compiled Fortran 90 object segments.
Other important commands are listed between lines of the form

       # ==================  EDIT HERE  =======================
       # ==================  end EDIT  =======================

You should also edit the path in the following files to be the path where GlobSol was installed.

fmake.bat (MS systems) or fmake (unix systems)
globsol.bat (MS systems) or globsol (unix systems)
glob0.bat (MS systems) or glob0 (unix systems)
create_f77.bat (MS systems) or create_f77 (unix systems)

As shipped, the path in the files for the unix-based systems are initially set to /home/rbk5287/GLOBSOL.local, whereas the files for the MS-based systems are initially set to c:\GlobSol as shipped. All instances of these strings should be changed to the desired root directory of GlobSol.

8. Set the search path

The search path for executables should be set to contain the paths

<GlobSol root directory>

and

<GlobSol root directory>/executables

On both unix and MS-based systems, this path is set by setting an environment variable such as PATH or path).

9. Run make

Issue the command

      make

or the command

      make >& make.out &

(With MS-OS and the Sun/Salford Fortran system, issue the command "mk32") This requires a fraction of an hour and a few tens of megabytes, depending on the system and compiler version.

10. Read the release notes

Read release_notes.txt, and read the general GlobSol documentation. GlobSol may now be used.

11. Do an installation test (and how to run GlobSol)

To run GlobSol's global optimization software on a particular problem, do the following.

Be sure a copy of the file GlobSol.CFG (found the subdirectory integration_test_data of the GlobSol root directory) is in the directory where you want to run GlobSol.
Provide a <problem name>.f90 and a <problem name>.DT# file, where <problem name> is any valid file name, and where "#" is a digit (1,2,3, etc.).
Issue the command

globsol

A simple test of the installation can be made by first changing to the integration_test_data subdirectory of GlobSol, then issuing the command globsol mixed 1 This command takes the files mixed.f90 and mixed.DT1 as input, and produces the file mixed.OT1 as output. The file mixed.OT1 can be compared to the corresponding golden file mixed.OT1.golden. The comparison may need to be done visually, since there can be minor differences, such as in the CPU time. However, the list of boxes and the statistics should be, for the most part, the same. If you have doubts, contact me at rbk@louisiana.edu.

A thorough test of GlobSol (not usually necessary during installation)

A thorough test of GlobSol may be done by running test_start in the integration_test_data subdirectory of the GlobSol root directory. This test is usually not necessary.

Configuration and additional capabilities of GlobSol

The user has control over tolerances, such as the final accuracy tolerance EPS_DOMAIN, the maximum number of boxes to be considered MAXITR, the maximum allowable CPU time MAX_CPU_SECONDS, and certain tolerances to control printing. These tolerances are documented in-line and may also be set in the file GlobSol.CFG. (Some of the switches and tolerances in the file GlobSol.CFG are mainly of research interest to the authors, and may be removed later.)
There are other executables built during installation. The potentially most useful ones are some tools documented in the file <GlobSol root directory>/evaluate/read.me
The global optimization procedure in GlobSol may be called as a subroutine. Examine the routines in the subdirectory f90intbi, and ask me if you have any questions.

Some notes on specific installations:

For the NAG/Salford compiler under MS-DOS (Windows 95/98), version 2.191 or later is required for successful compilation. Furthermore, with version 2.191, the routine listops\bounddns.f90 does not compile, and must be replaced by the stub in the system-specific routines. This stub does not supply functionality for specifying which box bounds are bound constraints. Thus, with this installation, no box bounds are ever considered to be bound constraints, unless they are explicitly input as inequality constraints.

Some reported difficulties:

1. On some unix systems, the build process makes object libraries using 'ranlib'. The system routine 'ranlib' should be in the path of the process running 'make'.

2. With version 6.0 of the DEC visual Fortran compiler, names of executable files passed to the loader appear to be truncated after 32 characters. For instance, if the root installation is C:\tmp\GlobSol, then the routine find_global_min.exe is to be put into C:\tmp\GlobSol\find_global_min.exe. However, what is actually produced is C:\tmp\GlobSol\find_global_.exe

3. NAG/Salford compiler version 2.191 or later is required. Also, version 2.191 has a bug in it that prevents the routine that handles bound constraints with the peeling process from being compiled. Because of this, the NAG/Salford version of GlobSol does not have the facility to handle bound constraints through the peeling process. Also because of this, problems tbills* in the integration test set (run by running test_start in the integration_test_data_directory) will give answers different from the golden files. If the integration test set is run with the NAG/Salford compiler, it is suggested to stop the process when it gets to "find_global_min < tbills.NAM".