This is a freeware software package, so there is little technical support. However, we are trying to make this package as useful as possible, and if you have questions or comments contact Bill Wingle at:
or
If you find software bugs, or better yet, fix software bugs, please contact us so that we can improve future releases.
The UNCERT package and the program modules within are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY. No author or distributor accepts any responsibility to anyone for the consequences of using them or for whether they serve any particular purpose or work at all, unless stated so in writing by the authors. No author or distributor accepts responsibility for the quality of data generated, nor the damage to existing data. Everyone is granted permission to copy, modify, and redistribute the UNCERT program, but only under the condition that the copyright notice in the software remain intact. The software is provided "as is" without express or implied warranty.
The UNCERT software package was written in ANSI C and FORTRAN (very little) using X-windows and motif under the UNIX operating system. Currently the software has been tested on IBM-RISC 6000, HP, Linux, Silicon Graphics (SGI), Sun OS, Sun Solaris, and SCO UNIX workstations with 8-bit color graphics cards. The software was written to be easily ported, and where possible follows ANSI-C standards. To use this software you must have:
The software may be acquired on the internet, by using anonymous ftp. The ftp site name is:
The UNCERT software is stored in the directory:
In this directory, releases with executables are available for several UNIX platforms, but only the file:
is guaranteed to be current. I have limited access to most platforms, and all versions may not be current. Check the dates on the files. The file 'uncert.tar.Z' contains the full UNCERT release, but no executable files. You will have to compile UNCERT yourself if you retrieve this file. There are also several files kept in:
that may be useful. These include public domain and shareware programs available from other locations on the internet. These versions may not be the most recent, but they may save to time trying to locate them elsewhere. These files include f2c (a FORTRAN to C preprocessor), gcc (an ANSI C compiler. You need a C compiler to build it), gs (a Postscript previewer), xv (a GIF/JPEG viewer), and gzip (a good compression utility). There are other files too.
A ftp session might look like:
user name: anonymous
password: (your e-mail address, e.g.. wwingle@mines.edu)
ftp > binary
ftp > cd /pub/wwingle/uncert
ftp> get uncert.tar.Z
ftp > quit
Once you have downloaded the UNCERT software there are several steps you need to follow to install UNCERT: 1) Unpack the software, 2) compile all the UNCERT modules (This step can to skipped if you downloaded a version with executable), and 3) set up user accounts.
Once you have downloaded the UNCERT package file, move it to the directory above where you want UNCERT stored (e.g. /usr/local). To unpack UNCERT type:
(On Linux computers use: `gzip -d uncert.tar.Z' instead of uncompress)
This will uncompress and untar UNCERT. During the tar process, all files will be put in their appropriate locations. If you get warning that directories cannot be created, you will need to download a script file called mk_uncert_dirs. This script also needs to be executed from the directory above where you want UNCERT stored. After running this command, execute the tar command given above again.
At this point you should read the README file in the uncert directory.
If you did not download a file with executable, or you have trouble with the executables you did download (e.g. cannot find shared library ..., etc.), you will have to compile UNCERT. Once the files are unpacked, change directories to the uncert directory, for example:
If you are not running on an IBM computer, you will need to setup the MakefileÕs you each module. This is done using the following command (select the appropriate command based on your system):
prompt> set_make ibm : IBM RS6000 prompt> set_make hp : HP prompt> set_make sun : Sun OS prompt> set_make sol : Sun Solaris prompt> set_make sgi : Silicon Graphics prompt> set_make sco : SCO prompt> set_make linux : Linux/Slackware
If your machine type is not listed, you will probably need to modify each Makefile in the directories:
This will mainly involve defining where the X-windows and motif library and include files are located. You may also have to define your C and FORTRAN compilers. Once the Makefile's are correctly defined, type:
This script will go into each ?/uncert/src directory and try to make each program. This may or may not work. Several things can go wrong.
2. You do not have an ANSI C compiler, or your compiler is named something other then 'cc'. If you have another compiler then 'cc', set the variable 'CC' to your compiler. If you don't have a ANSI C compiler, you can get gcc from our ftp site. gcc is a shareware C and C++ compiler. It may take some effort to compile. Note: our posted version may not be the most recent.
3. You do not have a FORTRAN compiler or your compiler is named something other then 'xlf' (or 'f77'). If you have another compiler then 'xlf' (or 'f77'), set the variable 'F77' to your compiler. If you don't have a FORTRAN compiler, you can get f2c from our ftp site. It is a shareware FORTRAN to C conversion program. You then compile the C. Contact me (Bill Wingle) if you have this problem. I'm still working on an instruction set.
4. The FORTRAN compiler does not recognize the -qextname compile option. Delete it. This is an IBM FORTRAN/C compile option.
5. In block, you cannot find su.h, segy.h, libcwp.a, libpar.a, or libsu.a. Remove the -DSU compile option. This is an option to compile SU (Seismic UNIX) which most users probably won't have.
Once you get the Makefile's corrected, you can type ÔmakeÕ in each src directory, or you can type 'build' from the ~/uncert directory.
If you are compiling on a non-supported system, I doubt that you will have to make more then a few changes to get the UNCERT modules compiled. There are a couple of important notes though.
2) On some computers (Solaris), you will get many warnings when compiling messages.c about the pixmaps being incorrectly aligned. These warnings can be ignored.
To run the programs correctly, each user will have to have several environment variables defined in there login file (ksh -> .profile, csh -> .cshrc, etc.). If you use ksh, they are defined as follows:
export PATH=$PATH:$UNCERT/bin
export UNCERT_TMPDIR=/tmp
export UNCERT_HELP_DIR=$UNCERT/help/
export XAPPLRESDIR=$UNCERT/app-defaults/
export WWWVIEWER=xhelp
setenv PATH $PATH:$UNCERT/bin
setenv UNCERT_TMPDIR /tmp
setenv UNCERT_HELP_DIR $UNCERT/help/
setenv XAPPLRESDIR $UNCERT/app-defaults/
setenv WWWVIEWER=xhelp
On SGI's you must make this substitution. In general, if your platform supports this option, it is better than XAPPLRESDIR.
You must also define a help browser. If you do not define a browser, you will still have on line text help, but no graphics for figures.We are currently developing the xhelp package, but we recommend you use netscape (Netscape Communications Corporation) or Mosaic (NCSA). These viewers may be downloaded from:
At this point netscape has more features, but it a commercial application, though they have been letting educational institutions use unlicensed versions. To define a browser other the xhelp, modify the line WWWVIEWER environment variable described above with one of the following commands:
setenv WWWVIEWER=/usr/local/netscape
setenv WWWVIEWER=/usr/local/Mosaic