Please enable JavaScript to view this site.

ModelMuse Help

Navigation: Online Guide to MODFLOW

Name File

Scroll Prev Top Next More

Purpose

The Name File specifies the names of the input and output files, associates each file name with a unit number and identifies the packages that will be used in the model.

Documentation

Harbaugh, A.W., Banta, E.R., Hill, M.C., and McDonald, M.G., 2000, MODFLOW-2000, the U.S. Geological Survey modular ground-water model -- User guide to modularization concepts and the Ground-Water Flow Process: U.S. Geological Survey Open-File Report 00-92, 121 p.

release.txt

ofr-00-92-errata.pdf

Hanson, R.T., Boyce, S.E., Schmid, Wolfgang, Hughes, J.D., Mehl, S.M., Leake, S.A., Maddock, Thomas, III, and Niswonger, R.G., 2014, One-Water Hydrologic Flow Model (MODFLOW-OWHM): U.S. Geological Survey Techniques and Methods 6–A51, 120 p., https://dx.doi.org/10.3133/tm6A51.

Supported in

MODFLOW-2000

MODFLOW-2005

MODFLOW-LGR

MODFLOW-CFP

MODFLOW-NWT

Other Notes

Space characters are not allowed in Fname.

Lines in the name file are limited to 300 characters.

Input Instructions

The name file contains the names of most input and output files used in a model simulation and controls the parts of the model program that are active. (“OPEN/CLOSE” files, described in the Input Instructions for Array Reading Utility Modules section, are not included in the name file.) The name file is read on unit 99. The name file is constructed as follows.

FOR EACH SIMULATION

Data Set 1

Ftype Nunit Fname  [LSTLVL] [Option]

The name file contains one of the above records (item 1) for each file. All variables are free format. The length of each record must be 199 characters or less. The records can be in any order except for records where Ftype (file type) is “GLOBAL” or “LIST” as described above.

Comment records are indicated by the # character in column one and can be located anywhere in the file. Any text characters can follow the # character. Comment records have no effect on the simulation; their purpose is to allow users to provide documentation about a particular simulation. All comment records after the first item-1 record are written in the listing file.