DAF, DAFG - DAFLOW with MODFLOW

  • Scroll to top of this topic Scroll to Top of Page

  • Print the current topic Print Topic

  • Expand/collapse expanding elements on page Show/Hide Expanders

Abbreviations in Name file

•DAF

•DAFG

Purpose

To simulate surface-water/groundwater interaction. To facilitate the simulation of this interaction, the surface-water flow model (DAFLOW) has been coupled to the modular, finite-difference, groundwater flow model (MODFLOW). The DAFLOW model routes flows through a system of inter-connected one-dimensional channels and subdivides the system into a series of branches, with each branch divided into a number of subreaches.

Documentation

•Jobson, H.E., and Harbaugh, A.W., 1999, Modifications to the diffusion analogy surface-water flow model (DAFLOW) for coupling to the modular finite-difference ground-water flow model (MODFLOW): U.S. Geological Survey Open-File Report 99-217, 107 p.

•daf.txt

Related Packages

•Stream (STR)

•Streamflow-Routing (SFR)

•Head-Dependent Flux Boundary Packages

Supported in

MODFLOW-2000

Other Notes

•Two separate input files are required to use DAFLOW with MODFLOW.  One is for the surface-water flow; the other is for the groundwater interaction.

•An output file must be specified in the name file with type DATA and a unit number one greater than that applied to the DAFG file.  The file is normally named bltm.flw.

•See Package Incompatibilities
hmtoggle_plus1Input Instructions for Input File DAF

Two input files are necessary to run DAFLOW with MODFLOW. One file is identical to the input file needed to run DAFLOW alone. It defines the physical system to be modeled, specifies model options used for the simulation, and contains the boundary conditions as a function of time. In DAFLOW without MODFLOW, this file must be named flow.in, and throughout this report, it will be referred to as the flow.in file. But in the coupled version of DAFLOW and MODFLOW, this file can have any name. The name of the flow.in file is specified in the MODFLOW name file. The MODFLOW name file specifies all of the files used in a MODFLOW simulation. One line is used for each file, and this line consists of the file type, file unit, and file name. The file type for the flow.in file must be DAF. For example, the following line indicates that the flow.in file will be named test.inf:

DAF 42 test.inf .

The information contained in flow.in is divided into three data groups: (1) general information, (2) branch information, and (3) boundary conditions.

Table 1 is a summary description of the input data records as required in the file flow.in.

Table 1.--Input format for the Diffusion Analogy Flow Model

The first data group consists of nine records that define parameters to control the simulation.

Record

Field

Variable

Format

1

Title of simulation

TITLE - The title is specified as any combination of letters, symbols, or numbers of up to 80 characters in length. It will be printed in the output file for identification purposes but otherwise is not used. The remaining lines of the general information are read as formatted input so it is important that the numbers be placed in columns 21 to 30.

A80

2

1

Number of branches

NBRCH and NJNCT - The number of branches is self evident and only the number of interior junctions, not total junctions, is input as the third record. An interior junction is one that connects two or more branches.

20X,I10

3

1

Number of interior junctions

NBRCH and NJNCT - The number of branches is self evident and only the number of interior junctions, not total junctions, is input as the third record. An interior junction is one that connects two or more branches.

20X,I10

4

1

Number of time steps to be modeled

NHR - The number of time steps in the simulation is calculated as the duration of the simulation divided by the SW time-step size, expressed in hours.

20X,I10

5

1

Number of time steps between midnight and the start of the simulation

JTS The time reference for the simulation is midnight of the first day of the simulation. This is specified to the model as the number of time steps from midnight to the start of the simulation. For example, if the simulation is to begin at 06:00 hours and the time-step size is 0.5 hours, the value specified for JTS is 6 divided by 0.5, which equals 12 time steps.

20X,I10

6

1

Number of time steps between printouts in FLOW.OUT

JGO The printout frequency is specified in terms of the number of time steps between printouts. For example, if tabular flow information is desired every 3 hours and the time-step size is 0.5 hours, the value of JGO is specified as 3 divided by 0.5, which equals 6 time steps.

20X,I10

7

1

