December 18, 1996 MOCV32 - Version: 3.2.2 1996/01/22 Method Of Characteristics ground-water flow and transport model For assistance, enhancement requests, or bug reports contact the Hydrologic Analysis Software Support Team via email at h2osoft@usgs.gov. See the file doc/moc.txt for descriptions, references, and additional contacts for this software. Instructions for installation, execution, and testing are provided below. TABLE OF CONTENTS A. FILES B. EXTRACTING FILES C. COMPILING D. INSTALLING E. RUNNING THE SOFTWARE F. TESTING A. FILES The following self-extracting DOS distribution files (containing the software, test data sets, and information files) are currently available. mocv32.exe - Compiled using Lahey Fortran 90 with source code mocv32b.exe - Compiled using Lahey Fortran 90 (binaries only) mocv32s.exe - Source code For use on personal computers, the program source code consists of the following files (found in the mocv32\src directory): mocv32.for makefile -- input instructions to the Lahey "make" utility for compiling MOC B. EXTRACTING FILES For whichever MOC distribution file that you have acquired, mocv32.exe, mocv32b.exe, or mocv32s.exe, the directory mocv32 is created (or overwritten) when the files are extracted. If the mocv32 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 file. Note, replace with the drive letter where you want to install MOC and optionally replace [directory] with the name of a directory on that drive: 1. If you are not in the directory where the distribution file is located, go there. For example (if already on the C disk drive): cd c:\wrdapp 2. Extract the files using the command: mocv32 -d -o :\[directory] Substitute "mocv32b" or "mocv32s" for "mocv32" if you are installing the executable-code-only or source-code distributions, respectively. Note, be sure to include the -d (restore directory structure) and -o (overwrite existing files) options and ":\" in the command. Examples are: mocv32 -d -o c:\ mocv32 -d -o c:\wrdapp The following directory structure will be created (the contents of each directory are shown to the right): mocv32 ; copy of this readme file `-----bin ; compiled executable and Lahey error file `-----doc ; documentation files `-----src ; makefile and source code `-----test ; batch files to run verification tests `-----data ; standard data sets used in verification tests Notes: a) The executable is not included in the mocv32s.exe distribution file. b) The source code is not included in the mocv32b.exe distribution file. c) It is recommended that no user files are kept in the mocv32 directory structure. If you do plan to put files in the mocv32 directory structure, do so only by creating subdirectories of mocv32. d) Brackets "[xxx]" are used to indicate optional arguments to commands. C. COMPILING The source code is provided in the mocv32.exe and mocv32s.exe distribution files 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 DOS operating system. As provided, the makefile and source code are optimized for use on a Pentium personal computer using the Lahey Fortran 90 compiler and supplied make program. To generate a new executable, do the following: 1. Change directory to the source directory: cd mocv32\src 2. Modify the beginning of the file named makefile to correctly specify system-dependent variables: FFLAGS Fortran compiler flags FC Fortran compiler name LINKER Fortran linker name LNKFLGS Fortran linker flags 3. Use the make program to initiate compilation of the source code and installation of the software: make [BINDIR=directory_for_executable] See the Installing instructions below for an explanation of BINDIR. The make will: a. create the directory mocv32\bin if it does not exist, b. compile the source code, c. place the executable (mocv32.exe) in mocv32\bin, and d. place a copy of the executable in BINDIR if specified. D: INSTALLING To make the MOC program accessible from any directory, the directory containing the executable should be included in the PATH environment variable. For example, you could add a line similar to the following to the AUTOEXEC.BAT file: PATH=%PATH%;C:\mocv32\bin Note, substitute the appropriate drive letter and pathname if not C:\ as shown above. As an alternative, the MOC executable can be installed in a directory already included in the PATH environment variable. The makefile (input instructions to the Lahey make program--located in mocv32\src) contains instructions to optionally place a copy of the executable contained in mocv32\bin in a specified directory. Use the following two commands to do this: cd moc_source_directory make install BINDIR=directory_for_executable For example: cd C:\mocv32\src make install BINDIR=C:\wrdapp\bin Note, the makefile may need to be modified to be used with make programs other than the Lahey make program. E. RUNNING THE SOFTWARE **System Requirements** - 386-based or higher personal computer with math co-processor - 8 MB application RAM - 20 MB disk space MOC has been compiled using the Lahey Fortran 90 extended memory compiler version 3.00f. The file "LF90.EER" (from the Lahey compiler) located in mocv32\bin contains error messages. If an error occurs, this file is used to print error messages if the mocv32\bin directory is included in the PATH environment variable; if LF90.ERR cannot be found, the error will only be identified by number. After MOC is properly installed in a directory that is included in your PATH, the program is initiated using the command: mocv32. The program prompts for the name of the file containing the input data for the MOC model. MOC generates a file name for MOC output data. If this file does not exist the simulation begins. If the output file exists, you are prompted whether to overwrite the file or quit. 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 mocv32\test contains batch files to run the tests. The directory mocv32\data contains the input data and expected results for each test. Run the tests in the mocv32\test directory using the command: test After the tests are completed, the results can be compared to the expected results. To clean-up after the tests, type the command: clean The tests are described in the table below. Test is the test number, program is the program used to run the test, and the usage column indicates how a file is used, with i for input, o for output, and i/o for both input and output. test program description of test and files file name & usage ---- ------- --------------------------------- ----------------- 1 MOC ROCKY MT ARSENAL -- APPROXIMATE SOLUTION MOC control file rmabig.dat i summary of processed data rmabig.out o final concentration data rmabig.cn1 o 2 MOC 60X60 GRID MOC control file big60.dat i summary of processed data big60.out o final concentration data big60.cn1 o 3 MOC PROBLEM SET 1 -- 1-D APPROXIMATION MOC input file one-d.dat i summary of processed data one-d.out o 4 MOC Problem Set 2 MOC control file prob2.dat i summary of processed data prob2.out o initial concentration data prob2.cn0 o final concentration data prob2.cn1 o initial hydraulic head data prob2.hd0 o final hydraulic head data prob2.hd1 o observation well data prob2.obs o hydraulic conductivity data prob2.prm o diffuse recharge/discharge data prob2.rec o saturated thickness data prob2.thk o transmissivity data prob2.trn o velocity data prob2.vel o 5 MOC TEST PROBLEM NO. 3 (STEADY FLOW, 1 WELL, CONSTANT-HEAD BOUNDARIES) MOC control file prob3_78.dat i summary of processed data prob3_78.out o 6 MOC Problem 3 (Steady flow, 1 well, constant-head boundaries, linear sorption) MOC control file prob3_94.dat i summary of processed data prob3_94.out o initial concentration data prob3_94.cn0 o final concentration data prob3_94.cn1 o observation well data prob3_94.o1 o observation well data prob3_94.o2 o 7 MOC ROCKY MT ARSENAL -- APPROXIMATE SOLUTION MOC control file rma.dat i summary of processed data rma.out o 8 MOC Problem Set 2 MOC control file s1.dat i summary of processed data s1.out o 9 MOC Problem Set 2 MOC control file s2.dat i summary of processed data s2.out o velocity data s2.vel o * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Good Luck! * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *