Every model requires an appropriate set of boundary conditions to represent the system’s relationship with the surrounding systems. In the case of a groundwater flow model, boundary conditions will describe the exchange of flow between the model and the external system. In the case of a mass transport model, the boundary conditions will also describe the exchange of solute mass between the model and the external system.

The following sections present an overview of the boundary condition packages supported in Visual MODFLOW Flex. Each section includes a brief description of the boundary condition, including the input data required by MODFLOW and the supported data objects for defining the boundary condition geometry. The following boundary conditions are discussed in this section:

•Well

•Lake

•Time-varying Material Properties

The pumping well boundary condition is used to simulate wells (or other features) that withdraw water from or add water to the model at a constant rate during a stress period, where the rate is independent of both the cell area and head in the cell.

For finite difference translations, Visual MODFLOW Flex uses the Well (WEL) package, provided with MODFLOW. The MODFLOW input data for Well cells is stored in the projectname.WEL file. You can define the location for horizontal or deviated wells, which include the well path and the screen location. When you translate your conceptual model to MODFLOW format, the horizontal well screen location is converted to set of pumping well cells side-by-side. Another option is to define a specified flux or drain boundary condition in VMOD Flex. These are the workarounds, since there is no MODFLOW package for horizontal wells.

For finite element model translations, VMOD Flex translates the pumping well boundary conditions as a Type 4 (Well) boundary condition. Please note that the defined screen interval must extend beyond half of the element height for it to be assigned the boundary condition.

Currently, deviated/horizontal well translation is not supported for finite element models. If you intend to translate to FEFLOW, please make sure all pumping well boundary conditions are defined using vertical wells.

Required Data

In VMOD Flex, pumping well boundary conditions are defined using the well data contained in a wells data object. During the boundary condition creation process, you will be required to select a wells data object from the Data Explorer.

A well can only be used if it meets the following requirements:

•The pumping well must be located within the simulation domain

•A screen must be defined for the pumping well

•A pumping schedule must be defined for the pumping well

For information on importing well data, please see "Importing Wells" section.

For information on defining well data for existing wells data objects, please see the "Well Table" section

Currently, this boundary condition is only supported for Finite Difference Model translation.

The Specified Head boundary condition, also known as Constant Head in VMOD Flex, is used to fix the head value in selected grid cells regardless of the system conditions in the surrounding grid cells, thus acting as an infinite source of water entering the system, or as an infinite sink for water leaving the system. Therefore, specified head boundary conditions can have a significant influence on the results of a simulation, and may lead to unrealistic predictions, particularly when used in locations close to the area of interest.

During translation, VMOD Flex uses the Time-Variant Specified-Head Package provided with MODFLOW. The MODFLOW input data for Specified Head cells is stored in projectname.CHD file.

Unlike most other transient MODFLOW boundary condition packages, the Specified-Head package allows the specified heads to be linearly interpolated in time between the beginning and end of each stress period, such that the specified head for a grid cell may change at each time step of a given stress period. If the simulation is steady-state, the specified starting head value will be used.

Required Data

The Specified-Head package requires the following information for each specified head grid cell for each stress period:

Start Head: Specified head value at the beginning of the stress period

Stop Head: Specified head value at the end of the stress period

Supported Geometry

The geometry for Specified Head boundary conditions can be specified using Polylines or Polygons

## A Note on Leakance vs. Conductance |

Some Type-3 (Head-Dependent Flux) boundary conditions (e.g. river and general head) require defining a conductance parameter (for MODFLOW). Conductance is a numerical parameter representing the resistance to flow between the cell assigned with that boundary condition and the surrounding cells. Conductance between cells is calculated using some average hydraulic conductivity of the cells, the area of the interface between the cells and the distance between the cell centers. The Conductance calculation requires the cell geometry (cell interfaces).
In Visual MODFLOW Flex, when you create a new conceptual boundary condition, this is done using shapes: polyline, polygon, and side faces. At this point, there is no notion of cell geometry, as a result, the conductance cannot be calculated since the cell face area cannot yet be calculated. For this reason, you are asked to define "Leakance" instead of "Conductance". Leakance is a conceptual (hydrogeological) term, and is expressed per unit area (if the conceptual boundary condition object is a polygon) or per unit length (if the conceptual boundary condition object is a polyline).
When you create the boundary condition, the Leakance can be calculated based on other defined parameters, or it can be explicitly defined.
When you look at the numerical representation (cell realization) of the boundary condition, you will see "Conductance" as the parameter, since this value can be calculated based on the intersecting cell geometry. For a boundary condition assigned with a polygon or side face, the Leakance is multiplied by the cell area, in order to get Conductance. For a boundary condition assigned with a polyline, the Leakance is multiplied by the length of the line that intersects the cell, in order to get the Conductance.
More details on this can be found at: http://water.usgs.gov/ogw/modflow/MODFLOW-2005-Guide/index.html?frequently_asked_questions.htm. |