Input units [0 = metric (length unit is meters except for river miles), 1 = English (length unit is feet except river miles)]. Make IENG consistent with LENUNI.

IENG - The length units are specified as either 1 = English (ft) or 0 = metric (meter), except that the distance to node points (specified in data group 2) is input as either miles or kilometers.

20X,I10

8

1

Time-step size in hours

DT The time-step size is input in hours. DAFLOW uses an iterative solution scheme, such that its solutions must converge to a given tolerance.

20X,F10.3

9

1

Maximum discharge of interest (“peak discharge”), discharge below QP/100000.0 will be considered to be zero

QP - DAFLOW assumes that discharges (cubic feet or meter per second), differences in discharges, and water volumes divided by the time-step size, which are less than a tolerance, to be insignificant (nearly zero). The model calculates the tolerance from a given “peak” discharge divided by 100,000. This peak discharge should be larger than the maximum discharge expected during the simulation. It follows that the accuracy of the model results can be no better than this tolerance value. If the tolerance value is set too small, the program may not converge because the tolerance is smaller than the round-off error of flows carried in computer memory.

20X,F10.0

Data group two consists of two types of records: (1) branch record, (2) node/subreach records.

Record

Field

Variable

Format

1

1

Number of nodes (cross sections) in branch N

NXSEC, PF,  JNCU, and  JNCD - The branch record specifies the number of nodes (cross sections) in the branch, the fraction of flow at the upstream junction that enters the branch, and the upstream and downstream junction numbers. When more than one branch originates at a junction, the water that enters the junction is split between these outgoing branches. This is specified to the model as the fraction of flow to enter the branch. For example, if two branches receive equal amounts of flow from the junction, this value should be specified as 0.5 for each branch. If only one branch receives flow from a junction (the most common case), this value is specified as 1.0.

13X,I3

1

2

Fraction of flow at upstream junction to enter branch N

NXSEC, PF,  JNCU, and  JNCD - The branch record specifies the number of nodes (cross sections) in the branch, the fraction of flow at the upstream junction that enters the branch, and the upstream and downstream junction numbers. When more than one branch originates at a junction, the water that enters the junction is split between these outgoing branches. This is specified to the model as the fraction of flow to enter the branch. For example, if two branches receive equal amounts of flow from the junction, this value should be specified as 0.5 for each branch. If only one branch receives flow from a junction (the most common case), this value is specified as 1.0.

16X,F5.2

1

3

Junction number at upstream end of branch N

NXSEC, PF,  JNCU, and  JNCD - The branch record specifies the number of nodes (cross sections) in the branch, the fraction of flow at the upstream junction that enters the branch, and the upstream and downstream junction numbers. When more than one branch originates at a junction, the water that enters the junction is split between these outgoing branches. This is specified to the model as the fraction of flow to enter the branch. For example, if two branches receive equal amounts of flow from the junction, this value should be specified as 0.5 for each branch. If only one branch receives flow from a junction (the most common case), this value is specified as 1.0.

16X,I3

1

4

Junction number at downstream end of branch N

NXSEC, PF,  JNCU, and  JNCD - The branch record specifies the number of nodes (cross sections) in the branch, the fraction of flow at the upstream junction that enters the branch, and the upstream and downstream junction numbers. When more than one branch originates at a junction, the water that enters the junction is split between these outgoing branches. This is specified to the model as the fraction of flow to enter the branch. For example, if two branches receive equal amounts of flow from the junction, this value should be specified as 0.5 for each branch. If only one branch receives flow from a junction (the most common case), this value is specified as 1.0.

8X,I3

2

1

Header A header line follows the branch information to define the columns of data for the nodes or subreaches. The model ignores this line so it could be simply a blank line.

3

1

Node of data in record

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

I3

3

2

Distance of node I of branch N from reference point in miles

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

G11.4

3

3

Output flag (equal 1 if output in BLTM.OUT is desired for this node, 0 otherwise)

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

I2

3

4

Initial flow in subreach I (between node I and I+1)

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

G11.4

3

5

Constant A1 in equation 3 for subreach I

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

G10.3

3

6

Constant A2 in equation 3 for subreach I

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

