14.07.2013 Views

User's guide of Proceessing Modflow 5.0

User's guide of Proceessing Modflow 5.0

User's guide of Proceessing Modflow 5.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Processing <strong>Modflow</strong> 307<br />

Appendix 3: Input Data Files <strong>of</strong> the supported Models<br />

The following tables gives the name <strong>of</strong> input data files for each packages <strong>of</strong> the supported models. The input files<br />

are saved in the same folder as the model data. Refer to the documentation <strong>of</strong> corresponding models for the format<br />

<strong>of</strong> the input files. You can find the documentions in the folder \document\ <strong>of</strong> the companion CD-ROM.<br />

Name File<br />

MODFLOW-88, MODFLOW-96 and MOC3D require a so-called Name File. The name file is also required if you<br />

want to import an existing model into PMWIN. The name file contains a list <strong>of</strong> file types, unit numbers and the<br />

associated file name.<br />

File Format<br />

1. Data: FTYPE NUNIT FNAME<br />

Explanation <strong>of</strong> Fields Used in Input Instructions<br />

ALL DATA IN THE SAME RECORD ARE SEPARATED BY A COMMA OR BLANK.<br />

FTYPE iis the file type, which must be one <strong>of</strong> the following character values. FTYPE may be entered in<br />

uppercase or lowercase.<br />

LIST for the simulation listing file<br />

BAS for the Basic Package<br />

OC for the Output Control Option<br />

BCF for the Block-Centered Flow Package<br />

RCH for the Recharge Package<br />

RIV for the River Package<br />

WEL for the Well Package<br />

DRN for the Drain Package<br />

GHB for the General-Head Boundary Package<br />

EVT for the Evapotranspiration Package<br />

SIP for the Strongly Implicit Procedure Package<br />

SOR for the Slice-Successive Over-Relaxation Package<br />

DATA(BINARY) for binary (unformatted) files such as those used to save cell-by-cell budget data<br />

and binary (unformatted) head and drawdown data.<br />

DATA for formatted (text) files such as those used to save formatted head and rawdown and<br />

for input <strong>of</strong> array data from files that are separate from the primary package input files.<br />

NUNIT is the Fortran unit to be used when reading from or writing to the file. Any legal unit number on the<br />

computer being used can be specified except units 97-99. Unit 99 is used for the name file and<br />

for reading arrays using the OPEN/CLOSE option (see Input Instructions for Array Reading Utility<br />

Modules section). Units 97 and 98 are used for batch files as explained below. Each file must have<br />

a unique unit number.<br />

FNAME is the name <strong>of</strong> the file, which is a character value.<br />

Notes:<br />

1. If you want to import a model into PMWIN, all files listed in the Name File must be located in the same<br />

folder as the Name File itself.<br />

2. Although MODFLOW allows array values <strong>of</strong> some packages (BAS, BCF, EVT and RCH) be saved in extra<br />

data files by using DATA(BINARY) or DATA, these features are not supported by the converter <strong>of</strong><br />

PMWIN. You must put the external array values into the package files before converting the model.<br />

3. An imported model will have the same model name as the Name File.<br />

Example <strong>of</strong> a Name File<br />

This example file is generated by PMWIN for the model located in \pm5\examples\basic\basic1\. The file name<br />

is basic1.nam.<br />

LIST 6 output.dat<br />

BAS 1 bas.dat<br />

BCF 11 bcf.dat<br />

OC 22 oc.dat<br />

WEL 12 wel.dat<br />

RCH 18 rch.dat<br />

Appendix 3: Input Data Files <strong>of</strong> the supported Models

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!