Manual Modflow 6 251 292

Time-Variable Input 239
Time-Variable Input
In earlier versions of MODFLOW, most stress-boundary packages read input on a stress period-by-stress
period basis, and those values were held constant during the stress period. In MODFLOW 6, many stress val-
ues can be specified with a higher degree of time resolution (from time step to time step or from subtime step
to subtime step) by using one of two time-variable approaches. Boundaries for which data are read as lists of
cells can reference “time series” to implement the time variation. Boundaries for which data are read as 2-D
arrays can reference “time-array series” to do so.
When MODFLOW 6 needs data from a time series or time-array series for a time interval representing
a time step or subtime step, the series is queried to provide a time-averaged value or array of values for the
requested time interval. For each series, the user specifies an interpolation method that determines how the
value is assumed to behave between listed times. The interpolation method thus determines how the time aver-
aging is performed. When a time-array series is used, interpolation is performed on an element-by-element
basis to generate a 2-D array of interpolated values as needed.
The supported interpolation methods are STEPWISE, LINEAR, and LINEAREND. When the STEPWISE
interpolation method is used, the value is assumed to remain constant at the value specified in one time-series
record until the time listed in the subsequent record, when the value changes abruptly to the new value. In
the LINEAR interpolation method, the value is assumed to change linearly between times listed in sequen-
tial records. LINEAREND is like LINEAR, except that instead of using the average value over a time step,
the value at the end of a time step is used. Following sections document the structure of time-series and time-
array-series files and their use.
Time Series
Any package that reads data as a list of cells and associated time-dependent input values can obtain those
values from time series. For example, flow rates for a well or stage for a river boundary can be extracted from
time series. During a simulation, values used for time-varying stresses (or auxiliary values) are based on the
values provided in the time series and are updated each time step (or each subtime step, as appropriate). Input
to define and use time series is described in this section.
A time series consists of a chronologically ordered list of time-series records, where each record includes
a discrete time and a corresponding value. The value can be used to provide any time-varying numeric input,
including stresses and auxiliary variables. A time series can be referenced in input for one or multiple vari-
ables in a given package.
Time-Series Files
Each time-series file is associated with exactly one package, and the name of a time-series file associated
with a package is listed in the OPTIONS block for the package, preceded by the keywords “TS6 FILEIN.”
Any number of time-series files can be associated with a given package; a TS6 entry is required for each time-
series file. A time-series file can contain one or more time series. Time-series files are not listed in either the
simulation Name File or the model Name File. A given time-series file cannot be associated with more than
one package. By convention, the extension “.ts” is used in names of time-series files.
Each time-series file contains an ATTRIBUTES block followed by a TIMESERIES block containing a
series of lines, where each line contains a time followed by values for one or more time series at the speci-
fied time. The ATTRIBUTES block is required to define the name for each time series and the interpolation
method to be used when an operation requires interpolation between times listed in the time series.
The time-series name(s) and interpolation method(s) are specified in the ATTRIBUTES block. Scale
factor(s) for multiplying values optionally can be provided in the ATTRIBUTES block. NAME, METHOD,
240 MODFLOW 6 – Description of Input and Output
METHODS, SFAC, and SFACS are keywords. For appearance when a time-series file includes multiple time
series, NAMES can be used as a synonym for the NAME keyword.
The syntax of the ATTRIBUTES block for a time-series file containing a single time series is as follows:
BEGIN ATTRIBUTES
NAME time-series-name
METHOD interpolation-method
[ SFAC sfac ]
END ATTRIBUTES
When a time-series file contains multiple time series, the time-series names are listed in a NAME (or
NAMES) entry, similar to the example above. If the time series are to have different interpolation methods,
the METHODS keyword is used in place of the METHOD keyword, and an interpolation method correspond-
ing to each name is listed. If the time series are to have different scale factors, the SFACS keyword is used in
place of the SFAC keyword.
The syntax of the ATTRIBUTES block for a time-series file containing multiple time series is as follows:
BEGIN ATTRIBUTES
NAMES time-series-name-1 [ time-series-name-2 ... time-series-name-n ]
METHODS interpolation-method-1 [ interpolation-method-2 ... ]
[ SFACS sfac-1 [ sfac-2 ... sfac-n ] ]
END ATTRIBUTES
In a case where a time-series file contains multiple time series and a single interpolation method applies to
all time series in the file, the METHOD keyword can be used, and a single interpolation method is read. Sim-
ilary, if a single scale factor applies to all time series in the file, the SFAC keyword can be used, and a single
scale factor is read.
The ATTRIBUTES block is followed by a TIMESERIES block of the form:
BEGIN TIMESERIES
time-series record
time-series record
...
time-series record
END TIMESERIES
where each time-series record is of the form:

tsr-time tsr-value-1 [ tsr-value-2 tsr-value-3 ... ]
In situations where an individual time series in a file containing multiple time series does not include val-
ues for all specified times, a “no-data” value (3.0E30) can be used as a placeholder. When the “no-data” value
is read for a time series, that time series will not include a time-series record for the corresponding time.
Explanation of Variables
time-series-name—Name by which a package references a particular time series. The name must be
unique among all time series used in a package.
interpolation-method—Interpolation method, which is either STEPWISE, LINEAR, or LINEAREND.
sfac—Scale factor, which will multiply all tsr-value values in the time series. SFAC and SFACS are
optional attributes; if omitted, sfac = 1.0.
tsr-time—A numeric time relative to the start of the simulation, in the time unit used in the simulation.
Times must be strictly increasing.
tsr-value—A numeric data value corresponding to tsr-time. The value 3.0E30 is treated as a “no-data”
value and can be used wherever a time series in a file containing multiple time series does not have a
value corresponding to the time specified by tsr-time.
Using Time Series in a Package

When one or more time series are to define numeric input for a package, the name(s) of time-series files
need to be defined in an OPTIONS block at the top of the package input file. The keyword TS6 followed by
the keyword FILEIN are used to identify the name of each time-series file. Each time-series file can contain
one or more time series, and each OPTIONS block can contain zero or more TS6 entries. The syntax for a TS6
entry in an OPTIONS block is:
BEGIN OPTIONS
TS6 FILEIN time-series-file-name
END OPTIONS
Explanation of Variables Read from a Package Input File:
TS6—Keyword to specify that record corresponds to a time-series file.
FILEIN—Keyword to specify that an input filename is expected next.
time-series-file-name—Name of a time-series file in which time series used in the package are defined.
Each time series has a name. To specify that time-dependent values for one or more stress periods is to
be extracted from a time series, the time-series name is listed in the position where a numeric value normally
would be provided.
Example use of time series to define package input

The following example illustrates the use of three time series in input for the Well Package in a model with
a structured grid. For an unstructured grid, the layer, row, and column indices for each observation would be
replaced by a node number.
Contents of file “well pump rates.ts”:

BEGIN ATTRIBUTES
NAMES well-A-series well-B-series well-C-series
METHODS stepwise linear stepwise
END ATTRIBUTES
BEGIN TIMESERIES
# time well-A-series well-B-series well-C-series
0.0 0.0 0.0 0.0
1.0 -500.0 0.0 -400.0
2.0 -500.0 -1000.0 -500.0
5.0 -500.0 -1200.0 -200.0
8.0 -500.0 -1100.0 0.0
END TIMESERIES
Contents of the Well Package input file:

BEGIN OPTIONS
TS6 FILEIN well_pump_rates.ts
END OPTIONS
BEGIN DIMENSIONS
MAXBOUND 4
END DIMENSIONS
BEGIN PERIOD 2
#layer row col Q (or time series)
9 192 44 well-A-series
10 43 17 well-B-series
11 12 17 well-C-series
END PERIOD
BEGIN PERIOD 4
#layer row col Q (or time series)
9 192 44 well-A-series
10 43 17 well-B-series
11 12 17 well-C-series
2 27 36 -900.0
END PERIOD
BEGIN PERIOD 8
2 27 36 -900.0
END PERIOD
In the example above, the Well package would have zero wells active in stress period 1. Three wells whose
discharge rates are controlled by time series well-A-series, well-B-series, and well-C-series would be active
in stress periods 2 and 3. Stress periods 4 through 7 would include the three time-series-controlled wells plus
a well with a constant discharge of 900 (L3 /T). In stress period 8, only the constant-discharge well would be
active.
Time-Array Series
Any package that reads data for a structured model in the form of 2-D arrays can obtain those array data
from a time-array series. For example, recharge rates or maximum evapotranspiration rates can be extracted
from time-array series. During a simulation, values used for time-varying stresses (or auxiliary values) are
based on the values provided in the time-array series and are updated each time step (or each subtime step, as
appropriate). Input to define and use time-array series is described in this section.
A time-array series consists of a chronologically ordered list of arrays, where each array is associated with
a discrete time. The array data can be used to provide any time-varying, array-based numeric input.
Time-Array-Series Files
Each time-array-series file is associated with exactly one package, and the name of a time-array-series
file associated with a package is listed in the OPTIONS block for the package, preceded by the keywords
“TAS6 FILEIN.” Any number of time-array-series files can be associated with a given package; a TAS6 entry
is required for each time-array-series file. Time-array-series files are not listed in either the simulation Name
File or the model Name File. A given time-array-series file cannot be associated with more than one package.
One time-array-series file defines a single time-array series. A time-array-series file contains an
ATTRIBUTES block followed by a series of TIME blocks, where each TIME block contains data to define an
array corresponding to a discrete time. The READARRAY array reading utility is used to read the array. The
ATTRIBUTES block is required to define the name for the time-array series and the interpolation method to be
used when an operation requires interpolation between times listed in the time-array series. By convention, the
extension “.tas” is used in names of time-array-series files.
The syntax of the ATTRIBUTES block for a time-array-series file is as follows:
BEGIN ATTRIBUTES
NAME time-array-series-name
METHOD interpolation-method
[ SFAC sfac ]
END ATTRIBUTES
The ATTRIBUTES block is followed by any number of TIME blocks of the form:
BEGIN TIME tas-time
tas-array
END TIME
Explanation of Variables
time-array-series-name—Name by which a package references a particular time-array series. The name
must be unique among all time-array series used in a package.
interpolation-method—Interpolation method, which is either STEPWISE or LINEAR.
sfac—Scale factor, which will multiply all array values in time series. SFAC is an optional attribute; if omit-
ted, SFAC = 1.0.
tas-time—A numeric time relative to the start of the simulation, in the time unit used in the simulation.
Times must be strictly increasing.
tas-array—A 2-D array of numeric, floating-point values, or a constant value, readable by the READAR-
RAY array-reading utility.
Using Time-Array Series in a Package