G10.3

3

7

Constant A0 in equation 3 for subreach I

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

G10.3

3

8

Bed slope of subreach, in ft/ft or m/m

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

G10.3

3

9

Constant W1 in equation 4 for subreach I

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

F7.1

3

10

Constant W2 in equation 4 for subreach I

I, X, IOUT, F, A1, A2, A0, SL, W1, and W2 - The node records define the node number, location of the node in miles or kilometers, an output flag, for each node and the initial flow, hydraulic-geometry parameters and slope for each subreach. The hydraulic-geometry exponents are independent of the system of units, but the hydraulic-geometry coefficients are dependent upon the units used. The number of node-records input must equal the number specified on the branch record. Node records are input in sequence starting with the node 1, at the upstream end of the branch. The node location is specified as the distance to the cross section from a reference point at or above the upstream end of the branch. The initial discharge, slope, and all coefficients apply to the subreach extending from the node for which it is specified to the next node downstream. For example, the value of A1 input for node 1 applies to the subreach extending from node 1 to node 2. Because there is no subreach downstream of the last node, only the river mile and output flag needs to be specified for the last node. The model is based on the assumption that tributaries enter the stream just upstream of the node. The initial discharge for subreach I, therefore, should include the effect of the tributary flow at node I. The output flag (IOUT) specifies whether or not the flow information for the node is to be printed in the output file. The data at each node is read as a free-field format, so it is not necessary to keep the numbers in any particular column or even to line them up. It is necessary that at least one blank space separate each number and that a number be available for each variable. Exponential formats (see slope) are acceptable. The formats shown in Table 1 are used if the file is created interactively using the program BDAFLOW (Jobson, 1989).

F7.6

Boundary conditions must represent the average flow during the time step. For example, the first boundary condition should represent the average flow between time 0 and the end of the first time step. For the first time step, all boundary conditions should be entered because DAFLOW assumes all unspecified boundary conditions to be zero. After the first time step, however, DAFLOW assumes all boundary conditions remain constant unless specifically changed. The third data group is used to input boundary conditions and consists of two types of records.

Record

Field

Variable

Format

1

1

Number of new boundary conditions to be input for this time step

NBC The first record for each time step specifies the number of boundary conditions that have changed for this time step (NBC). A line for each boundary condition that has changed must follow. For example, if NBC=0, no records are required but if NBC = 5, five records must follow.

18X,I3

2

1

Branch number for new boundary condition

N, I, and TRB - The second type of record specifies the branch number, node number, and flow for the changed boundary condition. Data group 3 must be input for each time step of the simulation. The first record is always required, whereas the second record is only required if one or more boundary conditions are changed.

10X,I3

2

2

Node number for new boundary condition

N, I, and TRB - The second type of record specifies the branch number, node number, and flow for the changed boundary condition. Data group 3 must be input for each time step of the simulation. The first record is always required, whereas the second record is only required if one or more boundary conditions are changed.

5X,I3

2

3

New boundary flow for branch N, node I

N, I, and TRB - The second type of record specifies the branch number, node number, and flow for the changed boundary condition. Data group 3 must be input for each time step of the simulation. The first record is always required, whereas the second record is only required if one or more boundary conditions are changed.

3X,G14.5

  Example input "flow.in" for example shown in figure 2

2 No. of Branches           3 *

3 No. of Internal           1 * Junctions

4 No. Time Steps            5 * Modeled

5 Model Starts              0 time steps after midnight.

6 Output Given Every        1 Time Steps in "flow.out"

7 0=Metric,1=Englis         1 *

8 Time Step Size        1.000 Hours.

9 Peak Discharge      100000. *

Branch  1 has 9 xsects & routes 1.00 of flow at JNCT  2 To JNCT  1

Grd  Mi/Km IOUT  Disch      A1        A2        AO      Slope       W1    W2

  1 0.0000    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  2 0.7000    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  3  1.500    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  4  1.600    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  5  2.400    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  6  2.500    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  7  3.000    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  8  3.150    0  5000.    7.00     0.660     0.000     0.800E-03   50.0 0.260

  9  3.160    0                 

