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. SYSTEM REQUIREMENTS B. DISTRIBUTION FILE C. INSTALLING D. COMPILING E. RUNNING THE SOFTWARE F. TESTING A. SYSTEM REQUIREMENTS - Power Macintosh, 68020 with fpu, or 68030/68040 with fpu - 4MB application RAM - 2MB disk space B. DISTRIBUTION FILE The following self-extracting Stuffit archive file in BinHex40 format (containing the software, test data sets, and information files) is currently available for Macintosh computer systems: mocv32.sea.hqx - Compiled using Language Systems Fortran with source code The archive file contains executables for the following Macintosh systems: mocv32.ppc Power Macintosh mocv32.020.fpu Macintosh 68020 with fpu mocv32.030.fpu Macintosh 68030 or 68040 with fpu The program source code consists of the following files (found in the mocv32:src folder): mocv32.f mocv32.make -- input instructions to the Language Systems compiler C. INSTALLING The mocv32 folder is created (or overwritten) when the files are extracted from the archive file. If the mocv32 folder already exists, you may want to delete or rename it before extracting the files. The following are the steps to extract the files from the archive file. 1. Move the file mocv32.sea to the folder where you want to create the mocv32 folder. 2. Double-click the file mocv32.sea. 3. Move or copy the appropriate executable from mocv32:bin into the folder where data files reside and where output files will be created. The MOC folder hierarchy is shown below (the contents of each folder are shown to the right): mocv32 ; copy of this README file `-----bin ; compiled executables `-----doc ; documentation files `-----src ; makefile and source code `-----test ; (empty) `-----data ; standard data sets used in verification tests D. COMPILING The source code is provided 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 Macintosh operating system. As provided, the makefile and source code are optimized for use on a Apple Power Macintosh personal computer using the Language Systems Fortran Compiler. E. RUNNING THE SOFTWARE The program is executed by double-clicking on the executable. The program prompts for the name of the file containing the input data for the MOC model. If the file containing input data is not located in the same folder as the executable, use the full pathname, for example, "hard_disk:mocv32:data:one-d.dat". MOC generates a file name for MOC output data and creates an output file in the folder where the input data file is located. 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 mocv32:data folder contains the input data and expected results for each test. Original output files are provided with the suffix .dg to prevent overwriting and to indicate that these files were created by running MOC on a Data General workstation. The tests are described in the table below, where '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 and o for 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 PROBLEM SET 1 -- 1-D APPROXIMATION MOC input file one-d.dat i summary of processed data one-d.out o 3 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 4 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 5 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 6 MOC ROCKY MT ARSENAL -- APPROXIMATE SOLUTION MOC control file rma.dat i summary of processed data rma.out o 7 MOC Problem Set 2 MOC control file s1.dat i summary of processed data s1.out o 8 MOC Problem Set 2 MOC control file s2.dat i summary of processed data s2.out o velocity data s2.vel o * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Good Luck! * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *