The name file contains one line for each input data file. This file provides the information needed to manage the input data files. MODPATH and MODPATH-PLOT prompt the user to specify the name file. The file then is opened internally within the program. Each line consists of 3 items: (1) a character string signifying the type of data file, (2) an integer file unit number, and (3) the file name. The data file is read using free format input. Any valid unit number for a given operating system may be specified. However, MODPATH reserves several numbers in the range 80 to 99 for internal use. Files can be specified in any order. For a typical simulation, the name file might look like:
main 11 main.dat
DIS 12 model.dis
data 31 ibound.1
budget 50 budget.out
head(binary) 60 head.out
The first data item on each line is a string of up to 15 characters that identifies the type of data file. The character string identifier is not case sensitive. MODPATH and MODPATH-PLOT reserve several special character strings to indicate specific data files:
MAIN = main data file
CBF = composite budget file
DIS = discretization file
DCF = drawing commands file
ENDPOINT = endpoint file
PATHLINE = pathline file
TIME-SERIES = time series file
TIME = time data file
LOCATIONS = starting locations file
BUDGET = binary (unformatted) budget file produced by MODFLOW
HEAD(BINARY) = binary (unformatted) head file produced by MODFLOW
HEAD = text head file produced by MODFLOW
DRAWDOWN(BINARY) = binary (unformatted) drawdown file produced by MODFLOW
DRAWDOWN = text drawdown file produced by MODFLOW
CONTOUR-DATA = text file containing 2-D data to contour
CONTOUR-LEVEL = text file containing contour levels
DATA = ancillary text input data files
LIST = summary output file
GUA = grid unit array file
Ancillary data files usually contain large arrays that are referenced by array control records in other data files. Ancillary data files always must be declared as type DATA. MODPATH’s data file requirements are summarized in Table A-1.
1.The MODFLOW discretization file must be included in the name file. Its file type is DIS.
2.The stress packages should no longer be included in the name file. If they are included, they will be ignored.
Table A-1. Summary of Data File Requirements
Description |
File Type Keyword |
Needed for MODPATH? |
Needed for MODPATH PLOT? |
Include in Name file? |
Main data file |
MAIN |
yes |
yes |
yes |
Composite budget file |
CBF |
transient only |
transient cross sections only |
optional3 |
Drawing commands file |
DCF |
no |
user’s option for map view plots |
optional3 |
Endpoint file |
ENDPOINT |
yes |
yes |
optional3 |
Pathline file |
PATHLINE |
pathline mode |
pathline mode |
optional3 |
Time series file |
TIME-SERIES |
time series mode |
time series mode |
optiona3 |
Time data file |
TIME |
user’s option |
no |
optional3 |
Starting locations file |
LOCATIONS |
user’s option |
no |
optional3 |
Binary budget file |
BUDGET |
yes1 |
no |
yes |
Head file (text or binary) |
HEAD HEAD(BINARY) |
yes1 |
yes2 |
yes |
Drawdown file (text or binary) |
DRAWDOWN DRAWDOWN(BINARY) |
no |
user’s option for map view plots |
yes |
Contour data file |
CONTOUR-DATA |
no |
user’s option for map view plots |
optional3 |
Contour level file |
CONTOUR-LEVEL |
no |
user’s option for map view plots |
optional3 |
Ancillary text data file |
DATA |
user’s option |
user’s option |
yes |
Summary output file |
LIST |
yes |
yes |
optional3 |
Grid unit array file |
GUA |
no |
users option |
yes |
Notes: 1. MODFLOW stress package, budget, and head files are not used by MODPATH in transient simulations that read data directly from a composite budget file.
2. The MODFLOW head file is not required by MODPATH-PLOT for some plot types. See section Plot Types in Chapter 4.
3. Users have the option of specifying these files in the name file or allowing MODPATH to prompt for file names or, in some cases, assign default file names.
