October 9, 1997
MODFLOWP
Parameter-Estimation Version of the Modular Model
MODFLOWP - Version: 3.2 1997/10/09
RESANP - Version: 3.2 1997/07/24
BCINT - Version: 3.1 1997/07/24
YCINT - Version: 3.1 1997/07/24
BEALEP - Version: 3.1 1997/07/24
For assistance, enhancement requests, or bug reports contact the Hydrologic
Analysis Software Support Team via email at h2osoft@usgs.gov. See the file
doc\Modflowp.txt for descriptions, references, and additional contacts for
this software. Instructions for installation, execution, and testing are
provided below.
This version of MODFLOWP is packaged for use on personal computers using the
DOS operating system. The installation procedures and the compiled
version of MODFLOWP must be run using either DOS directly or a DOS window
within Microsoft Windows, Windows 95, or Windows NT.
TABLE OF CONTENTS
A. SYSTEM REQUIREMENTS
B. DISTRIBUTION FILES
C. EXTRACTING FILES
D. COMPILING
E. INSTALLING
F. RUNNING THE SOFTWARE
G. TESTING
A. SYSTEM REQUIREMENTS
For installation of MODFLOWP, 5.0 megabytes of free disk space is needed.
To run MODFLOWP, the following are necessary:
- 386 or greater processor
- math coprocessor
- 8 megabytes of combined free extended memory and free disk space
on installation drive (the greater proportion available as memory,
the better performance will be)
- at least 40K free disk space in current working directory
You must also allow for at least 50 files to be opened at one time.
CONFIG.SYS must contain a line such as
FILES=50
NOTE: Reboot your system if you modify CONFIG.SYS.
B. DISTRIBUTION FILES
The following self-extracting DOS distribution files (containing the software,
test data sets, and information files) are currently available.
mdfp32.exe - Compiled using Lahey Fortran 90 with source code
mdfp32b.exe - Compiled using Lahey Fortran 90 (binaries only)
mdfp32s.exe - Source code
For use on personal computers, the program source code consists of the
following files (found in the Modflwp3.2\src directory):
adv1.for chd1.for hfb1.for rch5.for sor5.for util.for
bas5p.for de45p.for ibs1.for res1.for spar.for utl5.for
bcf1.for drn5p.for modflowp.for resanp.for ssen-ai.for wel5.for
bcf5p.for evt5p.for obs.for riv5p.for ssen-jz.for ycint.for
bcint.for gfd1.for par.for sen.for str5p.for
bealep.for ghb5p.for pcg2.for sip5.for tlk1.for
makefile -- input instructions to the Lahey "make" utility for
compiling MODFLOWP
C. EXTRACTING FILES
For whichever MODFLOWP distribution file that you have acquired, mdfp32.exe,
mdfp32b.exe, or mdfp32s.exe, the directory Modflwp3.2 is created (or
overwritten) when the files are extracted. If the Modflwp3.2 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 MODFLOWP 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:
mdfp32 -d -o [:\[directory]]
Substitute "mdfp32b" or "mdfp32s" for "mdfp32" 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. The default
path to install to is the current directory. If you specify a
a path to install to be sure to include ":\" in your specification.
Examples are:
mdfp32 -d -o
mdfp32 -d -o c:\
mdfp32 -d -o c:\wrdapp
The following directory structure will be created (the contents of each
directory are shown to the right):
Modflwp3.2 ; 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 mdfp32s.exe distribution file.
b) The source code is not included in the mdfp32b.exe distribution file.
c) It is recommended that no user files are kept in the Modflwp3.2 directory
structure. If you do plan to put files in the Modflwp3.2 directory
structure, do so only by creating subdirectories of Modflwp3.2.
d) Brackets "[xxx]" are used to indicate optional arguments to commands.
D. COMPILING
The source code is provided in the mdfp32.exe and mdfp32s.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 Modflwp3.2\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 Modflwp3.2\bin if it does not exist,
b. compile the source code,
c. place the executable (modflowp.exe) in Modflwp3.2\bin, and
d. place a copy of the executable in BINDIR if specified.
E: INSTALLING
To make the MODFLOWP 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:\Modflwp3.2\bin
Note, substitute the appropriate drive letter and pathname if not C:\
as shown above.
As an alternative, the MODFLOWP 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 Modflwp3.2\src) contains
instructions to optionally place a copy of the executable contained in
Modflwp3.2\bin in a specified directory. Use the following two commands to
do this:
cd modflowp_source_directory
make install BINDIR=directory_for_executable
For example:
cd C:\Modflwp3.2\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
MODFLOWP has been compiled using the Lahey Fortran 90 extended memory
compiler version 2.01h. The file "LF90.EER" (from the Lahey compiler)
located in Modflwp3.2\bin contains error messages. If an error occurs,
this file is used to print error messages if the Modflwp3.2\bin directory
is included in the PATH environment variable; if LF90.ERR cannot be found,
the error will only be identified by number.
The X array is dimensioned to 5,000,000. This is large enough for a model
having approximately 250,000 cells.
After MODFLOWP is properly installed in a directory that is included in your
PATH, the program is initiated using the command: Modflowp. MODFLOWP prompts
the user to enter the name of the Name File, and then it automatically opens
all the files specified in the Name File. Each record of the Name File
specifies a file type, unit number, and file name for each file used in the
MODFLOWP simulation. In addition to defining the file names and unit numbers,
the Name File activates packages. That is, the IUNIT elements that correspond
to the packages indicated by the file types are turned "on". The IUNIT record
in the BAS Package input file is ignored; packages can now only be
activated through the Name File. The Name File is read on unit 99, so
this unit should not be used for any other model files. Refer to the
MODFLOW-96 documentation (USGS Open-File Report 96-485) for details
about preparing the Name File. An example of a Name File follows:
list 4 tc2.lsp
bas 5 ..\data\tc2.bas
par 16 ..\data\tc2.par
data 10 ..\data\tc2.bnd
data 12 ..\data\tc2.shd
oc 11 ..\data\tc2.out
bcf 7 ..\data\tc2.bcf
riv 15 ..\data\tc2.riv
rch 31 ..\data\tc2.rch
wel 8 ..\data\tc2.wel
pcg 9 ..\data\tc2.pcg
data 13 tc2.b
data 35 tc2.res
G. 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 Modflwp3.2\test
contains batch files to run the tests. The directory Modflwp3.2\data
contains the input data and expected results for each test. Run the
tests in the Modflwp3.2\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 Modflowp TEST CASE 1, TWO-LAYER EXAMPLE
Steady State
Name File to designate files tc1ss.fil i
MODFLOW basic data tc1ss.bas i
Block-Centered Flow data tc1ss.bcf i
Streams Package data tc1ss.str i
General-Head Boundary data tc1ss.ghb i
Recharge Package data tc1ss.rch i
Preconditioned Conjugate-Gradient tc1.pcg i
Output control data tc1ss.out i
BCF data array tc1file.18 i
recharge array tc1arr.rch i
Program results tc1ss.lsp o
head data results tc1ss.hds o
2 Modflowp TEST CASE 1, TWO-LAYER EXAMPLE
Transient
Name File to designate files tc1tr.fil i
MODFLOW basic data tc1tr.bas i
Block-Centered Flow data tc1tr.bcf i
Well data tc1tr.wel i
Streams Package data tc1tr.str i
General-Head Boundary data tc1tr.ghb i
Recharge Package data tc1tr.rch i
recharge array tc1arr.rch i
Preconditioned Conjugate-Gradient tc1.pcg i
Output control data tc1tr.out i
Steady-state head data tc1tr.hds i
BCF data array tc1file.18 i
Program results tc1tr.lsp o
3 Modflowp TEST CASE 1, TWO-LAYER EXAMPLE
Parameter Estimation
Name File to designate files tc1.fil i
MODFLOW basic data tc1.bas i
parameter data tc1.par i
Output control data tc1.out i
Block-Centered Flow data tc1.bcf i
Recharge Package data tc1.rch i
recharge array tc1arr.rch i
Well data tc1.wel i
General-Head Boundary data tc1.ghb i
Streams Package data tc1.str i
DE45 Package data tc1.de4 i
Program results tc1.lsp o
Restart data tc1.res o
head data results tc1.b o
4 Modflowp TEST CASE 2, ONE-LAYER EXAMPLE
Steady state, without parameter estimation
Name File to designate files tc2ss.fil i
MODFLOW basic data tc2ss.bas i
Boundary condition data (file 10) tc2.bnd i
File 12 for basic input data tc2.shd i
Output control data tc2.out i
Block-Centered Flow data tc2.bcf i
River Package data tc2.riv i
Recharge Package data tc2.rch i
Well data tc2.wel i
Preconditioned Conjugate-Gradient tc2.pcg i
Program results tc2ss.lsp o
5 Modflowp TEST CASE 2, ONE-LAYER EXAMPLE
with parameter estimation
Name File to designate files tc2.fil i
MODFLOW basic data tc2.bas i
parameter data tc2.par i
Boundary condition data (file 10) tc2.bnd i
File 12 for basic input data tc2.shd i
Output control data tc2.out i
Block-Centered Flow data tc2.bcf i
River Package data tc2.riv i
Recharge Package data tc2.rch i
Well data tc2.wel i
Preconditioned Conjugate-Gradient tc2.pcg i
Program results tc2.lsp o
head data results tc2.b o
Restart data tc2.res o
6 Modflowp Runs the storage depletion test problem in OFR 88-482
Name File to designate files ibs.fil i
BAS5 Package ibs.bas i
BCF5 Package ibs.bcf i
SIP5 Package ibs.sip i
Output Control ibs.oc i
IBS1 Package ibs.ibs i
Listing of results ibs.lst o
7 Modflowp Runs the example problem in OFR 88-729
Name File to designate files str.fil i
BAS5 Package str.bas i
BCF5 Package str.bcf i
SIP5 Package str.sip i
Output Control str.oc i
STR1 Package str.str i
Listing of results str.lst o
8 Modflowp Runs the problem in Appendix D of TWRI 6-A1
Name File to designate files twri.fil i
BAS5 Package twri.bas i
BCF5 Package twri.bcf i
WEL1 Package twri.wel i
DRN5 Package twri.drn i
RCH5 Package twri.rch i
SIP5 Package twri.sip i
Listing of results twri.lst o
9 Modflowp Runs problem 1 in OFR 91-536
Name File to designate files bcf2ss.fil i
BAS5 Package bcf2ss.bas i
BCF5 Package bcf2ss.bcf i
WEL1 Package bcf2ss.wel i
RIV5 Package bcf2ss.riv i
RCH5 Package bcf2ss.rch i
PCG2 Package bcf2ss.pcg i
Output Control bcf2ss.oc i
listing of results bcf2ss.lst o
10 Modflowp Runs the first problem in OFR 94-59
Name File to designate files tlkp1.fil i
BAS5 Package tlkp1.bas i
BCF5 Package tlkp1.bcf i
TLK1 Package tlkp1.tlk i
SIP5 Package tlkp1.sip i
Output Control tlkp1.oc i
Listing of results tlkp1.lst o
cell-by-cell flows, storage tlkp1.bud o
drawdown and heads results tlkp1.ddn o
11 Modflowp Runs the example problem in OFR 96-364
Name File to designate files restest.fil i
BAS5 Package restest.bas i
BCF5 Package restest.bcf i
GHB5 Package restest.ghb i
SIP5 Package restest.sip i
Output Control restest.oc i
RES1 (Reservoir) Package restest.res i
Listing of results restest.lst o
12 Modflowp Runs the Otis Air Force Base Test Problem 2
Name File to designate files adv1.fil i
ADV1 Package adv1.adv i
BAS5 Package adv1.bas i
BCF5 Package adv1.bcf i
GHB5 Package adv1.ghb i
Output Control adv1.oc i
parameter data adv1.par i
PCG2 Package adv1.pcg i
RCH5 Package adv1.rch i
RIV5 Package adv1.riv i
File 12 for basic input data adv1.shd i
THK data adv1.thk i
bottom data adv1.bot i
top data adv1.top i
WEL5 Package adv1.wel i
head data results adv1.b o
Listing of results adv1.lsp o
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Good Luck!
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *