Manual Modflow 6 101 150

Groundwater Flow (GWF) Model Input 89
Recharge (RCH) Package – List-Based Input

Input to the Recharge (RCH) Package is read from the file that has type “RCH6” in the Name File. Any
number of RCH Packages can be specified for a single groundwater flow model.
Recharge input can be specified using lists or arrays, unless the DISU Package is used. List-based input
must be used if discretization is specified using the DISU Package. List-based input for recharge is the default,
and is described here. Instructions for specifying array-based recharge are described in the next section.
List-based input offers several advantages over the array-based input for specifying recharge. First, multi-
ple list entries can be specified for a single cell. This makes it possible to divide a cell into multiple areas, and
assign a different recharge rate for each area (perhaps based on land use or some other criteria). In this case,
the user would likely specify an auxiliary variable to serve as a multiplier. This multiplier would be calculated
by the user and provided in the input file as the fractional cell are for the individual recharge entries. Another
advantage to using list-based input for specifying recharge is that boundnames can be specified. Boundnames
work with the Observations capability and can be used to sum recharge rates for entries with the same bound-
name. A disadvantage of the list-based input is that one cannot easily assign recharge to the entire model
without specifying a list of model cells. For this reason MODFLOW 6 also supports array-based input for
recharge.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
[FIXED_CELL]
[AUXILIARY <auxiliary(naux)>]
[AUXMULTNAME <auxmultname>]
[BOUNDNAMES]
[PRINT_INPUT]
[PRINT_FLOWS]
[SAVE_FLOWS]
[TS6 FILEIN <ts6_filename>]
[OBS6 FILEIN <obs6_filename>]
END OPTIONS
BEGIN DIMENSIONS
MAXBOUND <maxbound>
END DIMENSIONS
FOR ANY STRESS PERIOD

BEGIN PERIOD <iper>
<cellid(ncelldim)> <recharge> [<aux(naux)>] [<boundname>]
<cellid(ncelldim)> <recharge> [<aux(naux)>] [<boundname>]
...
END PERIOD
All of the stress package information in the PERIOD block will continue to apply for subsequent stress periods
until the end of the simulation, or until another PERIOD block is encountered. When a new PERIOD block
is encountered, all of the stresses from the previous block are replaced with the stresses in the new PERIOD
block. Note that this behavior is different from the advanced packages (MAW, SFR, LAK, and UZF). To turn
off all of the stresses for a stress period, a PERIOD block must be specified with no entries. If a PERIOD
block is not specified for the first stress period, then no stresses will be applied until the iper value of the first
PERIOD block in the file.
90 MODFLOW 6 – Description of Input and Output
Explanation of Variables
Block: OPTIONS
FIXED CELL—indicates that recharge will not be reassigned to a cell underlying the cell specified in the
list if the specified cell is inactive.
auxiliary—defines an array of one or more auxiliary variable names. There is no limit on the number
of auxiliary variables that can be provided on this line; however, lists of information provided in
subsequent blocks must have a column of data for each auxiliary variable name defined here. The
number of auxiliary variables detected on this line determines the value for naux. Comments cannot
be provided anywhere on this line as they will be interpreted as auxiliary variable names. Auxiliary
variables may not be used by the package, but they will be available for use by other parts of the
program. The program will terminate with an error if auxiliary variables are specified on more than
one line in the options block.
auxmultname—name of auxiliary variable to be used as multiplier of recharge.
BOUNDNAMES—keyword to indicate that boundary names may be provided with the list of recharge cells.
PRINT INPUT—keyword to indicate that the list of recharge information will be written to the listing file
immediately after it is read.
PRINT FLOWS—keyword to indicate that the list of recharge flow rates will be printed to the listing file
for every stress period time step in which “BUDGET PRINT” is specified in Output Control. If
there is no Output Control option and “PRINT FLOWS” is specified, then flow rates are printed
for the last time step of each stress period.
SAVE FLOWS—keyword to indicate that recharge flow terms will be written to the file specified with
“BUDGET FILEOUT” in Output Control.
TS6—keyword to specify that record corresponds to a time-series file.
FILEIN—keyword to specify that an input filename is expected next.
ts6 filename—defines a time-series file defining time series that can be used to assign time-varying
values. See the “Time-Variable Input” section for instructions on using the time-series capability.
OBS6—keyword to specify that record corresponds to an observations file.
obs6 filename—name of input file to define observations for the Recharge package. See the “Obser-
vation utility” section for instructions for preparing observation input files. Tables 30 and 31 lists
observation type(s) supported by the Recharge package.
Block: DIMENSIONS
maxbound—integer value specifying the maximum number of recharge cells cells that will be specified
for use during any stress period.
Block: PERIOD
iper—integer value specifying the starting stress period number for which the data specified in the
PERIOD block apply. IPER must be less than or equal to NPER in the TDIS Package and greater
than zero. The IPER value assigned to a stress period block must be greater than the IPER value
assigned for the previous PERIOD block. The information specified in the PERIOD block will con-
tinue to apply for all subsequent stress periods, unless the program encounters another PERIOD
block.
cellid—is the cell identifier, and depends on the type of grid that is used for the simulation. For a
structured grid that uses the DIS input file, CELLID is the layer, row, and column. For a grid that
uses the DISV input file, CELLID is the layer and CELL2D number. If the model uses the unstruc-
tured discretization (DISU) input file, CELLID is the node number for the cell.
recharge—is the recharge flux rate (LT −1 ). This rate is multiplied inside the program by the surface
area of the cell to calculate the volumetric recharge rate. If the Options block includes a TIME-
SERIESFILE entry (see the “Time-Variable Input” section), values can be obtained from a time
series by entering the time-series name in place of a numeric value.
aux—represents the values of the auxiliary variables for each recharge. The values of auxiliary variables
must be present for each recharge. The values must be specified in the order of the auxiliary vari-
ables specified in the OPTIONS block. If the package supports time series and the Options block
includes a TIMESERIESFILE entry (see the “Time-Variable Input” section), values can be obtained
from a time series by entering the time-series name in place of a numeric value.
boundname—name of the recharge cell. BOUNDNAME is an ASCII character variable that can con-
tain as many as 40 characters. If BOUNDNAME contains spaces in it, then the entire name must be
enclosed within single quotes.
Example Input File

BEGIN OPTIONS
AUXILIARY var1 var2 mult
PRINT_INPUT
PRINT_FLOWS
SAVE_FLOWS
BOUNDNAMES
TS6 FILEIN recharge_rates.ts
# Note: Time-series file recharge_rates.ts defines time series rch_1
AUXMULTNAME mult
END OPTIONS
BEGIN DIMENSIONS
MAXBOUND 10
END DIMENSIONS
BEGIN PERIOD 1
RECHARGE
# Lay Row Col Rate Var1 Var2 mult BoundName
1 1 1 rch_1 1.0 2.0 1.0 Rch-1-1
1 1 2 rch_1 1.1 2.1 1.0 Rch-1-2
1 1 3 rch_1 1.2 2.2 0.5
1 2 1 rch_1 1.3 2.3 1.0 Rch-2-1
1 2 2 rch_1 1.4 2.4 1.0 Rch-2-2
1 2 3 rch_1 1.5 2.5 1.0
1 2 4 rch_1 1.6 2.6 0.5
1 3 1 rch_1 1.7 2.7 1.0
1 3 2 rch_1 1.8 2.8 1.0
1 3 3 rch_1 1.9 2.9 1.0
END PERIOD
Available observation types

Recharge Package observations are limited to the simulated recharge flow rates (rch). The data required
for the RCH Package observation type is defined in table 14. Negative and positive values for an observation
represent a loss from and gain to the GWF model, respectively.
Table 14. Available RCH Package observation types.
Stress Observation ID ID2 Description

Package type
RCH rch cellid or – Flow to the groundwater system through a
boundname recharge boundary or a group of recharge
boundaries.
Example Observation Input File
BEGIN OPTIONS
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.rch.csv

rch1-1 RCH Rch-1-1
rch1-2 RCH Rch-1-2
rch2-1 RCH Rch-2-1
rch2-2 RCH Rch-2-2
rch2-3 RCH 1 2 3
END CONTINUOUS
Recharge (RCH) Package – Array-Based Input

Input to the Recharge (RCH) Package is read from the file that has type “RCH6” in the Name File. Any
number of RCH Packages can be specified for a single groundwater flow model.
Recharge input can be specified using lists or arrays. Array-based input for recharge is activated by pro-
viding READASARRAYS within the OPTIONS block. Instructions for specifying list-based recharge is
described in the previous section. Array-based input for recharge provides a similar approach for providing
recharge rates as previous MODFLOW versions. Array-based input for recharge can be used only with the
DIS and DISV Packages. Array-based input for recharge cannot be used with the DISU Package.
When array-based input is used for recharge, the DIMENSIONS block should not be specified. The array
size is determined from the model grid.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
READASARRAYS
[FIXED_CELL]
[PRINT_INPUT]
[PRINT_FLOWS]
[SAVE_FLOWS]
[TAS6 FILEIN <tas6_filename>]
END OPTIONS

BEGIN PERIOD <iper>
[IRCH
<irch(ncol*nrow; ncpl)> -- READARRAY]
RECHARGE
<recharge(ncol*nrow; ncpl)> -- READARRAY
[AUX
<aux(ncol*nrow; ncpl)> -- READARRAY]
END PERIOD
Block: OPTIONS
READASARRAYS—indicates that array-based input will be used for the Recharge Package. This keyword
must be specified to use array-based input.
FIXED CELL—indicates that recharge will not be reassigned to a cell underlying the cell specified in the
list if the specified cell is inactive.
auxmultname—name of auxiliary variable to be used as multiplier of recharge.
PRINT INPUT—keyword to indicate that the list of recharge information will be written to the listing file
PRINT FLOWS—keyword to indicate that the list of recharge flow rates will be printed to the listing file
for every stress period time step in which “BUDGET PRINT” is specified in Output Control. If
there is no Output Control option and “PRINT FLOWS” is specified, then flow rates are printed
for the last time step of each stress period.
SAVE FLOWS—keyword to indicate that recharge flow terms will be written to the file specified with
TAS6—keyword to specify that record corresponds to a time-array-series file.
tas6 filename—defines a time-array-series file defining a time-array series that can be used to assign
time-varying values. See the Time-Variable Input section for instructions on using the time-array
series capability.
obs6 filename—name of input file to define observations for the Recharge package. See the “Obser-
vation utility” section for instructions for preparing observation input files. Tables 30 and 31 lists
observation type(s) supported by the Recharge package.
Block: PERIOD
block.
irch—IRCH is the layer number that defines the layer in each vertical column where recharge is
applied. If IRCH is omitted, recharge by default is applied to cells in layer 1. IRCH can only be
used if READASARRAYS is specified in the OPTIONS block. If IRCH is specified, it must be
specified as the first variable in the PERIOD block or MODFLOW will terminate with an error.
recharge—is the recharge flux rate (LT −1 ). This rate is multiplied inside the program by the surface
area of the cell to calculate the volumetric recharge rate. The recharge array may be defined by a
time-array series (see the ”Using Time-Array Series in a Package” section).
aux—is an array of values for auxiliary variable aux(iaux), where iaux is a value from 1 to naux, and
aux(iaux) must be listed as part of the auxiliary variables. A separate array can be specified for
each auxiliary variable. If an array is not specified for an auxiliary variable, then a value of zero is
assigned. If the value specified here for the auxiliary variable is the same as auxmultname, then the
recharge array will be multiplied by this array.
Example Input File
BEGIN OPTIONS
AUXILIARY var1 var2 mymult
READASARRAYS
PRINT_INPUT
PRINT_FLOWS
SAVE_FLOWS
AUXMULTNAME mymult
END OPTIONS
BEGIN PERIOD 1
# For this model, the absence of an IRCH array causes

# recharge to apply to model layer 1. To make recharge
# apply to layer 2 instead, the following lines
# (uncommented) could be used:
# IRCH
# constant 2
# recharge rate
RECHARGE
constant 0.0040
# auxiliary variable (var1) array

var1
constant 100.
# auxiliary variable (var2) array

var2
constant 0.
# auxiliary variable (mymult) array

# Because ‘‘AUXMULTNAME mymult’’ was specified in the
# options block, the MYMULT array will be used to multiply
# the values in the RECHARGE array
MYMULT
INTERNAL FACTOR 1.0
0.5 1.0 1.0 0.5
1.0 1.0 1.0 1.0
0.5 1.0 1.0 0.5
END PERIOD
Evapotranspiration (EVT) Package – List-Based Input