The River boundary condition is used to simulate the influence of a surface water body on the groundwater flow. Surface water bodies such as rivers, streams, lakes and swamps may either contribute water to the groundwater system, or act as groundwater discharge zones, depending on the hydraulic gradient between the surface water body and the groundwater system.

For finite difference models, VMOD Flex uses the River Package included with MODFLOW. The MODFLOW input data for River grid cells is stored in projectname.RIV file. Currently, translation of river boundary conditions is not supported for finite element (FEFLOW) translations.

The MODFLOW River Package simulates the surface water/groundwater interaction via a seepage layer separating the surface water body from the groundwater system (see following figure).

Required Data

The MODFLOW River Package input file requires the following information for each grid cell containing a River boundary;

•River Stage: The free water surface elevation of the surface water body. This elevation may change with time.

•Riverbed Bottom: The elevation of the bottom of the seepage layer (bedding material) of the surface water body.

•Conductance: A numerical parameter representing the resistance to flow between the surface water body and the groundwater caused by the seepage layer (riverbed).

The Conductance value (C) may be calculated from the length of a reach (L) through a cell, the width of the river (W) in the cell, the thickness of the riverbed (M), and the vertical hydraulic conductivity of the riverbed material (K) using the following formula:

For situations where the River package is used to simulate lakes or wetlands, the L and W variables would correspond to the X-Y dimension of the River boundary grid cells.

When a River boundary condition is assigned, the Use default Leakance option is automatically selected.

If the Use default Leakance option is selected, the River boundary condition requires the following data:

•River Stage: The free water surface elevation of the surface water body. [L]

•Riverbed Bottom: The elevation of the bottom of the seepage layer (bedding material) of the surface water body. [L]

•Riverbed Thickness: Thickness of the riverbed (seepage layer) [L].

•Leakance: A numerical parameter representing the resistance to flow between the surface water body and the aquifer (this field is read-only and is calculated using the formula described below). [L2/T]

•Riverbed Kz: Vertical hydraulic conductivity of the riverbed material. [L/T]

•River Width: Width of the river. [L]

When a polyline is used to define the river geometry, the default conductance formula is as follows:

When a polygon is used to define the river geometry, the default conductance formula is as follows::

where:

•$COND: is the Conductance

•$RCHLNG: is the reach length of the river line in each grid cell

•$WIDTH: is the River Width in each grid cell

•$K: is the Riverbed Kz

•$UCTOCOND: is the conversion factor for converting the $K value to the same L and T units used by $COND

•$RBTHICK: is the Riverbed Thickness

•$DX: is the length of each grid cell in the X-direction

•$DY: is the length of each grid cell in the Y-direction

If the Use default Leakance option is turned off, the fields used for calculating the River Leakance value (Riverbed Thickness, Riverbed Kz, and River Width) are removed from the table, and the Leakance field becomes a writable field where a value may be entered.

Supported Geometry

The geometry for River boundary conditions can be specified using polylines or polygons

For finite difference models, VMOD Flex supports translation of the General-Head Boundary Package included with MODFLOW. The MODFLOW input data for General-Head grid cells is stored in the projectname.GHB file. Currently, for finite element models, translation of this boundary condition is not supported.

The function of the General-Head Boundary (GHB) Package is mathematically similar to that of the River, Drain, and Evapotranspiration Packages. Flow into or out of a cell from an external source is provided in proportion to the difference between the head in the cell and the reference head assigned to the external source. The application of this boundary condition is intended to be general, as indicated by its name, but the typical application of this boundary condition is to represent heads in a model that are influenced by a large surface water body outside the model domain with a known water elevation. The purpose of using this boundary condition is to avoid unnecessarily extending the model domain outward to meet the element influencing the head in the model. As a result, the General Head boundary condition is usually assigned along the outside edges (sides) of the simulation model domain. This scenario is illustrated in the following figure.

The primary differences between the General-Head boundary and the Specified Head boundary are:

•the model solves for the head values in the General-Head grid cells whereas the head values are specified in Constant Head cells.

•the General-Head grid cells do not act as infinite sources of water whereas Specified Head cells can provide an infinite amount of water as required to maintain the specified head. Therefore, under some circumstances, the General-Head grid cells may become dry cells.

Required Data

