README May 10, 1999 SHARP A quasi-three-dimensional, numerical finite-difference model to simulate freshwater and saltwater flow separated by a sharp interface in layered coastal aquifer systems SHARP - Version 1.1 1999/05/10 Instructions for installation, execution, and testing are provided below. After installation, see the file doc\sharp.txt in the SHARP installation directory for summary information on SHARP, including documentation references. For assistance, enhancement requests, or to report bugs, contact the Hydrologic Analysis Software Support Program by sending e-mail to h2osoft@usgs.gov. TABLE OF CONTENTS A. DISTRIBUTION FILES B. EXTRACTING FILES C. COMPILING D. INSTALLING E. RUNNING THE SOFTWARE F. TESTING A. DISTRIBUTION FILES The following distribution files (containing the software, test data sets, and information files) are currently available for UNIX systems: sharp1.1.DGUX.tar.gz - Compiled for Data General AViiON under DG/UX 4.11 sharp1.1.Solaris.tar.gz - Compiled for Sun UltraSPARC-II under Solaris 2.6 sharp1.1.SGI.tar.gz - Compiled for Silicon Graphics Indigo (32-bit) under Irix 6.5 sharp1.1.source.tar.gz - Source code only B. EXTRACTING FILES The compressed tar file, named sharp1.1.OS.tar.gz, contains all the files needed to install and test SHARP on a computer with a particular operating system, where OS is a string indicating the operating system the distribution is intended for. If a version is not available for your operating system, the file sharp1.1.source.tar.gz contains the source code and all other files needed to compile, install, and test the software on a UNIX-based computer. For either type of distribution, the directory sharp1.1 is created (or overwritten) when the files are extracted from the tar file. If the sharp1.1 directory already exists, you may want to delete or rename it before extracting the files. The following are the steps to extract the files from a distribution tar file. 1. If the tar file is not already in the directory under which you want the distribution installed, move it there. For example: mv sharp1.1.____.tar.gz /usr/opt/wrdapp 2. If you are not in the directory where the tar file is located, go there. For example: cd /usr/opt/wrdapp 3. Uncompress the distribution file. For example: gunzip sharp1.1.____.tar.gz 4. Extract the distribution files from the tar file. For example: tar -xvpof sharp1.1.____.tar This creates the following directory structure (the contents of each directory are shown to the right): sharp1.1 ; copy of this README file `-----bin ; compiled executable `-----doc ; documentation file `-----src ; Makefile and source code `-----test ; scripts to run verification tests `-----data ; standard data sets used in verification tests Notes: a) The bin directory is not included in the sharp1.1.source.tar.gz distribution (it is created during compilation). b) Source code is included only with the sharp1.1.source.tar.gz distribution. c) It is recommended that no user files be kept in the sharp1.1 directory structure. If you do plan to put files in the sharp1.1 directory structure, do so only by creating subdirectories of sharp1.1. C. COMPILING If a compiled version of the software is not available for your computer, or if you want to build the executable yourself, follow the instructions in this section. If you have retrieved a pre-compiled distribution of the software, skip to the Installing section below. The source code is provided in the sharp1.1.source.tar.gz distribution so that users can generate the executable themselves. No support can be provided for users generating their own versions of the software. In general, the requirements are a Fortran compiler and a minimal level of knowledge of the compiler and the UNIX operating system. As provided, the Makefile and source code are set up for use on Data General AViiON workstations running the DG/UX operating system. To generate a new executable, do the following: 1. Change directory to the source directory: cd sharp1.1/src 2. Modify the beginning of the file named Makefile to correctly specify system-dependent variables: F77 Fortran compiler name FFLAGS Fortran compiler flags 3. Use the make program to initiate compilation of the source code and installation of the software: make [BINDIR=directory_for_links] See the Installing instructions below for an explanation of BINDIR. The make will: a. create the directories sharp1.1/bin and BINDIR if they do not already exist, b. compile the source code, c. place the executable (sharp) in sharp1.1/bin, and d. place a link to the executable in BINDIR if specified. D. INSTALLING To make the executable (sharp) easy to use, it should be installed in a directory included in the user's search path. The Makefile (input instructions to the UNIX make program--located in sharp1.1/src) contains instructions to optionally place a link in a specified directory to the executable contained in sharp1.1/bin. Use the following two commands to do this: cd sharp1.1/src make install [BINDIR=directory_for_links] If BINDIR is specified, a link to the executable is placed in the specified directory. For example, if your search path consists of: /usr/bin:/usr/opt/bin:/usr/local/bin use the command: make install BINDIR=/usr/local/bin to make the executable accessible from any directory without requiring the full pathname of the software's location. Notes: a) Brackets "[xxx]" are used to indicate optional arguments to commands. b) To create and delete a link to the sharp executable, the installer must have sufficient rights in the directory that BINDIR is set to. E. RUNNING THE SOFTWARE After SHARP is properly installed in a directory that is included in your PATH, it can be executed with the command "sharp". Input data for the SHARP model is read from the file named "INPUT". Output is written to predefined output file names. F. TESTING Test data sets are provided to verify that the program is correctly installed and running on the system. The tests may also be looked at as examples of how to use the program. The directory sharp1.1/test contains the scripts to run the tests. The directory sharp1.1/data contains the input data and expected results for each test. Tests are usually run in the directory sharp1.1/test, but they can be run in any user directory if the installation procedure was completed (make install performed). Run the tests using any of the commands in the table below. To test the installation, change to the sharp1.1/test directory and type the command: ./test.sh [m [n]] If running from another directory, specify the full path to the script; for example: /usr/opt/wrdapp/sharp1.1/test/test.sh [m [n]] where: m = the number of the first test to perform, default=1 n = the number of the last test to perform, default=2 For example: command what happens ------------------ ------------------------------------ ./test.sh runs all of the tests ./test.sh n runs test 'n' through the last test ./test.sh n m runs test 'n' through 'm' After the tests are completed, the results are compared to the expected results. If all goes well, there should be no differences. To clean up after the tests, type the command: ./clean.sh NOTE: the standard data sets included with the source code in sharp1.1.source.tar.gz were created on a Data General AViiON workstation. You may notice slight numeric differences in the results on other computers. These are generally due to different round-off algorithms and the different architecture of the central processing unit chip. Also, slight differences in output formats may occur on other computers. The tests are described in the table below. Test is the test number and the usage column indicates how a file is used, with i for input and o for output. Note that file name suffixes of "t1" and "t2" have been added to the input and output files to indicate the test to which each set of files corresponds; the input and output file names do not normally bear suffixes. test description of test and files file name & usage ---- ------------------------------------- ----------------- 1 Areal model of SE Oahu SHARP input file INPUT.t1 i summary of processed data OUTPUT.t1 o final head and interface data RESULTS.t1 o observation location heads HEADS.t1 o grid block leakages LEAK.t1 o 2 Cape May cross-sectional model SHARP input file INPUT.t2 i summary of processed data OUTPUT.t2 o final head and interface data RESULTS.t2 o observation location heads HEADS.t2 o grid block leakages LEAK.t2 o