SMS:CMS-Flow

CMS-Flow
Model Info
Model type	Hydrodynamic model intended for local applications, primarily at inlets, the nearshore, and bays
Developer	Christopher W. Reed, Ph.D. Alejandro Sanchez Mitchell E. Brown
Web site	http://cirpwiki.info/wiki/CMS-Flow
Tutorials	General Section Data Visualization Observation Models Section CMS - CMS-Flow

CMS-Flow is a component of the Coastal Modeling System (CMS). Until 2007, it was developed under the name M2D. At that point in time, it was revised, file formats were updated for better flexibility and expandability, and it was incorporated into the CMS suite. The model developers at the United States Army Corps of Engineers maintain a wiki specifically for the numerical engine. It can be viewed at: cirpwiki.info/wiki/CMS-Flow. For more information on the model itself, refer to the users manual published by USACE-ERDC. The model is a finite-volume numerical engine which includes the capabilities to compute both hydrodynamics (water levels and current flow values under any combination of tide, wind, surge, waves and river flow) sediment transport as bedload, suspended load, and total load, and morphology change. The interface in SMS allows setting up and editing computational grids, specifying model parameters, defining interaction of this model with the wave counterpart (CMS-Wave), launching the model, and visualizing the results. The model is intended to be run on a project-scale, meaning the domain should only be on the order of 1-100 kilometers in length and width. The following sections describe the interface and make recommendations for application of the model.

Beginning with SMS 12.1 a quadtree grid system was implemented allowing for telescoping and refinement while replacing the previous cartesian grid. Sediment transport is less stable in version of SMS after 11.2. The CMS-Flow model can be added to a paid edition of SMS.

Graphical Interface

CMS-Flow makes use of SMS’s simulation interface. The simulation interface works by creating a simulation object in the Project Explorer then adding components for the simulation. CMS-Flow makes use of the following components:

• A quadtree grid
• A CMS-Flow Boundary Conditions coverage
• A CMS-Flow Save Points coverage (optional)
• An Activity Classification coverage. (optional)

The CMS-Flow simulation has its own menu commands that can be accessed by right-clicking on the simulation object. Each of the CMS-Flow coverage may also have a right-click menu to access dialogs and functions specific to the coverage or objects in the coverage.

From the simulation menu, the CMS-Flow Model Control dialog can be accessed. In the Model Control, parameters for the simulation run can be set.

Using the Model / Practical Notes

For new simulations, create the CMS-Flow grid based on a conceptual model. The conceptual model includes:

• Grid Generation – It's recommend generate a CMS-Flow grid using the conceptual model and a Quadtree Generator Coverage. This coverage has attributes associated with a two-dimensional quadtree grid and the model parameters associated with CMS-Flow. The grid position and extents are defined in the coverage using a grid frame, which can be defined with three clicks of the mouse (recommendation is to click the lower left corner, lower right corner and then upper right corner, but the position, orientation and size can all be edited during the grid generation process. The grid's i,j origin, however, will always be at the lower-left corner regardless of where the clicks are done. The coverage also defines the location of land and water in the grid using one of three methods:

• Land/Water cells defined based bathymetric values – CMS-Flow uses depths, so positive depth indicates water, negative depth indicates land. Cells with depth less than the negative value of the water surface are dry. This option requires a geometric survey that includes both the bathymetric area and the areas that could potentially be flooded. This is the most intuitive option and the preferred method if geometric data is available.
• Land/Water interface defined by coastline arcs – This option allows defining, reading, or importing arc definitions that delineate the water area. These arcs include an orientation. To the left of the arc is land, to the right is water. If necessary, select an arc and swap its orientation. All the area inside the grid frame on the "water" side of the arc must have elevations defined either from a survey, or by specification. Cells created on the "land" side of the arc will never be included in calculations (they are permanently dry). These arcs also include an attribute defining how cells spanning this interface are to be classified. They may be forced to be water (ocean preference), forced to be land (land preference) or split based on the percentage of the cell on each side of the arc (percent preference).
• Land/Water interface defined by polygons – This option also requires defining arcs that delineate the extents of the computational area. However, these arcs must be closed into polygons. Each polygon is specified to enclose land or water and cells are classified accordingly.

• Model Output – The numerical engine consists of several components. The base engine computes hydrodynamics. To this, sediment transport and salinity can be enabled as well. Each process produces spatially varied solutions (values for each wet cell) that SMS can display as spatial datasets. Additional observation cells can be created to view output at a higher temporal resolution.

CMS-Flow Files

See the article CMS-Flow Files.

Here are tables of some of the available input and output files for CMS-Flow.

• For more information on these files see pages 224 and 242 of the manual.

Required Input Files

Name	Description
DB3	dBASE III
_Depth.H5	Grid Depth Values XMDF
_Quadtrees.H5	Telescoping Grid
MAP	Grid and Projection Information
MATERIALS	Material Values
VTU	Visual Toolkit Unstructured Mesh

Output Files

Name	Description
CMCARDS	Coastal Modeling Card Settings
Hot_Start.H5	Hot Start Information
_Datasets.H5	Mannings Number Dataset
_Diag.H5	Diagnostic Solutions XMDF
_MP.H5	Model Parameters XMDF
_Vel.H5	Current Velocity XMDF
_WSE.H5	Water Surface Elevation XMDF
TEL	Telescoping Quadtree Mesh
TXT	Output Text

Case Studies / Sample Problems

The following tutorials may be helpful for learning to use CMS-Flow in SMS:

• Models Section

• CMS – CMS-Flow

Related Links

• SMS Models page
• CMS-Wave

External Links

• CMS-FLOW Users Manual
• Sep 2008 Modeling of Morphologic Changes Caused by Inlet Management Strategies at Big Sarasota Pass, Florida [1]
• Jul 2007 ERDC/CHL CHETN-IV-69 Tips for Developing Bathymetry Grids for Coastal Modeling System Applications [2]
• Aug 2006 ERDC/CHL TR-06-9 Two-Dimensional Depth-Averaged Circulation Model CMS-M2D: Version 3.0, Report 2, Sediment Transport and Morphology Change [3]
• Feb 2006 ERDC/CHL CHETN-IV-67 Frequently-Asked Questions (FAQs) About Coastal Inlets and U.S. Army Corps of Engineers' Coastal Inlets Research Program (CIRP) [4] Updated FAQ Website [5]
• May 2005 ERDC/CHL CHETN-IV-63 Representation of Nonerodible (Hard) Bottom in Two-Dimensional Morphology Change Models [6]
• May 2004 ERDC/CHL TR-04-2 Two-Dimensional Depth-Averaged Circulation Model M2D: Version 2.0, Report 1, Technical Documentation and User’s Guide [7]
• Dec 2003 ERDC/CHL CHETN-IV-60 SMS Steering Module for Coupling Waves and Currents, 2: M2D and STWAVE [8]