Input to the Evapotranspiration (EVT) Package is read from the file that has type “EVT6” in the Name
File. Any number of EVT Packages can be specified for a single groundwater flow model. All single-valued
variables are free format.
Evapotranspiration input can be specified using lists or arrays, unless the DISU Package is used. List-
based input must be used if discretization is specified using the DISU Package. List-based input for evapo-
transpiration is the default, and is described here. Instructions for specifying array-based evapotranspiration
are described in the next section.
List-based input offers several advantages over the array-based input for specifying evapotranspiration.
First, multiple list entries can be specified for a single cell. This makes it possible to divide a cell into multiple
areas, and assign a different evapotranspiration rate or extinction depth for each area (perhaps based on vege-
tation type or some other criteria). In this case, the user would likely specify an auxiliary variable to serve as a
multiplier. This multiplier would be calculated by the user and provided in the input file as the fractional cell
are for the individual evapotranspiration entries. Another advantage to using list-based input for specifying
evapotranspiration is that boundnames can be specified. Boundnames work with the Observations capability
and can be used to sum evapotranspiration rates for entries with the same boundname. A disadvantage of the
list-based input is that one cannot easily assign evapotranspiration to the entire model without specifying a list
of model cells. For this reason MODFLOW 6 also supports array-based input for evapotranspiration.
ET input is read in list form, as shown in the PERIOD block below. Each line in the PERIOD block
defines all input for one cell. Entries following cellid, in order, define the ET surface (etss), maximum ET
flux rate (etsr), extinction depth (etsx), all (netseg – 1) pxdp values, all (netseg – 1) petm values, all aux-
iliary variables (if AUXILIARY option is specified), and boundary name (if BOUNDNAMES option is speci-
fied).
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
[FIXED_CELL]
[BOUNDNAMES]
[PRINT_INPUT]
[PRINT_FLOWS]
[SAVE_FLOWS]
[SURF_RATE_SPECIFIED]
END OPTIONS
BEGIN DIMENSIONS
MAXBOUND <maxbound>
NSEG <nseg>
END DIMENSIONS

BEGIN PERIOD <iper>
<cellid(ncelldim)> <surface> <rate> <depth> <pxdp(nseg-1)> <petm(nseg-1)> [<petm0>] [<aux(naux)>] [<boundname>]
<cellid(ncelldim)> <surface> <rate> <depth> <pxdp(nseg-1)> <petm(nseg-1)> [<petm0>] [<aux(naux)>] [<boundname>]
...
END PERIOD
Block: OPTIONS
FIXED CELL—indicates that evapotranspiration will not be reassigned to a cell underlying the cell speci-
fied in the list if the specified cell is inactive.
auxmultname—name of auxiliary variable to be used as multiplier of evapotranspiration rate.
BOUNDNAMES—keyword to indicate that boundary names may be provided with the list of evapotranspi-
ration cells.
PRINT INPUT—keyword to indicate that the list of evapotranspiration information will be written to the
listing file immediately after it is read.
PRINT FLOWS—keyword to indicate that the list of evapotranspiration flow rates will be printed to the
listing file for every stress period time step in which “BUDGET PRINT” is specified in Output Con-
trol. If there is no Output Control option and “PRINT FLOWS” is specified, then flow rates are
printed for the last time step of each stress period.
SAVE FLOWS—keyword to indicate that evapotranspiration flow terms will be written to the file specified
with “BUDGET FILEOUT” in Output Control.
obs6 filename—name of input file to define observations for the Evapotranspiration package. See the
“Observation utility” section for instructions for preparing observation input files. Tables 30 and 31
lists observation type(s) supported by the Evapotranspiration package.
SURF RATE SPECIFIED—indicates that the proportion of the evapotranspiration rate at the ET surface
will be specified as PETM0 in list input.
Block: DIMENSIONS
maxbound—integer value specifying the maximum number of evapotranspiration cells cells that will be
specified for use during any stress period.
nseg—number of ET segments. Default is one. When NSEG is greater than 1, PXDP and PETM arrays
must be specified NSEG - 1 times each, in order from the uppermost segment down. PXDP defines
the extinction-depth proportion at the bottom of a segment. PETM defines the proportion of the
maximum ET flux rate at the bottom of a segment.
Block: PERIOD
block.
surface—is the elevation of the ET surface (L). If the Options block includes a TIMESERIESFILE
entry (see the “Time-Variable Input” section), values can be obtained from a time series by entering
the time-series name in place of a numeric value.
rate—is the maximum ET flux rate (LT −1 ). If the Options block includes a TIMESERIESFILE entry
(see the “Time-Variable Input” section), values can be obtained from a time series by entering the
time-series name in place of a numeric value.
depth—is the ET extinction depth (L). If the Options block includes a TIMESERIESFILE entry (see
the “Time-Variable Input” section), values can be obtained from a time series by entering the time-
series name in place of a numeric value.
pxdp—is the proportion of the ET extinction depth at the bottom of a segment (dimensionless). If the
Options block includes a TIMESERIESFILE entry (see the “Time-Variable Input” section), values
can be obtained from a time series by entering the time-series name in place of a numeric value.
petm—is the proportion of the maximum ET flux rate at the bottom of a segment (dimensionless). If the
petm0—is the proportion of the maximum ET flux rate that will apply when head is at or above the ET
surface (dimensionless). PETM0 is read only when the SURF RATE SPECIFIED option is used.
If the Options block includes a TIMESERIESFILE entry (see the “Time-Variable Input” section),
values can be obtained from a time series by entering the time-series name in place of a numeric
value.
aux—represents the values of the auxiliary variables for each evapotranspiration. The values of auxil-
iary variables must be present for each evapotranspiration. The values must be specified in the order
of the auxiliary variables specified in the OPTIONS block. If the package supports time series and
the Options block includes a TIMESERIESFILE entry (see the “Time-Variable Input” section), val-
ues can be obtained from a time series by entering the time-series name in place of a numeric value.
boundname—name of the evapotranspiration cell. BOUNDNAME is an ASCII character variable that

can contain as many as 40 characters. If BOUNDNAME contains spaces in it, then the entire name
must be enclosed within single quotes.
Example Input File
# Example for structured model with list-based input

BEGIN OPTIONS
AUXNAMES Mult
BOUNDNAMES
TS6 FILEIN EtRate.ts
# Note: Time-series file EtRate.ts defines time series et_rate
AUXMULTNAME Mult
PRINT_INPUT
BEGIN DIMENSIONS
MAXBOUND 10
END DIMENSIONS
BEGIN PERIOD 1
# Lay Row Col SURFACE RATE DEPTH PXPD1 PXPD2 PETM1 PETM2 Mult Name
1 1 13 110.0 et_rate 10.0 0.2 0.5 0.3 0.1 0.2 ET-1
1 2 13 110.0 et_rate 10.0 0.2 0.5 0.3 0.1 0.4 ET-2
1 3 13 110.0 et_rate 10.0 0.2 0.5 0.3 0.1 0.6 ET-3
1 4 13 110.0 et_rate 10.0 0.2 0.5 0.3 0.1 0.8 ET-4
1 5 13 110.0 2.e-2 10.0 0.2 0.5 0.3 0.1 1.0 ET-5
1 6 13 110.0 2.e-2 10.0 0.2 0.5 0.3 0.1 1.0 ET-6
1 7 13 110.0 2.e-2 10.0 0.2 0.5 0.3 0.1 0.7 ET-7
1 8 13 110.0 2.e-2 10.0 0.2 0.5 0.3 0.1 0.5 ET-8
1 9 13 110.0 2.e-2 10.0 0.2 0.5 0.3 0.1 0.3 ET-9
1 10 13 110.0 et_rate 10.0 0.2 0.5 0.3 0.1 0.1 ET-10
END PERIOD

Evapotranspiration Package observations are limited to the simulated evapotranspiration flow rates (evt).
The data required for the EVT Package observation type is defined in table 15. Negative and positive values
for an observation represent a loss from and gain to the GWF model, respectively.
Table 15. Available EVT Package observation types.

Package type
EVT evt cellid or – Flow from the groundwater system through
boundname an evapotranspiration boundary or group of
evapotranspiration boundaries.
BEGIN OPTIONS
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.evt.csv

et1-1 EVT 1 1 1
et1-2 EVT 1 1 2
et2-1 EVT 1 2 1
et2-2 EVT 1 2 2
et2-3 EVT 1 2 3
END CONTINUOUS
Evapotranspiration (EVT) Package – Array-Based Input

Input to the Evapotranspiration (EVT) Package is read from the file that has type “EVT6” in the Name
File. Any number of EVT Packages can be specified for a single groundwater flow model. All single-valued
variables are free format.
Evapotranspiration input can be specified using lists or arrays. Array-based input for evapotranspiration is
activated by providing READASARRAYS within the OPTIONS block. Instructions for specifying list-based
evapotranspiration is described in the previous section. Array-based input for evapotranspiration provides a
similar approach for providing evapotranspiration rates as previous MODFLOW versions. Array-based input
for evapotranspiration can be used only with the DIS and DISV Packages. Array-based input for evapotranspi-
ration cannot be used with the DISU Package.
When array-based input is used for evapotranspiration, the DIMENSIONS block should not be speci-
fied. The array size is determined from the model grid. Segmented evapotranspiration cannot be used with
the READASARRAYS option.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
READASARRAYS
[FIXED_CELL]
[PRINT_INPUT]
[PRINT_FLOWS]
[SAVE_FLOWS]
[TAS6 FILEIN <tas6_filename>]
END OPTIONS

BEGIN PERIOD <iper>
[IEVT
<ievt(ncol*nrow; ncpl)> -- READARRAY]
SURFACE
<surface(ncol*nrow; ncpl)> -- READARRAY
RATE
<rate(ncol*nrow; ncpl)> -- READARRAY
DEPTH
<depth(ncol*nrow; ncpl)> -- READARRAY
AUX(IAUX)
<aux(iaux)(ncol*nrow; ncpl)> -- READARRAY
END PERIOD
Block: OPTIONS
READASARRAYS—indicates that array-based input will be used for the Evapotranspiration Package. This
keyword must be specified to use array-based input.
FIXED CELL—indicates that evapotranspiration will not be reassigned to a cell underlying the cell speci-
fied in the list if the specified cell is inactive.
auxmultname—name of auxiliary variable to be used as multiplier of evapotranspiration rate.
PRINT INPUT—keyword to indicate that the list of evapotranspiration information will be written to the
PRINT FLOWS—keyword to indicate that the list of evapotranspiration flow rates will be printed to the
SAVE FLOWS—keyword to indicate that evapotranspiration flow terms will be written to the file specified
TAS6—keyword to specify that record corresponds to a time-array-series file.
tas6 filename—defines a time-array-series file defining a time-array series that can be used to assign
time-varying values. See the Time-Variable Input section for instructions on using the time-array
series capability.
obs6 filename—name of input file to define observations for the Evapotranspiration package. See the
“Observation utility” section for instructions for preparing observation input files. Tables 30 and 31
lists observation type(s) supported by the Evapotranspiration package.
Block: PERIOD
block.
ievt—IEVT is the layer number that defines the layer in each vertical column where evapotranspiration
is applied. If IEVT is omitted, evapotranspiration by default is applied to cells in layer 1. If IEVT is
specified, it must be specified as the first variable in the PERIOD block or MODFLOW will termi-
nate with an error.
surface—is the elevation of the ET surface (L).

rate—is the maximum ET flux rate (LT −1 ).
depth—is the ET extinction depth (L).
aux(iaux)—is an array of values for auxiliary variable AUX(IAUX), where iaux is a value from 1 to
NAUX, and AUX(IAUX) must be listed as part of the auxiliary variables. A separate array can be
specified for each auxiliary variable. If an array is not specified for an auxiliary variable, then a
value of zero is assigned. If the value specified here for the auxiliary variable is the same as aux-
multname, then the evapotranspiration rate will be multiplied by this array.
Example Input File
BEGIN OPTIONS
READASARRAYS
AUXILIARY var1 var2
PRINT_INPUT
PRINT_FLOWS
SAVE_FLOWS
END OPTIONS
BEGIN PERIOD 1
#For a structured grid, IEVT defaults to model
# layer 1, so no need to enter IEVT here.
#ET surface elevation

SURFACE
constant 150.0
#Maximum ET rate
RATE
constant 0.007
#ET extinction depth
DEPTH
constant 15.0
#auxiliary variable (var1) array
var1
constant 100.0
#auxiliary variable (var2) array
var2
constant 0.0
END PERIOD
Multi-Aquifer Well (MAW) Package

