SMS:TUFLOW Boundary Conditions

TUFLOW Boundary conditions may be defined at nodes, arcs, or polygons in a boundary conditions coverage.

Boundary Condition Locations

Boundary condition attributes must be assigned to a feature object. The boundary condition type is determined by the feature object being used.

1D Boundary Conditions at Nodes

File:TUFLOW BC Node Attribute.jpg

TUFLOW point or node Boundary Conditions dialog

Boundary conditions defined at points are 1D boundary conditions and must be placed at the same location as a 1D boundary node. (See Snapping Feature Objects) The boundary condition information is specified in the BC Node Attributes dialog.

Available boundary condition types for nodes and points include:

• "No BC" – No boundary condition exists at the location.
• "Flow vs Time" – Sets the flowrate as a curve through time.
• "Flow vs Wse" – Sets the flowrate based upon a relationship with the water surface elevation.
• "Wse vs Time" – Sets the water surface elevation as a curve through time.
• "Wse vs Flow" – Defines a relationship to determine the water surface elevation from a flowrate. The relationship can be specified or TUFLOW can compute it using water surface slope.

All of the boundary condition types for nodes or points include the options described below.

2D Boundary Conditions at Arcs

Arcs can be used to define 2D Boundary conditions applied to the 2D domain. The boundary conditions attributes are specified in the Boundary Conditions dialog.

Arcs can be assigned any of the following boundary condition types:

• "No BC" – No boundary condition exists at the location.
• "Flow vs Time" – Sets the flowrate as a curve through time.
• "Flow vs Wse" – Sets the flowrate based upon a relationship with the water surface elevation.
• "Wse vs Time" – Sets the water surface elevation as a curve through time.
• "Wse vs Flow" – Defines a relationship to determine the water surface elevation from a flowrate. The relationship can be specified or TUFLOW can compute it using water surface slope.
• "1D Flow/2D Water Level Connection (HX)" – Defines the interface between a 1D and 2D domain. See Combining 1D and 2D Domains. Options unique to this type include:
  • Set ZU and ZV elevations to ZC value if lower
  • Allocate water levels along dry sections
  • Set 1D and 2D water levels to same value
  • Adjust ZC to slightly above 1D bed elevation
• "Non-directional Flow vs Time" – Defines a flowrate that enters along each cell of the boundary.
• "Non-directional Flow vs Wse" – Defines a flowrate that enters along each cell of the boundary based upon a relationship to the water surface elevation.
• "Flow Source from 1D model (SX)" – Defines an interface between a 1D and 2D domain which is often useful for culverts rather than using the 1D Flow/2D Water Level Connection. Options unique to this type include:
  • Adjust z elevation in each cell center
  • Do not set 1D water level

File:TUFLOW Arc BC.jpg

TUFLOW arc Boundary Conditions dialog

2D Boundary Conditions for Polygons

File:TUFLOW Polygon BC.jpg

TUFLOW polygon Boundary Conditions dialog

Polygons can be used to define rainfall applied to 2D domains or to specify active/inactive information for 2D domains. The BC Polygon Attributes dialog specifies the type of information stored with the polygons.

Polygon boundary conditions can be assigned one of the following three types:

• "No BC" – No boundary condition exists at the location. Includes the option Set cell node which can be set to "Inactive—not in mesh", "Inactive—in mesh", or "Active".
• "Flow/Rainfall over Area" – Defines either an amount of flow entering the polygon (applies to all wet cells or lowest cell if none) or rainfall amounts (applies to all cells in the polygon).
• "Cell Codes" – Specifies whether cells are active or inactive and whether or not they will be included in the mesh output files.

Convert GIS Rainfall Data to TUFLOW BC Polygons

GIS files containing TUFLOW rainfall data may be imported into SMS and a Boundary Condition coverage with the data assigned to polygons will be created. The data for each polygon should be contained in the following columns: 8 STARTYEAR – Year of first data point (integer)

• STARTMONTH – Month of first data point (integer)
• STARTDAY – Day of first data point (integer)
• STARTHOUR – Hour of first data point (integer)
• STARTMIN – Minutes of first data point (integer)
• STARTSEC – Seconds of first data point (integer)
• TIMESPAN – Time span between data point in minutes (integer)
• NUMRAINPTS – Number of data points (integer)
• PT0 – Data for the first point (double)
• PT1, PT2,... – Data for each point

When converting GIS rainfall data to TUFLOW rainfall polygons, a prompt will appear to set a reference time. Each rainfall data point will be stored as total mm for each interval of time (hrs) from the reference time.

Events

Every boundary condition should be setup for each event that will be used with the boundary condition. The events can be defined by clicking on the Add or Remove buttons. Event names can be changed by double-clicking on the event. The list of events is common to all the boundary conditions in the project.

File:TUFLOW BC Events.jpg

TUFLOW BC Event dialog

Options

Depending upon the type of boundary condition, there are several additional boundary condition options. Options common to all boundary types include:

• Override Default Name – SMS creates a default unique boundary condition identifier based upon the coverage and id of the arc. Override this value to more easily find boundary condition information in the TUFLOW check, and log files.
• Spline Curve – If this option is on, TUFLOW will smooth the boundary condition curve using a spline algorithm. This should generally only be used for smooth, cyclic boundary conditions such as a tidal boundary.
• Advection Dispersion BC – Brings up the Advection Dispersion dialog for TUFLOW AD. Requires having constituents created in the TUFLOW 2D Model Control dialog.

Related Topics

• TUFLOW
• TUFLOW Coverages