SVFLUX Boundary Condition Types Page

SOILVISION 10 Help Manual - 12/16/2019

SVFLUX Boundary Condition Types

In addition to the common boundary conditions, the following boundary conditions are available:

Flux
Normal Flux
X-Flux
Y-Flux
Z-Flux
Head
Head Data Flow
Head Data Review
Pressure Head
Excess Pore Pressure
Saturation
Surface Pond
Unit Gradient
Gradient
Review by Pressure
Climate
Geomembrane
Cauchy (Mixed)

NOTE:
Most boundary condition options will have a Constant, Expression, and Data options.

In most steady state models the constant option will be used.

Further details may be found in the Expressions section.

The data option allows values to be entered in a data table as a function of time. This option is only available in a
transient model.

NOTE:
Note on Unsaturated conditions for Consolidation analyis: The SVSOLID/SVFLUX consolidation formulation is based
on equations that assume fully saturated conditions. Care should be taken in choosing Initial Conditions or Boundary
Conditions, such that unsaturated conditions would not be imposed on the solution.

· Flux:
Flux boundary conditions allow the user to specify a unit flux, q, in or out of a model along the boundary. These types of
boundary conditions are typically referred to as Neumann type boundary conditions in literature. The units of the flux
3 2 3 2
boundary are L /T/ L . For example, if a flux rate of 0.2 m /day/m is applied over a region boundary 5m in length (and
3
unit width), the total flow into the model would be 0.2 x 5 x 1 = 1 m /day.

In most steady state models the Flux Expression will take the form of a constant. A single number will then be entered to
represent a constant water flux into or out of the model. It should also be noted that it is possible to force more water into
the model than is physically possible using a flux boundary condition. In certain cases of unrealistically high flux boundary
conditions numerical instability will result.

A description of the coordinate system used in the specification of boundary conditions may be seen in the
Conditions Coordinate System section.
SVFLUX Boundary Condition Types Page

Z-Flux

In transient models it may be desirable to vary the boundary flux value with time. This situation can be simulated with the
use of an expression or data boundary condition. The expression boundary condition could be used to model a varying flux
rate. Expression boundary conditions may contain any variable defined in the SVFLUX solver descriptor file. Typical
variables that may be used in the boundary condition may be seen in the Expressions section.

One method of applying the expression boundary condition is entering an equation in terms of “t”, for time. The following
equation is an example of a Flux Expression that was used to simulate a flux rate that at time = 0 was 1.5 m
(m/day) and at time = 24 it was 3.5 m/day (assuming time is in days):

2 * t + 1.5

If the model were run for longer than twenty-four hours the boundary condition would continue to increase. The expression
could be further modified using if then else logic to control the boundary condition. If then else syntax will be interpreted
by the SVFLUX solver if it is defined as follows:

if <conditional subexpression> then <subexpression> else <subexpression>

For the above example it would be desirable to use an if statement which set the flux equal to zero if the time exceeded
twenty-four hours. To accomplish this, the following expression may be entered in SVFLUX:

if t <= 1 then 2 * t + 1.5 else 0

SVFLUX also gives you the ability to import flux data. The purpose of this feature is to allow you to use your electronically
gathered precipitation data as a boundary condition. For instruction on using this feature see Climate Manager.

· Normal Flux:
If a Normal Flux is chosen as the boundary condition for a line segment or a surface, the flux will enter the model normal
to the line segment or surface.

Normal Flux Boundary Condition Interpretation

If a Normal Flux boundary condition is entered, (i), the SVFLUX solver will model that flux as being perpendicular to each of
the boundaries it is applied to. This behavior is shown in Case A and Case B outlined below.

In Case A and Case B it was desired to model a situation where the flux entering the model would be the same as the flux
exiting the model. In Case A this was achieved by applying a flux into the model of intensity i over a length L and a flux
exiting the model of intensity and i over a length L. In Case A, the flux entering and exiting the model is the same and is
equal to Q = i(m/s) x L(m) x 1(m) resulting in a flow Q = i x L = iL(m3/s). In Case B, however, the flow entering the
3
model is Q = i(m /s) x (L1+L2+L3)(m) x 1m, while the flow exiting the model is the same as Case A, Q = i(m/s) x
1m. From the diagram it can be seen that the length L1+L2+L3 is larger than the length L. Therefore, in Case B there is
more flow entering the model than can exit and mass balance for the model is not achieved.
SVFLUX Boundary Condition Types Page