Input to the Multi-Aquifer Well (MAW) Package is read from the file that has type “MAW6” in the Name
File. Any number of MAW Packages can be specified for a single groundwater flow model.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
[BOUNDNAMES]
[PRINT_INPUT]
[PRINT_HEAD]
[PRINT_FLOWS]
[SAVE_FLOWS]
[HEAD FILEOUT <headfile>]
[BUDGET FILEOUT <budgetfile>]
[NO_WELL_STORAGE]
[FLOW_CORRECTION]
[FLOWING_WELLS]
[SHUTDOWN_THETA <shutdown_theta>]
[SHUTDOWN_KAPPA <shutdown_kappa>]
[MOVER]
END OPTIONS
BEGIN DIMENSIONS
NMAWWELLS <nmawwells>
END DIMENSIONS
BEGIN PACKAGEDATA
<wellno> <radius> <bottom> <strt> <condeqn> <ngwfnodes> [<aux(naux)>] [<boundname>]
<wellno> <radius> <bottom> <strt> <condeqn> <ngwfnodes> [<aux(naux)>] [<boundname>]
...
END PACKAGEDATA
BEGIN CONNECTIONDATA
<wellno> <icon> <cellid(ncelldim)> <scrn_top> <scrn_bot> <hk_skin> <radius_skin>
<wellno> <icon> <cellid(ncelldim)> <scrn_top> <scrn_bot> <hk_skin> <radius_skin>
...
END CONNECTIONDATA