Branch  2 has 8 xsects & routes 1.00 of flow at JNCT  3 To JNCT  1

Grd R Mile IOUT  Disch      A1        A2        AO      Slope       W1    W2

  1  3.000    0  50.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  2  3.400    0  50.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  3  4.000    0  50.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  4  4.600    1  25.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  5  5.500    0  25.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  6  6.000    0  25.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  7  6.490    0  25.00    7.00     0.660     0.000     0.150E-02   50.0 0.260

  8  6.500    0                  

Branch  3 has 8 xsects & routes 1.00 of flow at JNCT  1 To JNCT  4

Grd R Mile IOUT  Disch      A1        A2        AO      Slope       W1    W2

  1  6.500    0  5025.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  2  7.000    0  5025.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  3  7.800    0  5025.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  4  8.300    0  5050.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  5  8.900    0  5050.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  6  9.500    0  5050.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  7  10.40    1  5050.    7.00     0.660     0.000     0.700E-03   50.0 0.260

  8  11.00    0                 

for Time   1 NBC=  4 *

 Branch    1 Node  1 Q=    5000.0     *

 Branch    2 Node  1 Q=    50.000     *

 Branch    2 Node  4 Q=   -25.000     *

 Branch    3 Node  4 Q=    25.000     *

for Time   2 NBC=  1 *

 Branch    1 Node  1 Q=    50000.     *

for Time   3 NBC=  0 *

for Time   4 NBC=  2 *

 Branch    1 Node  1 Q=    5000.0     *

 Branch    2 Node  4 Q=   0.00000     *

for Time   5 NBC=  0 *

Figure 6. Input file, flow.in, to run the example shown in figure 2.
hmtoggle_plus1Input Instructions for Input File DAFG

Data Set 1

TITLE - When DAFLOW is linked to MODFLOW, input information is required in addition to what is contained in the flow.in file. This information is contained in a file that has file type DAFG in the MODFLOW name file. The first 80 characters of the first three lines of the DAFG file are simply read in as text and printed in the MODFLOW output file for information purposes. It is recommended that the first line contain identifying information, and the second two lines contain column headings to identify the eight data fields that will follow. Examples of the column headings are shown in figure 7, which contains input data for the example shown in figure 2.

Data Set 2

TITLE - When DAFLOW is linked to MODFLOW, input information is required in addition to what is contained in the flow.in file. This information is contained in a file that has file type DAFG in the MODFLOW name file. The first 80 characters of the first three lines of the DAFG file are simply read in as text and printed in the MODFLOW output file for information purposes. It is recommended that the first line contain identifying information, and the second two lines contain column headings to identify the eight data fields that will follow. Examples of the column headings are shown in figure 7, which contains input data for the example shown in figure 2.

Data Set 3

TITLE - When DAFLOW is linked to MODFLOW, input information is required in addition to what is contained in the flow.in file. This information is contained in a file that has file type DAFG in the MODFLOW name file. The first 80 characters of the first three lines of the DAFG file are simply read in as text and printed in the MODFLOW output file for information purposes. It is recommended that the first line contain identifying information, and the second two lines contain column headings to identify the eight data fields that will follow. Examples of the column headings are shown in figure 7, which contains input data for the example shown in figure 2.

Data Set 4

N, I, BEL(I,N), BTH, CND, NLY, NRW, NCL

Repeat data set 4 for each interior node within each branch.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Following the three header lines, eight fields of bed property and linkage information are needed for each interior node of each SW branch. The data fields include;

•(1) branch number (N),

•(2) node number (I),

•(3) bed elevation of subreach upstream of the node (BEL),

•(4) average bed thickness of the subreach (BTH),

•(5) bed hydraulic conductivity of subreach (CND), and

•(6), (7), (8) layer (NLY), row (NRW), and column (NCL) number respectively, of the cell in MODFLOW that is in hydraulic connection with the subreach.