SVFLUX offers you the use of several boundary conditions, which restrict flow to be strictly vertical or horizontal. They
include Y-Flux, X-Flux, and Z-Flux. Each of these boundary conditions is presented below.

· X-Flux:
The X-Flux scales the flux down based on the boundary’s angle to the vertical. This means that the flux is restricted to
being only in the x-direction and the amount of flux that enters the model is scaled down to take into account the angle of
the line segment or surface to the vertical. The mathematical expression that the SVFLUX solver uses to implement this
boundary condition for a flux of magnitude i, in a 2D model is, Normal(Vector(i,0)). In a 3D model the statement will
become Normal(Vector(i,0,0)).

· Y-Flux:
In order to model the above flux correctly, there must be some way to tell SVFLUX to only take the vertical component of
flux into account. For this you must use a Y-Flux as the boundary condition for the line segment. If the flux that you are
trying to model is i, the statement that the SVFLUX solver uses to restrict the flow to the vertical direction in a 2D model
Normal(Vector(0,i). This statement tells the solver that there are potentially two components of flow. The horizontal
component will be zero and the vertical or y-component will be i. The solver then normalizes each of these components of
flow to the boundary so it will be reduced by the proper amount to compensate for the angle of the boundary condition. In
a 3D model the statement will become Normal(Vector(0,i,0)). This method is also illustrated in the above diagram.

NOTE:
In 3D models the Z-Flux must be used to restrict flow to be strictly vertical due to the coordinate system change.

· Z-Flux:
The Z-Flux is only available in three-dimensional and axisymmetric models. This boundary condition will only account for
flux in the vertical direction the same as the Y-Flux. The mathematical expression that the SVFLUX solver uses to
implement this boundary condition for a flux of magnitude i, in a 3D model is, Normal(Vector(0,0,i)). The main use for this
boundary condition is modeling rainfall, which is strictly a vertical flux. A full description of this can be found in the

· Head:
A Head boundary condition allows the user to enter a boundary condition in terms of total head. Total head is defined as
the summation of pressure head, hp, and elevation (y or z) as shown in the following equation:

h = hp + z

where:
h = total head,
hp = pressure head,
z = elevation (y in 2D models).
SVFLUX Boundary Condition Types Page

-3/10 * t + 10

At time equal to zero, the reservoir is at a height of 10m and at a time of thirty days the reservoir has been drained to a
height of 4m. If you would like to run the model longer than thirty days but have the reservoir remain at an elevation of
4m, an if statement must be used as follows.

if t <= 30 then –3/10 * t + 10 else 4

The above statement will allow you to run the model for an indefinite time period allowing the draw down from 10m to 4m
to take place from zero to thirty days.

NOTE:
The THEN or ELSE expression may contain nested IF...THEN...ELSE expressions. Each ELSE will bind to the nearest
IF.

· Head Data Flow:

A Head boundary condition allows the user to enter a boundary condition in terms of total head on the upstream side of an
earth dam under rapid draw-down conditions. Total head is defined as the summation of pressure head, hp, and elevation
(y or z) as shown in the following equation:

h = hp + z

where:
h = total head,
hp = pressure head,
z = elevation (y in 2D models).

The Head Flow boundary condition is designed to divide the upstream boundary condition into two segments; i) below the
reservoir level, and ii) above the reservoir level. Below the reservoir level the water is allowed to flow freely in or out of the
model depending upon if the model is under rapid filling or rapid drawdown conditions. Above the reservoir elevation the
boundary is treated as a “no flow” boundary condition.

Further description of head data flow boundary conditions may be found in the SVFLUX Theory Manual.

· Head Data Review:

A Head boundary condition allows the user to enter a boundary condition in terms of total head on the upstream side of an
earth dam under rapid draw-down conditions. Total head is defined as the summation of pressure head, hp, and elevation
(y or z) as shown in the following equation:

h = hp + z