The General-Head Boundary Package requires the following information for each General-Head grid cell:

•Stage: This is the head of the external source/sink. This head may be physically based, such as a large lake, or may be obtained through model calibration.

•Conductance: The is a numerical parameter that represents the resistance to flow between the boundary head and the model domain.

In contrast to the River, Drain, and Evapotranspiration packages, the General Head package provides no limiting value of head to bind the linear function in either direction. Therefore, as the head difference between a model cell and the boundary head increases/decreases, flow into or out of the cell continues to increase without limit. Accordingly, care must be used to ensure that unrealistic flows into or out of the system do not develop during the simulation.

The leakance value may be physically based, representing the conductance associated with an aquifer between the model area and a large lake, or may be obtained through model calibration. The leakance value (C) for the scenarios illustrated in the preceding figure may be calculated using the following formula:

where

•(LxW) is the surface area of the grid cell face exchanging flow with the external source/sink

•K is the average hydraulic conductivity of the aquifer material separating the external source/sink from the model grid

•D is the distance from the external source/sink to the model grid

When a General-Head boundary condition is assigned, the Use default leakance option is automatically selected.

If the "Use default leakance" option is selected, the General-Head boundary condition requires the following data:

•Stage: The head value for the external source/sink

•Leakance: A numerical parameter representing the resistance to flow between the boundary head and the model domain (this field is read-only and is calculated using formula described below)

•Distance to Reservoir: The distance from the external source/sink to the General-Head grid cell

•General Head Average Conductivity: The average hydraulic conductivity of the aquifer material separating the external source/sink from the model grid

The default formula used to calculate the Leakance value for the General-Head boundary is:

where

•$COND: is the Leakance for each General-Head grid cell

•$KAVG: is the Average Conductivity

•$FACEAREA: is the surface area of the selected grid cell Face for each General-Head grid cell (automatically calculated during translation)

•$UCTOCOND: is the conversion factor for converting the $K value to the same Length (L) and Time (T) units used by $COND

•$DIST: is the Boundary Distance, the distance from the external source to the assigned general head boundary

If the "Use default conductance" formula option is not selected, the fields used for calculating the General-Head Conductance value (Distance to Reservoir, Average Conductivity) are removed from the table, and the Leakance field becomes a writable field where a value may be entered.

Supported Geometry

The geometry for General-Head boundary conditions can be specified using a polygon data objects.

For finite difference models, VMOD Flex supports the standard Drain Boundary Package included with MODFLOW. The MODFLOW input data for Drain grid cells is stored in the projectname.DRN file. Currently, for finite element model translation, this boundary condition is not supported.

MODFLOW's Drain Package is designed to simulate the effects of features such as agricultural drains, which remove water from the aquifer at a rate proportional to the difference between the head in the aquifer and some fixed head or elevation. The Drain package assumes the drain has no effect if the head in the aquifer falls below the fixed head of the drain.

Required Data

The Drain Package requires the following information as input for each cell containing this boundary condition:

•Elevation: The drain elevation, or drain head of the free surface of water within the drain. The drain is assumed to run only partially full, so that the head within the drain is approximately equal to the median elevation of the drain.

•Leakance: The drain leakance is a lumped coefficient describing the head loss between the drain and the groundwater system. This loss is caused by converging flow patterns near the drain, the presence of foreign material around the drain, channel bed materials, the drain wall, and the degree to which the drain pipe openings may be blocked by chemical precipitates, plant roots, etc.

There is no general formulation for calculating drain leakance. In most situations, the detailed information required to calculate drain leakance is not available to the groundwater modeler. These details include the detailed head distribution around the drain, aquifer hydraulic conductivity near the drain, distribution of fill material, number and size of the drain pipe openings, the amount of clogging materials, and the hydraulic conductivity of clogging materials. It is common to calculate drain leakance from measured values of flow rate and head difference. Drain leakance value is usually adjusted during model calibration.

When a polyline is used to define the boundary condition geometry, the default formula for the leakance is as follows:

When a polygon is used to define the boundary condition geometry, the default leakance formula is as follows:

where

•$COND: is the Leakance

•$RCHLNG: is the reach length of the drain in each grid cell

•$LCOND: is the Leakance per unit length of the drain in each grid cell

•$SCOND: is the Leakance per unit area of the drain in each grid cell

•$DX: is the length of each grid cell in the X-direction

•$DY: is the length of each grid cell in the Y-direction

If the Use default leakance option is turned off, the fields used for calculating the Drain Leakance value (Leakance per unit length or area) are removed from the table and the Leakance field becomes a read/write field where any value may be entered.

Supported Geometry