These columns of information are read using free format so it is not important that the numbers be in any particular column or that the numbers line up. It is necessary, however that there be at least one blank space between each data field and that a number be available for each field. There must be one row of data for each interior node of each branch. For example, branch 1 contains nine nodes so seven entries are needed, for nodes 2 through 8. Node 2 defines the groundwater interaction for subreach 1 and GW interaction is not allowed for the last subreach. If a SW subreach is not connected to a GW cell enter zero for the layer, row, and column numbers.

The time unit of CND is always seconds regardless of the time unit used in the rest of the model (ITMUNI).  The length unit of CND is determined by IENG.

Data Set 5

TITLE2 - Following the bed properties and linkage information is another line of text information that can be used to identify the three parameters that are input as the last line of the file.

Data Set 6

IDAFCB, IDBG, IDAFBK

If the first parameter (IDAFCB) is an integer less than zero, the cell-by-cell flows will be printed to the output file, if it is an integer greater than zero they will be saved to a file in binary format and the value of IDAFCB is the value of Nunit of the file in the name file to which the flows will be saved.

If the second parameter (IDBG) is set to 1, extra debugging information will be written to the output file, otherwise it will not. This parameter should normally be set to zero (not 1) because the debug information generates a large volume of output.

The third parameter (IDAFBK) specifies whether central or backwards differencing will be used for groundwater heads in MODFLOW. Enter a zero if central differencing is to be used. Any integer, other than zero, causes backwards differencing to occur. These integers can be placed in any column as long as they are separated by at least one blank space.

Figure 7 contains an example DAFG file that could be used to run the example problem shown in figure 2. The streambed elevations for this example are computed on the basis of the assumption that the elevation of node 1, in branch 1 is 100 ft, and the bed slopes are as shown in figure 6. For example, figure 2 shows that the subreach upstream of node 2 in branch 1 should be in communication with row 1, column 1 of the aquifer, and it is assumed that only one layer is involved. The elevation of the bed for this subreach is estimated as the elevation of the midpoint of the subreach. So it should be the elevation of node 1 (100) minus the slope (0.0008 = 4.224 ft/mile) times one-half the subreach length (0.7 - 0.0 mile), or 98.522 ft.

Also, notice that there is no connection for node 2, branch 2 (subreach 1) with the aquifer so zeros are entered for the layer, row, and column of the interaction. Leakage from all three branches interact with cell 3,3. The thickness of the streambed layer is assumed to be 1.0 ft, and the hydraulic conductivity of the bed layer is assumed to be 0.00120 ft/s for all subreaches.

Because IDAFCB is greater than zero, the cell-by-cell flows will be saved to a separate file rather than printed to the output file. The code IDBG is not equal to 1 so the extensive debug printout will not be listed. Because IDAFBK is not equal to zero, backwards differencing will be used in MODFLOW.

Figure 7. Example input file for DAFG

Example "DAFG" input for example shown in figure 2

               Bed        Bed         Bed      GW node of exchange

 Brch  Node    Elev     Thickness  Conductivity Layer   Row Column

  1     2     98.522     1.0        1.20E-01       1      1     1

  1     3     95.354     1.0        1.20E-01       1      1     2

  1     4     93.453     1.0        1.20E-01       1      2     2

  1     5     91.522     1.0        1.20E-01       1      2     3

  1     6     89.651     1.0        1.20E-01       1      2     2

  1     7     88.384     1.0        1.20E-01       1      3     2

  1     8     86.652     1.0        1.20E-01       1      3     3

  2     2    112.788     1.0        1.20E-01       0      0     0

  2     3    108.828     1.0        1.20E-01       1      1     5

  2     4    104.076     1.0        1.20E-01       1      1     4

  2     5     98.136     1.0        1.20E-01       1      2     4

  2     6     92.592     1.0        1.20E-01       1      3     4

  2     7     88.672     1.0        1.20E-01       1      3     3

  3     2     85.728     1.0        1.20E-01       1      3     3

  3     3     83.326     1.0        1.20E-01       1      3     4

  3     4     80.923     1.0        1.20E-01       1      4     4

  3     5     78.891     1.0        1.20E-01       1      4     4

  3     6     76.673     1.0        1.20E-01       1      5     4

  3     7     73.901     1.0        1.20E-01       1      5     5

IDAFCB IDBG IDAFBK

  1     0     1