where:
h = total head,
hp = pressure head,
z = elevation (y in 2D models).

With this boundary condition the upstream side of an earth dam is divided into the following sections:

1. Above the reservoir level (unsaturated), - No flow

2. Above the reservoir level (saturated), and - Flow allowed out of the slope
3. Below the reservoir level. - Flow allowed in or out of the slope depending on gradient.

Specifically, water is allowed to flow into or out of the model (depending on the difference in pressures) below the reservoir
elevation. Between the phreatic line exit point and the reservoir elevation water may exit the model if pore
pressures approach zero in this area. Above the phreatic line are unsaturated conditions which allow “no flow” conditions.

Further description of head boundary conditions may be found in the SVFLUX Theory Manual.
SVFLUX Boundary Condition Types Page

where:
h = total head,
hp = pressure head,
z = elevation (y in 2D models).

In this boundary condition it is assumed that the user will enter pressure head in terms of units of length. Elevation will
then be added to the entry to convert the values to total head and apply them to the model.

· Excess Pore Pressure:

An excess pore pressure boundary condition allows the user to enter a boundary condition in terms of excess pore
pressure. Excess pore pressure, ue, is defined as shown in the following equation:

ue = (h-ho)*gww

where:
h = total head,
ho = initial total head,
gww = unit weight of water.

· Saturation:
A saturation boundary condition allows the user to enter a boundary condition in terms of saturation. This is the fixed
saturation sequence for changes to follow.

· Surface Pond:
A Surface Pond boundary condition allows the user to specify a boundary condition in terms of total head, where the head
is equal to the ground surface elevation at the boundary. The head applied at the boundary can be considered as shown in
the following equation:

h = y + pond height

where:
h = total head,
pond height = height of the water column above the ground surface (defaulting to 0m),
y = ground surface elevation.

In 2D and Axisymmetric models, the ground surface is determined by the software as the region (or regions) coordinates
defining the uppermost boundary. This boundary condition is not available in 1D or Plan models.

In 3D models the reference surface can be chosen as any surface in the model, but it will most often be the ground surface
(top surface).

h = z + pond height

where:
h = total head,
pond height = height of the water column above the ground surface (defaulting to 0m),
z = specified surface elevation.

· Unit Gradient:
This type of boundary condition assumes that the gradient (dh/dl) outward normally from a boundary is equal to 1.0. This
being the case the flux outward is then equal to the hydraulic conductivity, k which is a function of soil suction in an
unsaturated model. This type of boundary condition is typically applied to the bottom of a 1D numerical model when
performing cover design as there is reasonable precedence for the unit gradient boundary condition in the cover design
application.

There is no value required for a unit gradient boundary condition and the direction of flow is always assumed to be out of
SVFLUX Boundary Condition Types Page

of an assumed gradient. The only way the unit gradient boundary condition can be used is if the natural model
gradient is extremely close to 1.0 naturally before the application of the unit gradient boundary condition.

· The unit gradient boundary condition is also only recommended for unsaturated models. In saturated models the
boundary condition becomes equal to ksat and therefore typically removes the maximum amount of water possible
to the model. This will typically result in a model immediately drying out.

· In a 3D numerical model the unit gradient boundary condition may only be applied to surfaces.

· The unit gradient boundary condition is not available in plan view analysis.

· Gradient:
The usage and theory of gradient boundary condition is the same as unit gradient. The only difference is that a particular
gradient (dh/dl) can be specified with the following notes:

· Specify a valid gradient. The recommended value should be in the range of 0 < dh/dl <= 1.

· A negative gradient value is not allowed.

· A gradient value > 1 is allowed, but a warning message will be displayed to validate that the user wants to apply this
condition.

· Review by Pressure (Drain):

The terminology Drain boundary condition or seepage face are sometimes used to refer to this type of boundary condition.

A Review by Pressure boundary condition is used when water will exit a material at an unknown exit point. With the review
by pressure boundary condition there is an iteration process which occurs in order to determine the natural exit point of a
water table.

In this discussion the dam will be used to discuss how the SVFLUX solver will determine the exit point on the downstream
face, with a head of 10m on the upstream face. The lowest corner of the dam on the downstream face of the dam is at the
coordinates (52,0) while the highest corner on the downstream face is at (28,12).