BEGIN PERIOD <iper>
<wellno> <mawsetting>
<wellno> <mawsetting>
...
END PERIOD
All of the advanced stress package information in the PERIOD block will continue to apply for subsequent
stress periods until the end of the simulation, or until another PERIOD block is encountered. When a new
PERIOD block is encountered only the wells specified in the new period block will be changed. A well
not specified in the new period block will continue to behave according to its specification in the previous
PERIOD block. Note that this behavior is different from the simple stress packages (CHD, WEL, DRN, RIV,
GHB, RCH and EVT), in which any stress not specified in a new PERIOD block will be removed. To turn off
all of the advanced stresses for a stress period, a PERIOD block must be specified with settings that deactivate
the wells. If a PERIOD block is not specified for the first stress period, then no stresses will be applied.
Block: OPTIONS
BOUNDNAMES—keyword to indicate that boundary names may be provided with the list of multi-aquifer
well cells.
PRINT INPUT—keyword to indicate that the list of multi-aquifer well information will be written to the
PRINT HEAD—keyword to indicate that the list of multi-aquifer well heads will be printed to the listing
file for every stress period in which “HEAD PRINT” is specified in Output Control. If there is no
Output Control option and PRINT HEAD is specified, then heads are printed for the last time step
of each stress period.
PRINT FLOWS—keyword to indicate that the list of multi-aquifer well flow rates will be printed to the
SAVE FLOWS—keyword to indicate that multi-aquifer well flow terms will be written to the file specified
HEAD—keyword to specify that record corresponds to head.
headfile—name of the binary output file to write head information.
BUDGET—keyword to specify that record corresponds to the budget.
FILEOUT—keyword to specify that an output filename is expected next.
budgetfile—name of the binary output file to write budget information.
NO WELL STORAGE—keyword that deactivates inclusion of well storage contributions to the multi-
aquifer well package continuity equation.
FLOW CORRECTION—keyword that activates flow corrections in cases where the head in a multi-aquifer
well is below the bottom of the screen for a connection or the head in a convertible cell connected
to a multi-aquifer well is below the cell bottom. When flow corrections are activated, unit head gra-
dients are used to calculate the flow between a multi-aquifer well and a connected GWF cell. By
default, flow corrections are not made.
FLOWING WELLS—keyword that activates the flowing wells option for the multi-aquifer well package.
shutdown theta—value that defines the weight applied to discharge rate for wells that limit the water
level in a discharging well (defined using the HEAD LIMIT keyword in the stress period data).
SHUTDOWN THETA is used to control discharge rate oscillations when the flow rate from the
aquifer is less than the specified flow rate from the aquifer to the well. Values range between 0.0 and
1.0, and larger values increase the weight (decrease under-relaxation) applied to the well discharge
rate. The HEAD LIMIT option has been included to facilitate backward compatibility with previ-
ous versions of MODFLOW but use of the RATE SCALING option instead of the HEAD LIMIT
option is recommended. By default, SHUTDOWN THETA is 0.7.
shutdown kappa—value that defines the weight applied to discharge rate for wells that limit the water
level in a discharging well (defined using the HEAD LIMIT keyword in the stress period data).
SHUTDOWN KAPPA is used to control discharge rate oscillations when the flow rate from the
aquifer is less than the specified flow rate from the aquifer to the well. Values range between 0.0
and 1.0, and larger values increase the weight applied to the well discharge rate. The HEAD LIMIT
option has been included to facilitate backward compatibility with previous versions of MODFLOW
but use of the RATE SCALING option instead of the HEAD LIMIT option is recommended. By
default, SHUTDOWN KAPPA is 0.0001.
obs6 filename—name of input file to define observations for the MAW package. See the “Observation
utility” section for instructions for preparing observation input files. Tables 30 and 31 lists observa-
tion type(s) supported by the MAW package.
MOVER—keyword to indicate that this instance of the MAW Package can be used with the Water Mover
(MVR) Package. When the MOVER option is specified, additional memory is allocated within the
package to store the available, provided, and received water.
Block: DIMENSIONS
nmawwells—integer value specifying the number of multi-aquifer wells that will be simulated for all
stress periods.
Block: PACKAGEDATA
wellno—integer value that defines the well number associated with the specified PACKAGEDATA data
on the line. WELLNO must be greater than zero and less than or equal to NMAWWELLS. Multi-
aquifer well information must be specified for every multi-aquifer well or the program will termi-
nate with an error. The program will also terminate with an error if information for a multi-aquifer
well is specified more than once.
radius—radius for the multi-aquifer well. The program will terminate with an error if the radius is less
than or equal to zero.
bottom—bottom elevation of the multi-aquifer well. If CONDEQN is SPECIFIED, THIEM, SKIN, or
COMPOSITE, BOTTOM is set to the cell bottom in the lowermost GWF cell connection in cases
where the specified well bottom is above the bottom of this GWF cell. If CONDEQN is MEAN,
BOTTOM is set to the lowermost GWF cell connection screen bottom in cases where the specified
well bottom is above this value. The bottom elevation defines the lowest well head that will be sim-
ulated when the NEWTON UNDER RELAXATION option is specified in the GWF model name
file. The bottom elevation is also used to calculate volumetric storage in the well.
strt—starting head for the multi-aquifer well. The program will terminate with an error if the starting
head is less than the specified well bottom.
condeqn—character string that defines the conductance equation that is used to calculate the saturated
conductance for the multi-aquifer well. Possible multi-aquifer well CONDEQN strings include:
SPECIFIED–character keyword to indicate the multi-aquifer well saturated conductance will be
specified. THIEM–character keyword to indicate the multi-aquifer well saturated conductance will
be calculated using the Thiem equation, which considers the cell top and bottom, aquifer hydraulic
conductivity, and effective cell and well radius. SKIN–character keyword to indicate that the multi-
aquifer well saturated conductance will be calculated using the cell top and bottom, aquifer and
screen hydraulic conductivity, and well and skin radius. CUMULATIVE–character keyword to
indicate that the multi-aquifer well saturated conductance will be calculated using a combination of
the Thiem and SKIN equations. MEAN–character keyword to indicate the multi-aquifer well satu-
rated conductance will be calculated using the aquifer and screen top and bottom, aquifer and screen
hydraulic conductivity, and well and skin radius. The CUMULATIVE conductance equation is iden-
tical to the SKIN LOSSTYPE in the Multi-Node Well (MNW2) package for MODFLOW-2005.
The program will terminate with an error condition if CONDEQN is SKIN or CUMULATIVE and
the calculated saturated conductance is less than zero; if an error condition occurs, it is suggested
that the THEIM or MEAN conductance equations be used for these multi-aquifer wells.
ngwfnodes—integer value that defines the number of GWF nodes connected to this (WELLNO) multi-
aquifer well. NGWFNODES must be greater than zero.
aux—represents the values of the auxiliary variables for each multi-aquifer well. The values of auxiliary
variables must be present for each multi-aquifer well. The values must be specified in the order of
the auxiliary variables specified in the OPTIONS block. If the package supports time series and the
boundname—name of the multi-aquifer well cell. BOUNDNAME is an ASCII character variable that
can contain as many as 40 characters. If BOUNDNAME contains spaces in it, then the entire name
must be enclosed within single quotes.
Block: CONNECTIONDATA
wellno—integer value that defines the well number associated with the specified CONNECTIONDATA
data on the line. WELLNO must be greater than zero and less than or equal to NMAWWELLS.
Multi-aquifer well connection information must be specified for every multi-aquifer well connection
to the GWF model (NGWFNODES) or the program will terminate with an error. The program will
also terminate with an error if connection information for a multi-aquifer well connection to the
GWF model is specified more than once.
icon—integer value that defines the GWF connection number for this multi-aquifer well connection
entry. ICONN must be greater than zero and less than or equal to NGWFNODES for multi-aquifer
well WELLNO.
cellid—is the cell identifier, and depends on the type of grid that is used for the simulation. For
a structured grid that uses the DIS input file, CELLID is the layer, row, and column. For a grid
that uses the DISV input file, CELLID is the layer and CELL2D number. If the model uses the
unstructured discretization (DISU) input file, CELLID is the node number for the cell. One or more
screened intervals can be connected to the same CELLID if CONDEQN for a well is MEAN. The
program will terminate with an error if MAW wells using SPECIFIED, THIEM, SKIN, or CUMU-
LATIVE conductance equations have more than one connection to the same CELLID.
scrn top—value that defines the top elevation of the screen for the multi-aquifer well connection. If
CONDEQN is SPECIFIED, THIEM, SKIN, or COMPOSITE, SCRN TOP can be any value and
is set to the top of the cell. If CONDEQN is MEAN, SCRN TOP is set to the multi-aquifer well
connection cell top if the specified value is greater than the cell top. The program will terminate
with an error if the screen top is less than the screen bottom.
scrn bot—value that defines the bottom elevation of the screen for the multi-aquifer well connection.
If CONDEQN is SPECIFIED, THIEM, SKIN, or COMPOSITE, SCRN BOT can be any value is
set to the bottom of the cell. If CONDEQN is MEAN, SCRN BOT is set to the multi-aquifer well
connection cell bottom if the specified value is less than the cell bottom. The program will terminate
with an error if the screen bottom is greater than the screen top.
hk skin—value that defines the skin (filter pack) hydraulic conductivity (if CONDEQN for the multi-
aquifer well is SKIN, CUMULATIVE, or MEAN) or conductance (if CONDEQN for the multi-
aquifer well is SPECIFIED) for each GWF node connected to the multi-aquifer well (NGWFN-
ODES). If CONDEQN is SPECIFIED, HK SKIN must be greater than or equal to zero. HK SKIN
can be any value if CONDEQN is THIEM. Otherwise, HK SKIN must be greater than zero. If
CONDEQN is SKIN, the contrast between the cell transmissivity (the product of geometric mean
horizontal hydraulic conductivity and the cell thickness) and the well transmissivity (the product
of HK SKIN and the screen thicknesses) must be greater than one in node CELLID or the program
will terminate with an error condition; if an error condition occurs, it is suggested that the HK SKIN
be reduced to a value less than K11 and K22 in node CELLID or the THEIM or MEAN conduc-
tance equations be used for these multi-aquifer wells.
radius skin—real value that defines the skin radius (filter pack radius) for the multi-aquifer well.
RADIUS SKIN can be any value if CONDEQN is SPECIFIED or THIEM. If CONDEQN is SKIN,
CUMULATIVE, or MEAN, the program will terminate with an error if RADIUS SKIN is less than
or equal to the RADIUS for the multi-aquifer well.
Block: PERIOD
block.
wellno—integer value that defines the well number associated with the specified PERIOD data on the
line. WELLNO must be greater than zero and less than or equal to NMAWWELLS.
mawsetting—line of information that is parsed into a keyword and values. Keyword values that
can be used to start the MAWSETTING string include: STATUS, FLOWING WELL, RATE,
WELL HEAD, HEAD LIMIT, SHUT OFF, RATE SCALING, and AUXILIARY.
STATUS <status>
FLOWING_WELL <fwelev> <fwcond> <fwrlen>
RATE <rate>
WELL_HEAD <well_head>
HEAD_LIMIT <head_limit>
SHUT_OFF <minrate> <maxrate>
RATE_SCALING <pump_elevation> <scaling_length>
AUXILIARY <auxname> <auxval>
status—keyword option to define well status. STATUS can be ACTIVE, INACTIVE, or CONSTANT.
By default, STATUS is ACTIVE.
FLOWING WELL—keyword to indicate the well is a flowing well. The FLOWING WELL option can be
used to simulate flowing wells when the simulated well head exceeds the specified drainage eleva-
tion.
fwelev—elevation used to determine whether or not the well is flowing.
fwcond—conductance used to calculate the discharge of a free flowing well. Flow occurs when the head
in the well is above the well top elevation (FWELEV).
fwrlen—length used to reduce the conductance of the flowing well. When the head in the well drops
below the well top plus the reduction length, then the conductance is reduced. This reduction length
can be used to improve the stability of simulations with flowing wells so that there is not an abrupt
change in flowing well rates.
rate—is the volumetric pumping rate for the multi-aquifer well. A positive value indicates recharge
and a negative value indicates discharge (pumping). RATE only applies to active (IBOUND >
0) multi-aquifer wells. If the Options block includes a TIMESERIESFILE entry (see the “Time-
Variable Input” section), values can be obtained from a time series by entering the time-series name
in place of a numeric value. By default, the RATE for each multi-aquifer well is zero.
well head—is the head in the multi-aquifer well. WELL HEAD is only applied to constant head (STA-
TUS is CONSTANT) and inactive (STATUS is INACTIVE) multi-aquifer wells. If the Options
block includes a TIMESERIESFILE entry (see the “Time-Variable Input” section), values can be
obtained from a time series by entering the time-series name in place of a numeric value. The pro-
gram will terminate with an error if WELL HEAD is less than the bottom of the well.
head limit—is the limiting water level (head) in the well, which is the minimum of the well RATE or
the well inflow rate from the aquifer. HEAD LIMIT can be applied to extraction wells (RATE <
0) or injection wells (RATE > 0). HEAD LIMIT can be deactivated by specifying the text string
‘OFF’. The HEAD LIMIT option is based on the HEAD LIMIT functionality available in the
MNW2 (Konikow and others, 2009) package for MODFLOW-2005. The HEAD LIMIT option has
been included to facilitate backward compatibility with previous versions of MODFLOW but use
of the RATE SCALING option instead of the HEAD LIMIT option is recommended. By default,
HEAD LIMIT is ‘OFF’.
SHUT OFF—keyword for activating well shut off capability. Subsequent values define the minimum and
maximum pumping rate that a well must exceed to shutoff or reactivate a well, respectively, during
a stress period. SHUT OFF is only applied to injection wells (RATE< 0) and if HEAD LIMIT is
specified (not set to ‘OFF’). If HEAD LIMIT is specified, SHUT OFF can be deactivated by spec-
ifying a minimum value equal to zero. The SHUT OFF option is based on the SHUT OFF func-
tionality available in the MNW2 (Konikow and others, 2009) package for MODFLOW-2005. The
SHUT OFF option has been included to facilitate backward compatibility with previous versions
of MODFLOW but use of the RATE SCALING option instead of the SHUT OFF option is recom-
mended. By default, SHUT OFF is not used.
minrate—is the minimum rate that a well must exceed to shutoff a well during a stress period. The
well will shut down during a time step if the flow rate to the well from the aquifer is less than MIN-
RATE. If a well is shut down during a time step, reactivation of the well cannot occur until the next
time step to reduce oscillations. MINRATE must be less than maxrate.
maxrate—is the maximum rate that a well must exceed to reactivate a well during a stress period. The
well will reactivate during a timestep if the well was shutdown during the previous time step and
the flow rate to the well from the aquifer exceeds maxrate. Reactivation of the well cannot occur
until the next time step if a well is shutdown to reduce oscillations. maxrate must be greater than
MINRATE.
RATE SCALING—activate rate scaling. If RATE SCALING is specified, both PUMP ELEVATION and
SCALING LENGTH must be specified. RATE SCALING cannot be used with HEAD LIMIT.
RATE SCALING can be used for extraction or injection wells. For extraction wells, the extraction
rate will start to decrease once the head in the well lowers to a level equal to the pump elevation plus
the scaling length. If the head in the well drops below the pump elevation, then the extraction rate
is calculated to be zero. For an injection well, the injection rate will begin to decrease once the head
in the well rises above the specified pump elevation. If the head in the well rises above the pump
elevation plus the scaling length, then the injection rate will be set to zero.
pump elevation—is the elevation of the multi-aquifer well pump (PUMP ELEVATION).
PUMP ELEVATION should not be less than the bottom elevation (BOTTOM) of the multi-aquifer
well.
scaling length—height above the pump elevation (SCALING LENGTH). If the simulated well head
is below this elevation (pump elevation plus the scaling length), then the pumping rate is reduced.
AUXILIARY—keyword for specifying auxiliary variable.
auxname—name for the auxiliary variable to be assigned AUXVAL. AUXNAME must match one of the
auxiliary variable names defined in the OPTIONS block. If AUXNAME does not match one of the
auxiliary variable names defined in the OPTIONS block the data are ignored.
auxval—value for the auxiliary variable. If the Options block includes a TIMESERIESFILE entry (see
Example Input File – Conductance Calculated using Thiem Equation

begin options
print_input
print_head
print_flows
boundnames
head fileout maw-1.head.bin
budget fileout maw-1.cbc
end options
begin dimensions
nmawwells 2
end dimensions
begin packagedata
# wellno radius bottom strt condeqn ngwnodes name
1 0.15 -100.0 9.14 thiem 2 pwell
2 0.25 -100.0 9.14 thiem 1 iwell
end packagedata
begin connectiondata
# wellno conn l r c stop sbot k rskin
1 1 1 51 51 0 0 0 0
1 2 2 51 51 0 0 0 0
2 1 2 2 2 0 0 0 0
end connectiondata
begin period 1
1 rate_scaling -90. 5.
1 rate -1767.
2 status inactive
end period
begin period 100

2 status active
2 rate 529.
1 rate -2767.
end period
Example Input File – Conductance Calculated using Screen Geometry
begin options
print_input
print_head
print_flows
boundnames
end options
begin dimensions
nmawwells 2
end dimensions
begin packagedata
1 0.15 -100.0 9.14 mean 2 pwell
2 0.25 -100.0 9.14 mean 1 iwell
end packagedata
1 1 1 51 51 0. -100. 361. .25
1 2 2 51 51 0. -100. 361. .25
2 1 2 2 2 -50. -100. 361 .50
end connectiondata
begin period 1
1 rate_scaling -90. 5.
1 rate -1767.
2 status inactive
end period
begin period 100

2 status active
2 rate 529.
1 rate -2767.
end period
Example Input File – Flowing Well with Conductance Specified
begin options
print_input
print_head
print_flows
boundnames
flowing_wells
end options
begin dimensions
nmawwells 1
end dimensions
begin packagedata
1 0.15 -514.9 9.14 specified 2 ntwell
end packagedata
1 1 1 51 51 -50 -514.9 111.3763 0
1 2 2 51 51 -50 -514.9 445.9849 0
end connectiondata
begin period 1
1 rate 0
1 flowing_well 0. 7500. 0.5
end period

Multi-Aquifer Well Package observations include well head and all of the terms that contribute to the con-
tinuity equation for each multi-aquifer well. Additional LAK Package observations include the conductance
for a well-aquifer connection conductance (conductance) and the calculated flowing well-aquifer connection
conductance (fw-conductance). The data required for each MAW Package observation type is defined in
table 16. Negative and positive values for maw observations represent a loss from and gain to the GWF model,
respectively. For all other flow terms, negative and positive values represent a loss from and gain from the
MAW package, respectively.
Table 16. Available MAW Package observation types.

Package type
MAW head wellno or – Head in a multi-aquifer well. If boundname
boundname is specified, boundname must be unique for
each multi-aquifer well.
MAW from-mvr wellno or – Simulated inflow to a well from the MVR
boundname package for a multi-aquifer well or a group
of multi-aquifer wells.
MAW maw wellno or icon or Simulated flow rate for a multi-aquifer well
boundname – or a group of multi-aquifer wells and its
aquifer connection(s). If boundname is not
specified for ID, then the simulated multi-
aquifer well-aquifer flow rate at a specific
multi-aquifer well connection is observed.
In this case, ID2 must be specified and is the
connection number icon.
MAW rate wellno or – Simulated pumping rate for a multi-aquifer
boundname well or a group of multi-aquifer wells.
MAW rate-to-mvr wellno or – Simulated well discharge that is available for
boundname the MVR package for a multi-aquifer well or
a group of multi-aquifer wells.
Table 16. Available MAW Package observation types.—Continued

Package type
MAW fw-rate wellno or – Simulated flowing well flow rate for a multi-
boundname aquifer well or a group of multi-aquifer
wells.
MAW fw-to-mvr wellno or – Simulated flowing well discharge rate that is
boundname available for the MVR package for a multi-
aquifer well or a group of multi-aquifer
wells.
MAW storage wellno or – Simulated storage flow rate for a multi-
wells.
MAW constant wellno or – Simulated constant-flow rate for a multi-
wells.
MAW conductance wellno or icon or Simulated well conductance for a multi-
boundname – aquifer well or a group of multi-aquifer wells
and its aquifer connection(s). If boundname
is not specified for ID, then the simulated
multi-aquifer well conductance at a specific
multi-aquifer well connection is observed.
In this case, ID2 must be specified and is the
connection number icon.
MAW fw-conductance wellno or – Simulated flowing well conductance for
boundname a multi-aquifer well or a group of multi-
aquifer wells.
BEGIN OPTIONS
DIGITS 10
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.maw.csv

m1head head 1
m1rate01 maw 1 1
m1rate02 maw 1 2
m1rate maw well-1
m2rate01 maw well-2
END CONTINUOUS
Streamflow Routing (SFR) Package

Input to the Streamflow Routing (SFR) Package is read from the file that has type “SFR6” in the Name
File. Any number of SFR Packages can be specified for a single groundwater flow model; however, water can-
not be routed between reaches in separate packages except in cases where the MVR Package is used to route
water between separate packages.
Reach connectivity must be explicitly specified for this version of the SFR Package, unlike the abbrevi-
ated SFR Package segment connectivity specified in previous versions of MODFLOW. Explicit specification
of reach connectivity has been adopted to facilitate better validation of stream network connectivity by the
program. Explicit reach connectivity means that a reach must be specified as an upstream connection for all
downstream connections to the reach. Downstream connections for a reach are denoted with a negative reach
number. Flow in a reach is unidirectional, always flowing from the upstream end to the downstream end of a
reach. An example of the reach connectivity for a hypothetical stream network is shown in figure 2.
U
D U
1 2
D U
U 5
EXPLANATION
Reach connections 3
Stream
Reach connectivity Reach connection
D
reach connections Flow direction
U
1 -2 5 Stream reach number
U Upstream end of reach
2 1 -3 -5
4 D Downstream end of reach
3 2 -4
4 3 -7
5 2 -6 U
D
6
6 5 -7 7
D
7 4 6
D
Figure 2. Simple stream network having seven reaches with a junction having two reaches, a confluence of two reaches, and
the resulting reach connectivity. Downstream connections for a reach must include the reach as an upstream connection for all
downstream connections to the reach. Downstream connections for a reach are denoted with a negative reach number.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
[BOUNDNAMES]
[PRINT_INPUT]
[PRINT_STAGE]
[PRINT_FLOWS]
[SAVE_FLOWS]
[STAGE FILEOUT <stagefile>]
[PACKAGE_CONVERGENCE FILEOUT <package_convergence_filename>]
[MOVER]
[MAXIMUM_PICARD_ITERATIONS <maximum_picard_iterations>]
[MAXIMUM_ITERATIONS <maximum_iterations>]
[MAXIMUM_DEPTH_CHANGE <maximum_depth_change>]
[UNIT_CONVERSION <unit_conversion>]
END OPTIONS
BEGIN DIMENSIONS
NREACHES <nreaches>
END DIMENSIONS
BEGIN PACKAGEDATA
<rno> <cellid(ncelldim)> <rlen> <rwid> <rgrd> <rtp> <rbth> <rhk> <man> <ncon> <ustrf> <ndv> [<aux(naux)>] [<boundname>]
<rno> <cellid(ncelldim)> <rlen> <rwid> <rgrd> <rtp> <rbth> <rhk> <man> <ncon> <ustrf> <ndv> [<aux(naux)>] [<boundname>]
...
END PACKAGEDATA
<rno> [<ic(ncon(rno))>]
<rno> [<ic(ncon(rno))>]
...
END CONNECTIONDATA
IF ndv IS GREATER THAN ZERO FOR ANY REACH

BEGIN DIVERSIONS
<rno> <idv> <iconr> <cprior>
<rno> <idv> <iconr> <cprior>
...
END DIVERSIONS

BEGIN PERIOD <iper>
<rno> <sfrsetting>
<rno> <sfrsetting>
...
END PERIOD
PERIOD block is encountered only the reaches specified in the new period block will be changed. A reach
the reaches. If a PERIOD block is not specified for the first stress period, then no stresses will be applied.
Block: OPTIONS
BOUNDNAMES—keyword to indicate that boundary names may be provided with the list of stream reach
cells.
PRINT INPUT—keyword to indicate that the list of stream reach information will be written to the list-
ing file immediately after it is read.
PRINT STAGE—keyword to indicate that the list of stream reach stages will be printed to the listing file
for every stress period in which “HEAD PRINT” is specified in Output Control. If there is no Out-
put Control option and PRINT STAGE is specified, then stages are printed for the last time step of
each stress period.
PRINT FLOWS—keyword to indicate that the list of stream reach flow rates will be printed to the listing
file for every stress period time step in which “BUDGET PRINT” is specified in Output Control. If
there is no Output Control option and “PRINT FLOWS” is specified, then flow rates are printed for
the last time step of each stress period.
SAVE FLOWS—keyword to indicate that stream reach flow terms will be written to the file specified with
STAGE—keyword to specify that record corresponds to stage.
stagefile—name of the binary output file to write stage information.
PACKAGE CONVERGENCE—keyword to specify that record corresponds to the package convergence
comma spaced values file.
package convergence filename—name of the comma spaced values output file to write package
convergence information.
obs6 filename—name of input file to define observations for the SFR package. See the “Observation
tion type(s) supported by the SFR package.
MOVER—keyword to indicate that this instance of the SFR Package can be used with the Water Mover
maximum picard iterations—value that defines the maximum number of Streamflow Routing
picard iterations allowed when solving for reach stages and flows as part of the GWF formulate
step. Picard iterations are used to minimize differences in SFR package results between subsequent
GWF picard (non-linear) iterations as a result of non-optimal reach numbering. If reaches are num-
bered in order, from upstream to downstream, MAXIMUM PICARD ITERATIONS can be set to 1
to reduce model run time. By default, MAXIMUM PICARD ITERATIONS is equal to 100.
maximum iterations—value that defines the maximum number of Streamflow Routing Newton-
Raphson iterations allowed for a reach. By default, MAXIMUM ITERATIONS is equal to 100.
maximum depth change—value that defines the depth closure tolerance. By default, DMAXCHG is
equal to 1 × 10−5 .
unit conversion—value (or conversion factor) that is used in calculating stream depth for stream
reach. A constant of 1.486 is used for flow units of cubic feet per second, and a constant of 1.0 is
used for units of cubic meters per second. The constant must be multiplied by 86,400 when using
time units of days in the simulation.
Block: DIMENSIONS
nreaches—integer value specifying the number of stream reaches. There must be NREACHES entries
in the PACKAGEDATA block.
Block: PACKAGEDATA
rno—integer value that defines the reach number associated with the specified PACKAGEDATA data on
the line. RNO must be greater than zero and less than or equal to NREACHES. Reach information
must be specified for every reach or the program will terminate with an error. The program will also
terminate with an error if information for a reach is specified more than once.
cellid—The keyword ‘NONE’ must be specified for reaches that are not connected to an underlying
GWF cell. The keyword ‘NONE’ is used for reaches that are in cells that have IDOMAIN values
less than one or are in areas not covered by the GWF model grid. Reach-aquifer flow is not calcu-
lated if the keyword ‘NONE’ is specified.
rlen—real value that defines the reach length. RLEN must be greater than zero.
rwid—real value that defines the reach width. RWID must be greater than zero.
rgrd—real value that defines the stream gradient (slope) across the reach. RGRD must be greater than
zero.
rtp—real value that defines the top elevation of the reach streambed.
rbth—real value that defines the thickness of the reach streambed. RBTH can be any value if CELLID
is ‘NONE’. Otherwise, RBTH must be greater than zero.
rhk—real value that defines the hydraulic conductivity of the reach streambed. RHK can be any positive
value if CELLID is ‘NONE’. Otherwise, RHK must be greater than zero.
man—real or character value that defines the Manning’s roughness coefficient for the reach. MAN must
be greater than zero. If the Options block includes a TIMESERIESFILE entry (see the “Time-
in place of a numeric value.
ncon—integer value that defines the number of reaches connected to the reach. If a value of zero is
specified for NCON an entry for RNO is still required in the subsequent CONNECTIONDATA
block.
ustrf—real value that defines the fraction of upstream flow from each upstream reach that is applied
as upstream inflow to the reach. The sum of all USTRF values for all reaches connected to the
same upstream reach must be equal to one and USTRF must be greater than or equal to zero. If the
ndv—integer value that defines the number of downstream diversions for the reach.
aux—represents the values of the auxiliary variables for each stream reach. The values of auxiliary vari-
ables must be present for each stream reach. The values must be specified in the order of the auxil-
iary variables specified in the OPTIONS block. If the package supports time series and the Options
obtained from a time series by entering the time-series name in place of a numeric value.
boundname—name of the stream reach cell. BOUNDNAME is an ASCII character variable that can
contain as many as 40 characters. If BOUNDNAME contains spaces in it, then the entire name must
be enclosed within single quotes.
rno—integer value that defines the reach number associated with the specified CONNECTIONDATA
data on the line. RNO must be greater than zero and less than or equal to NREACHES. Reach con-
nection information must be specified for every reach or the program will terminate with an error.
The program will also terminate with an error if connection information for a reach is specified
more than once.
ic—integer value that defines the reach number of the reach connected to the current reach and whether
it is connected to the upstream or downstream end of the reach. Negative IC numbers indicate con-
nected reaches are connected to the downstream end of the current reach. Positive IC numbers indi-
cate connected reaches are connected to the upstream end of the current reach. The absolute value
of IC must be greater than zero and less than or equal to NREACHES. IC should not be specified
when NCON is zero but must be specified otherwise.
Block: DIVERSIONS
rno—integer value that defines the reach number associated with the specified DIVERSIONS data on
the line. RNO must be greater than zero and less than or equal to NREACHES. Reach diversion
information must be specified for every reach with a NDV value greater than 0 or the program will
terminate with an error. The program will also terminate with an error if diversion information for a
given reach diversion is specified more than once.
idv—integer value that defines the downstream diversion number for the diversion for reach RNO. IDV
must be greater than zero and less than or equal to NDV for reach RNO.
iconr—integer value that defines the downstream reach that will receive the diverted water. IDV must
be greater than zero and less than or equal to NREACHES. Furthermore, reach ICONR must be a
downstream connection for reach RNO.
cprior—character string value that defines the the prioritization system for the diversion, such as when
insufficient water is available to meet all diversion stipulations, and is used in conjunction with the
value of FLOW value specified in the STRESS PERIOD DATA section. Available diversion options
include: (1) CPRIOR = ‘FRACTION’, then the amount of the diversion is computed as a fraction
of the streamflow leaving reach RNO (QDS ); in this case, 0.0 ≤ DIVFLOW ≤ 1.0. (2) CPRIOR
= ‘EXCESS’, a diversion is made only if QDS for reach RNO exceeds the value of DIVFLOW. If
this occurs, then the quantity of water diverted is the excess flow (QDS − DIVFLOW) and QDS
from reach RNO is set equal to DIVFLOW. This represents a flood-control type of diversion, as
described by Danskin and Hanson (2002). (3) CPRIOR = ‘THRESHOLD’, then if QDS in reach
RNO is less than the specified diversion flow DIVFLOW, no water is diverted from reach RNO.
If QDS in reach RNO is greater than or equal to DIVFLOW, DIVFLOW is diverted and QDS is
set to the remainder (QDS − DIVFLOW)). This approach assumes that once flow in the stream is
sufficiently low, diversions from the stream cease, and is the ‘priority’ algorithm that originally was
programmed into the STR1 Package (Prudic, 1989). (4) CPRIOR = ‘UPTO’ – if QDS in reach RNO
is greater than or equal to the specified diversion flow DIVFLOW, QDS is reduced by DIVFLOW.
If QDS in reach RNO is less than DIVFLOW, DIVFLOW is set to QDS and there will be no flow
available for reaches connected to downstream end of reach RNO.
Block: PERIOD
block.
rno—integer value that defines the reach number associated with the specified PERIOD data on the line.
RNO must be greater than zero and less than or equal to NREACHES.
sfrsetting—line of information that is parsed into a keyword and values. Keyword values that can be
used to start the SFRSETTING string include: STATUS, MANNING, STAGE, INFLOW, RAIN-
FALL, EVAPORATION, RUNOFF, DIVERSION, UPSTREAM FRACTION, and AUXILIARY.
STATUS <status>
MANNING <manning>
STAGE <stage>
INFLOW <inflow>
RAINFALL <rainfall>
EVAPORATION <evaporation>
RUNOFF <runoff>
DIVERSION <idv> <divflow>
UPSTREAM_FRACTION <upstream_fraction>
status—keyword option to define stream reach status. STATUS can be ACTIVE, INACTIVE, or SIM-
PLE. The SIMPLE STATUS option simulates streamflow using a user-specified stage for a reach
or a stage set to the top of the reach (depth = 0). In cases where the simulated leakage calculated
using the specified stage exceeds the sum of inflows to the reach, the stage is set to the top of the
reach and leakage is set equal to the sum of inflows. Upstream fractions should be changed using
the UPSTREAM FRACTION SFRSETTING if the status for one or more reaches is changed to
ACTIVE or INACTIVE. For example, if one of two downstream connections for a reach is inacti-
vated, the upstream fraction for the active and inactive downstream reach should be changed to 1.0
and 0.0, respectively, to ensure that the active reach receives all of the downstream outflow from the
upstream reach. By default, STATUS is ACTIVE.
manning—real or character value that defines the Manning’s roughness coefficient for the reach. MAN-
NING must be greater than zero. If the Options block includes a TIMESERIESFILE entry (see
stage—real or character value that defines the stage for the reach. The specified STAGE is only applied
if the reach uses the simple routing option. If STAGE is not specified for reaches that use the sim-
ple routing option, the specified stage is set to the top of the reach. If the Options block includes a
TIMESERIESFILE entry (see the “Time-Variable Input” section), values can be obtained from a
time series by entering the time-series name in place of a numeric value.
inflow—real or character value that defines the volumetric inflow rate for the streamflow routing reach.
If the Options block includes a TIMESERIESFILE entry (see the “Time-Variable Input” section),
values can be obtained from a time series by entering the time-series name in place of a numeric
value. By default, inflow rates are zero for each reach.
rainfall—real or character value that defines the volumetric rate per unit area of water added by pre-
cipitation directly on the streamflow routing reach. If the Options block includes a TIMESERIES-
FILE entry (see the “Time-Variable Input” section), values can be obtained from a time series by
entering the time-series name in place of a numeric value. By default, rainfall rates are zero for each
reach.
evaporation—real or character value that defines the volumetric rate per unit area of water sub-
tracted by evaporation from the streamflow routing reach. A positive evaporation rate should be
provided. If the Options block includes a TIMESERIESFILE entry (see the “Time-Variable Input”
section), values can be obtained from a time series by entering the time-series name in place of a
numeric value. If the volumetric evaporation rate for a reach exceeds the sources of water to the
reach (upstream and specified inflows, rainfall, and runoff but excluding groundwater leakage into
the reach) the volumetric evaporation rate is limited to the sources of water to the reach. By default,
evaporation rates are zero for each reach.
runoff—real or character value that defines the volumetric rate of diffuse overland runoff that enters
the streamflow routing reach. If the Options block includes a TIMESERIESFILE entry (see the
“Time-Variable Input” section), values can be obtained from a time series by entering the time-
series name in place of a numeric value. If the volumetric runoff rate for a reach is negative and
exceeds inflows to the reach (upstream and specified inflows, and rainfall but excluding groundwater
leakage into the reach) the volumetric runoff rate is limited to inflows to the reach and the volumet-
ric evaporation rate for the reach is set to zero. By default, runoff rates are zero for each reach.
DIVERSION—keyword to indicate diversion record.
idv—an integer value specifying which diversion of reach RNO that DIVFLOW is being specified for.
Must be less or equal to ndv for the current reach (RNO).
divflow—real or character value that defines the volumetric diversion (DIVFLOW) rate for the stream-
flow routing reach. If the Options block includes a TIMESERIESFILE entry (see the “Time-
upstream fraction—real value that defines the fraction of upstream flow (USTRF) from each
upstream reach that is applied as upstream inflow to the reach. The sum of all USTRF values for
all reaches connected to the same upstream reach must be equal to one.
Example Input File
BEGIN OPTIONS
UNIT_CONVERSION 1.486
BOUNDNAMES
PRINT_STAGE
PRINT_FLOWS
STAGE FILEOUT sfr-1.stage.bin
BUDGET FILEOUT sfr-1.cbc
END OPTIONS
#dimension block is required

BEGIN DIMENSIONS
NREACHES 37
END DIMENSIONS
BEGIN PACKAGEDATA
#rno k i j rlen rwid rgrd rtp rbth rhk man ncon ustrf ndv boundname
1 1 1 1 4500. 12 8.67E-04 1093.048 3.0 0.00003 0.03 1 1.0 0 reach1
2 1 2 2 7000. 12 8.67E-04 1088.059 3.0 0.00003 0.03 2 1.0 0 reach2
3 1 3 3 6000. 12 8.67E-04 1082.419 3.0 0.00003 0.03 2 1.0 0 reach3
4 1 3 4 5550. 12 8.67E-04 1077.408 3.0 0.00003 0.03 3 1.0 1 reach4
5 1 4 5 6500. 12 9.43E-04 1071.934 3.0 0.00003 0.03 2 1.0 0
6 1 5 6 5000. 12 9.43E-04 1066.509 3.0 0.00003 0.03 2 1.0 0
7 1 6 6 5000. 12 9.43E-04 1061.792 3.0 0.00003 0.03 2 1.0 0
8 1 7 6 5000. 12 9.43E-04 1057.075 3.0 0.00003 0.03 2 1.0 0
9 1 8 6 5000. 12 9.43E-04 1052.359 3.0 0.00003 0.03 2 1.0 0
10 1 3 5 5000. 10 5.45E-04 1073.636 2.0 0.00003 0.03 2 0.0 0 canal
11 1 3 6 5000. 10 5.45E-04 1070.909 2.0 0.00003 0.03 2 1.0 0 canal
12 1 3 7 4500. 10 5.45E-04 1068.318 2.0 0.00003 0.03 2 1.0 0 canal
13 1 4 8 6000. 10 5.45E-04 1065.455 2.0 0.00003 0.03 2 1.0 0 canal
14 1 5 8 5000. 10 5.45E-04 1062.455 2.0 0.00003 0.03 2 1.0 0 canal
15 1 6 8 2000. 10 5.45E-04 1060.545 2.0 0.00003 0.03 2 1.0 0 canal
16 1 510 2500. 10 1.81E-03 1077.727 3.0 0.00003 0.03 1 1.0 0
17 1 5 9 5000. 10 1.81E-03 1070.909 3.0 0.00003 0.03 2 1.0 0
18 1 6 8 3500. 10 1.81E-03 1063.182 3.0 0.00003 0.03 2 1.0 0
19 1 6 8 4000. 15 1.00E-03 1058.000 3.0 0.00003 0.03 3 1.0 0
20 1 7 7 5000. 15 1.00E-03 1053.500 3.0 0.00003 0.03 2 1.0 0
21 1 8 7 3500. 15 1.00E-03 1049.250 3.0 0.00003 0.03 2 1.0 0
22 1 8 6 2500. 15 1.00E-03 1046.250 3.0 0.00003 0.03 2 1.0 0
23 1 9 6 5000. 12 9.09E-04 1042.727 3.0 0.00003 0.03 3 1.0 0
24 1 10 7 5000. 12 9.09E-04 1038.182 3.0 0.00003 0.03 2 1.0 0
25 1 11 7 5000. 12 9.09E-04 1033.636 3.0 0.00003 0.03 2 1.0 0
26 1 12 7 5000. 12 9.09E-04 1029.091 3.0 0.00003 0.03 2 1.0 0
27 1 13 7 2000. 12 9.09E-04 1025.909 3.0 0.00003 0.03 2 1.0 0
28 1 14 9 5000. 55 9.67E-04 1037.581 3.0 0.00006 0.025 1 1.0 0
29 1 13 8 5500. 55 9.67E-04 1032.500 3.0 0.00006 0.025 2 1.0 0
30 1 13 7 5000. 55 9.67E-04 1027.419 3.0 0.00006 0.025 2 1.0 0
31 1 13 6 5000. 40 1.25E-03 1021.875 3.0 0.00006 0.025 3 1.0 0
32 1 13 5 5000. 40 1.25E-03 1015.625 3.0 0.00006 0.025 2 1.0 0
33 1 13 4 5000. 40 1.25E-03 1009.375 3.0 0.00006 0.025 2 1.0 0
34 1 13 3 5000. 40 1.25E-03 1003.125 3.0 0.00006 0.025 2 1.0 0
35 1 13 2 5000. 40 1.25E-03 996.8750 3.0 0.00006 0.025 2 1.0 0
36 1 13 1 3000. 40 1.25E-03 991.8750 3.0 0.00006 0.025 2 1.0 0
37 none 5000. 40 1.25E-03 985.6250 3.0 0.00006 0.025 1 1.0 0
END PACKAGEDATA
#rno ic1 ic2 ic3
1 -2
2 1 -3
3 2 -4
4 3 -5 -10
5 4 -6
6 5 -7
7 6 -8
8 7 -9
9 8 -23
10 4 -11
11 10 -12
12 11 -13
13 12 -14
14 13 -15
15 14 -19
16 -17
17 16 -18
18 17 -19
19 15 18 -20
20 19 -21
21 20 -22
22 21 -23
23 9 22 -24
24 23 -25
25 24 -26
26 25 -27
27 26 -31
28 -29
29 28 -30
30 29 -31
31 27 30 -32
32 31 -33
33 32 -34
34 33 -35
35 34 -36
36 35 -37
37 36
END CONNECTIONDATA
BEGIN DIVERSIONS
# rno idv iconr cprior
4 1 10 UPTO
END DIVERSIONS
BEGIN PERIOD 1
# rno sfrsetting
1 inflow 25.
16 inflow 10.
28 inflow 150.
4 diversion 1 10.
10 status simple
11 status simple
12 status simple
13 status simple
14 status simple
15 status simple
10 stage 1075.5454
11 stage 1072.6363
12 stage 1069.8727
13 stage 1066.8181
14 stage 1063.6181
15 stage 1061.5818
END PERIOD
Streamflow Routing Package observations include reach stage and all of the terms that contribute to the
continuity equation for each stream reach. Additional SFR Package observations include the sum of inflows
from upstream reaches and from mover terms (upstream-flow) and downstream outflow from a reach prior
to diversions and the mover package (downstream-flow). The data required for each SFR Package observa-
tion type is defined in table 17. Negative and positive values for sfr observations represent a loss from and
gain to the GWF model, respectively. For all other flow terms, negative and positive values represent a loss
from and gain from the SFR package, respectively.
Table 17. Available SFR Package observation types.

Package type
SFR stage rno or – Surface-water stage in a stream-reach bound-
boundname ary. If boundname is specified, boundname
must be unique for each reach.
SFR ext-inflow rno or – Inflow into a stream-reach from an external
boundname boundary for a stream-reach or a group of
stream-reaches.
SFR inflow rno or – Inflow into a stream-reach from upstream
boundname reaches for a stream-reach or a group of
stream-reaches.
SFR from-mvr rno or – Inflow into a stream-reach from the MVR
boundname package for a stream-reach or a group of
stream-reaches.
SFR rainfall rno or – Rainfall rate applied to a stream-reach or a
boundname group of stream-reaches.
SFR runoff rno or – Runoff rate applied to a stream-reach or a
boundname group of stream-reaches.
SFR sfr rno or – Simulated flow rate for a stream-reach and
boundname its aquifer connection for a stream-reach or a
group of stream-reaches.
SFR evaporation rno or – Simulated evaporation rate from a stream-
boundname reach or a group of stream-reaches.
SFR outflow rno or – Outflow from a stream-reach to downstream
boundname reaches for a stream-reach or a group of
stream-reaches.
SFR ext-outflow rno or – Outflow from a stream-reach to an external
boundname boundary for a stream-reach or a group of
stream-reaches.
SFR to-mvr rno or – Outflow from a stream-reach that is available
boundname for the MVR package for a stream-reach or a
group of stream-reaches.
SFR upstream-flow rno or – Upstream flow for a stream-reach or a group
boundname of stream-reaches from upstream reaches and
the MVR package.
SFR downstream-flow rno or – Downstream flow for a stream-reach or a
boundname group of stream-reaches prior to diversions
and the MVR package.
BEGIN OPTIONS
DIGITS 8
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.sfr.csv

# obsname obstype id
gage1stage STAGE reach4
gage2stage STAGE 7
gage2inflow INFLOW 7
gage2disch DOWNSTREAM-FLOW 7
gage3stage STAGE 14
END CONTINUOUS
BEGIN CONTINUOUS FILEOUT my_model.sfr.leakage.csv

# obsname obstype id
leak1 SFR reach1
leak10 SFR 10
leak11 SFR 11
leak12 SFR 12
leak13 SFR 13
leak14 SFR 14
leak15 SFR 15
leakcanal SFR canal #Sum of flows between canal reaches and groundwater
END CONTINUOUS
Lake (LAK) Package

Input to the Lake (LAK) Package is read from the file that has type “LAK6” in the Name File. Any num-
ber of LAK Packages can be specified for a single groundwater flow model.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
[BOUNDNAMES]
[PRINT_INPUT]
[PRINT_STAGE]
[PRINT_FLOWS]
[SAVE_FLOWS]
[STAGE FILEOUT <stagefile>]
[MOVER]
[SURFDEP <surfdep>]
[TIME_CONVERSION <time_conversion>]
[LENGTH_CONVERSION <length_conversion>]
END OPTIONS
BEGIN DIMENSIONS
NLAKES <nlakes>
NOUTLETS <noutlets>
NTABLES <ntables>
END DIMENSIONS
BEGIN PACKAGEDATA
<lakeno> <strt> <nlakeconn> [<aux(naux)>] [<boundname>]
<lakeno> <strt> <nlakeconn> [<aux(naux)>] [<boundname>]
...
END PACKAGEDATA
IF nlakeconn IS GREATER THAN ZERO FOR ANY LAKE

<lakeno> <iconn> <cellid(ncelldim)> <claktype> <bedleak> <belev> <telev> <connlen> <connwidth>
<lakeno> <iconn> <cellid(ncelldim)> <claktype> <bedleak> <belev> <telev> <connlen> <connwidth>
...
END CONNECTIONDATA
IF ntables IS GREATER THAN ZERO

BEGIN TABLES
<lakeno> TAB6 FILEIN <tab6_filename>
<lakeno> TAB6 FILEIN <tab6_filename>
...
END TABLES
IF noutlets IS GREATER THAN ZERO FOR ANY LAKE

BEGIN OUTLETS
<outletno> <lakein> <lakeout> <couttype> <invert> <width> <rough> <slope>
<outletno> <lakein> <lakeout> <couttype> <invert> <width> <rough> <slope>
...
END OUTLETS

BEGIN PERIOD <iper>
<number> <laksetting>
<number> <laksetting>
...
END PERIOD
PERIOD block is encountered only the lakes specified in the new period block will be changed. A lake
the lakes. If a PERIOD block is not specified for the first stress period, then no stresses will be applied.
Block: OPTIONS
BOUNDNAMES—keyword to indicate that boundary names may be provided with the list of lake cells.
PRINT INPUT—keyword to indicate that the list of lake information will be written to the listing file
PRINT STAGE—keyword to indicate that the list of lake stages will be printed to the listing file for every
stress period in which “HEAD PRINT” is specified in Output Control. If there is no Output Control
option and PRINT STAGE is specified, then stages are printed for the last time step of each stress
period.
PRINT FLOWS—keyword to indicate that the list of lake flow rates will be printed to the listing file for
every stress period time step in which “BUDGET PRINT” is specified in Output Control. If there is
no Output Control option and “PRINT FLOWS” is specified, then flow rates are printed for the last
time step of each stress period.
SAVE FLOWS—keyword to indicate that lake flow terms will be written to the file specified with “BUD-
GET FILEOUT” in Output Control.
STAGE—keyword to specify that record corresponds to stage.
stagefile—name of the binary output file to write stage information.
PACKAGE CONVERGENCE—keyword to specify that record corresponds to the package convergence

comma spaced values file.
package convergence filename—name of the comma spaced values output file to write package
convergence information.
obs6 filename—name of input file to define observations for the LAK package. See the “Observation
tion type(s) supported by the LAK package.
MOVER—keyword to indicate that this instance of the LAK Package can be used with the Water Mover
surfdep—real value that defines the surface depression depth for VERTICAL lake-GWF connec-
tions. If specified, SURFDEP must be greater than or equal to zero. If SURFDEP is not specified,
a default value of zero is used for all vertical lake-GWF connections.
time conversion—value that is used in converting outlet flow terms that use Manning’s equation or
gravitational acceleration to consistent time units. TIME CONVERSION should be set to 1.0, 60.0,
3,600.0, 86,400.0, and 31,557,600.0 when using time units (TIME UNITS) of seconds, minutes,
hours, days, or years in the simulation, respectively. CONVTIME does not need to be specified if no
lake outlets are specified or TIME UNITS are seconds.
length conversion—real value that is used in converting outlet flow terms that use Manning’s equa-
tion or gravitational acceleration to consistent length units. LENGTH CONVERSION should be set
to 3.28081, 1.0, and 100.0 when using length units (LENGTH UNITS) of feet, meters, or centime-
ters in the simulation, respectively. LENGTH CONVERSION does not need to be specified if no
lake outlets are specified or LENGTH UNITS are meters.
Block: DIMENSIONS
nlakes—value specifying the number of lakes that will be simulated for all stress periods.
noutlets—value specifying the number of outlets that will be simulated for all stress periods. If
NOUTLETS is not specified, a default value of zero is used.
ntables—value specifying the number of lakes tables that will be used to define the lake stage, volume
relation, and surface area. If NTABLES is not specified, a default value of zero is used.
Block: PACKAGEDATA
lakeno—integer value that defines the lake number associated with the specified PACKAGEDATA data
on the line. LAKENO must be greater than zero and less than or equal to NLAKES. Lake informa-
tion must be specified for every lake or the program will terminate with an error. The program will
also terminate with an error if information for a lake is specified more than once.
strt—real value that defines the starting stage for the lake.
nlakeconn—integer value that defines the number of GWF cells connected to this (LAKENO) lake.
There can only be one vertical lake connection to each GWF cell. NLAKECONN must be greater
than zero.
aux—represents the values of the auxiliary variables for each lake. The values of auxiliary variables
must be present for each lake. The values must be specified in the order of the auxiliary variables
specified in the OPTIONS block. If the package supports time series and the Options block includes
a TIMESERIESFILE entry (see the “Time-Variable Input” section), values can be obtained from a
time series by entering the time-series name in place of a numeric value.
boundname—name of the lake cell. BOUNDNAME is an ASCII character variable that can contain
as many as 40 characters. If BOUNDNAME contains spaces in it, then the entire name must be
enclosed within single quotes.
lakeno—integer value that defines the lake number associated with the specified CONNECTIONDATA
data on the line. LAKENO must be greater than zero and less than or equal to NLAKES. Lake
connection information must be specified for every lake connection to the GWF model (NLAKE-
CONN) or the program will terminate with an error. The program will also terminate with an error
if connection information for a lake connection to the GWF model is specified more than once.
iconn—integer value that defines the GWF connection number for this lake connection entry. ICONN
must be greater than zero and less than or equal to NLAKECONN for lake LAKENO.
claktype—character string that defines the lake-GWF connection type for the lake connection. Pos-
sible lake-GWF connection type strings include: VERTICAL–character keyword to indicate the
lake-GWF connection is vertical and connection conductance calculations use the hydraulic con-
ductivity corresponding to the K33 tensor component defined for CELLID in the NPF package.
HORIZONTAL–character keyword to indicate the lake-GWF connection is horizontal and connec-
tion conductance calculations use the hydraulic conductivity corresponding to the K11 tensor com-
ponent defined for CELLID in the NPF package. EMBEDDEDH–character keyword to indicate the
lake-GWF connection is embedded in a single cell and connection conductance calculations use the
hydraulic conductivity corresponding to the K11 tensor component defined for CELLID in the NPF
package. EMBEDDEDV–character keyword to indicate the lake-GWF connection is embedded in
a single cell and connection conductance calculations use the hydraulic conductivity corresponding
to the K33 tensor component defined for CELLID in the NPF package. Embedded lakes can only be
connected to a single cell (NLAKECONN = 1) and there must be a lake table associated with each
embedded lake.
bedleak—character string or real value that defines the bed leakance for the lake-GWF connection.
BEDLEAK must be greater than or equal to zero or specified to be NONE. If BEDLEAK is speci-
fied to be NONE, the lake-GWF connection conductance is solely a function of aquifer properties in
the connected GWF cell and lakebed sediments are assumed to be absent.
belev—real value that defines the bottom elevation for a HORIZONTAL lake-GWF connection. Any
value can be specified if CLAKTYPE is VERTICAL, EMBEDDEDH, or EMBEDDEDV. If CLAK-
TYPE is HORIZONTAL and BELEV is not equal to TELEV, BELEV must be greater than or equal
to the bottom of the GWF cell CELLID. If BELEV is equal to TELEV, BELEV is reset to the bot-
tom of the GWF cell CELLID.
telev—real value that defines the top elevation for a HORIZONTAL lake-GWF connection. Any value
can be specified if CLAKTYPE is VERTICAL, EMBEDDEDH, or EMBEDDEDV. If CLAKTYPE
is HORIZONTAL and TELEV is not equal to BELEV, TELEV must be less than or equal to the top
of the GWF cell CELLID. If TELEV is equal to BELEV, TELEV is reset to the top of the GWF cell
CELLID.
connlen—real value that defines the distance between the connected GWF CELLID node and the lake
for a HORIZONTAL, EMBEDDEDH, or EMBEDDEDV lake-GWF connection. CONLENN must
be greater than zero for a HORIZONTAL, EMBEDDEDH, or EMBEDDEDV lake-GWF connec-
tion. Any value can be specified if CLAKTYPE is VERTICAL.
connwidth—real value that defines the connection face width for a HORIZONTAL lake-GWF connec-
tion. CONNWIDTH must be greater than zero for a HORIZONTAL lake-GWF connection. Any
value can be specified if CLAKTYPE is VERTICAL, EMBEDDEDH, or EMBEDDEDV.
Block: TABLES
lakeno—integer value that defines the lake number associated with the specified TABLES data on the
line. LAKENO must be greater than zero and less than or equal to NLAKES. The program will ter-
minate with an error if table information for a lake is specified more than once or the number of
specified tables is less than NTABLES.
TAB6—keyword to specify that record corresponds to a table file.
tab6 filename—character string that defines the path and filename for the file containing lake table
data for the lake connection. The TAB6 FILENAME file includes the number of entries in the file
and the relation between stage, volume, and surface area for each entry in the file. Lake table files
for EMBEDDEDH and EMBEDDEDV lake-GWF connections also include lake-GWF exchange
area data for each entry in the file. Instructions for creating the TAB6 FILENAME input file are
provided in Lake Table Input File section.
Block: OUTLETS
outletno—integer value that defines the outlet number associated with the specified OUTLETS data
on the line. OUTLETNO must be greater than zero and less than or equal to NOUTLETS. Outlet
information must be specified for every outlet or the program will terminate with an error. The pro-
gram will also terminate with an error if information for a outlet is specified more than once.
lakein—integer value that defines the lake number that outlet is connected to. LAKEIN must be
greater than zero and less than or equal to NLAKES.
lakeout—integer value that defines the lake number that outlet discharge from lake outlet OUTLETNO
is routed to. LAKEOUT must be greater than or equal to zero and less than or equal to NLAKES.
If LAKEOUT is zero, outlet discharge from lake outlet OUTLETNO is discharged to an external
boundary.
couttype—character string that defines the outlet type for the outlet OUTLETNO. Possible COUT-
TYPE strings include: SPECIFIED–character keyword to indicate the outlet is defined as a specified
flow. MANNING–character keyword to indicate the outlet is defined using Manning’s equation.
WEIR–character keyword to indicate the outlet is defined using a sharp weir equation.
invert—real value that defines the invert elevation for the lake outlet. Any value can be specified if
COUTTYPE is SPECIFIED. If the Options block includes a TIMESERIESFILE entry (see the
width—real value that defines the width of the lake outlet. Any value can be specified if COUTTYPE
is SPECIFIED. If the Options block includes a TIMESERIESFILE entry (see the “Time-Variable
Input” section), values can be obtained from a time series by entering the time-series name in place
of a numeric value.
rough—real value that defines the roughness coefficient for the lake outlet. Any value can be specified
if COUTTYPE is not MANNING. If the Options block includes a TIMESERIESFILE entry (see
slope—real value that defines the bed slope for the lake outlet. Any value can be specified if COUT-
TYPE is not MANNING. If the Options block includes a TIMESERIESFILE entry (see the “Time-
Block: PERIOD
block.
number—integer value that defines the lake or outlet number associated with the specified PERIOD
data on the line. NUMBER must be greater than zero and less than or equal to NLAKES for a lake
number and less than or equal to NOUTLETS for an outlet number.
laksetting—line of information that is parsed into a keyword and values. Keyword values that can
be used to start the LAKSETTING string include both keywords for lake settings and keywords
for outlet settings. Keywords for lake settings include: STATUS, STAGE, RAINFALL, EVAPO-
RATION, RUNOFF, INFLOW, WITHDRAWAL, and AUXILIARY. Keywords for outlet settings
include RATE, INVERT, WIDTH, SLOPE, and ROUGH.
STATUS <status>
STAGE <stage>
RAINFALL <rainfall>
EVAPORATION <evaporation>
RUNOFF <runoff>
INFLOW <inflow>
WITHDRAWAL <withdrawal>
RATE <rate>
INVERT <invert>
WIDTH <width>
SLOPE <slope>
ROUGH <rough>
status—keyword option to define lake status. STATUS can be ACTIVE, INACTIVE, or CONSTANT.
By default, STATUS is ACTIVE.
stage—real or character value that defines the stage for the lake. The specified STAGE is only applied
if the lake is a constant stage lake. If the Options block includes a TIMESERIESFILE entry (see
rainfall—real or character value that defines the rainfall rate (LT −1 ) for the lake. Value must be
greater than or equal to zero. If the Options block includes a TIMESERIESFILE entry (see the
evaporation—real or character value that defines the maximum evaporation rate (LT −1 ) for the lake.
Value must be greater than or equal to zero. If the Options block includes a TIMESERIESFILE
entry (see the “Time-Variable Input” section), values can be obtained from a time series by enter-
ing the time-series name in place of a numeric value.
runoff—real or character value that defines the runoff rate (L3 T −1 ) for the lake. Value must be greater
than or equal to zero. If the Options block includes a TIMESERIESFILE entry (see the “Time-
inflow—real or character value that defines the volumetric inflow rate (L3 T −1 ) for the lake. Value
must be greater than or equal to zero. If the Options block includes a TIMESERIESFILE entry (see
series name in place of a numeric value. By default, inflow rates are zero for each lake.
withdrawal—real or character value that defines the maximum withdrawal rate (L3 T −1 ) for the lake.
Value must be greater than or equal to zero. If the Options block includes a TIMESERIESFILE
entry (see the “Time-Variable Input” section), values can be obtained from a time series by enter-
ing the time-series name in place of a numeric value.
rate—real or character value that defines the extraction rate for the lake outflow. A positive value
indicates inflow and a negative value indicates outflow from the lake. RATE only applies to active
(IBOUND > 0) lakes. A specified RATE is only applied if COUTTYPE for the OUTLETNO is
SPECIFIED. If the Options block includes a TIMESERIESFILE entry (see the “Time-Variable
of a numeric value. By default, the RATE for each SPECIFIED lake outlet is zero.
invert—real or character value that defines the invert elevation for the lake outlet. A specified
INVERT value is only used for active lakes if COUTTYPE for lake outlet OUTLETNO is not
SPECIFIED. If the Options block includes a TIMESERIESFILE entry (see the “Time-Variable
of a numeric value.
rough—real value that defines the roughness coefficient for the lake outlet. Any value can be specified
if COUTTYPE is not MANNING. If the Options block includes a TIMESERIESFILE entry (see
width—real or character value that defines the width of the lake outlet. A specified WIDTH value is
only used for active lakes if COUTTYPE for lake outlet OUTLETNO is not SPECIFIED. If the
slope—real or character value that defines the bed slope for the lake outlet. A specified SLOPE value is
only used for active lakes if COUTTYPE for lake outlet OUTLETNO is MANNING. If the Options
obtained from a time series by entering the time-series name in place of a numeric value.
Example Input File

BEGIN OPTIONS
PRINT_INPUT
BOUNDNAMES
PRINT_STAGE
PRINT_FLOWS
STAGE FILEOUT lak-1.stage.bin
BUDGET FILEOUT lak-1.cbc
END OPTIONS
BEGIN DIMENSIONS
NLAKES 1
NOUTLETS 1
END DIMENSIONS
BEGIN PACKAGEDATA
# lakeno strt lakeconn boundname
1 110.00 57 LAKE_1
END PACKAGEDATA
# lakeno iconn layer row column ctype bedleak belev telev dx width
1 1 1 7 6 HORIZONTAL 0.1 0 0 500 500
1 2 1 8 6 HORIZONTAL 0.1 0 0 500 500
1 3 1 9 6 HORIZONTAL 0.1 0 0 500 500
1 4 1 10 6 HORIZONTAL 0.1 0 0 500 500
1 5 1 11 6 HORIZONTAL 0.1 0 0 500 500
1 6 1 6 7 HORIZONTAL 0.1 0 0 500 500
1 7 2 7 7 VERTICAL 0.1 0 0 0 0
1 8 2 8 7 VERTICAL 0.1 0 0 0 0
1 9 2 8 7 HORIZONTAL 0.1 0 0 250 500
1 10 2 9 7 VERTICAL 0.1 0 0 0 0
1 11 2 9 7 HORIZONTAL 0.1 0 0 250 500
1 12 2 10 7 VERTICAL 0.1 0 0 0 0
1 13 2 10 7 HORIZONTAL 0.1 0 0 250 500
1 14 2 11 7 VERTICAL 0.1 0 0 0 0
1 15 1 12 7 HORIZONTAL 0.1 0 0 500 500
1 16 1 6 8 HORIZONTAL 0.1 0 0 500 500
1 17 2 7 8 VERTICAL 0.1 0 0 0 0
1 18 2 7 8 HORIZONTAL 0.1 0 0 250 500
1 19 3 8 8 VERTICAL 0.1 0 0 0 0
1 20 3 9 8 VERTICAL 0.1 0 0 0 0
1 21 3 10 8 VERTICAL 0.1 0 0 0 0
1 22 2 11 8 VERTICAL 0.1 0 0 0 0
1 23 2 11 8 HORIZONTAL 0.1 0 0 250 500
1 24 1 12 8 HORIZONTAL 0.1 0 0 500 500
1 25 1 6 9 HORIZONTAL 0.1 0 0 500 500
1 26 2 7 9 VERTICAL 0.1 0 0 0 0
1 27 2 7 9 HORIZONTAL 0.1 0 0 250 500

1 28 3 8 9 VERTICAL 0.1 0 0 0 0
1 29 3 9 9 VERTICAL 0.1 0 0 0 0
1 30 3 10 9 VERTICAL 0.1 0 0 0 0
1 31 2 11 9 VERTICAL 0.1 0 0 0 0
1 32 2 11 9 HORIZONTAL 0.1 0 0 250 500
1 33 1 12 9 HORIZONTAL 0.1 0 0 500 500
1 34 1 6 10 HORIZONTAL 0.1 0 0 500 500
1 35 2 7 10 VERTICAL 0.1 0 0 0 0
1 36 2 7 10 HORIZONTAL 0.1 0 0 250 500
1 37 3 8 10 VERTICAL 0.1 0 0 0 0
1 38 3 9 10 VERTICAL 0.1 0 0 0 0
1 39 3 10 10 VERTICAL 0.1 0 0 0 0
1 40 2 11 10 VERTICAL 0.1 0 0 0 0
1 41 2 11 10 HORIZONTAL 0.1 0 0 250 500
1 42 1 12 10 HORIZONTAL 0.1 0 0 500 500
1 43 1 6 11 HORIZONTAL 0.1 0 0 500 500
1 44 2 7 11 VERTICAL 0.1 0 0 0 0
1 45 2 8 11 VERTICAL 0.1 0 0 0 0
1 46 2 8 11 HORIZONTAL 0.1 0 0 250 500
1 47 2 9 11 VERTICAL 0.1 0 0 0 0
1 48 2 9 11 HORIZONTAL 0.1 0 0 250 500
1 49 2 10 11 VERTICAL 0.1 0 0 0 0
1 50 2 10 11 HORIZONTAL 0.1 0 0 250 500
1 51 2 11 11 VERTICAL 0.1 0 0 0 0
1 52 1 12 11 HORIZONTAL 0.1 0 0 500 500
1 53 1 7 12 HORIZONTAL 0.1 0 0 500 500
1 54 1 8 12 HORIZONTAL 0.1 0 0 500 500
1 55 1 9 12 HORIZONTAL 0.1 0 0 500 500
1 56 1 10 12 HORIZONTAL 0.1 0 0 500 500
1 57 1 11 12 HORIZONTAL 0.1 0 0 500 500
END CONNECTIONDATA
BEGIN OUTLETS
# outletno lakein lakeout couttype invert width rough slope
1 1 0 SPECIFIED 0 0 0 0
END OUTLETS
BEGIN PERIOD 1
1 RAINFALL 0.0116
1 EVAPORATION 0.0103
END PERIOD
BEGIN PERIOD 100

1 STATUS CONSTANT
1 STAGE 110.
END PERIOD

Lake Package observations include lake stage and all of the terms that contribute to the continuity equa-
tion for each lake. Additional LAK Package observations include flow rates for individual outlets, lakes, or
groups of lakes (outlet); the lake volume (volume); lake surface area (surface-area); wetted area for
a lake-aquifer connection (wetted-area); and the conductance for a lake-aquifer connection conductance
(conductance). The data required for each LAK Package observation type is defined in table 18. Nega-
tive and positive values for lak observations represent a loss from and gain to the GWF model, respectively.
For all other flow terms, negative and positive values represent a loss from and gain from the LAK package,
respectively.
Table 18. Available LAK Package observation types.

Package type
LAK stage lakeno or – Surface-water stage in a lake. If boundname
boundname is specified, boundname must be unique for
each lake.
LAK ext-inflow lakeno or – Specified inflow into a lake or group of
boundname lakes.
LAK outlet-inflow lakeno or – Simulated inflow from upstream lake outlets
boundname into a lake or group of lakes.
LAK inflow lakeno or – Sum of specified inflow and simulated inflow
boundname from upstream lake outlets into a lake or
group of lakes.
LAK from-mvr lakeno or – Inflow into a lake or group of lakes from the
boundname MVR package.
LAK rainfall lakeno or – Rainfall rate applied to a lake or group of
boundname lakes.
LAK runoff lakeno or – Runoff rate applied to a lake or group of
boundname lakes.
LAK lak lakeno or iconn Simulated flow rate for a lake or group
boundname or – of lakes and its aquifer connection(s). If
boundname is not specified for ID, then the
simulated lake-aquifer flow rate at a specific
lake connection is observed. In this case,
ID2 must be specified and is the connection
number iconn.
LAK withdrawal lakeno or – Specified withdrawal rate from a lake or
boundname group of lakes.
LAK evaporation lakeno or – Simulated evaporation rate from a lake or
LAK ext-outflow outletno or – External outflow from a lake outlet, a lake, or
boundname a group of lakes to an external boundary. If
external outflow from a specific lake outlet
is observed. In this case, ID is the outlet
number outletno.
LAK to-mvr outletno or – Outflow from a lake outlet, a lake, or a group
boundname of lakes that is available for the MVR pack-
age. If boundname is not specified for ID,
then the outflow available for the MVR pack-
age from a specific lake outlet is observed. In
this case, ID is the outlet number outletno.
LAK storage lakeno or – Simulated storage flow rate for a lake or
Table 18. Available LAK Package observation types.—Continued

Package type
LAK constant lakeno or – Simulated constant-flow rate for a lake or
LAK outlet outletno or – Simulated outlet flow rate from a lake outlet,
boundname a lake, or a group of lakes. If boundname
is not specified for ID, then the flow from a
specific lake outlet is observed. In this case,
ID is the outlet number outletno.
LAK volume lakeno or – Simulated lake volume or group of lakes.
boundname
LAK surface-area lakeno or – Simulated surface area for a lake or group of
boundname lakes.
LAK wetted-area lakeno or iconn Simulated wetted-area for a lake or group
wetted area of a specific lake connection is
observed. In this case, ID2 must be specified
and is the connection number iconn.
LAK conductance lakeno or iconn Calculated conductance for a lake or group
boundname is not specified for ID, then
the calculated conductance of a specific
lake connection is observed. In this case,
ID2 must be specified and is the connection
number iconn.
BEGIN OPTIONS
DIGITS 10
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.lak.csv

l1stage stage 1
l1vol volume 1
vflow lak 1 1
hflow1 lak 1 2
hflow2 lak 1 3
hflow3 lak 1 4
hflow4 lak 1 5
lakflow lak lake_1
END CONTINUOUS
Lake Table Input File

Lake tables of stage, volume, and surface area can be specified for individual lakes. Lake tables are spec-
ified by including file names in the LAKE TABLES block of the LAK Package. These file names correspond
to a lake table input file. The format of the lake table input file is described here.
Structure of Blocks
BEGIN DIMENSIONS
NROW <nrow>
NCOL <ncol>
END DIMENSIONS
BEGIN TABLE
<stage> <volume> <sarea> [<barea>]
<stage> <volume> <sarea> [<barea>]
...
END TABLE
Block: DIMENSIONS
nrow—integer value specifying the number of rows in the lake table. There must be NROW rows of
data in the TABLE block.
ncol—integer value specifying the number of columns in the lake table. There must be NCOL columns
of data in the TABLE block. For lakes with HORIZONTAL and/or VERTICAL CTYPE connec-
tions, NCOL must be equal to 3. For lakes with EMBEDDEDH or EMBEDDEDV CTYPE connec-
tions, NCOL must be equal to 4.
Block: TABLE
stage—real value that defines the stage corresponding to the remaining data on the line.
volume—real value that defines the lake volume corresponding to the stage specified on the line.
sarea—real value that defines the lake surface area corresponding to the stage specified on the line.
barea—real value that defines the lake-GWF exchange area corresponding to the stage specified on the
line. BAREA is only specified if the CLAKTYPE for the lake is EMBEDDEDH or EMBEDDEDV.
Example Input File

begin dimensions
nrow 11
ncol 3
end dimensions
begin table
# stage volume sarea
0 0. 0.
1 0.5 1.
2 1.0 2.
3 2.0 2.
4 3.0 2.
5 4.0 2.
6 5.0 2.
7 6.0 2.
8 7.0 2.
9 8.0 2.
10 9.0 2.
end table
Unsaturated Zone Flow (UZF) Package

Input to the Unsaturated Zone Flow (UZF) Package is read from the file that has type “UZF6” in the Name
File.
Structure of Blocks
FOR EACH SIMULATION

BEGIN OPTIONS
[BOUNDNAMES]
[PRINT_INPUT]
[PRINT_FLOWS]
[SAVE_FLOWS]
[WATER_CONTENT FILEOUT <wcfile>]
[MOVER]
[SIMULATE_ET]
[LINEAR_GWET]
[SQUARE_GWET]
[SIMULATE_GWSEEP]
[UNSAT_ETWC]
[UNSAT_ETAE]
END OPTIONS
BEGIN DIMENSIONS
NUZFCELLS <nuzfcells>
NTRAILWAVES <ntrailwaves>
NWAVESETS <nwavesets>
END DIMENSIONS
BEGIN PACKAGEDATA
<iuzno> <cellid(ncelldim)> <landflag> <ivertcon> <surfdep> <vks> <thtr> <thts> <thti> <eps> [<boundname>]
<iuzno> <cellid(ncelldim)> <landflag> <ivertcon> <surfdep> <vks> <thtr> <thts> <thti> <eps> [<boundname>]
...
END PACKAGEDATA

BEGIN PERIOD <iper>
<iuzno> <finf> <pet> <extdp> <extwc> <ha> <hroot> <rootact> [<aux(naux)>]
<iuzno> <finf> <pet> <extdp> <extwc> <ha> <hroot> <rootact> [<aux(naux)>]
...
END PERIOD
PERIOD block is encountered only the UZF cells specified in the new period block will be changed. A UZF
cell not specified in the new period block will continue to behave according to its specification in the previous
the UZF cells. If a PERIOD block is not specified for the first stress period, then no stresses will be applied.

Manual Modflow 6 101 150

Uploaded by

Copyright:

Available Formats

Manual Modflow 6 101 150

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Modflow 6 101 150

Uploaded by

Copyright:

Available Formats

Groundwater Flow (GWF) Model Input 89

Recharge (RCH) Package – List-Based Input

FOR EACH SIMULATION

FOR ANY STRESS PERIOD

Example Input File

Available observation types

Table 14. Available RCH Package observation types.

Stress Observation ID ID2 Description

Example Observation Input File

BEGIN CONTINUOUS FILEOUT my_model.rch.csv

Recharge (RCH) Package – Array-Based Input

FOR EACH SIMULATION

FOR ANY STRESS PERIOD

Example Input File

# For this model, the absence of an IRCH array causes

# auxiliary variable (var1) array

# auxiliary variable (var2) array

# auxiliary variable (mymult) array

Evapotranspiration (EVT) Package – List-Based Input

FOR EACH SIMULATION

FOR ANY STRESS PERIOD

boundname—name of the evapotranspiration cell. BOUNDNAME is an ASCII character variable that

Example Input File

# Example for structured model with list-based input

Available observation types

Table 15. Available EVT Package observation types.

Stress Observation ID ID2 Description

Example Observation Input File

BEGIN CONTINUOUS FILEOUT my_model.evt.csv

Evapotranspiration (EVT) Package – Array-Based Input

FOR EACH SIMULATION

FOR ANY STRESS PERIOD

surface—is the elevation of the ET surface (L).

Example Input File

#ET surface elevation

Multi-Aquifer Well (MAW) Package

FOR EACH SIMULATION

FOR ANY STRESS PERIOD

Example Input File – Conductance Calculated using Thiem Equation

begin period 100

Example Input File – Conductance Calculated using Screen Geometry

begin period 100

Example Input File – Flowing Well with Conductance Specified

Available observation types

Table 16. Available MAW Package observation types.

Stress Observation ID ID2 Description

Table 16. Available MAW Package observation types.—Continued

Stress Observation ID ID2 Description

Example Observation Input File

BEGIN CONTINUOUS FILEOUT my_model.maw.csv

Streamflow Routing (SFR) Package

FOR EACH SIMULATION

IF ndv IS GREATER THAN ZERO FOR ANY REACH

FOR ANY STRESS PERIOD

Example Input File

#dimension block is required

Available observation types

Table 17. Available SFR Package observation types.

Stress Observation ID ID2 Description

Example Observation Input File