When one or more time-array series are to define numeric input for a package, the name(s) of time-array-
series file(s) need to be defined in an OPTIONS block at the top of the package input file. The keywords
“TAS6 FILEIN” are used to identify the name of each time-array-series file. Each time-array-series file con-
tains exactly one time-array series, and each OPTIONS block can contain zero or more TAS6 entries. The syn-
tax for a TAS6 entry in an OPTIONS block is:
BEGIN OPTIONS
TAS6 FILEIN time-array-series-file-name
END OPTIONS
A time-array series is linked to an array in one or more stress period blocks used to define package input.
To indicate that an array is to be controlled by a time-array series, the array property word is followed by the
keyword TIMEARRAYSERIES and the time-array series name. When the TIMEARRAYSERIES keyword is
found (and the array to be populated supports time-array series), the array reader is not invoked. Consequently,
the array-control record and any associated input are omitted. The syntax to define the link is:
BEGIN PERIOD kper
property-name TIMEARRAYSERIES time-array-series-name
END PERIOD
Explanation of Variables Read from a Package Input File:
TAS6—Keyword to specify that record corresponds to a time-array-series file.
FILEIN—Keyword to specify that an input filename is expected next.
time-array-series-file-name—Name of a time-array-series file in which a time-array series used in the

package is defined.
property-name—Name of property represented by array to be controlled by a time-array series.
time-array-series-name—Name of time-array series. The time-array series must be defined in one of the
files listed in the OPTIONS block with the TAS6 FILEIN keywords.
Example use of time-array series to define package input

The following example illustrates the use of a time-array series to control the Recharge property of the
Recharge package in a model with a structured grid. In this example time-array series values are obtained from
the time-array series “RchArraySeries 1” defined in file “rch time array series.tas.” The RchMult array is an
auxiliary-variable array that is identified by the AUXMULTNAME keyword to be a multiplier for the recharge
array. Accordingly, the recharge array is defined each time step as the element-by-element product of values
interpolated from the “RchArraySeries 1” time-array series and values from the auxiliary-variable RchMult
array.
Contents of Recharge package input file:

BEGIN OPTIONS
READASARRAYS
AUX RchMult
TAS6 FILEIN rch_time_array_series.tas
AUXMULTNAME RchMult
PRINT_INPUT
END OPTIONS
BEGIN PERIOD 1
IRCH
CONSTANT 1
RECHARGE TIMEARRAYSERIES RchArraySeries_1
RchMult
INTERNAL FACTOR 1.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 1.0 1.0 0.5 0.5 0.0 0.0 0.0 0.0 0.0
0.0 1.0 1.0 1.0 1.0 0.5 0.0 0.0 0.0 0.0
0.0 1.0 1.0 1.0 1.0 1.0 0.5 0.0 0.0 0.0
0.0 0.2 1.0 1.0 1.0 1.0 1.0 0.5 0.2 0.0
0.0 0.0 0.5 1.0 1.0 1.0 1.0 0.5 0.0 0.0
0.0 0.0 0.0 0.2 0.2 0.2 0.2 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
END PERIOD
Contents of file “rch time array series.tas”:

BEGIN ATTRIBUTES
NAME RchArraySeries_1
METHOD LINEAR
END ATTRIBUTES
BEGIN TIME 0.0

CONSTANT 0.0033
END TIME
BEGIN TIME 91.0

CONSTANT 0.0035
END TIME
BEGIN TIME 183.0

CONSTANT 0.0037
END TIME
BEGIN TIME 274.0

CONSTANT 0.0039
END TIME
BEGIN TIME 365.0

CONSTANT 0.0035
END TIME
Description of Binary Output Files for the Groundwater Flow (GWF) and Groundwater Transport (GWT) . . . 245
Description of Binary Output Files for the Groundwater Flow (GWF) and
Groundwater Transport (GWT) Models
Users can optionally write MODFLOW 6 output to binary files. There are several different types of binary
output files. The first type is new to MODFLOW and is called a binary grid file. The binary grid file contains
all of the information necessary for a post-processing program to quickly reconstruct the the model grid and
understand how cells are connected within the grid. The option to specify an IDOMAIN array for DIS and
DISV grids may result in cells being connected across model layers. For this reason, cell connectivity informa-
tion is written to the binary grid file. The second type of binary file is one that contains simulated results, such
as head. Simulated flows are written to a third type of binary file, called a budget file. The budget file contains
simulated flows between connected cells and flows from stress packages. Lastly, observations can also be writ-
ten to binary output files.
All floating point variables are written to the binary output files as DOUBLE PRECISION Fortran vari-
ables. Integer variables are written to the output files as Fortran integer variables. Some variables are character
strings and are indicated as so in the following descriptions.
The file formats for the binary files are described in the following sections. The frequency of output and
the types of output files that are created is described in the Output Control Option and in the individual pack-
age input files.
Binary Grid File

MODFLOW 6 writes a binary grid file that can be used for post processing model results. The file struc-
ture was designed to be self-documenting so that it can evolve if necessary. The file name is assigned auto-
matically by the program by adding “.grb” to the end of the discretization input file name. The structure of
the binary grid file depends on the type of discretization package that is used. The following subsections sum-
marize the binary grid file for the different grid types. The red text is not written to the binary grid file, but is
shown here to explain the file content. The binary grid file is written for the GWF Model, but is not written for
the GWT Model.
DIS Grids
Header 1: ‘GRID DIS’ CHARACTER(LEN=50)

Header 2: ‘VERSION 1’ CHARACTER(LEN=50)
Header 3: ‘NTXT 16’ CHARACTER(LEN=50)
Header 4: ‘LENTXT 100’ CHARACTER(LEN=50)
Read NTXT strings of size LENTXT. Set the number of data records (NDAT) equal to number of lines that do not
begin with #.
Definition 0: ‘#Comment ...’ CHARACTER(LEN=LENTXT), comments not presently written
Definition 1: ‘NCELLS INTEGER NDIM 0 # ncells’ CHARACTER(LEN=LENTXT)
Definition 2: ‘NLAY INTEGER NDIM 0 # nlay’ CHARACTER(LEN=LENTXT)
Definition 3: ‘NROW INTEGER NDIM 0 # nrow’ CHARACTER(LEN=LENTXT)
Definition 4: ‘NCOL INTEGER NDIM 0 # ncol’ CHARACTER(LEN=LENTXT)
Definition 5: ‘NJA INTEGER NDIM 0 # nja’ CHARACTER(LEN=LENTXT)
Definition 6: ‘XORIGIN DOUBLE NDIM 0 # xorigin’ CHARACTER(LEN=LENTXT)
Definition 7: ‘YORIGIN DOUBLE NDIM 0 # yorigin’ CHARACTER(LEN=LENTXT)
Definition 8: ‘ANGROT DOUBLE NDIM 0 # angrot’ CHARACTER(LEN=LENTXT)
Definition 9: ‘DELR DOUBLE NDIM 1 ncol’ CHARACTER(LEN=LENTXT)
Definition 10: ‘DELC DOUBLE NDIM 1 nrow’ CHARACTER(LEN=LENTXT)
Definition 11: ‘TOP DOUBLE NDIM 1 nrow*ncol’ CHARACTER(LEN=LENTXT)
Definition 12: ‘BOTM DOUBLE NDIM 1 ncells’ CHARACTER(LEN=LENTXT)
Definition 13: ‘IA INTEGER NDIM 1 ncells+1’ CHARACTER(LEN=LENTXT)
Definition 14: ‘JA INTEGER NDIM 1 nja’ CHARACTER(LEN=LENTXT)
Definition 15: ‘IDOMAIN INTEGER NDIM 1 ncells’ CHARACTER(LEN=LENTXT)
Definition 16: ‘ICELLTYPE INTEGER NDIM 1 ncells’ CHARACTER(LEN=LENTXT)
Read NDAT data variables using the definitions defined above.

