View source

From XMS Wiki - http://wikis.aquaveo.com/xms/

You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page:
{{SMS Infobox Model |
|name=          CMS-Flow
|model_type=    Hydrodynamic model intended for local applications, primarily at inlets, the nearshore, and bays
|developer=     
Christopher W. Reed, Ph.D. <br />
Alejandro Sanchez<br />
Mitchell E. Brown
|web_site=     http://cirp.usace.army.mil/wiki/CMS-Flow
|tutorials=     
General Section
* Data Visualization
* Observation
Models Section
* CMS - CMS-Flow
}}

CMS-Flow is a component of the Coastal Modeling System ([[SMS:CMS|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 here [http://cirp.usace.army.mil/wiki/CMS-Flow].  For more information on the model itself, refer to the [http://cirp.usace.army.mil/pubs/pdf/TR-06-9.pdf users manual] published by USACE-ERDC.

CMS-Flow 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 the user to set up and edit computational grids, specify model parameters, define interaction of this model with the wave counterpart ([[SMS:CMS-Wave|CMS-Wave]]), launch the model and visualize 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.  

== Functionality ==

== Graphical Interface ==
The [[SMS:CMS-Flow Graphical Interface|CMS-Flow Graphical Interface]] is contained in the [[SMS:Cartesian Grid Module|Cartesian Grid Module]] as well as the [[SMS:Map Module|Map Module]] and includes tools to create and edit a CMS-Flow simulation. The simulation consists of a geometric definition of the model domain (the grid) and a set of numerical parameters. The parameters define the boundary conditions and options pertinent to the model.

The interface is accessed by selecting the [[SMS:Cartesian Grid Module|Cartesian Grid Module]] and setting the current model to CMS-Flow.  If a grid has already been created for a CMS-Flow simulation or an existing simulation read, the grid object will exist in the [[SMS:Project Explorer|Project Explorer]] and selecting that object will make the Cartesian grid module active and set the model to CMS-Flow. See [[SMS:Cartesian Grid Module#Creating 2D Grids|Creating 2D Cartesian Grids]] for more information.


== Using the Model / Practical Notes ==

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

*Grid Generation: We recommend that you generate a CMS-Flow grid using the conceptual model and a CMS-Flow Coverage.  This coverage has attributes associated with a two-dimensional Cartesian grid and the model parameters associated with CMS-Flow.  The grid position and extents are defined in the coverage using a grid frame, which you can define 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 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 the user to define, read or import 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.  The user can 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 the user to define arcs delineating 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 [[SMS:CMS-Flow Spatial Data Sets|spatial data sets]].  Additional observation cells can be created to view output at a higher temporal resolution.

== Case Studies / Sample Problems ==
The following [[SMS:Tutorials|tutorials]] may be helpful for learning to use CMS-Flow in SMS:
* Models Section
** CMS - CMS-Flow

== Related Links ==
* [[SMS:SMS Models|SMS Models page]]
* [[SMS:CMS-Wave|CMS-Wave]]

== External Links ==
* Sep 2008 Modeling of Morphologic Changes Caused by Inlet Management Strategies at Big Sarasota Pass, Florida [http://www.fsbpa.com/08Proceedings/07AlymovTruittPoffAnderson2008.pdf]
* Jul 2007  ERDC/CHL CHETN-IV-69 Tips for Developing Bathymetry Grids for Coastal Modeling System Applications [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-69.pdf]
* 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 [http://cirp.usace.army.mil/pubs/pdf/TR-06-9.pdf]
* 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) [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-67.pdf] Updated FAQ Website [http://cirp.usace.army.mil/pubs/FAQs/FAQ.html]
* May 2005  ERDC/CHL CHETN-IV-63 Representation of Nonerodible (Hard) Bottom in Two-Dimensional Morphology Change Models [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-63.pdf]
* 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 [http://cirp.usace.army.mil/pubs/pdf/TR-04-2.pdf]
* Dec 2003  ERDC/CHL CHETN-IV-60 SMS Steering Module for Coupling Waves and Currents, 2: M2D and STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-60.pdf]

{{Template:SMSMain}}

[[Category:CMS-Flow]]
Templates used on this page:
Return to SMS:CMS-Flow.
Retrieved from "http://www.xmswiki.com/xms/SMS:CMS-Flow"
View source

From XMS Wiki - http://wikis.aquaveo.com/xms/

Views

Personal tools

XMS Projects

Links

Wiki Resources

Search

Toolbox