The finite element solver will automatically iterate to determine the optimal exit point when a review boundary condition is
applied.

NOTE:
From more information on the settings for the SVFLUX review boundary conditions see Model Settings.
If review boundary conditions are applied in a steady-state model and its number of stages is less than five, a
warning message would popup to suggest increasing the number of stages by default. To enable or disable this
message, please go to Project Manager -> Options Menu -> Global Settings Dialog

The following is a typical plot that will report the pressure along the review boundary.
SVFLUX Boundary Condition Types Page

The x-axis in the above plot is the distance along the review boundary while the y-axis is the pressure along the review
boundary. The exit point is where the pressure switches from being positive or zero to being negative. In the above plot
this occurs at a distance of 3m along the review boundary. In the above case the exit point will be calculated by:

Exit Point = sin α x Distance

sin α = a / c
c =√ a + b
2 2

sin α = a / √a + b
2 2

Exit Point = (a / √a + b ) x Distance

2 2

a = 12m
b = 52 – 28 = 24m
Distance = 3m

Exit Point = (12 / √ 12 + 24 ) x 3m

2 2

Exit Point = 1. 34 m
SVFLUX Boundary Condition Types Page

· Climate:

A climate boundary type allows the user to select a climate dataset which has been created using the Climate Manager
dialog. This boundary type provides settings to account for precipitation, runoff, potential evaporation, actual evaporation,
transpiration, and other climate considerations.

NOTE:
The precipitation component of a climate boundary condition is equivalent to specifying a Vertical Flux boundary
condition (In 2D, a Y-Flux).

NOTE:
Multiple climate datasets can be created in the Climate Manager. A climate dataset can be applied to multiple
boundaries. In SVFLUX SVENVIRO multiple climate datasets can be applied to different boundaries.

· Geomembrane:
Geomembranes are a kind of geosynthetic material used in a variety of geotechnical engineering projects, including cut
offs, and liners for canals, ponds, and landfills. They are intended to be impermeable membranes, but in fact have some
hydraulic conductivity. The hydraulic conductivity will be very low and may increase over time as the materials break down.
Physical problems such as punctures, tears, or poor seams can drastically degrade the geomembrane performance.

In SVFLUX a geomembrane can be simulated as a boundary condition by providing 2 properties: the geomembrane
thickness and hydraulic conductivity.

Geomembranes can also be modeled in SVFLUX by defining a thin region and assigning a material to it with the properties
of a geomembrane, but by using the Geomembrane boundary conditions significant solution time savings are experienced
due to the decrease in nodes required.

Geomembrane boundary conditions are available for 1D, 2D, and 3D models. In 3D models a geomembrane can be applied
to a region sidewall to simulate a cutoff wall for example. The geomembrane boundary condition can also be applied to a
3D surface. In 3D models, the solver cannot currently handle automatic mesh refinement when this type of boundary
condition is used. It will be turned off when the model is analyzed.

NOTE:
Geomembrane boundary conditions must daylight the model on both ends. If both ends of the geomembrane do
not lie on an external boundary then a singularity is created and a solution cannot be calculated. In addition, the
boundary segment(s) must be internal to the model.
To avoid creating a singularity, apply the geomembrane to the remaining boundary segment(s) and supply a
thickness/conductivity that will not impact your model analysis.

NOTE:
It is recommended that the hydraulic conductivity of the geomembrane be within 7 orders of magnitude of the
hydraulic conductivity of any adjacent regions. Any greater range of hydraulic conductivity may approach computer
precision limitations and a solution may not be possible.

· Cauchy (Mixed):
Cauchy (or called Mixed) boundary conditions allow the user to specify the situation when flux is dependent on the head.
The above expression can be interpreted that if h > ha then water flow out with value of hc*(h -ha) otherwise no water
flow out.
when ha = elevation, the Cauchy b/c is the review b/c that has been implemented in SVFLUX.

SVFLUX also gives you the ability to import flux data. The purpose of this feature is to allow you to use your electronically
gathered precipitation data as a boundary condition. For instruction on using this feature see Climate Manager.