Record 1: NCELLS INTEGER
Record 2: NLAY INTEGER
Record 3: NROW INTEGER
Record 4: NCOL INTEGER
Record 5: NJA INTEGER
Record 6: XORIGIN DOUBLE
Record 7: YORIGIN DOUBLE
Record 8: ANGROT DOUBLE
Record 9: DELR DOUBLE PRECISION ARRAY SIZE(NCOL)
Record 10: DELC DOUBLE PRECISION ARRAY SIZE (NROW)
Record 11: (TOP(J),J=1,NROW*NCOL) DOUBLE PRECISION ARRAY SIZE(NROW*NCOL)
Record 12: (BOTM(J),J=1,NCELLS) DOUBLE PRECISION ARRAY SIZE(NCELLS)
Record 13: (IA(J),J=1,NCELLS+1) INTEGER ARRAY SIZE(NCELLS+1)
Record 14: (JA(J),J=1,NJA) INTEGER ARRAY SIZE(NJA)
Record 15: (IDOMAIN(J),J=1,NCELLS) INTEGER ARRAY SIZE(NCELLS)
Record 16: (ICELLTYPE(J),J=1,NCELLS) INTEGER ARRAY SIZE(NCELLS)
DISV Grids
The binary grid file for DISV grids contains information on the vertices and which vertices comprise a
cell. The x, y coordinates for each vertex are stored in the VERTICES array. The list of vertices that comprise
all of the cells is stored in the JAVERT array. The list of vertices for any cell can be found using the IAVERT
array. The following pseudocode shows how to loop through every cell in the DISV grid and obtain the cell
vertices. The list of vertices is “closed” for each cell in that the first listed vertex is equal to the last listed ver-
tex.
DO K = 1, NLAY
DO N = 1, NCPL
PRINT *, ’THIS IS CELL (LAYER, ICELL2D): ’, K, N
NVCELL = IAVERT(N+1) - IAVERT(N)
PRINT*, ’NUMBER OF VERTICES FOR CELL IS’, NVCELL
DO IPOS = IAVERT(N), IAVERT(N + 1) - 1
IVERT = JAVERT(IPOS)
X = VERTICES(1,IVERT)
Y = VERTICES(2,IVERT)
PRINT *,’ VERTEX PAIR: ’, X, Y
ENDDO
ENDDO
ENDDO
The IA and JA arrays are also contained in the DISV binary grid file. These arrays describe the cell con-
nectivity. Connections in the JA array correspond directly with the FLOW-JA-FACE record that is written to
the budget file.
The content of the DISV binary grid file is as follows.
Header 1: ‘GRID DISV’ CHARACTER(LEN=50)

Header 3: ‘NTXT 20’ CHARACTER(LEN=50)
begin with #.
Definition 1: ‘NCELLS INTEGER NDIM 0 # ncells’ CHARACTER(LEN=LENTXT)
Definition 2: ‘NLAY INTEGER NDIM 0 # nlay’ CHARACTER(LEN=LENTXT)
Definition 3: ‘NCPL INTEGER NDIM 0 # ncpl’ CHARACTER(LEN=LENTXT)
Definition 4: ‘NVERT INTEGER NDIM 0 # nvert’ CHARACTER(LEN=LENTXT)
Definition 5: ‘NJAVERT INTEGER NDIM 0 # njavert’ CHARACTER(LEN=LENTXT)
Definition 10: ‘TOP DOUBLE NDIM 1 ncpl’ CHARACTER(LEN=LENTXT)
Definition 11: ‘BOTM DOUBLE NDIM 1 ncells’ CHARACTER(LEN=LENTXT)
Definition 12: ‘VERTICES DOUBLE NDIM 2 2 nvert’ CHARACTER(LEN=LENTXT)
Definition 13: ‘CELLX DOUBLE NDIM 1 ncpl’ CHARACTER(LEN=LENTXT)
Definition 14: ‘CELLY DOUBLE NDIM 1 ncpl’ CHARACTER(LEN=LENTXT)
Definition 15: ‘IAVERT INTEGER NDIM 1 ncpl+1’ CHARACTER(LEN=LENTXT)
Definition 16: ‘JAVERT INTEGER NDIM 1 njavert’ CHARACTER(LEN=LENTXT)

Definition 19: ‘IDOMAIN INTEGER NDIM 1 ncells’ CHARACTER(LEN=LENTXT)

