SMS:CGWAVE Graphical Interface
The CGWAVE Graphical Interface includes tools to assist with creating, editing, and debugging a CGWAVE model. The CGWAVE interface exists in the 2D Mesh Module.
Model Construction Steps
There is a very consistent method that can be used to apply the CGWAVE model. The steps to this process include:
- Load bathymetry – This data can come from LIDAR surveys, digital elevation maps (DEMs), previous grids or a variety of other sources. They must be referenced to the same datum the wave data will reference, and must have positive values represent depths. SMS includes functionality to convert datums, reverse directions and smoothor filter data.
- Limit bathymetry to positive values – CGWAVE does not handle wetting/drying or runup processes. All the nodes in the model must have a positive depth. This limiting process can be handled later in the mesh generation process, or the bathymetry itself can be modified (in a copied dataset) using the data calculator. For example, if you want to limit the domain to areas of at least one meter of depth use the following equation in the data calculator max(d1, 1.0) (where d1 is the label for the depth dataset).
- Compute the wave length – This is also done in the data set toolbox, using the Wave Length and Celerity tool. Enter the smallest wave period of interest (to generate the highest needed resolution).
- Create a size function – Typically this is simply a scaled version of the wave length data set. For example, a basic rule would be to have at least six elements per wave length. Some experts recommend at least 10 elements per wave length. The real issue is that you need enough resolution to represent the wave shape.
- To create a "Size" function with "N" elements per wave length, go to the data calculator and enter the equation d3/N (where d3 is the label for the wave length dataset).
- An alternative that may be needed with large domains is to create a spatially varied scale for the wave length function. For example, you may want to have 15 elements per wave length in the shallow region or your model (i.e. depths less than 3 meters), but only have 7 elements per wave length in the deep regions (i.e. depths greater than 200 meters). To create this size function, you would still use the data calculator and enter the equation d3/max(min(15+(d1-3)/(200-3)*(7-15),7)) (where d1 is the label for the depth function and d3 is the label for the wave length dataset).
- Define the coastline or land edge of the domain – This can be done using a contour of the bathymetry or reading a coastline vector file. It should be stored in SMS as a coastline arc in a CGWAVE coverage in the map module.
- Define the ocean boundary – This is also an arc in the CGWAVE coverage. It must be either a semi circle or circle and can be defined in SMS by selecting the coastline (or extreme locations on the coastline) and issuing the Feature Objects | Define domain... command in the map module.
- Build polygons in the map module and assign polygon attributes for the polygon to use the depth and size functions for bathymetry and size respectively in the mesh generation process. Then generate the mesh.
- With this mesh constructed, the rest of the graphical interface, defined below can be used to control the numerical simulation.
Model Control
The CGWAVE Model Control Dialog is used to setup the options that apply to the simulation as a whole. These options include time controls (steady state/dynamic), run types, output options, global parameters, print options and other global settings.
Boundary Conditions
All numeric models require boundary condition data. In CGWAVE boundary conditions are defined on nodestrings. The default boundary condition is a closed boundary (no flow). See CGWAVE BC Nodestrings for more information.
Material Properties
Each element is assigned a material type. Material properties describe the hydraulic characteristics of each material type.
Running the Model
The CGWAVE Files are written automatically with the SMS project file or can be saved separately using the File | Save CGWAVE or File | Save As menu commands.
CGWAVE can be launched from SMS using the CGWAVE | Run CGWAVE menu command. A check of some of the common problems called the Model Checker is done each time the model is launched, or by selecting the CGWAVE | Model Check menu command.
CGWAVE Menu
See CGWAVE Menu for more information.
Processing Solutions
CGWave creates a single output file (normally including ".cgo" extension when run with SMS). This file can be brought into SMS to graphically view the results. As SMS reads the file, it translates (using an embeded version of the CGWAVE "trans" code) the complex numbers representing wave heights and phases for each wave component into spatial and temporal data sets including:
- Steady State
- Wave Height
- Wave Phase
- Direction of Maximum Particle Velocity
- Time Varying (through a single wave period. SMS breaks the period into 20 timesteps)
- Pressures (at surface, mid depth and bed)
- Particle Velocities (at surface, mid depth and bed)
- Sea Surface Elevation
- Wave Velocity.
When the solution is read in, SMS allows the user to limit the wave heights in the solution. This only applies to linear runs of CGWAVE to allow the heights to be adjusted to be more realistic. This is accomplished by applying a factor, whose value ranges from 0 to 1 (defined as H/d). (Because wave height cannot exceed the value of depth or factor=1). SMS recommends a range of 0.4 to 0.8 and defaults to 0.64. The user may enter another factor dependent on that users knowledge of wave mechanics, type of problem, etc.
Related Topics
SMS – Surface-water Modeling System | ||
---|---|---|
Modules: | 1D Grid • Cartesian Grid • Curvilinear Grid • GIS • Map • Mesh • Particle • Quadtree • Raster • Scatter • UGrid | |
General Models: | 3D Structure • FVCOM • Generic • PTM | |
Coastal Models: | ADCIRC • BOUSS-2D • CGWAVE • CMS-Flow • CMS-Wave • GenCade • STWAVE • WAM | |
Riverine/Estuarine Models: | AdH • HEC-RAS • HYDRO AS-2D • RMA2 • RMA4 • SRH-2D • TUFLOW • TUFLOW FV | |
Aquaveo • SMS Tutorials • SMS Workflows |