The geometry for General-Head boundary conditions can be specified using polygon or polylines

For finite difference models, VMOD Flex supports the Recharge Package (RCH) included with MODFLOW. The Recharge input data for MODFLOW is stored in the projectname.RCH file. For finite element models, recharge boundary conditions are translated as the In(+)/Out(-)flow material parameter.

The recharge boundary condition is typically used to simulate surficially distributed recharge to the groundwater system. Most commonly, recharge occurs as a result of precipitation percolating into the groundwater system. However, the recharge boundary can potentially be used to simulate recharge from sources other than precipitation, such as irrigation, artificial recharge, or seepage from a pond.

Note: The recharge rate is a parameter that is not often measured at a site, but rather, it is assumed to be a percentage of the precipitation. This percentage typically ranges from 5% to 20% depending on many different factors including:

•the predominant land use and vegetation type,

•the surface topography (slope), and

•the soil cover material

Required Data

The Recharge Package requires the following information as input for each cell containing this boundary condition:

•Recharge (L/T): The input flux due to recharge. The recharge is applied in one of three ways as part of the package translation settings: 1. recharge is applied only to cells in layer 1, 2. recharge is applied to cells the specified layer, 3. recharge is applied to the upper-most active cell. See the documentation in the Recharge Translation Settings documentation for more details.

•Ponding (L) [optional, only used in the MODFLOW-SURFACT engine]: The maximum allowable depth of the water table above the ground surface. Calculated heads elevations above this depth (+ground surface) are truncated by the model. Note: that excess water is simply removed from the model without being routed to other cells.

Supported Geometry

The geometry for Recharge boundary conditions can be specified using polygon data objects and by points, and for an entire layer.

For finite difference models, Visual MODFLOW Flex supports the Evapotranspiration Package (ET) included with MODFLOW. After translation, the Evapotranspiration input data for MODFLOW is stored in the projectname.EVT file. Currently, this boundary condition is not supported for finite element translation.

The evapotranspiration boundary condition simulates the effects of plant transpiration, direct evaporation, and seepage at the ground surface by removing water from the saturated groundwater regime.

The evapotranspiration boundary approach is based on the following assumptions:

•When the water table is at or above the ground surface (top of layer 1), evapotranspiration loss from the water table occurs at the maximum rate specified by the user.

•When the elevation of the water table is below the ‘extinction depth’, or is beneath layer 1, evapotranspiration from the water table is negligible.

Between these limits, evapotranspiration from the water table varies linearly with water table elevation.

Required Data

The Evapotranspiration Package requires the following information:

•Evapotranspiration rate: The rate of evapotranspiration as it occurs when the water table elevation is equal to the top of the grid cell elevation. This value should be entered in the units set for recharge as defined in the Project Settings.

•Extinction Depth: The depth below the top of grid cell elevation where the evapotranspiration rate is negligible.

The Evapotranspiration Package approach is based on the following assumptions:

When the water table is at or above the ground surface (top of layer 1), evapotranspiration loss from the water table occurs at the maximum rate specified by the user.

When the elevation of the water table is below the ‘extinction depth’, or is beneath layer 1, evapotranspiration from the water table is negligible.

Between these limits, evapotranspiration from the water table varies linearly with water table elevation.

Supported Geometry

The geometry for Evapotranspiration boundary conditions can be specified using polygon data objects

For finite difference models, Visual MODFLOW Flex supports the Lake (LAK3) package for MODFLOW. After translation, the Lake input data for MODFLOW is stored in the projectname.LAK file. Currently, translation of this boundary condition is not supported for finite element models.

The lake boundary condition can be used to simulate the effects of stationary surface-water bodies such as lakes and reservoirs on an aquifer. The lake boundary is an alternative to the traditional approach of using the general head boundary condition. The main difference in the lake boundary is that the lake stage is calculated automatically based on the water budget, which is a function of inflow, outflow, recharge, etc.

For more information on the Lake package, please refer to USGS publication, Documentation of a Computer Program to Simulate Lake-Aquifer Interaction Using the MODFLOW Ground-Water Flow Model and the MOC3D Solute-Transport Model.

Required Data

The lake package requires the following input parameters:

•Stage: The initial stage of the lake at the beginning of the run.

•Bottom: The elevation of the bottom of the seepage layer (bedding material) of the surface water body.

•Leakance: A numerical parameter representing the resistance to flow between the boundary head and the model domain (this field is read-only and is calculated using formula described below)

•Lakebed Thickness: Thickness of the lakebed (seepage layer).

•Lakebed Conductivity: Vertical hydraulic conductivity of the lakebed material.