Record 1: NCELLS INTEGER
Record 2: NLAY INTEGER
Record 3: NCPL INTEGER
Record 4: NVERT INTEGER
Record 5: NJAVERT INTEGER
Record 10: (TOP(J),J=1,NCPL) DOUBLE PRECISION ARRAY SIZE(NCPL)
Record 11: ((BOTM(J),J=1,NCELLS) DOUBLE PRECISION ARRAY SIZE(NCELLS)
Record 12: ((VERTICES(J,K),J=1,2),K=1,NVERT) DOUBLE PRECISION ARRAY SIZE(2,NVERT)
Record 13: (CELLX(J),J=1,NCPL) DOUBLE PRECISION ARRAY SIZE(NCPL)
Record 14: (CELLY(J),J=1,NCPL) DOUBLE PRECISION ARRAY SIZE(NCPL)
Record 15: (IAVERT(J),J=1,NCPL+1) INTEGER ARRAY SIZE(NCPL+1)
Record 16: (JAVERT(J),J=1,NJAVERT) INTEGER ARRAY SIZE(NJAVERT)
Record 17: (IA(J),J=1,NCELLS+1) INTEGER ARRAY SIZE(NCELLS+1)
Record 19: (IDOMAIN(J),J=1,NCELLS) INTEGER ARRAY SIZE(NCELLS)
DISU Grids
The binary grid file for DISU grids may contain information on the vertices and which vertices comprise
a cell, but this depends on whether or not the user provided the information in the DISU Package. This infor-
mation is not required unless the XT3D or SAVE SPECIFIC DISCHARGE options are specified in the NPF
Package. If provided, the x, y coordinates for each vertex are stored in the VERTICES array. The list of ver-
tices that comprise all of the cells is stored in the JAVERT array. The list of vertices for any cell can be found
using the IAVERT array. Pseudocode for looping through cells in the grid is listed above in the section on the
binary grid file for the DISV Package. As for the DISV binary grid file, the list of vertices is “closed” for each
cell in that the first listed vertex is equal to the last listed vertex.
Header 1: ‘GRID DISU’ CHARACTER(LEN=50)

Header 3: ‘NTXT 10’ or ‘NTXT 15’ CHARACTER(LEN=50)
begin with #.
Definition 1: ‘NODES INTEGER NDIM 0 # nodes’ CHARACTER(LEN=LENTXT)
Definition 6: ‘TOP DOUBLE NDIM 1 nodes’ CHARACTER(LEN=LENTXT)
Definition 7: ‘BOT DOUBLE NDIM 1 nodes’ CHARACTER(LEN=LENTXT)
If vertices are provided in the DISU Package, then 5 additional definitions are included:
Definition 11: ‘VERTICES DOUBLE NDIM 2 2 nvert’ CHARACTER(LEN=LENTXT)
Definition 12: ‘CELLX DOUBLE NDIM 1 nodes’ CHARACTER(LEN=LENTXT)
Definition 13: ‘CELLY DOUBLE NDIM 1 nodes’ CHARACTER(LEN=LENTXT)
Definition 14: ‘IAVERT INTEGER NDIM 1 nodes+1’ CHARACTER(LEN=LENTXT)
Definition 15: ‘JAVERT INTEGER NDIM 1 njavert’ CHARACTER(LEN=LENTXT)

Record 1: NODES INTEGER
Record 6: (TOP(J),J=1,NODES) DOUBLE PRECISION ARRAY SIZE(NODES)
Record 7: ((BOT(J),J=1,NODES) DOUBLE PRECISION ARRAY SIZE(NODES)
Record 8: (IA(J),J=1,NODES+1) INTEGER ARRAY SIZE(NODES+1)
If vertices are provided in the DISU Package, then 5 additional records are included:
Record 11: ((VERT(J,K),J=1,2),K=1,NVERT) DOUBLE PRECISION ARRAY SIZE(2,NVERT)
Record 12: (CELLX(J),J=1,NODES) DOUBLE PRECISION ARRAY SIZE(NODES)
Record 13: (CELLY(J),J=1,NODES) DOUBLE PRECISION ARRAY SIZE(NODES)
Record 14: (IAVERT(J),J=1,NODES+1) INTEGER ARRAY SIZE(NODES+1)
Record 15: (JAVERT(J),J=1,NJAVERT) INTEGER ARRAY SIZE(NJAVERT)
Dependent Variable File

In the present MODFLOW 6 version, the TEXT value is specified as “HEAD” for the GWF Model and
“CONCENTRATION” for the GWT Model. Cells that have been assigned an IDOMAIN value of zero or less
are assigned a head value of 1.0 x 1030 . Cells that have converted to dry are assigned a dry value of −1.0 x
1030 . The large negative value allows the results from a previous simulation to be used as starting heads for a
subsequent simulation. Cells assigned a large negative value as an initial condition will start the simulation as
dry. Note that the dry value is not used if the Newton-Raphson Formulation is active. In this case, a dry cell
will have a calculated head value that is below or at the bottom of the cell.
DIS Grids
For each stress period, time step, and layer for which data are saved to the binary output file, the following
two records are written:
Record 1: KSTP,KPER,PERTIM,TOTIM,TEXT,NCOL,NROW,ILAY
Record 2: ((DATA(J,I,ILAY),J=1,NCOL),I=1,NROW)
where
KSTP is the time step number;

KPER is the stress period number;
PERTIM is the time value for the current stress period;
TOTIM is the total simulation time;
TEXT is a character string (character*16);
NCOL is the number of columns;
NROW is the number of rows;
ILAY is the layer number; and
DATA is the head data of size (NCOL,NROW,NLAY).
DISV Grids
Record 1: KSTP,KPER,PERTIM,TOTIM,TEXT,NCPL,1,ILAY
Record 2: (DATA(J,ILAY),J=1,NCPL)
where

NCPL is the number of cells per layer;
ILAY is the layer number; and
DATA is the head data of size (NCPL,NLAY).
DISU Grids
Record 1: KSTP,KPER,PERTIM,TOTIM,TEXT,NODES,1,1
Record 2: (DATA(N),N=1,NODES)
where

NODES is the number cells in the model grid;
DATA is unstructured head data of size (NODES).
Advanced Flow and Transport Packages
The dependent variable can be saved to a binary file for the LAK, SFR, and MAW Packages of the GWF
Model and for the LKT, SFT, MWT, and UZT Packages of the GWT Model. Table 32 shows the text identifier
and description of the dependent variable for these packages.
Table 32. Dependent variable written for advanced flow and transport packages.
Model/Package TEXT Description

GWF/LAK STAGE Simulated lake stage
GWF/SFR STAGE Simulated stream reach stage
GWF/MAW HEAD Simulated well head
GWF/UZF WATER-CONTENT Simulated unsaturated zone cell
water content
GWT/LKT CONCENTRATION Simulated lake concentration
GWT/SFT CONCENTRATION Simulated stream reach concen-
tration
GWT/MWT CONCENTRATION Simulated well concentration
GWT/UZT CONCENTRATION Simulated unsaturated zone cell
concentration
Record 1: KSTP,KPER,PERTIM,TOTIM,TEXT,MAXBOUND,1,1
Record 2: (DATA(N),N=1,MAXBOUND)
where

MAXBOUND is the number advanced boundary items in the package;
DATA is unstructured dependent variable data of size (MAXBOUND).
Model Budget Files

MODFLOW 6 can optionally write a budget file, also referred to as a cell-by-cell flow file. The budget file
is written in a binary format that can be post-processed using other software programs, such as ZONEBUD-
GET. The budget file for the MODFLOW 6 models, such as the GWF and GWT Models, contains intercell
water and solute flows, flows due to changes in storage, flows from the stress packages and advanced stress
packages, and exchange flows with another model. The intent of budget file is to contain all flow to and from
any cell in the model. Users must activate saving of flow terms in the Output Control Package and in the indi-
vidual packages.
The format for the budget file is different from the formats for previous MODFLOW versions. Specif-
ically, intercell flows are written in a different manner using a compressed sparse row storage scheme. The
record structure for the stress packages is also different and uses a method code 6, to distinguish it from the
five method codes available in previous MODFLOW versions. The new code 6 indicates that additional text
identifiers are present, that auxiliary variables may be present, and that two identifying integer numbers are
contained in the list (one for the node number of the GWF Model cell, and the other for an identifier to where
the flow is from).
Format of Budget File

The generalized form of the budget file is described so that utilities may be created to read the budget file.
Additional information about the content and the form of the content for different grid types is described in
subsequent sections.
Record 1: KSTP,KPER,TEXT,NDIM1,NDIM2,-NDIM3
Record 2: IMETH,DELT,PERTIM,TOTIM
IMETH=1: Read 1D array of size NDIM1*NDIM2*NDIM3.

Record 3: (DATA(J),J=1,NDIM1*NDIM2*NDIM3)
IMETH=6: Read text identifiers, auxiliary text labels, and list of information.
Record 3: TXT1ID1
Record 4: TXT2ID1
Record 5: TXT1ID2
Record 6: TXT2ID2
Record 7: NDAT
Record 8: (AUXTXT(N),N=1,NDAT-1)
Record 9: NLIST
Record 10: ((ID1(N),ID2(N),(DATA2D(I,N),I=1,NDAT)),N=1,NLIST)
where
KSTP is the integer time step number;

KPER is the integer stress period number;
TEXT is a character string (character*16) indicating the flow type;
PERTIM is the double precision time value for the current stress period;
TOTIM is the double precision total simulation time;
NDIM1 is the integer size of first dimension;
NDIM2 is the integer size of second dimension;
NDIM3 is the integer size of third dimension;
IMETH is an integer code that specifies the form of the remaining data;
DELT is the double precision length of the timestep;
PERTIM is the double precision time value for the current stress period;
TOTIM is the double precision total simulation time;
DATA is a double precision array of budget values;
TXT1ID1 is a character string (character*16) containing the first text identifier for information in ID1;
TXT2ID1 is a character string (character*16) containing the second text identifier for information in ID1;
TXT1ID2 is a character string (character*16) containing the model name for information in ID2;
TXT2ID2 is a character string (character*16) containing the package or model name for information in ID2;
NDAT is the number of columns in DATA2D, which is the number of auxiliary values plus 1;
AUXTXT is an array of size NDAT - 1 containing character*16 text names for each auxiliary variable;
NLIST is the size of the list;
ID1 is the first identifying number;
ID2 is the second identifying number, and
DATA2D is a double precision 2D array of size (NDAT,NLIST). The first column in DATA2D is the budget
term; any remaining columns are auxiliary variable values.
Intercell Flows
MODFLOW 6 writes a special budget record for flow between connected cells. This record has a TEXT
identifier equal to FLOW-JA-FACE. For this record (corresponding to Record 3 for IMETH=1), the total num-
ber of values is equal to NJA, which is the total number of connections. For each cell, the number of connec-
tions is equal to the number of connections to adjacent cells plus one, to represent the cell itself. Therefore,
this budget record corresponds to the JA array. A value of zero is written to the node positions in the FLOW-
JA-FACE record. The JA array that is written in the binary grid corresponds directly to the FLOW-JA-FACE
record.
For regular MODFLOW grids, there are no longer records for FLOW RIGHT FACE, FLOW FRONT
FACE, and FLOW LOWER FACE. Instead, intercell flows are written to the FLOW-JA-FACE record. Writing
FLOW-JA-FACE allows face flows to be specified in straightforward manner, particularly when the IDOMAIN
capability is used to remove cells and specify vertical pass-through cells.
The following pseudocode shows how to loop through and process intercell flows using the IA and JA
arrays (which can be read from the binary grid file) and the FLOWJA array, which is written to the budget
file. For a cell (N) that has been eliminated with IDOMAIN, the value for IA(N) and IA(N+1) will be equal,
indicating that there are no connections or flows for that cell.
DO N = 1, NCELLS
PRINT *, ’THIS IS CELL: ’, N
NCON = IA(N+1) - IA(N) - 1
IF(NCON<0) NCON=0
PRINT*, ’NUMBER OF CONNECTED CELLS IS ’, NCON
DO IPOS = IA(N) + 1, IA(N + 1) - 1
M = JA(IPOS)
Q = FLOWJA(IPOS)
PRINT *,’ N M Q: ’, N,M,Q
ENDDO
ENDDO
Variations for Discretization Types

The format for the GWF and GWT Model budget files is the same no matter what discretization package
is used; however, the variables may have different meanings depending on the grid type and the TEXT iden-
tifier. If the TEXT identifier in Record 1 is FLOW-JA-FACE and IMETH is 1, then the DATA array contains
intercell flows and is of size NJA. If the TEXT identifier in Record 1 is something other than FLOW-JA-FACE
(STO-SS or STO-SY, for example), then the dimension variables in Record 1 (NDIM1, NDIM2, and NDIM3)
provide information about the size of the grid (table 33).
Table 33. Budget file variations that depend on discretization package type.
Grid or Flow NDIM1 NDIM2 NDIM3

Type
DIS NCOL NROW NLAY
DISV NCPL 1 NLAY
DISU NODES 1 1
FLOW-JA-FACE, NJA 1 1
IMETH=1
Budget File Contents for the GWF Model

The type of information that is written to the budget file for a GWF Model depends on the packages used
for the model and whether or not the save flags are set. Table 34 contains a list of the types of information
that may be contained in a GWF Model budget file. In all cases, the flows in table 34 are flows to or a from
a GWF Model cell. As described previously, intercell flows are written as FLOW-JA-FACE using IMETH=1.
If the model has an active Storage Package, then STORAGE-SS and STORAGE-SY are written to the budget
file using IMETH=1. If the model has an active Skeletal Storage, Compaction, and Subsidence Package, then
CSUB-CGELASTIC and CSUB-WATERCOMP are written to the budget file using IMETH=1.
The remaining flow terms in table 34 are all written using IMETH=6. When IMETH=6 is used, the
records contain additional text descriptors and two identifying numbers. For all records in the GWF Model
budget file, TXT1ID1 is the name of the GWF Model and TXT2ID1 is also the name of the GWF Model.
These text identifiers describe what is contained in ID1. For the GWF Model budget file, ID1 is the cell or
node number in the GWF Model grid. The second set of text identifiers refer to the information in ID2. Unless
noted otherwise in the description in table 34, TXT1ID2 is the name of the GWF Model, TXT2ID2 is the
name of the package, and ID2 is the bound number in the package; for example, this is the first constant head
cell, second constant head cell, and so forth.
Table 34. Types of information that may be contained in the GWF Model budget file.
Flow Type (TEXT) Method Description

Code
(IMETH)
FLOW-JA-FACE 1 intercell flow; array of size(NJA)
STO-SS 1 confined storage; array of size (NCELLS)
STO-SY 1 unconfined storage; array of size (NCELLS)
CSUB-CGELASTIC 1 coarse-grained elastic storage from CSUB Package; array
of size (NCELLS)
CSUB-WATERCOMP 1 water compressibility from CSUB Package; array of size
(NCELLS)
CSUB-ELASTIC 6 interbed elastic storage from CSUB package; list of
size(NINTERBEDS)
CSUB-INELASTIC 6 interbed inelastic storage from CSUB package; list of
size(NINTERBEDS)
CHD 6 constant head flow
WEL 6 well flow
WEL-TO-MVR 6 well flow that is routed to Mover Package
DRN 6 drain flow
DRN-TO-MVR 6 drain flow that is routed to Mover Package
RIV 6 river leakage
RIV-TO-MVR 6 river leakage that is routed to Mover Package
GHB 6 general-head boundary flow
GHB-TO-MVR 6 general-head boundary flow that is routed to Mover Pack-
age
RCH 6 recharge flow
EVT 6 evapotranspiration flow
Table 34. Types of information that may be contained in the GWF Model budget file.

Code
(IMETH)
MAW 6 multi-aquifer well flow; ID2 contains the well number
LAK 6 lake leakage; ID2 contains the lake number
SFR 6 stream leakage; ID2 contains the stream reach number
UZF-GWRCH 6 water table recharge from UZF Package
UZF-GWET 6 water table evapotranspiration from UZF Package
UZF-GWD 6 groundwater discharge to land surface from UZF Package
UZF-GWD-TO-MVR 6 groundwater discharge to land surface from UZF Package
that is routed to Mover Package
FLOW-JA-FACE 6 flow to or from a cell in another GWF Model; TXT1ID1
is the name of the GWF Model described by this budget
file, TXT2ID1 is the name of the GWF-GWF Exchange,
TXT1ID2 is the name of the connected GWF Model,
TXT2ID2 is the name of the GWF-GWF Exchange, and
ID2 is the cell or node number of the cell in the connected
model
DATA-SPDIS 6 specific discharge at the cell center. The x, y, and z com-
ponents are stored in auxiliary variables called “qx”, “qy”,
and “qz”, respectively. The flow value written for each
cell is zero. The “DATA” prefix on the text identifier can
be used by post-processors to recognize that the record
does not contain a cell flow budget term.
DATA-SAT 6 cell saturation. The cell saturation is stored in an auxiliary
variable called “sat”. The flow value written for each cell
is zero. The “DATA” prefix on the text identifier can be
used by post-processors to recognize that the record does
not contain a cell flow budget term. The cell saturation
can be used by post-processors to determine how much of
the cell is saturated without having to know the value for
ICELLTYPE or the value for head. If a cell is marked as
confined (ICELLTYPE=0) then saturation is always one.
If ICELLTYPE is one, then saturation ranges between
zero and one. For Newton GWF simulations, saturation is
zero if the head is below the cell bottom.
GWF Model CSUB Package
For each stress period, time step, and compaction data type that is saved to the CSUB Package binary out-
put files as IMETH=1 budget file type. The compaction data that are written to the CSUB Package binary files
are summarized in Tables 35.
Table 35. Data written to the CSUB Package compaction binary output files.

Code
(IMETH)
CSUB-COMPACTION 1 total compaction for cell; array of size (NCELLS)
CSUB-INELASTIC 1 inelastic compaction for cell; array of size (NCELLS)
CSUB-ELASTIC 1 elastic compaction for cell; array of size (NCELLS)
CSUB-INTERBED 1 interbed compaction for cell; array of size (NCELLS)
CSUB-COARSE 1 coarse-grained compaction for cell; array of size
(NCELLS)
CSUB-ZDISPLACE 1 z-displacement for cell; z-displacement of the upper most
model cells represents subsidance at land-surface; array of
size (NCELLS)
GWF Model LAK, MAW, SFR, and UZF Packages
For each stress period, time step, and data type that is saved to the LAK, MAW, SFR, and UZF Packages
binary output files as IMETH=6 budget file type. For all advanced packages, NDIM1 is equal to the number of
nodes, NDIM2 is equal to 1, and NDIM3 is equal to -1. The data that are written to the LAK, MAW, SFR, and
UZF Package binary files are summarized in Tables 36 to 39, respectively.
Table 36. Data written to the LAK Package binary output file. Flow terms are listed in the order they are written to the LAK
Package binary output file.
Flow term IMETH NDAT / NLIST Description

FLOW-JA-FACE 6 1 / 2*nlen Connection flow from lake (ID1) to lake
through a lake outlet to another lake
(ID2). nlen is calculated as the sum of
lake outlets that are connected to another
lake (lakeout for a lake outlet is not
equal to 0).
GWF 6 2 / maxbound Calculated flow from lake (ID1) to GWF
cell (ID2). The lake connection-aquifer
flow area (FLOW-AREA) is saved as an
auxiliary data item for this flow term.
EXT-INFLOW 6 1 / nlakes Specified inflow to reach. The lake num-
ber is written to (ID1) and (ID2).

RUNOFF 6 1 / nlakes Specified runoff to reach. The lake num-
ber is written to (ID1) and (ID2).
RAINFALL 6 1 / nlakes Specified rainfall on reach. The lake
number is written to (ID1) and (ID2).
EVAPORATION 6 1 / nlakes Calculated evaporation from lake. The
lake number is written to (ID1) and
(ID2).
WITHDRAWAL 6 1 / nlakes Specified withdrawal from lake. The lake
STORAGE 6 2 / nlakes Calculated flow from storage for lake.
The lake number is written to (ID1) and
(ID2). The lake volume (VOLUME) is
saved as an auxiliary data item for this
flow term.
CONSTANT 6 1 / nlakes Calculated flow to maintain constant
stage for lake. The lake number is written
to (ID1) and (ID2).
EXT-OUTFLOW 6 1 / nlakes Calculated outflow to external boundaries
(is nonzero for lakes with outlets not con-
nected to another lake). The lake number
is written to (ID1) and (ID2).
FROM-MVR 6 1 / nlakes Calculated flow to lake from the MVR
Package. Only saved if MVR Package
is used in the LAK Package. The lake
TO-MVR 6 1 / noutlets Calculated flow from a lake outlet to the
MVR Package. Only saved if MVR Pack-
age is used in the LAK Package. The lake
number LAKEIN for the connected outlet
AUXILIARY 6 naux+1 / nlakes Auxiliary variables, if specified in the
LAK Package, are saved to this flow
term. The first entry of the DATA2D col-
umn has a value of zero. The lake number
Table 37. Data written to the MAW Package binary output file. Flow terms are listed in the order they are written to the MAW

GWF 6 2 / maxbound Calculated flow from multi-aquifer
well (ID1) to GWF cell (ID2). The
multi-aquifer well-aquifer flow area
(FLOW-AREA) is saved as an auxiliary data
item for this flow term.
RATE 6 1 / nmawwells Calculated pumping rate from the multi-
aquifer well. The multi-aquifer well
FW-RATE 6 1 / nmawwells calculated flowing well discharge rate
from the multi-aquifer well. Only saved
if FLOWING WELLS is specified in the
OPTIONS block. The multi-aquifer well
STORAGE 6 2 / nmawwells Calculated flow from storage for
multi-aquifer well. Only saved if the
NO WELL STORAGE is not specified in the
number is written to (ID1) and (ID2). The
multi-aquifer well volume (VOLUME) is
saved as an auxiliary data item for this
flow term.
CONSTANT 6 1 / nmawwells Calculated flow to maintain constant
head in multi-aquifer well. The multi-
aquifer well number is written to (ID1)
and (ID2).
FROM-MVR 6 1 / nmawwells Calculated flow to lake from the MVR
is used in the MAW Package. The lake
RATE-TO-MVR 6 1 / nmawwells Calculated pumping rate from the multi-
aquifer well to the MVR Package. Only
saved if MVR Package is used in the
MAW Package. The multi-aquifer well
FW-RATE-TO-MVR 6 1 / nmawwells Calculated flowing well flow from a
multi-aquifer well to the MVR Pack-
age. Only saved if MVR Package is
used in the MAW Package and the
FLOWING WELLS is specified in the

AUXILIARY 6 naux+1 / nmawwells Auxiliary variables, if specified in the
MAW Package, are saved to this flow
term. The first entry of the DATA2D
column has a value of zero. The multi-
aquifer well number is written to (ID1)
and (ID2).
Table 38. Data written to the SFR Package binary output file. Flow terms are listed in the order they are written to the SFR

2 / maxbound
P
FLOW-JA-FACE 6 n=1 nconnn Connection flow from reach (ID1) to
unmanaged and managed (tributaries)
connections (ID2). The cross-sectional
GWF 6 2 / maxbound Calculated flow from reach (ID1) to GWF
cell (ID2). The reach-aquifer flow area
(FLOW-AREA) is saved as an auxiliary data
item for this flow term.
EXT-INFLOW 6 1 / maxbound Specified inflow to reach. The reach
RUNOFF 6 1 / maxbound Specified runoff to reach. The reach
RAIN 6 1 / maxbound Specified rainfall on reach. The reach
EVAPORATION 6 1 / maxbound Calculated evaporation from reach. The
reach number is written to (ID1) and
(ID2).
EXT-OUTFLOW 6 1 / maxbound Calculated outflow to external boundaries
(is nonzero for reaches with no down-
stream connections). The reach number is
written to (ID1) and (ID2).
STORAGE 6 2 / maxbound Calculated storage changes for each
reach. This value is always zero for the
present implementation. The water vol-
ume in the reach (VOLUME) is saved as
an auxiliary data item for this flow term.
The reach number is written to (ID1) and
(ID2).
FROM-MVR 6 1 / maxbound Calculated flow to reach from the MVR
is used in the SFR Package. The reach
TO-MVR 6 1 / maxbound Calculated flow from reach to the MVR
is used in the SFR Package. The reach

AUXILIARY 6 naux+1 / maxbound Auxiliary variables, if specified in the
SFR Package, are saved to this flow term.
The first entry of the DATA2D column
has a value of zero. The reach number is
Table 39. Data written to the UZF Package binary output file. Flow terms are listed in the order they are written to the UZF

FLOW-JA-FACE 6 1 / 2*nlen Connection flow from UZF cell (ID1)
to a connected UZF cell (ID2). nlen is
calculated as the number of uzf cells with
vertcon values greater than 0.
GWF 6 2 / maxbound Calculated flow from UZF cell (ID1) to
GWF cell (ID2). The UZF cell-aquifer
INFILTRATION 6 1 / maxbound Specified infiltration to UZF cell. The
UZF cell number is written to (ID1) and
(ID2).
REJ-INF 6 1 / maxbound Calculated rejected infiltration from the
UZF cell. The UZF cell number is written
to (ID1) and (ID2).
UZET 6 1 / maxbound Calculated evaporation from the UZF
cell. The UZF cell number is written to
(ID1) and (ID2).
STORAGE 6 2 / maxbound Calculated flow from mobile storage
(mobile storage is water in excess of the
residual water content) for the UZF cell.
The UZF cell number is written to (ID1)
and (ID2). The mobile water volume in
the UZF cells (VOLUME) is saved as an
FROM-MVR 6 1 / maxbound Calculated flow to the UZF cell from
the MVR Package. Only saved if MVR
Package is used in the UZF Package. The
UZF cell number is written to (ID1) and
(ID2).
REJ-INF-TO-MVR 6 1 / maxbound Calculated rejected infiltration flow from
the UZF cell to the MVR Package. Only
saved if MVR Package is used in the UZF
Package. The UZF cell number is written
to (ID1) and (ID2).
AUXILIARY 6 naux+1 / maxbound Auxiliary variables, if specified in the
UZF Package, are saved to this flow term.
The first entry of the DATA2D column has
a value of zero. The UZF cell number is
Budget File Contents for the GWT Model

The type of information that is written to the budget file for a GWT Model depends on the packages
used for the model and whether or not the save flags are set. Table 40 contains a list of the types of informa-
tion that may be contained in a GWT Model budget file. In all cases, the flows in table 40 are solute mass
flows (in mass per time) to or a from a GWT Model cell. Intercell flows are written as FLOW-JA-FACE using
IMETH=1.
The remaining flow terms in table 40 are all written using IMETH=6. When IMETH=6 is used, the
records contain additional text descriptors and two identifying numbers. For all records in the GWT Model
budget file, TXT1ID1 is the name of the GWT Model and TXT2ID1 is also the name of the GWT Model.
These text identifiers describe what is contained in ID1. For the GWT Model budget file, ID1 is the cell or
node number in the GWT Model grid. The second set of text identifiers refer to the information in ID2. Unless
noted otherwise in the description in table 40, TXT1ID2 is the name of the GWT Model, TXT2ID2 is the
name of the package, and ID2 is the bound number in the package; for example, this is the first constant con-
centration cell, second constant concentration cell, and so forth.
Table 40. Types of information that may be contained in the GWT Model budget file. All terms represent solute flows in dimen-
sions of mass per time.

Code
(IMETH)
FLOW-JA-FACE 1 intercell solute flow due to advection and dispersion;
array of size(NJA)
STORAGE-AQUEOUS 1 solute aqueous storage; array of size (NCELLS)
DECAY-AQUEOUS 1 solute aqueous decay; array of size (NCELLS)
STORAGE-SORBED 1 solute sorbed storage; array of size (NCELLS)
DECAY-SORBED 1 solute sorbed decay; array of size (NCELLS)
SOURCE-SINK MIX 6 mass flow from SSM sources and sinks
CNC 6 mass flow for constant-concentration cells
SRC 6 mass flow for specified mass source cells
LKT 6 mass flow between lake and aquifer
SFT 6 mass flow between stream and aquifer
MWT 6 mass flow between multi-aquifer well and aquifer
UZT 6 mass flow between unsaturated zone cell and aquifer
IST 6 mass flow between mobile and immobile domain
FLOW-JA-FACE 6 flow to or from a cell in another GWT Model (note
that this is not implemented yet for the GWT Model);
TXT1ID1 is the name of the GWT Model described
by this budget file, TXT2ID1 is the name of the GWF-
GWF Exchange, TXT1ID2 is the name of the connected
GWT Model, TXT2ID2 is the name of the GWT-GWT
Exchange, and ID2 is the cell or node number of the cell
in the connected model
GWT Model LKT, MWT, SFT, and UZT Packages
For each stress period, time step, and data type that is saved to theLKT, MWT, SFT, and UZT Packages
binary output files as IMETH=6 budget file type. For all advanced transport packages, NDIM1 is equal to the
number of nodes, NDIM2 is equal to 1, and NDIM3 is equal to -1. The data that are written to the LKT, MWT,
SFT, and UZT Package binary files are mass flows with entries similar to those listed in Tables 36 to 39 for the
advanced flow packages.
Observation Output File

When the BINARY option is used to open an observation output file (see section “Observation (OBS) Util-
ity”), the output file has the following form. Record 1 has a length of 100 bytes.
Record 1: TYPE, PRECISION, LENOBSNAME (Record 1 includes 85 blanks following LENOBSNAME.)

Record 2: NOBS
Record 3: OBSNAME(1), OBSNAME(2), ..., OBSNAME(NOBS)
Repeat for each time step.
Record 4: TIME, SIMVALUE(1), SIMVALUE(2), ..., SIMVALUE(NOBS)
where
TYPE (bytes 1–4 of Record 1) is “cont “ — “cont” indicates the file contains continuous observations;
PRECISION (bytes 6–11 of Record 1) will always be “double” to indicate that floating-point values are writ-
ten in double precision (8 bytes);
LENOBSNAME (bytes 12–15 of Record 1) is an integer indicating the number of characters used to store each
observation name in following records (in the initial release of MODFLOW 6, LENOBSNAME equals
40);
NOBS (4-byte integer) is the number of observations recorded in the file;
OBSNAME (LENOBSNAME bytes) is an observation name;
TIME (floating-point) is the simulation time; and
SIMVALUE (floating-point) is the simulated value.
References Cited R–1
References Cited
Anderman, E.R., and Hill, M.C., 2000, MODFLOW-2000, the U.S. Geological Survey modular ground-water
model-documentation of the Hydrogeologic-Unit Flow (HUF) Package: U.S. Geological Survey Open-File
Report 2000–342, 89 p.
Anderman, E.R., and Hill, M.C., 2003, MODFLOW-2000, the U.S. Geological Survey modular ground-water
model—Three additions to the Hydrogeologic-Unit Flow (HUF) Package: Alternative storage for the upper-
most active cells, flows in hydrogeologic units, and the hydraulic-conductivity depth-dependence (KDEP)
capability: U.S. Geological Survey Open-File Report 2003–347, 36 p.
Bakker, Mark, Schaars, Frans, Hughes, J.D., Langevin, C.D., and Dausman, A.M., 2013, Documentation of
the seawater intrusion (SWI2) package for MODFLOW: U.S. Geological Survey Techniques and Methods,
book 6, chap. A46, 47 p., accessed June 27, 2017, at https://pubs.er.usgs.gov/publication/tm6A46.
Banta, E.R., 2000, MODFLOW-2000, the U.S. Geological Survey Modular Ground-Water Model; documenta-
tion of packages for simulating evapotranspiration with a segmented function (ETS1) and drains with return
flow (DRT1): U.S. Geological Survey Open File Report 2000–466, 127 p.
Banta, E.R., 2011, MODFLOW-CDSS, a version of MODFLOW-2005 with modifications for Colorado Deci-
sion Support Systems: U.S. Geological Survey Open-File Report 2011–1213, 19 p., accessed June 27, 2017,
at https://pubs.er.usgs.gov/publication/ofr20111213.
Fenske, J.P., Leake, S.A., and Prudic, D.E., 1996, Documentation of a computer program (RES1) to simulate
leakage from reservoirs using the modular finite-difference ground-water flow model (MODFLOW): U.S.
Geological Survey Open-File Report 96–364, 51 p., accessed June 27, 2017, at https://pubs.er.usgs.gov/
publication/ofr96364.
Halford, K.J., and Hanson, R.T., 2002, User guide for the drawdown-limited, multi-node well (MNW) pack-
age for the U.S. Geological Survey’s modular three-dimensional finite-difference ground-water flow model,
versions MODFLOW-96 and MODFLOW-2000: U.S. Geological Survey Open-File Report 02–293, 33 p.
Hanson, R.T., and Leake, S.A., 1999, Documentation for HYDMOD—A program for extracting and process-
ing time-series data from the U.S. Geological Survey’s modular three-dimensional finite-difference ground-
water flow model: U.S. Geological Survey Open-File Report 98–564, 57 p., accessed June 27, 2017, at
https://pubs.er.usgs.gov/publication/ofr98564.
Harbaugh, A.W., 2005, MODFLOW-2005, the U.S. Geological Survey modular ground-water model—the
Ground-Water Flow Process: U.S. Geological Survey Techniques and Methods, book 6, chap. A16, vari-
ously paged, accessed June 27, 2017, at https://pubs.usgs.gov/tm/2005/tm6A16/.
Hill, M.C., 1990, Preconditioned Conjugate-Gradient 2 (PCG2), a computer program for solving ground-water
flow equations: U.S. Geological Survey Water-Resources Investigations Report 90–4048, 25 p., accessed
June 27, 2017, at https://pubs.usgs.gov/wri/wrir 90-4048.
Hill, M.C., Banta, E.R., Harbaugh, A.W., and Anderman, E.R., 2000, MODFLOW-2000, the U.S. Geological
Survey modular ground-water model—User guide to the observation, sensitivity, and parameter-estimation
processes and three post-processing programs: U.S. Geological Survey Open-File Report 00–184, 210 p.
Hoffmann, Jörn, Leake, S.A., Galloway, D.L., and Wilson, A.M., 2003, MODFLOW-2000 Ground-Water
Model—User Guide to the Subsidence and Aquifer-System Compaction (SUB) Package: U.S. Geolog-
ical Survey Open-File Report 03–233, 44 p., accessed June 27, 2017, at https://pubs.usgs.gov/of/2003/
ofr03-233/.
Hsieh, P.A., and Freckleton, J.R., 1993, Documentation of a computer program to simulate horizontal-flow
barriers using the U.S. Geological Survey’s modular three-dimensional finite-difference ground-water flow
model: U.S. Geological Survey Open-File Report 92–477, 32 p., accessed June 27, 2017, at https://pubs.er.
usgs.gov/publication/ofr92477.
R–2 MODFLOW 6 – Description of Input and Output
Hughes, J.D., Langevin, C.D., Chartier, K.L., and White, J.T., 2012, Documentation of the Surface-Water
Routing (SWR1) Process for modeling surface-water flow with the U.S. Geological Survey modular
groundwater model (MODFLOW-2005): U.S. Geological Survey Techniques and Methods, book 6, chap.
A40 (Version 1.0), 113 p., accessed June 27, 2017, at https://pubs.usgs.gov/tm/6a40/.
Hughes, J.D., Langevin, C.D., and Banta, E.R., 2017, Documentation for the MODFLOW 6 framework: U.S.
Geological Survey Techniques and Methods, book 6, chap. A57, 36 p., accessed August 4, 2017, at https:
//doi.org/10.3133/tm6A57.
Konikow, L.F., Hornberger, G.Z., Halford, K.J., and Hanson, R.T., 2009, Revised multi-node well (MNW2)
package for MODFLOW ground-water flow model: U.S. Geological Survey Techniques and Methods, book
6, chap. A30, 67 p., accessed June 27, 2017, at https://pubs.usgs.gov/tm/tm6a30/.
Langevin, C.D., Thorne Jr, D.T., Dausman, A.M., Sukop, M.C., and Guo, Weixing, 2008, SEAWAT Version
4—A computer program for simulation of multi-species solute and heat transport: U.S. Geological Sur-
vey Techniques and Methods, book 6, chap. A22, 39 p., accessed June 27, 2017, at https://pubs.er.usgs.gov/
publication/tm6A22.
Langevin, C.D., Hughes, J.D., Provost, A.M., Banta, E.R., Niswonger, R.G., and Panday, Sorab, 2017, Docu-
mentation for the MODFLOW 6 Groundwater Flow (GWF) Model: U.S. Geological Survey Techniques and
Methods, book 6, chap. A55, 197 p., accessed August 4, 2017, at https://doi.org/10.3133/tm6A55.
Langevin, C.D., Panday, Sorab, and Provost, A.M., 2020, Hydraulic-head formulation for density-dependent
flow and transport: Groundwater, v. 58, no. 3, p. 349–362.
Leake, S.A., and Galloway, D.L., 2007, MODFLOW Ground-water model—User guide to the Subsidence
and Aquifer-System Compaction Package (SUB-WT) for Water-Table Aquifers: U.S. Geological Survey
Techniques and Methods, book 6, chap. A23, 42 p., accessed June 27, 2017, at https://pubs.er.usgs.gov/
publication/tm6A23.
Leake, S.A., and Lilly, M.R., 1997, Documentation of computer program (FHB1) for assignment of transient
specified-flow and specified-head boundaries in applications of the modular finite-diference ground-water
flow model (MODFLOW): U.S. Geological Survey Open-File Report 97–571, 50 p., accessed June 27,
2017, at https://pubs.er.usgs.gov/publication/ofr97571.
Maddock, Thomas, III, Baird, K.J., Hanson, R.T., Schmid, Wolfgang, and Ajami, Hoori, 2012, RIP-ET—A
Riparian Evapotranspiration Package for MODFLOW-2005: U.S. Geological Survey Techniques and Meth-
ods, book 6, chap. A39, 76 p., accessed June 27, 2017, at https://pubs.usgs.gov/tm/tm6a39/.
Merritt, M.L., and Konikow, L.F., 2000, Documentation of a computer program to simulate lake-aquifer inter-
action using the MODFLOW ground-water flow model and the MOC3D solute-transport model: U.S.
Geological Survey Water-Resources Investigations Report 00–4167, 146 p., accessed June 27, 2017, at
https://pubs.er.usgs.gov/publication/wri004167.
Niswonger, R.G., and Prudic, D.E., 2005, Documentation of the Streamflow-Routing (SFR2) Package to
include unsaturated flow beneath streams—A modification to SFR1: U.S. Geological Survey Techniques
and Methods, book 6, chap. A13, 50 p., accessed June 27, 2017, at https://pubs.er.usgs.gov/publication/
tm6A13.
Niswonger, R.G., Prudic, D.E., and Regan, R.S., 2006, Documentation of the Unsaturated-Zone Flow (UZF1)
Package for modeling unsaturated flow between the land surface and the water table with MODFLOW-
2005: U.S. Geological Survey Techniques and Methods, book 6, chap. A19, 62 p., accessed June 27, 2017,
at https://pubs.usgs.gov/tm/2006/tm6a19/.
Panday, Sorab, Langevin, C.D., Niswonger, R.G., Ibaraki, Motomu, and Hughes, J.D., 2013, MODFLOW-
USG version 1—An unstructured grid version of MODFLOW for simulating groundwater flow and tightly
coupled processes using a control volume finite-difference formulation: U.S. Geological Survey Techniques
and Methods, book 6, chap. A45, 66 p., accessed June 27, 2017, at https://pubs.usgs.gov/tm/06/a45/.
References Cited R–3
Provost, A.M., Langevin, C.D., and Hughes, J.D., 2017, Documentation for the “XT3D” Option in the Node
Property Flow (NPF) Package of MODFLOW 6: U.S. Geological Survey Techniques and Methods, book 6,
chap. A56, 46 p., accessed August 4, 2017, at https://doi.org/10.3133/tm6A56.
Prudic, D.E., 1989, Documentation of a computer program to simulate stream-aquifer relations using a mod-
ular, finite-difference, ground-water flow model: U.S. Geological Survey Open-File Report 88–729, 113 p.,
accessed June 27, 2017, at https://pubs.er.usgs.gov/publication/ofr88729.
Prudic, D.E., Konikow, L.F., and Banta, E.R., 2004, A New Streamflow-Routing (SFR1) Package to simulate
stream-aquifer interaction with MODFLOW-2000: U.S. Geological Survey Open File Report 2004–1042,
104 p., accessed June 27, 2017, at https://pubs.er.usgs.gov/publication/ofr20041042.
Zheng, Chunmiao, 2010, MT3DMS v5.3, Supplemental User’s Guide: Technical Report Prepared for the U.S.
Army Corps of Engineers, 51 p.
Zheng, Chunmiao, Hill, M.C., and Hsieh, P.A., 2001, MODFLOW-2000, the U.S. Geological Survey Modu-
lar Ground-Water Model—User guide to the LMT6 package, the linkage with MT3DMS for multi-species
mass transport modeling: U.S. Geological Survey Open-File Report 01–82, 43 p., accessed June 27, 2017,
at https://pubs.er.usgs.gov/publication/ofr0182.
Appendix A. List of Blocks A–1
Appendix A. List of Blocks
Table A–1. List of block names organized by component and input file type. OPEN/CLOSE indicates whether or not the block
information can be contained in separate file.
Component FTYPE Blockname OPEN/CLOSE

SIM NAM OPTIONS yes
SIM NAM TIMING yes
SIM NAM MODELS yes
SIM NAM EXCHANGES yes
SIM NAM SOLUTIONGROUP yes
SIM TDIS OPTIONS yes
SIM TDIS DIMENSIONS yes
SIM TDIS PERIODDATA yes
EXG GWFGWF OPTIONS yes
EXG GWFGWF DIMENSIONS yes
EXG GWFGWF EXCHANGEDATA yes
SLN IMS OPTIONS yes
SLN IMS NONLINEAR yes
SLN IMS LINEAR yes
GWF NAM OPTIONS yes
GWF NAM PACKAGES yes
GWF DIS OPTIONS yes
GWF DIS DIMENSIONS yes
GWF DIS GRIDDATA no
GWF DISV OPTIONS yes
GWF DISV DIMENSIONS yes
GWF DISV GRIDDATA no
GWF DISV VERTICES yes
GWF DISV CELL2D yes
GWF DISU OPTIONS yes
GWF DISU DIMENSIONS yes
GWF DISU GRIDDATA no
GWF DISU CONNECTIONDATA yes
GWF DISU VERTICES yes
GWF DISU CELL2D yes
GWF IC GRIDDATA no
GWF NPF OPTIONS yes
GWF NPF GRIDDATA no
GWF BUY OPTIONS yes
GWF BUY DIMENSIONS yes
GWF BUY PACKAGEDATA yes
GWF STO OPTIONS yes
GWF STO GRIDDATA no
GWF STO PERIOD yes
A–2 MODFLOW 6 – Description of Input and Output
information can be contained in separate file.—Continued

GWF CSUB OPTIONS yes
GWF CSUB DIMENSIONS yes
GWF CSUB GRIDDATA no
GWF CSUB PACKAGEDATA yes
GWF CSUB PERIOD yes
GWF HFB OPTIONS yes
GWF HFB DIMENSIONS yes
GWF HFB PERIOD yes
GWF CHD OPTIONS yes
GWF CHD DIMENSIONS yes
GWF CHD PERIOD yes
GWF WEL OPTIONS yes
GWF WEL DIMENSIONS yes
GWF WEL PERIOD yes
GWF DRN OPTIONS yes
GWF DRN DIMENSIONS yes
GWF DRN PERIOD yes
GWF RIV OPTIONS yes
GWF RIV DIMENSIONS yes
GWF RIV PERIOD yes
GWF GHB OPTIONS yes
GWF GHB DIMENSIONS yes
GWF GHB PERIOD yes
GWF RCH OPTIONS yes
GWF RCH DIMENSIONS yes
GWF RCH PERIOD yes
GWF RCHA OPTIONS yes
GWF RCHA PERIOD yes
GWF EVT OPTIONS yes
GWF EVT DIMENSIONS yes
GWF EVT PERIOD yes
GWF EVTA OPTIONS yes
GWF EVTA PERIOD yes
GWF MAW OPTIONS yes
GWF MAW DIMENSIONS yes
GWF MAW PACKAGEDATA yes
GWF MAW CONNECTIONDATA yes
GWF MAW PERIOD yes
GWF SFR OPTIONS yes
GWF SFR DIMENSIONS yes
GWF SFR PACKAGEDATA yes
GWF SFR CONNECTIONDATA yes

GWF SFR DIVERSIONS yes
GWF SFR PERIOD yes
GWF LAK OPTIONS yes
GWF LAK DIMENSIONS yes
GWF LAK PACKAGEDATA yes
GWF LAK CONNECTIONDATA yes
GWF LAK TABLES yes
GWF LAK OUTLETS yes
GWF LAK PERIOD yes
GWF UZF OPTIONS yes
GWF UZF DIMENSIONS yes
GWF UZF PACKAGEDATA yes
GWF UZF PERIOD yes
GWF MVR OPTIONS yes
GWF MVR DIMENSIONS yes
GWF MVR PACKAGES yes
GWF MVR PERIOD yes
GWF GNC OPTIONS yes
GWF GNC DIMENSIONS yes
GWF GNC GNCDATA yes
GWF OC OPTIONS yes
GWF OC PERIOD yes
GWF API OPTIONS yes
GWF API DIMENSIONS yes
GWT ADV OPTIONS yes
GWT DSP OPTIONS yes
GWT DSP GRIDDATA no
GWT CNC OPTIONS yes
GWT CNC DIMENSIONS yes
GWT CNC PERIOD yes
GWT DIS OPTIONS yes
GWT DIS DIMENSIONS yes
GWT DIS GRIDDATA no
GWT DISV OPTIONS yes
GWT DISV DIMENSIONS yes
GWT DISV GRIDDATA no
GWT DISV VERTICES yes
GWT DISV CELL2D yes
GWT DISU OPTIONS yes
GWT DISU DIMENSIONS yes
GWT DISU GRIDDATA no
GWT DISU CONNECTIONDATA yes
A–4 MODFLOW 6 – Description of Input and Output

GWT DISU VERTICES yes
GWT DISU CELL2D yes
GWT IC GRIDDATA no
GWT NAM OPTIONS yes
GWT NAM PACKAGES yes
GWT OC OPTIONS yes
GWT OC PERIOD yes
GWT SSM OPTIONS yes
GWT SSM SOURCES yes
GWT SRC OPTIONS yes
GWT SRC DIMENSIONS yes
GWT SRC PERIOD yes
GWT MST OPTIONS yes
GWT MST GRIDDATA no
GWT IST OPTIONS yes
GWT IST GRIDDATA no
GWT SFT OPTIONS yes
GWT SFT PACKAGEDATA yes
GWT SFT PERIOD yes
GWT LKT OPTIONS yes
GWT LKT PACKAGEDATA yes
GWT LKT PERIOD yes
GWT MWT OPTIONS yes
GWT MWT PACKAGEDATA yes
GWT MWT PERIOD yes
GWT UZT OPTIONS yes
GWT UZT PACKAGEDATA yes
GWT UZT PERIOD yes
GWT FMI OPTIONS yes
GWT FMI PACKAGEDATA yes
GWT MVT OPTIONS yes
GWT API OPTIONS yes
GWT API DIMENSIONS yes
UTL LAK DIMENSIONS yes
UTL LAK TABLE yes
UTL OBS OPTIONS yes
UTL OBS CONTINUOUS yes
UTL TS ATTRIBUTES yes
UTL TS TIMESERIES yes
UTL TAS ATTRIBUTES yes
UTL TAS TIME yes
UTL ATS DIMENSIONS yes

UTL ATS PERIODDATA yes
Publishing support provided by the U.S. Geological Survey
MODFLOW 6 Development Team
For information concerning this publication, please contact:
Office of Groundwater
U.S. Geological Survey
Mail Stop 411
12201 Sunrise Valley Drive
Reston, VA 20192
(703) 648–5001
https://water.usgs.gov/ogw/
MODFLOW 6 Development Team— MODFLOW 6 – Description of Input and Output
https://doi.org/10.5066/F76Q1VQV

Manual Modflow 6 251 292

Uploaded by

Copyright:

Available Formats

Manual Modflow 6 251 292

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 251 292

Uploaded by

Copyright:

Available Formats

Time-Variable Input 239

where each time-series record is of the form:

interpolation-method—Interpolation method, which is either STEPWISE, LINEAR, or LINEAREND.

Using Time Series in a Package

Explanation of Variables Read from a Package Input File:

TS6—Keyword to specify that record corresponds to a time-series file.

FILEIN—Keyword to specify that an input filename is expected next.

Example use of time series to define package input

Contents of file “well pump rates.ts”:

Contents of the Well Package input file:

interpolation-method—Interpolation method, which is either STEPWISE or LINEAR.

Using Time-Array Series in a Package

Explanation of Variables Read from a Package Input File:

TAS6—Keyword to specify that record corresponds to a time-array-series file.

FILEIN—Keyword to specify that an input filename is expected next.

time-array-series-file-name—Name of a time-array-series file in which a time-array series used in the

property-name—Name of property represented by array to be controlled by a time-array series.

Example use of time-array series to define package input

Contents of Recharge package input file:

Contents of file “rch time array series.tas”:

BEGIN TIME 0.0

BEGIN TIME 91.0

BEGIN TIME 183.0

BEGIN TIME 274.0

BEGIN TIME 365.0

Binary Grid File

Header 1: ‘GRID DIS’ CHARACTER(LEN=50)

Read NDAT data variables using the definitions defined above.

Header 1: ‘GRID DISV’ CHARACTER(LEN=50)

Definition 17: ‘IA INTEGER NDIM 1 ncells+1’ CHARACTER(LEN=LENTXT)

Read NDAT data variables using the definitions defined above.

Header 1: ‘GRID DISU’ CHARACTER(LEN=50)

Read NDAT data variables using the definitions defined above.

Dependent Variable File

KSTP is the time step number;

KSTP is the time step number;

KSTP is the time step number;

Advanced Flow and Transport Packages

Model/Package TEXT Description

KSTP is the time step number;

Model Budget Files

Format of Budget File

IMETH=1: Read 1D array of size NDIM1*NDIM2*NDIM3.

KSTP is the integer time step number;

Variations for Discretization Types

Grid or Flow NDIM1 NDIM2 NDIM3

Budget File Contents for the GWF Model

Flow Type (TEXT) Method Description

Flow Type (TEXT) Method Description

GWF Model CSUB Package

Flow Type (TEXT) Method Description

GWF Model LAK, MAW, SFR, and UZF Packages

Flow term IMETH NDAT / NLIST Description

Flow term IMETH NDAT / NLIST Description

Flow term IMETH NDAT / NLIST Description

Flow term IMETH NDAT / NLIST Description

Flow term IMETH NDAT / NLIST Description

Flow term IMETH NDAT / NLIST Description

Flow term IMETH NDAT / NLIST Description

Budget File Contents for the GWT Model

IMETH=1: Read 1D array of size NDIM1NDIM2NDIM3.