•Precipitation Rate per Unit Area: The rate of precipitation per unit area at the surface of the lake (L/T).

•Evaporation Rate per Unit Area: The rate of evaporation per unit area from the surface of the lake (L/T).

•Overland Runoff: Overland runoff (L3/T) from an adjacent watershed entering the lake.

•Artificial Withdrawal: The volumetric rate, or flux (L3/T) of water removal from a lake by means other than rainfall, evaporation, surface outflow, or ground-water seepage. Normally, this would be used to specify the rate of artificial withdrawal from a lake for human water use, or if negative, artificial augmentation of a lake volume for esthetic or recreational purposes.

The default leakance formula is as follows:

where

•$COND: is the Leakance

•$K: is the Lakebed Kz

•$UCTOCOND: is the conversion factor for converting the $K value to the same L and T units used by $COND

•$RBTHICK: is the Lakebed Thickness

•$DX: is the length of each grid cell in the X-direction

•$DY: is the length of each grid cell in the Y-direction

If the Use default Leakance option is turned off, the fields used for calculating the River Conductance value (Lakebed Thickness, Lakebed Kz) are removed from the table, and the Leakance field becomes a writable field where a value may be entered.

Supported Geometry

The geometry for Lake boundary conditions can be specified using polygon data objects

When you create the flux object, the value you define should be the flux per unit length (when using polyline) or per unit area (for polygon). When the cell realization is calculated, then VMOD Flex will calculate the flux for each cell based on the length of the line that passes thru the cell (for polyline) or the cell area (for polygon). For these reasons, you will see a significant difference in the parameter values for the conceptual object (shape) vs. the summed values for all cells (the cell realization).

For finite difference models, VMOD Flex supports the Specified Flux (FHB1) package for MODFLOW. After translation, the specified flux input data for MODFLOW is stored in the projectname.FHB file. Currently, translation of this boundary condition is not supported for finite element models.

The Specified Flux boundary condition allows you to specify flow, as a function of time, at selected model cells. FHB1 is an alternative and (or) supplement to the recharge (RCH) package for simulating specified-flow boundary conditions. The main differences between the FHB1 package and the recharge package are as follows:

•FHB1 package can simulate specified-flux on the top, side, bottom or intermediate layers in the simulation domain, whereas the recharge package can only be applied to the top and intermediate layers.

•FHB1 package allows you to specify a starting flux and an ending flux (for each stress period, if transient). The package then uses linear interpolation to compute values of flow at each model time step.

For more information on the Specified-Flow (FHB1) package, please refer to Documentation of a Computer Program (FHB1) for Assignment of Transient Specified-Flow and Specified-Head Boundaries in Applications of the Modular Finite-Difference Ground-Water Flow Model (MODFLOW, Open-File Report 97-571, U.S. Geological Survey).

Required Data

The specified flux package requires the following input parameters:

•Starting Flux (L3/T)

•Ending Flux (L3/T)

Supported Geometry

The geometry for Specified Flux boundary conditions can be specified using polygon or polyline data objects

Time-varying material properties can be specified for transient groundwater flow simulations (using the TMP1 package add-on in MODFLOW-SURFACT). The list of time-dependent properties includes:

•horizontal hydraulic conductivity,

•either vertical hydraulic conductivity or leakance,

•specific storage, and

•specific yield.

The reference values of these properties are assigned in the standard format associated with the BCF4 package. These reference values are then scaled by factors assigned in the TMP1 package, where the factors are time-dependent over the simulation period.

Required Data

The time-varying material package requires the following dimensionless input parameters for each stress period specified in the boundary condition:

•Kxx/Kyy Scaling [-]: the scaling factor by which the base horizontal conductivities (Kxx and Kyy) values will be multiplied for the associated stress period

•Kzz Scaling [-]: the scaling factor by which the base vertical conductivity (Kzz) value will be multiplied for the associated stress period

•Leakance Scaling [-]: the scaling factor by which the base vertical leakance values will be multiplied for the associated stress period.

•Sy Scaling [-]: the scaling factor by which the base specific yield values will be multiplied for the associated stress period.

•Ss Scaling [-]: the scaling factor by which the base specific storage values will be multiplied for the associated stress period.

NOTE: the Kzz and Leakance Scaling factors are mutually exclusive and which one is used is based on the settings in the BCF4 package.

Supported Geometry

The geometry for time-varying material boundary conditions can be specified using polygon or polyline data objects or on a cell-by-cell basis.

Page url:http://www.waterloohydrogeologic.com/help/vmod-flex/index.html?vm_about_boundary_conditions____t.htm