https://cirpwiki.info/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0CIRPwiki - New pages [en]2024-03-28T22:22:30ZFrom CIRPwikiMediaWiki 1.39.2https://cirpwiki.info/wiki/GenCade_2.0_SimulationGenCade 2.0 Simulation2024-03-28T15:43:47Z<p>Rdchlmeb: Created page with "== Creating a GenCade simulation in SMS == If no GenCade simulation has been added to the SMS data tree, simply right click in the open space within the data tree and select "New Simulation..." and then "GenCade" (Figure 2). This option is called "GenCade Beta" in SMS 13.3.x. Once there is a GenCade simulation, GenCade 2.0 coverages can be added by: * Right clicking on the desired coverage as it appears in the Map Data section of the data tree * Click <u>Apply to</u>..."</p>
<hr />
<div>== Creating a GenCade simulation in SMS ==<br />
If no GenCade simulation has been added to the SMS data tree, simply right click in the open space within the data tree and select "New Simulation..." and then "GenCade" (Figure 2). This option is called "GenCade Beta" in SMS 13.3.x.<br />
Once there is a GenCade simulation, GenCade 2.0 coverages can be added by:<br />
<br />
* Right clicking on the desired coverage as it appears in the Map Data section of the data tree <br />
* Click <u>Apply to</u><br />
* Then choose the name of the simulation to apply that coverage to.<br />
<br />
<br />
'''Notes:'''<br />
<br />
* One coverage of each type (Grid, Structures, Point) must be added to a single simulation. <br />
* There can be no duplicated coverage types (i.e., two grid coverages or multiple structures coverages.<br />
<br />
<br />
One there is a GenCade coverage, the user may enter [[GenCade 2.0 Model Control Dialog|<u>GenCade Model Control</u>]].<br />
<br />
When the user is ready to save the GenCade simulation, they should Right-click the GenCade simulation in the data tree and choose "Save Simulation."</div>Rdchlmebhttps://cirpwiki.info/wiki/GenCade2.0GenCade2.02024-03-28T14:18:46Z<p>Rdchlmeb: /* Interface and User Guide */</p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 - A Regional Shoreline Evolution Simulation Model}}<br />
=Summary=<br />
{{TOC right}}<br />
GenCade is a one-line shoreline simulation model that combines the capabilities of regional-scale, planning-level calculations of CasCade and project-scale, engineering design-level calculations of GENESIS. GenCade computes shoreline change and wave-induced longshore and cross-shore sand transport. It has been operated within the Surface-water Modeling System (SMS) <br />
<br />
* GenCade version 1.x was officially released in April 2012 and SMS 11.1 was released in October 2012. Publications for GenCade, including technical reports, notes, tutorial materials (video clips and presentation slides) can be found on the [https://cirp.usace.army.mil/products/gencade.php CIRP website GenCade page].<br />
<br />
* Wiki pages for GenCade version 1.x can be found [[GenCade|<u>here</u>]].<br />
<br />
The GenCade interface has undergone many changes and improvements and being developed for SMS 13.3 and later. Most of the changes have come in the actual SMS interface for the setup for the GenCade simulations using a new Dynamic Model Interface in the SMS which allows for faster integration of updates and new features. Other changes to GenCade have been as new features implemented in the actual GenCade mode, such as Cross-Shore sediment transport and the ability to perform a series of Monte Carlo simulations.<br />
<br />
=Tech Transfer=<br />
[[Image:Example_GenCade_setup.jpg|200px|thumb|right|Figure 2. Example GenCade Setup]]<br />
<br />
A few workshops have included a demonstration and information transfer showing the new GenCade Cross-shore transport and Monte Carlo features, but did not cover any changes to the SMS interface. These were: <br />
*September, 2022 - Mobile, Alabama - Full day workshop highlighting new cross-shore transport feature and Monte Carlo simulations.<br />
*June, 2023 - Los Angeles, California - Full day workshop highlighting new cross-shore transport feature and Monte Carlo simulations.<br />
<br />
The upcoming CIRP Workshop in Chicago, Illinois in May 2024 will also cover the new GenCade features, but there will also be demonstration of the new SMS interface. It is our hope that all users will have access to the new interface in Q4 of 2024.<br />
<br />
<!-----------POC-----------------------><br />
{| style="width:75%; border-spacing:8px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #cedff2; background:#234B7C ; vertical-align:top; color:#000;" |<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#f5faff;"<br />
!{{POC|Yan Ding|Yan.Ding@usace.army.mil}}<br />
|-<br />
| style="color:#000;" |<br />
<center>U.S. Army Engineer Research and Development Center (ERDC), Coastal and Hydraulics Lab (CHL)<br><br />
For any questions, please contact [mailto://Yan.Ding@usace.army.mil Yan Ding]. </center><br />
|-<br />
|}<br />
|}<br />
<br />
=GenCade 2.0 Documentation=<br />
{| class="main" width="99%"<br />
| style="vertical-align:top;width:33%" |<!-- Left Column Portal --><br />
===Technical Documentation===<br />
----<br />
'''Model Theory'''<br />
:*[[GenCade:Basic Assumptions|Basic Assumptions]]<br />
:*[[GenCade:Model Capabilities|Model Capabilities]]<br />
:*[[GenCade:Basic Governing Equations|Governing Equations]] <br />
:*[[GenCade:Sand Transport Rates|Sand Transport Rates]]<br />
:*[[GenCade:Empirical Parameters|Empirical Parameters]]<br />
'''Wave Model'''<br />
:*[[GenCade:Wave Calculation|Wave Calculation]]<br />
:*[[GenCade:Internal Wave Transformation|Internal Wave Transformation]]<br />
'''Model Structure'''<br />
:*[[GenCade:Grid System|Grid System]]<br />
:*[[GenCade:Boundary Conditions|Boundary Conditions]]<br />
:*[[GenCade:Numerical Stability|Numerical Stability]]<br />
:*[[GenCade:Representation of Inlets|Representation of Inlets]]<br />
:*[[GenCade:Structures|Structures]]<br />
:*[[GenCade:Sediment Sources and Sinks|Sediment Sources and Sinks]] <br />
<br />
*'''[[GenCade_Tech_Documentation|Technical Documentation]]'''<br />
<br />
| style="vertical-align:top;width:33%;border-left:1px" solid #aaa;padding-left:1em |<!-- Middle Column Portal --><br />
<br />
===Interface and User Guide===<br />
---- <br />
*[[GenCade_Users_Guide | User Guide]]<br />
'''Getting Started with GenCade 2.0'''<br />
<br />
:'''GenCade Coverages'''<br />
:*[[GenCade 2.0 Grid Coverage|GenCade Grid]]<br />
:*[[GenCade 2.0 Structures Dialog|GenCade Structures]]<br />
:*[[GenCade 2.0 Point Dialog|GenCade Point]]<br />
*[[GenCade 2.0 Simulation|GenCade Simulation]]<br />
*[[GenCade 2.0 Model Control Dialog|GenCade Model Control]]<br />
*[[GenCade Input Files| Input Files and Formats]]<br />
*[[GenCade_Output_Files | Output Files and Formats]]<br />
<br />
<br />
*[[GenCade_Calibration | Model Calibration]]<br />
*[[GenCade_Users_Guide#Developing_Alternatives | Developing Alternatives]]<br />
*[[GenCade_Example | GenCade Tutorial/Example]]<br />
*[[GenCade_FAQs | Frequently Asked Questions]]<br />
<br />
===Releases===<br />
----<br />
<br />
* [[GenCadeReleases|GenCade Model Releases]]<br />
<br />
| style="vertical-align:top;width:33%;border-left:1px" solid #aaa;padding-left:1em |<!-- Right Column Portal --><br />
<br />
===Model Validation & Benchmark Cases===<br />
----<br />
<br />
*[[GenCade_Val:LSTF|LSTF Laboratory Cases]]<br />
*[[GenCade_Val:Benchmark Cases|Benchmark Cases]]<br />
*[[GenCade_Val:Genesis Validation - Jucar River|GenCade Validation to Jucar River, Cullera, Spain]]<br />
<br />
===Examples===<br />
----<br />
<br />
*[[GenCade Applications]] <br />
<br />
*[[GenCade_Applications_USACE Districts Previous Projects | USACE Districts]]<br />
<br />
*[[GenCade_Applications_CIRP Projects Previous Projects | CIRP Led Projects]]<br />
<br />
'''Private Sector'''<br />
:*[[GenCade_Applications_Private Sector U.S. Previous Projects|United States]]<br />
:*[[GenCade_Applications_Private Sector International Previous Projects|International]]<br />
<br />
*[[GenCade Lessons Learned]]<br />
<br />
===Tools & Links===<br />
----<br />
*[[Statistics| Goodness-of-Fit Statistics]]<br />
* [[ GenCade References]]<br />
|}</div>Rdchlmebhttps://cirpwiki.info/wiki/Gencade_Point_CoverageGencade Point Coverage2024-03-27T19:07:05Z<p>Rdchlmeb: /* Add GenCade Point Coverage */</p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 Point Coverage}}<br />
{{TOC right}}<br />
The GenCade Point coverage allows the user to define specific points in the interface used by GenCade. This coverage uses Feature Points within the SMS to define the positioning for each type and to assign the attributes. There are three types of functionality that can assigned to a point:<br />
*Attribute Modification<br />
*Wave Gage<br />
* Tidal Current Gage<br />
<br />
'''Notes:''' <br />
*Only one of this type coverage can be added to the simulation.<br />
*Only one functionality type is available for each point. For example, this means the same point cannot be used for both a Wave gage and an Attribute Modification point.<br />
<br />
== Add GenCade Point Coverage ==<br />
This coverage is added to SMS by right-clicking on the "Map Data" icon in the data tree and selecting <u>New Coverage</u>, then <u>Models</u> and then <u>GenCade Beta</u>. Inside the GenCade Beta item, there are three options: ''GenCade Grid'', ''GenCade Structures-Events'', and ''GenCade Point Attributes''. For the Point coverage, select the <u>GenCade Point Attributes</u> option.<br />
<br />
'''Note:'''<br />
<br />
* Until this new interface fully replaces the old interface, there will be the older (GenCade) and newer (GenCade Beta) options in the coverage list.<br />
<br />
<br />
This coverage is combined with the GenCade <u>[[GenCade 2.0 Structures Dialog|Structures/Events]]</u> and <u>[[GenCade 2.0 Grid Coverage|Grid]]</u> coverages to define all necessary pieces for the GenCade simulation.<br />
<br />
=Attribute Modification=<br />
[[File:Point_Mod.png|thumb|251x251px|alt=Figure 1. Display of Point Attribute screen for Attribute Modification points.|Figure 1. Display of Point Attribute screen for Attribute Modification points.]]<br />
This type of point will modify from the existing default values for all cells leading up to the point location. <br />
<br />
For example, in the GenCade Model Control, the default values for K1 and K2 have been set to 0.4 and 0.25, respectively. If the user wanted to use different values for these parameters in specific parts of the grid, they can use Attribute Modification points to accomplish it.<br />
<br />
The seven parameters which can have "modification" values set are:<br />
*'''K1'''<br />
*'''K2'''<br />
*'''Angle Amplification'''<br />
*'''Angle Incremental Adjustment'''<br />
*'''Height Amplification'''<br />
*'''Berm Height'''<br />
*'''Depth of Closure'''<br />
Any one or more of these parameters may be set for each point of this type. An example of this dialog screen is shown in Figure 1.<br />
<br />
=Wave Gage=<br />
[[File:Point_Wave.png|thumb|251x251px|alt=Figure 2. Display of Point Attribute screen for Wave gages.|Figure 2. Display of Point Attribute screen for Wave gages.]]<br />
This type of point will allow the user to designate the point as being a wave gage and to attach a series of times and wave parameters to be used in the simulation.<br />
<br />
For this type, the user is able to define the '''Wave Gage depth''' as well as other wave parameters for a range of dates and times.<br />
<br />
The table contains the following columns for each row:<br />
*'''Date/Time'''<br />
*'''H0''' &ndash; The wave height (m) <br />
*'''Period''' &ndash; The significant wave period (seconds).<br />
*'''Direction''' &ndash; the mean wave direction (degrees).<br />
<br />
An example of this dialog screen is shown in Figure 2<br />
<br />
=Tidal Current Gage=<br />
[[File:Point_Tide.png|thumb|251x251px|alt=Figure 3. Display of Point Attribute screen for Tidal Current gages.|Figure 3. Display of Point Attribute screen for Tidal Current gages.]]<br />
This type of point will allow the user to designate this point as being a tidal current gage and to attach a series of times and current speeds to be used in the simulation.<br />
<br />
For this type, the user is able to define the tidal parameters for a range of dates and times.<br />
<br />
The table contains the following columns for each row:<br />
<br />
* '''Date/Time'''<br />
* '''Current (ft/s or m/s)'''<br />
<br />
An example of this dialog screen is shown in Figure 3.<br />
<br />
<br />
[[Category:GenCade 2.0 Dialogs|P]]<br />
[[Category:GenCade|P]]</div>Rdchlmebhttps://cirpwiki.info/wiki/GenCade_Grid_DefinitionGenCade Grid Definition2024-03-27T16:27:59Z<p>Rdchlmeb: </p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 Grid Definition Dialog}}<br />
[[File:Grid_definition.png|alt=GenCade Grid Definition dialog showing the option for specifying base cell size.|thumb|291x291px|Figure 1. ''GenCade Grid Definition '' dialog showing the option for specifying base cell size.]]<br />
The GenCade Grid Definition dialog contains only one item at present.<br />
<br />
* '''Base cell size (<unit>)''' - This is the default grid spacing for the GenCade grid to be created (Figure 1).<br />
<br />
'''Note:''' The <unit> will vary between either <u>'''ft'''</u> or '''<u>m</u>''' depending on the SMS display projection for this GenCade project.<br />
<br />
<br />
<br />
To return to the Grid Coverage wiki page, click [[Gencade Grid Coverage|<u>here</u>]].<br />
<br />
For information about other dialogs, select from the options under '''Categories''' below.<br />
[[Category:GenCade 2.0 Dialogs|G]]<br />
[[Category:GenCade|G]]</div>Rdchlmebhttps://cirpwiki.info/wiki/GenCade_Grid_Point_AttributesGenCade Grid Point Attributes2024-03-27T16:27:22Z<p>Rdchlmeb: /* Defining the type for a point */</p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 Grid Point Attributes Dialog}}<br />
There are a few things to take into consideration when defining the GenCade grid. The locations of the point of origin and ending point matter for the GenCade simulation to be successful. For GenCade, all references to "left" and "right", imagine the user is standing on land and looking out toward the water. The same goes for the grid orientation. The point of origin is the left-most location to be made available to GenCade.<br />
<br />
For example, for a GenCade grid in the northern Gulf of Mexico (Galveston, TX), the point of origin (Begin point) will be on the right hand side of the screen and the End point will be on the left.<br />
<br />
As previously noted, there can only be '''one''' <u>Begin</u> point and only '''one''' <u>End</u> point as defined by this dialog. <br />
<br />
[[File:Grid_point_options.png|alt=GenCade Grid Point Attributes dialog showing the available options.|thumb|400x400px|Figure 1. ''GenCade Grid Point Attributes'' dialog showing the available options.]]<br />
=Creating a new point=<br />
To create a new point, click the "Create Feature Point" tool and then click the appropriate location for that point in the main graphics window. You can create several new points before assigning a type to them. Each newly created point will default to be an "Unassigned" type. No points that remain "Unassigned" will be considered in the grid generation process.<br />
<br />
=Defining the type for a point=<br />
[[File:Grid_refine.png|alt=GenCade Grid Point Attributes dialog showing the Refine option and resolution parameter.|thumb|400x400px|Figure 2. ''GenCade Grid Point Attributes'' dialog showing the Refine option and resolution parameter.]]To define the type for the point, change to the "Select Feature Point" tool and double-click a point, or select multiple points you wish to assign the same type too and right-click then select "Assign Point Type...". A combo box (shown in Figure 1) on the resulting dialog will have several options to choose from:<br />
*'''Unassigned'''<br />
*'''Begin'''<br />
*'''End'''<br />
*'''Refine'''<br />
<br />
If '''Refine''' is chosen, then an entry box will appear for the user to enter the resolution to be considered for that point (or point's) location. The resulting dialog for the Refine option is shown in Figure 2.<br />
<br />
<br />
<br />
To return to the Grid Coverage wiki page, click [[Gencade Grid Coverage|<u>here</u>]].<br />
<br />
For information about other dialogs, select from the options under '''Categories''' below.<br />
<br />
[[Category:GenCade 2.0 Dialogs|G]]<br />
[[Category:GenCade|G]]</div>Rdchlmebhttps://cirpwiki.info/wiki/Gencade_Grid_DialogGencade Grid Dialog2024-03-27T15:37:45Z<p>Rdchlmeb: /* Add Grid coverage to simulation */</p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 Grid Coverage}}<br />
{{TOC right}}<br />
[[File:Grid definition selection.png|thumb|357x357px|alt=Figure 1. Selecting "Grid Definition Options" for the Grid coverage.|Figure 1. Selecting "Grid Definition Options" for the Grid coverage.]]The GenCade Grid coverage allows the user to define the grid to be used by GenCade for all computations in a simulation. This coverage uses Feature Points within the SMS to define the positioning for each type and to assign the attributes:<br />
<br />
'''Notes:''' <br />
<br />
*Only one of this type coverage can be added to the simulation.<br />
*Only one Begin and End point can be created in this coverage.<br />
*As many Refine points can be added as needed to adequately represent all structures and events for the simulation.<br />
<br />
== Add GenCade Grid Coverage ==<br />
This coverage is added to SMS by right-clicking on the "Map Data" icon in the data tree and selecting <u>New Coverage</u>, then <u>Models</u> and then <u>GenCade Beta</u>. Inside the GenCade Beta item, there are three options: ''GenCade Grid'', ''GenCade Structures-Events'', and ''GenCade Point Attributes''. For the Grid coverage, select <u>GenCade Grid</u>.<br />
<br />
'''Note:''' <br />
<br />
* Until this new interface fully replaces the old interface, there will be the older (GenCade) and newer (GenCade Beta) options in the coverage list.<br />
<br />
<br />
This coverage is combined with the GenCade <u>[[GenCade 2.0 Structures Dialog|Structures/Events]]</u> and <u>[[GenCade 2.0 Point Dialog|Points]]</u> coverages to define all necessary pieces for the GenCade simulation.[[File:GenCade addSimulation.png|alt=Figure 2. Adding GenCade simulation to the SMS data tree.|thumb|225x225px|Figure 2. Adding GenCade simulation to the SMS data tree.]]<br />
<br />
== Grid Creation ==<br />
First, the user should use create two points which will define the Begin and Ending points for the GenCade Grid.<br />
<br />
See the <u>[[GenCade 2.0 Grid Point Attributes|GenCade_Grid_Point_Attributes]]</u> dialog for instructions and important notes. <br />
== Grid Definition Options ==<br />
Next, the user should define the default grid cell size for this coverage. This is done by right clicking on the GenCade grid coverage in the SMS Data Tree and selecting "Grid Definitions Options" as shown Figure 1 on the right.<br />
<br />
See the <u>[[GenCade 2.0 Grid Definition|GenCade Grid Definition]]</u> dialog for instructions and important notes. <br />
<br />
== Add Grid coverage to simulation ==<br />
[[File:Grid_freedraw.png|thumb|251x251px|alt=Figure 3. Display of resulting GenCade grid.|Figure 3. Display of resulting GenCade grid.]]<br />
Once there is a Begin and End point defined and the default grid spacing has been set, the grid can be built by adding it to a GenCade simulation.<br />
<br />
* Steps for creating a GenCade simulation can be found [[GenCade 2.0 Simulation|here]].<br />
<br />
Once the grid has been added to the GenCade simulation, it will be generated and appear on the SMS Graphics Window (Figure 3).<br />
[[Category:GenCade|G]]</div>Rdchlmebhttps://cirpwiki.info/wiki/GenCade_Structures_DialogGenCade Structures Dialog2024-03-26T21:31:57Z<p>Rdchlmeb: /* Add GenCade Structures Coverage */</p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 Structures/Events Coverage Dialog}}<br />
{{TOC right}}<br />
The GenCade Structures/Events coverage allows the user to define the structures and planned events for a GenCade simulation. Only one of this type coverage can be added to the simulation, so it should contain arcs for all structures and events needed. However, there can be multiple arcs of the same types within this coverage unless it is mentioned in the sections below.<br />
<br />
This coverage uses Feature Arcs within the SMS to define the positioning for each type and to assign a variety of attributes including:<br />
*Geometric objects &ndash; shoreline and contours.<br />
*Structures &ndash; jetty, inlet, seawall, or breakwater and their associated parameters.<br />
*Events &ndash; bypass or beach nourishment events and their time ranges and parameters.<br />
<br />
== Add GenCade Structures Coverage ==<br />
This coverage is added to SMS by right-clicking on the "Map Data" icon in the data tree and selecting <u>New Coverage</u>, then <u>Models</u> and then <u>GenCade Beta</u>. Inside the GenCade Beta item, there are three options: ''GenCade Grid'', ''GenCade Structures-Events'', and ''GenCade Point Attributes''. For the Structures coverage, select the <u>GenCade Structures-Events</u> option.<br />
<br />
'''Note:''' <br />
<br />
* Until this new interface fully replaces the old interface, there will be the older (GenCade) and newer (GenCade Beta) options in the coverage list.<br />
<br />
This coverage is combined with the GenCade <u>[[GenCade 2.0 Grid Coverage|Grid]]</u> and <u>[[GenCade 2.0 Point Dialog|Points]]</u> coverages to define all necessary pieces for the GenCade simulation. The Structures and Events coverage contains many different types as shown and described below.<br />
<br />
=Generic Arc=<br />
A Generic arc is the default for this dialog. Generic arcs are not yet assigned to be of any type and no information for these arcs is written to the input files.<br />
<br />
=Geometric Objects=<br />
==Initial Shoreline==<br />
Only one Initial Shoreline is allowed per GenCade simulation. This is the definition of where the water meets the land. The points for the shoreline can be loaded into SMS in several ways including from ArcGIS Shapefiles. As mentioned in the USACE Technical Report<ref>GenCade Version 1 Model Theory and User's Guide, https://hdl.handle.net/11681/7333</ref>, <blockquote>Rigorous quality control is required to make sure the initial shoreline accurately represents the shoreline of interest. This process requires a detailed inspection of the shoreline. It is recommended to smooth out sudden changes in shoreline orientation especially near an inlet. The smoothing algorithm [in SMS] can be used for this purpose. </blockquote><br />
<br />
==Regional Contour==<br />
In some cases, a regional contour may be added to the simulation. This arc can be defined in a similar manner, however it should be declared as the "Regional Contour" type under Arc Options on this dialog. Once the regional contour is specified, GenCade will maintain a desired overall shoreline curvature, e.g., preserving a bay shape without the presence of structures, even if the model is run for very long time periods. <br />
<br />
Adding a regional contour represents a simplified method to describe the effects on the shoreline evolution of processes acting at longer time scales than what is simulated in GenCade. Thus, the regional contour should incorporate large-scale trends in shoreline shape, and not small-scale features that are expected to change at time scales modeled by GenCade.<br />
<br />
==Reference Line==<br />
If the user wishes to see another shoreline within the SMS interface, they can add one or more shorelines as the "Reference Line" type. This type is not written to any input file and is not used by GenCade in any way. It is merely for the user to reference within the SMS display window.<br />
<br />
=Structures=<br />
GenCade simulates the effects of common coastal structures on the shoreline position. Common types structures that can be represented are groins, jetties, harbor breakwaters (with respect to their functioning as a jetty or groin), detached breakwaters, seawalls, and "soft structures" such as beach fills. Considerable flexibility is allowed in combining these basic structures to produce more complex configurations, e.g., T-shaped groins, Y-shaped and half-Y groins, and jetties with spurs. Combinations of these types of structures are also possible.<br />
<br />
==Restrictions==<br />
There may be as many structures as needed for a GenCade simulation, however there are a few restrictions. <br />
*Groins/jetties must be placed at least two grid cells apart.<br />
*A groin/jetty may not be placed in the cell adjacent to a boundary cells, regardless if the boundary is gated by a groin or jetty or if it is an open beach.<br />
*Diffracting structures of any type cannot overlap, except having their tips at the same cell wall.<br />
<br />
==Breakwater==<br />
[[File:Structure_Breakwater.png|alt=GenCade Structures dialog showing the Breakwater option|thumb|400x400px|''GenCade Structures'' dialog showing the ''Breakwater'' option]]<br />
Detached breakwaters have a few options to define for each structure.<br />
*''Depth 1'' (depth of the cell nearest the grid origin)<br />
*''Depth 2'' (depth of the cell farthest from the grid origin)<br />
*''Transmission Type'' - selection from this combo box defines other parameters used in breakwater computations.<br />
**''Constant'' - single constant transmission coefficient.<br />
**''Ahren's'' - first of three formulations taking several additional coefficients.<br />
**''Seabrook & Hall'' - second formulation<br />
**''d'Angremond'' - third formulation<br />
<br />
Note: All of these formulations take 5 parameters, and the first four are the same for each case.<br />
*'''Freeboard to MSL'''<br />
*'''Width'''<br />
*'''Seaward side slope'''<br />
*'''Shoreward side slope'''<br />
<br />
The Ahren's and Seabrook & Hall formulations each take a fifth parameter for '''Armor stone D50'''.<br />
<br />
The d'Angremond formulation takes a fifth parameter for '''Permeability'''.<br />
<br />
'''<span style="color:red">Tip:</span>'''<br />
*For detailed analysis, it is recommended that at least nine grid points (eight cells) be placed behind detached breakwaters.<br />
*For general analysis, a minimum of four cells is recommended.<br />
<br />
==Seawall==<br />
Effective sections of seawalls may be defined anywhere on the grid. It is noted that the seawall does not need to be straight, but may form a "curve" to follow the trend of the beach contours. The seawall may be placed at the shoreline or behind it. However, a seawall cannot be placed seaward of the shoreline.<br />
<br />
* The Seawall option for this dialog has no parameters associated with it.<br />
<br />
==Groin==<br />
[[File:Structure_Groin.png|alt=GenCade Structures dialog showing the Groin option|thumb|400x400px|''GenCade Structures'' dialog showing the ''Groin'' option]]<br />
The Groin option takes a few parameters:<br />
*Permeability<br />
*Diffracting (check box)<br />
**Seaward Depth (if Diffracting is checked).<br />
<br />
'''<span style="color:red">Tip:</span>'''<br />
*For detailed analysis, it is recommended that at least nine grid points (eight cells) be placed between adjacent groins.<br />
*For general analysis, a minimum of four cells is recommended.<br />
<br />
==Jetty (Left and Right)==<br />
The '''Left Jetty on Inlet''' and '''Right Jetty on Inlet''' options take a few parameters and is treated very similar to groins:<br />
*Permeability<br />
*Diffracting (check box)<br />
**Seaward Depth (if Diffracting is checked).<br />
<br />
The dialog for jetties is exactly the same as for Groins, see the figure for that example for reference.<br />
<br />
==Inlet==<br />
[[File:Structure_Inlet.png|alt=GenCade Structures dialog showing the Inlet option|thumb|400x400px|''GenCade Structures'' dialog showing the ''Inlet'' option]]<br />
The inlet name, shoal volumes, dredging events, and bypassing coefficients are all defined when an inlet type is created.<br />
<br />
The Inlets screen on this dialog has the following options:<br />
*''Name of Inlet''<br />
*''Inlet Shoal Volumes''<br />
**'''Ebb Shoal''' - <u>Initial</u> and <u>Equilibrium</u> volumes<br />
**'''Flood Shoal''' - <u>Initial</u> and <u>Equilibrium</u> volumes<br />
**'''Left Bypass''' - <u>Initial</u> and <u>Equilibrium</u> volumes AND a bypass <u>Coefficient</u><br />
**'''Left Attachment''' - <u>Initial</u> and <u>Equilibrium</u> volumes<br />
**'''Right Bypass''' - <u>Initial</u> and <u>Equilibrium</u> volumes AND a bypass <u>Coefficient</u><br />
**'''Right Attachment''' - <u>Initial</u> and <u>Equilibrium</u> volumes<br />
*''Manage Dredging Events'' - If this option is enabled (checked), a table consisting of numerous rows with a few columns appears. <br />
**'''Begin Date'''<br />
**'''End Date'''<br />
** '''Shoal to be Mined'''<br />
**'''Volume''' (to be mined).<br />
'''Note:''' It is important to note that bypassing for each inlet defaults to the one cell immediately adjacent to either side of the inlet. However, the size and location may be defined by creating an <u>Attachment Bar</u> on one or both sides of the inlet. <br />
<br />
==Attachment Bar==<br />
The attachment bar option defines where bypassing to the left or right from an inlet will be bypassed to.<br />
<br />
*The Attachment Bar option for this dialog has no parameters associated with it.<br />
<br />
=Events=<br />
==Bypass Event==<br />
[[File:Structure_Bypass.png|alt=GenCade Structures dialog showing the Bypass Event option|thumb|400x400px|''GenCade Structures'' dialog showing the ''Bypass Event'' option]]<br />
Bypass events act as a source and sink to the GenCade simulation. This event is treated differently than the bypassing that is associated with an Inlet. This type represents a physical bypass plant or operation where material is removed from one section of the grid and then placed onto another section of the grid. <br />
<br />
For this type in the dialog, a table of columns appears once the "Manage Bypass Events" option is selected. The available column values are:<br />
<br />
*'''Begin Date'''<br />
*'''End Date'''<br />
*'''Bypass Rate''' (yd<sup>3</sup>/hr or m<sup>3</sup>/hr)<br />
<br />
'''Note:''' A ''positive'' value for the bypass rate will be interpreted as a <u>source</u> of sand and a ''negative'' value as a <u>sink</u>. <br />
<br />
==Beach Fill Event==<br />
[[File:Structure_Beachfill.png|alt=GenCade Structures dialog showing the Beach Fill event option|thumb|400x400px|''GenCade Structures'' dialog showing the ''Beach Fill event'' option]]<br />
Beach fills may be created either seaward or landward of the shoreline. If there are many beach fills in one location during the simulation, draw the beach fills carefully so that the arcs do not connect or intersect.<br />
<br />
For this type in the dialog, a table of columns appears once the "Manage Beach Fill Events" option is selected. The available column values are:<br />
*'''Begin Date'''<br />
*'''End Date'''<br />
*'''Added Berm Width''' (ft or m)<br />
<br />
=Other=<br />
These types will have more information added soon.<br />
<br />
==SBAS Polygon==<br />
<br />
==SBAS Flux==<br />
<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:GenCade 2.0 Dialogs|S]]<br />
[[Category:GenCade|S]]</div>Rdchlmebhttps://cirpwiki.info/wiki/GenCade_Model_Control_DialogGenCade Model Control Dialog2024-03-26T18:54:57Z<p>Rdchlmeb: /* Water Level Tab *NEW* */</p>
<hr />
<div>{{DISPLAYTITLE:GenCade 2.0 Model Control Dialog}}<br />
{{TOC right}}<br />
The ''Gencade Model Control'' dialog is used to set beach conditions, lateral boundary conditions and general simulation options. This document highlights the more commonly used options. Refer to the [[GenCade|GenCade web site]] for a more detailed description of how these parameters affect the model results. <br />
<br />
*This dialog has been updated for use with SMS 13.3 and the new GenCade interface. New items added are shown in <span style="color:red">red</span>. <br />
*Note: At the bottom of each tab is a note shown in <span style="color:red">red</span> that tells the user whether they are using Imperial (feet and yards) or Metric values for most fields. This determination is made based on the SMS Display Projection. <br />
<br />
==Model Setup Tab==<br />
[[File:ModelControl Setup.png|alt=GenCade Model Control dialog showing the Model Setup tab|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Model Setup'' tab]]<br />
The following parameters are specified in the ''model setup'' tab: <br />
*''Simulation''<br />
**''Title'' &ndash; Title of simulation run.<br />
**''Full print output'' &ndash; Path and name of printed output file.<br />
*''Computational Time''<br />
**''Start Date'' &ndash; Simulation start date.<br />
**''End Date'' &ndash; Simulation end date.<br />
**''Time Step'' &ndash; Model time step in hours.<br />
**''Recording Time Step'' &ndash; Recorded model time step in hours.<br />
*''Print Dates'' &ndash; Dates to save simulated shoreline. Use the '''Add''' button to create dates and the '''Remove''' button to delete any unwanted dates.<br />
*''Grid Information'' &ndash; static information about the GenCade grid including number of cells, grid angle, and length of 1d Grid.<br />
<br clear="all"><br />
==Beach Setup Tab ==<br />
[[File:ModelControl Beach.png|alt=GenCade Model Control dialog showing the Beach Setup tab|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Beach Setup'' tab]]<br />
The following parameters are specified in the ''beach setup'' tab: <br />
*''Sand and Beach Data ''<br />
**''Effective Grain Size'' &ndash; Medium sediment grain size in millimeters.<br />
**''Average Berm Height'' &ndash; In feet or meters.<br />
** ''Closure Depth'' &ndash; In feet or meters.<br />
**''<span style="color:red">Regional Sea Level Change</span>'' in mm/year.<br />
**''<span style="color:red">Regional Subsidence</span>'' in mm/year.<br />
**''<span style="color:red">Beach Slope</span>''.<br />
*''Longshore Sand Transport Calibration Coefficients '' <br />
**''K1'' &ndash; Range should be 0.1 < K1 <1<br />
**''K2'' &ndash; Range should be 0.5(K1) < K2 < 1.5(K1)<br />
**''<span style="color:red">KTIDE</span>'' &ndash; longshore transport coefficient for tide current.<br />
<br clear="all"><br />
==Seaward BC Tab ==<br />
[[File:ModelControl Seaward.png|alt=GenCade Model Control dialog showing the Seaward BC tab|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Seaward BC'' tab]]<br />
The following parameters are specified in the ''seaward boundary condition'' tab: <br />
* ''Input Wave Adjustments'' &ndash; This section contains the following options: <br />
**''Height Amplification Factor''<br />
**''Angle Amplification Factor ''<br />
**''Angle Offset ''<br />
*''Wave Components to Apply'' &ndash; option is always "Primary (1)".<br />
*''Number of Cells in Offshore contour Smoothing Window'' &ndash; Default value is 11, but it is suggested that this be and '''odd''' number in the range between 11 and 101. ''If an even number is entered, GenCade will change to the next smaller odd value.''<br />
<br clear="all"><br />
==Lateral BC Tab ==<br />
[[File:ModelControl Lateral.png|alt=GenCade Model Control dialog showing the Lateral BC tab|thumb|''GenCade Model Control'' dialog showing the ''Lateral BC'' tab]]<br />
The following parameters are specified in the ''lateral boundary condition'' tab for the left and right lateral boundary condition: <br />
*''Type'' &ndash; Determines one of three boundary types: <br />
**"Pinned" &ndash; Boundary will not move from the initial shoreline position.<br />
**"Gated" &ndash; Bounded with a groin. Requires that a groin exist and must be located in cell 1.<br />
***''Length of Groin from Shoreline to Seaward Tip''<br />
**"Moving" &ndash; Represents the amount of shoreline change at a boundary over a specified period of time.<br />
***''Shoreline Displacement Velocity'' &ndash; Shoreline can be displaced over one of the following options:<br />
****"Simulation Period"<br />
****"Day"<br />
****"Time Step"<br />
<br clear="all"><br />
==Adaptive Time Steps Tab==<br />
[[File:ModelControl Adaptive.png|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Adaptive Time Steps'' tab]]<br />
The following parameters are specified in the adaptive time steps tab:<br />
*''Enable adaptive time steps'' &ndash; If turned on, allows the option to use the default values or set custom values.<br />
*Once enabled, the following 5 values will have defaults. They can be changed based on user preference. <br />
**''Threshold minimum''<br />
**''Threshold maximum''<br />
**''Number of days stable''<br />
**''Stability minimum''<br />
**''Stability maximum''<br />
<br clear="all"><br />
==<span style="color:red">Cross Shore Tab</span> ''*NEW*''==<br />
[[File:ModelControl XShore.png|alt=GenCade Model Control dialog showing the Cross Shore tab|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Cross Shore'' tab]]<br />
The following parameters are specified in the cross shore tab:<br />
*''Enable cross-shore transport'' &ndash; If turned on, enables GenCade to include cross shore transport in sediment transport calculations.<br />
*''Cross-shore scaling parameter''<br />
*''Onshore transport rate (mm/yr)''<br />
*''Enable variable berm height with SLC''<br />
*''Enable varying slope with shoreline position'' <br />
<br />
<br />
<br />
<br />
==<span style="color:red">Monte Carlo Tab</span> ''*NEW*''==<br />
[[File:ModelControl MCarlo.png|alt=GenCade Model Control dialog showing the Monte Carlo tab|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Monte Carlo'' tab]]<br />
The following parameters are specified in the Monte Carlo tab:<br />
*''Enable Monte Carlo transport'' &ndash; If turned on, enables run multiple GenCade simulations dependent on several criteria.<br />
*''Probability Function''<br />
**''Rayleigh Distribution''<br />
**''Rayleigh + Weibull Distribution''<br />
**''User Defined (still under development)''<br />
*''Number of MC simulations''<br />
*''Mean Wave Angle (deg)''<br />
*''Angle Standard Deviation''<br />
*''Maximum Absolute Wave Angle (deg)''<br />
*''Enable Beach Fill''<br />
**''Beach Fill Std. Dev. percentage''<br />
*''Wave Height Threshold (m)''<br />
*''Min Wave Height''<br />
*''Max Wave Height''<br />
*''Mean Wave Height''<br />
*''Wave Interval''<br />
*If "Rayleigh + Weibull Distribution" selected, the following additional parameters are required:<br />
**''Weibull A Parameter''<br />
**''Weibull B Parameter''<br />
**''Weibull K Parameter''<br />
==<span style="color:red">Water Level Tab</span> ''*NEW*''==<br />
[[File:ModelControl WLevel.png|alt=GenCade Model Control dialog showing the Water Level tab|thumb|400x400px|''GenCade Model Control'' dialog showing the ''Water Level'' tab]]<br />
<br />
The following parameters are specified in the Water Level tab:<br />
<br />
* ''Enable Water Level Forcing'' &ndash; If turned on, enables the user to enter times and values into a table which will be used to provide additional forcing for the GenCade simulation.<br />
* Water Level Table &ndash; Use the '''Add''' button to create dates and the '''Remove''' button to delete any unwanted dates.<br />
** ''Date/Time''<br />
** ''Water Level'' (ft or m)<br />
<br />
[[Category:GenCade 2.0 Dialogs|M]]<br />
[[Category:GenCade|M]]</div>Rdchlmebhttps://cirpwiki.info/wiki/NewGenCade_Users_GuideNewGenCade Users Guide2024-03-20T15:07:05Z<p>Rdchlmeb: </p>
<hr />
<div>{{DISPLAYTITLE:New GenCade Users Guide}}<br />
{{TOC right}}<br />
=Getting Started =<br />
This GenCade guide was last updated in November 2012. Most of the screenshots used in this guide were created with the August 19, 2011, build of the SMS. Developers are constantly upgrading the SMS and GenCade executables, so the graphics in a future version may look slightly different than the visuals included in this user guide.<br />
<br />
A very simple example can be found [[GenCade_Example|here]]. This example shows all steps necessary to produce results and includes a zip file with all of the input and output files that can be used to reproduce the results on another computer.<br />
<br />
==Setup GenCade in the SMS ==<br />
GenCade is run within the SMS 11.1 Development. SMS 11.0 and earlier versions do not have interfaces for GenCade. This section will guide a user through the process to set up the conceptual model, convert to a 1D grid, review the GenCade model, run GenCade, visualize results, and develop alternatives. It is assumed that the reader has no previous experience with GenCade. <br />
<br />
First, the GenCade executable must be identified on the machine. The GenCade executable is GenCade_v1r3.exe. If SMS 11.1 Beta is installed on the machine, the GenCade executable will be located in the models folder.<br />
<br />
Once SMS 11.1 is open on the machine, it is necessary to specify the location of the GenCade executable. If this is specified incorrectly or not at all, GenCade will not run. In order to indicate the location of the executable, it is necessary to click on ''Edit'', go to ''Preferences'', and click on the tab labeled ''File Locations''. The user should scroll down to ''GenCade'' under ''Model Executables'' and click on ''BROWSE''. Once the GenCade executable is selected, the path for the executable should be listed under ''Model Executables'' next to ''GenCade''. Figure 1 shows the ''File Locations'' window.<br />
<br />
[[Image:fig1_def_Gen.jpg|400px|thumb|left|Figure 1. Define GenCade model executable]]<br />
<br style="clear:both" /><br />
<br />
==Set the Current Projection ==<br />
GenCade uses a real world coordinate system, so it is necessary to set up the current projection upon opening the SMS. GenCade projects may be set up in either U.S. customary units or SI units. The user may select the appropriate projection by clicking ''Edit->Projection''. The steps to set up the projection are shown in Figure 2. This ensures all shorelines, structures, wave gauges, and other important features are mapped correctly. The user may also open aerial photographs to aid in completing the conceptual model. In many cases, the files representing shorelines and other features may be georeferenced correctly without defining the current projection; however, it is a good idea to define the projection before starting a GenCade project. <br />
<br />
[[Image:fig2_spec_proj.jpg|400px|thumb|left|Figure 2. Specify projection]]<br />
<br style="clear:both" /><br />
<br />
==Changing the Projection ==<br />
In some cases, an aerial photograph may be defined in a different coordinate system than the shorelines. There are two ways to change the projection of the project. For a case where the user would like to convert the shoreline and the project to the same projection as the imported aerial photo, there are several steps to follow. First, go to ''Edit->Project'', specify the projection used for the shoreline, and bring in the shoreline (more information on the format of shorelines is in 2.1). Right click on the coverage including the shoreline under ''Map Data'' in the left panel and go to ''Reproject''. A warning will pop up notifying the user that the command is non-reversible. After clicking ''Yes'', the ''Reproject Object'' window will open. Check ''Set'' and change the new projection to the projection of the aerial photo (Figure 3). Go back to ''Edit->Project'' and change the projection to match the projection of the aerial photo (Figure 4). All of the units will match the projection of the aerial photo. Now the aerial photo can be opened in the SMS, and the shoreline will overlay the aerial photograph correctly (Figure 5).<br />
<br />
[[Image:reproject_coverage.jpg|400px|thumb|left|Figure 3. Reprojection map projection]]<br />
<br style="clear:both" /><br />
<br />
[[Image:change_projection.jpg|400px|thumb|left|Figure 4. Change projection]]<br />
<br style="clear:both" /><br />
<br />
[[Image:current_projection_aerial.jpg|400px|thumb|left|Figure 5. Confirmation of change in projection]]<br />
<br style="clear:both" /><br />
<br />
It is much simpler to use the units from the shoreline shapefile or text file for the project. In this case, the aerial photograph will need to be reprojected. First, go to ''Edit->Project'' and define the projection. Then open the shoreline, right click on the coverage, and go to ''Projection (floating)'' (Figure 6). It should be confirmed that the object projection matches the projection defined under ''Edit->Project''. When the aerial photo is opened, SMS will automatically convert the aerial photo to the correct projection so that the photo matches the shorelines (Figure 7).<br />
<br />
[[Image:object_projection_coverage.jpg|400px|thumb|left|Figure 6. Reproject object projection]]<br />
<br style="clear:both" /><br />
<br />
[[Image:current_projection_shore.jpg|400px|thumb|left|Figure 7. Reproject current projection]]<br />
<br style="clear:both" /><br />
<br />
=Preparing Input Files =<br />
==Open and Define Initial Shoreline ==<br />
As mentioned previously, an initial shoreline is required to run GenCade. The model type must be defined as ''GenCade'' before opening any file in the SMS. This can be accomplished by selecting ''Type->Models->GenCade'' after right clicking on the default coverage under ''Map Data'' in the data tree (panel on left side of screen). If the user has a file with a list of shoreline points that is in the same projection as the project, the file may be opened in the SMS. Before the file is opened in the SMS, it is important to double check the projection of coverage under ''Map Data''. This can be done by right clicking on the coverage and clicking on Projection. If it is necessary to convert to a new projection for the shoreline, right click on the coverage and go to ''Reproject''. A warning will pop up explaining that this is a non-reversible command; select ''Yes''. Then a new window will open allowing the user to define the ''Current projection'' and the ''New projection''. To read the file into the conceptual model correctly, the file must be in *.cst format. The *.cst format requires the x and y coordinates of every point along the shoreline. An example of the format is shown in Figure 8. In order to modify a file with x and y coordinates for a shoreline, add the first three lines shown in Figure 8 which have been carried over from the old GENESIS format. The first number on the third line represents the total number of shoreline points listed in the file. This is the only number in the first three lines that will differ from the file shown in Figure 8.<br />
<br />
[[Image:fig4_cst.jpg|400px|thumb|left|Figure 8. Example format of *.cst file]]<br />
<br style="clear:both" /><br />
<br />
There are many different ways to create an initial shoreline for GenCade in the SMS. If the shoreline is represented by points in a shapefile, these can be converted into a scatter set and saved as a text file. Then the text file can be modified to create the proper *.cst format and opened in the SMS. <br />
<br />
A GenCade initial shoreline can also be created from a polyline shapefile. Once the shapefile is opened in the SMS, it is necessary to click on ''Mapping'' and select ''Shapes->Feature Objects'' (Figure 9). This will create a ''Feature Arc''. After converting the ''Map Data'' to ''GenCade'', the arc may be selected by clicking on the ''Select Feature Arc'' button and by double-clicking. If the shapefile was converted into multiple arcs, it is necessary to connect these segments to create one arc (Figure 10). Click on the ''Create Feature Arc'' button and draw an arc connecting the existing arcs. Click on the ''Select Feature Point'' button and select all of the nodes between the existing and the new arcs. To convert the nodes to vertices, go to ''Feature Objects'' and select ''Vertices<->Nodes''. Once all of the nodes have been converted to vertices, the shoreline is in the proper format for GenCade. When developing a shoreline in GenCade from a polyline shapefile, it is not necessary to create a *.cst file. <br />
<br />
[[Image:fig5_convert.jpg|400px|thumb|left|Figure 9. Convert shapefile to feature objects]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig6_connect.jpg|400px|thumb|left|Figure 10. Connect segments to create one feature arc]]<br />
<br style="clear:both" /><br />
<br />
Regardless of whether or not the initial shoreline is opened as a *.cst file, the initial shoreline must be defined. To define the initial shoreline, ''GenCade'' must be selected as the model type for the coverage. The feature arc representing the shoreline should be double-clicked (or right-click and select Attributes) after clicking on the ''Select Feature'' Arc button. The ''GenCade Arc Attributes'' window will open. The ''Initial Shoreline'' option should be selected under ''Arc Options''. These steps are shown in Figure 11.<br />
<br />
[[Image:fig7_shoreline.jpg|400px|thumb|left|Figure 11. Define arc as initial shoreline]]<br />
<br style="clear:both" /><br />
<br />
==Open and Define Regional Contour or Additional Shorelines ==<br />
In some cases, a regional contour or additional shorelines may need to be added to the conceptual model. In order to define a second feature arc, it is necessary to right-click on ''Map Data'' and select a ''New Coverage''. This new coverage must also be defined as ''GenCade''. The user can rename the new coverage, so that it can easily be identified. It is very important to open the new arc in a new coverage. If the arc is opened in the same coverage as the initial shoreline, the two arcs will most likely overlap, and the arcs will be split into many arcs. Once the regional contour is opened in the interface, define the arc as ''Regional Contour'' in the ''GenCade Arc Attributes'' window (Figure 12). A shoreline representing the final shoreline or an additional shoreline may be defined as a ''Reference Line''. <br />
<br />
[[Image:fig8_rc.jpg|400px|thumb|left|Figure 12. Define arc as regional contour]]<br />
<br style="clear:both" /><br />
<br />
==Merge Coverages ==<br />
After the initial shoreline and regional contour have been loaded and defined in the SMS interface, it is necessary to merge the two lines in a single coverage. All structures, inlets, wave gages, and other features will be created in this single coverage. Highlight both the default coverage (initial shoreline) and the new coverage (regional contour). This can be done by hitting ctrl on the keyboard and clicking on both coverages. After right-clicking, select ''Merge Coverages''. A window will open asking if the user would like to delete the coverages used to make the merged coverage. If no is selected, the initial shoreline and regional contour coverages will remain in the interface. It is a good idea to keep these coverages in the interface. If a problem occurs with the merged coverage, the initial shoreline and regional contour may be merged again. Figure 13 shows how coverages are merged while Figure 14 illustrates the initial shoreline and regional contour in the merged coverage.<br />
<br />
[[Image:fig9_merge.jpg|400px|thumb|left|Figure 13. Merge initial shoreline and regional contour in a single coverage]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig10_merge.jpg|400px|thumb|left|Figure 14. Arcs for initial shoreline and regional contour defined after merging into a single coverage]]<br />
<br style="clear:both" /><br />
<br />
=Development of a Conceptual Model =<br />
==Create Inlets, Shoals, Dredging Events, and Jetties ==<br />
The inlet name, inlet shoal volumes, dredging events, and bypassing coefficients may be defined when an inlet is created. To do this, select the ''Create Feature Arc'' button and draw a line from one side of the inlet to the other. When creating inlets and other features, a high quality aerial photo is very helpful. After the inlet is created, click on the ''Select Feature Arc'' button and double-click on the arc representing the inlet. This can also be accomplished by a single click, followed by a right click. The ''GenCade Arc Attributes'' window will open. Select ''Inlet'' and click on ''Attributes''. The ''Inlet Reservoir Model'' window will open. The inlet can be named, shoal volumes can be defined, and dredging events can be added. The initial and equilibrium shoal volumes for the ebb, flood, left bypass, left attachment, right bypass, and right attachment can be defined after clicking on the ''Volume'' button. Similarly, after clicking on ''Dredging'', the ''Dredging Events'' window will open and the user can specify the beginning and ending date, the volume, and the shoal to be mined for each dredging event. The user also has the option to modify the left and right bypassing coefficients when jetties are present. Both the left and right bypassing coefficients have a default value of 1. This value will always be zero or larger. However, due to the measured distances included in the bypassing coefficient equation, it is highly unlikely that the bypassing coefficient will be larger than 100. Inlets that do not have jetties will not have a bypassing coefficient. After the inlet information is specified, the arc representing the inlet will turn blue. All of the steps create an inlet and add shoal volumes and dredging events are shown in Figure 15.<br />
<br />
[[Image:fig11_inlets.jpg|400px|thumb|left|Figure 15. Create and define an inlet, shoal volumes, and dredging events]]<br />
<br style="clear:both" /><br />
<br />
A jetty can be created at the inlet after selecting the ''Create Feature Arc'' button. The arc representing the jetty should not intersect with the arc representing the inlet, regional contour, or initial shoreline. If this occurs, either the arc representing the jetty or the regional contour or initial shoreline will be split into two separate arcs. To remedy the problem of splitting arcs; the user should delete the arc representing the jetty, convert the newly created node to a vertex, and redefine the formerly split arc. After drawing the jetty, the user should click on the ''Select Feature Arc'' and double-click on the line representing the jetty. When the ''GenCade Arc Attributes'' window opens, the ''Left Jetty on Inlet'' or ''Right Jetty on Inlet'' should be selected. The left jetty is to the left of a person standing on land looking at the ocean. After ''Attributes'' is selected, a new window will open where the ''Permeability'' can be specified, ''Diffracting'' can be checked or unchecked, and a seaward depth can be added. The default value for ''Permeability'' is 0. Although ''Diffracting'' is unchecked as a default option, the user should check this box in most cases. The line representing a jetty will also turn blue once all of required jetty information is provided. Figure 16 shows how to create a jetty.<br />
<br />
[[Image:fig12_jetty.jpg|400px|thumb|left|Figure 16. Create and define a jetty]]<br />
<br style="clear:both" /><br />
<br />
Once the grid is converted to GenCade, the bypassing associated with an inlet is defaulted to the one cell immediately adjacent to either side of the inlet. However, the size and location may be defined in the conceptual model by selecting the ''Create Feature Arc'' button and drawing the arc. Double-click on the arc after creating to open the ''GenCade Arc Attributes'' window. The arc should be defined as an ''Attachment Bar'' (Figure 17). The attachment bar is also represented by a blue line.<br />
<br />
[[Image:fig13_attach.jpg|400px|thumb|left|Figure 17. Create and define an attachment bar]]<br />
<br style="clear:both" /><br />
<br />
==Seawalls ==<br />
To draw a seawall, first the ''Create Feature Arc'' button should be selected. The seawall must be drawn landward of the shoreline. If the user attempts to draw the seawall directly on top of the initial shoreline, an error will occur. The seawall drawn by the user should resemble the shape of the real seawall as closely as possible. If the user is not meticulous in drawing the seawall, the shape of the seawall in the GenCade model may not resemble the actual seawall. Additionally, since cell numbers are used in the GenCade model, the seawall shape may look different after converting from the conceptual model. After the seawall is drawn, the user should click on the Select Feature Arc button and click on the seawall. The ''GenCade Arc Attributes'' window will open. ''Seawall'' should be selected in ''Arc Options''. The seawall will turn blue. When the model is converted to a 1D grid, an error message referring to the seawall may pop up. This message should be ignored; GenCade will modify the cells defined for the seawall. The user should review the seawall in the GenCade model. If the seawall does not resemble the actual seawall, the cell numbers and distances from the grid should be revised. A smaller cell size near the seawall may also be helpful. The process to create a seawall is shown in Figure 18.<br />
<br />
[[Image:fig14_seawall.jpg|400px|thumb|left|Figure 18. Create and define a seawall]]<br />
<br style="clear:both" /><br />
<br />
==Beach Fills ==<br />
Beach fills can be created in the same way as inlets and seawalls. One should select the ''Create Feature Arc'' button to draw the beach fill. Beach fills should be drawn slightly offshore. If there are many beach fills in one location during the simulation, draw the beach fills carefully so they do not connect or intersect. After each beach fill is drawn, click on the ''Select Feature Arc'' and double-click on the line representing the beach fill. Select the ''Beach Fill Event'' after the ''GenCade Arc Attributes'' window opens. For each beach fill, add the ''Begin Date'' and ''End Date'' and the ''Added Berm Width''. After selecting ''OK'' in the ''GenCade Arc Attributes'' window, the line representing the beach fill will turn green. Figure 19 demonstrates the steps to create and define beach fill events.<br />
<br />
[[Image:fig15_beach_fill.jpg|400px|thumb|left|Figure 19. Create and define a beach fill]]<br />
<br style="clear:both" /><br />
<br />
==Bypass Event ==<br />
<br />
Another option in GenCade is a bypass event. The user should select the ‘’Create Feature Arc’’ button and draw the bypass event in the desired location. After the event is created, the user should click on the ‘’Select Feature Arc’’ button and double-click on the arc representing the bypass event. Once ‘’Bypass Event’’ is selected in the ‘’GenCade Arc Attributes’’ window, the ‘’Bypassing’’ window will open. A ‘’Begin Date’’, ‘’End Date’’, and ‘’Bypass Rate’’ can be specified. If the project projection is in USCS, the bypass rate is cubic yards per hour. Likewise, the bypass rate is cubic meters per hour when SI units are used. Figure 20 demonstrates the steps to create and define bypass events.<br />
<br />
[[Image:bypass_event.jpg|400px|thumb|left|Figure 20. Create and define a bypass event]]<br />
<br style="clear:both" /><br />
<br />
==Detached Breakwaters ==<br />
A detached breakwater is created by selecting the ''Create Feature Arc'' button and drawing the arc representing the detached breakwater. The user should click on the ''Select Feature Arc'' button and double-click on the detached breakwater. The ''GenCade Arc Attributes'' window will open. Scroll down to ''Breakwater'' and click on ''Attributes''. The depth at each end of the detached breakwater can be entered in the ''Detached Breakwater'' window. There is a pull-down window for wave transmission which includes constant transmission and three equations for time-dependent wave transmission: Ahrens, Seabrook and Hall, and d'Angremond.<br />
<br />
===Constant Transmission ===<br />
Under the ''Transmission'' bar, select ''Constant''. The last column in the detached breakwaters window is ''Coeff/Perm/Atts''. For constant transmission, this represents the permeability of the detached breakwater. Once all necessary information is entered, click ''OK''. The detached breakwater will turn orange. A detached breakwater with constant transmission is shown in Figure 21.<br />
<br />
[[Image:fig16_breakwater.jpg|400px|thumb|left|Figure 21. Create and define a breakwater with constant transmission]]<br />
<br style="clear:both" /><br />
<br />
===Time-dependent Wave Transmission ===<br />
'''Ahrens''' - After selecting Ahrens under ''Transmission'' in the ''Detached Breakwater'' window, the final column (''Coeff/Perm/Atts'') can be selected. Clicking this box will open the ‘’Breakwater Attributes’’ window. For Ahrens, the required values include freeboard to MSL, width, seaward side slope, shoreward side slope, and the D50 of the armor stone (Figure 22). Click ''OK'', and the detached breakwater should turn orange.<br />
<br />
'''d'Angremond''' - Another equation that can be used for time-dependent wave transmission is d'Angremond. Similarly to the option for ''Ahrens'', click on the final column of the ''Detached Breakwaters'' window which should now say ''Atts''. For d'Angremond, the freeboard to MSL, width, seaward side slope, shoreward side slope, and permeability are required (Figure 23).<br />
<br />
'''Seabrook and Hall''' - Seabrook and Hall can also be used for time-dependent wave transmission. After selecting Seabrook and Hall in the ''Detached Breakwaters'' window, click on ''Atts'' in the final column. The ''Breakwater Attributes'' window will open, and the freeboard to MSL, width, seaward side slope, shoreward side slope, and D50 of the armor stone can be entered (Figure 24). <br />
<br />
[[Image:fig17_ahrens.jpg|400px|thumb|left|Figure 22. Define breakwater using Ahren’s method for transmission]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig18_dangremond.jpg|400px|thumb|left|Figure 23. Define breakwater using d’Angremond method for transmission]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig19_seabrook_hall.jpg|400px|thumb|left|Figure 24. Define breakwater using Seabrook and Hall method for transmission]]<br />
<br style="clear:both" /><br />
<br />
==Groins ==<br />
Once the location for a groin is chosen, select the ''Create Feature Arc'' button. In many cases, the arc representing the groin will cross the regional contour and initial shoreline. Do not draw either end of the groin near the regional contour or initial shoreline. When this occurs, the node from the groin will connect to the initial shoreline or regional contour. This will divide the regional contour or initial shoreline into two separate arcs, where only one of the arcs will still be defined as the regional contour or initial shoreline. To remedy this, delete the arc that was created to represent the groin. Highlight the node that divides the initial shoreline into two segments. Under Feature ''Objects'', select ''Vertices<->Nodes''. The node will become a vertex, and the initial shoreline will once again be a single arc. After drawing the feature arc for the groin, click on the ''Select Feature Arc'' button. The ''GenCade Arc Attributes'' window will open. Select ''Groin'' in the ''Arc Options'' menu and click on ''Attributes''. The window for groins is very similar to the window for jetties. The window for groins includes the ''Permeability'' and ''Seaward Depth'' (in the user specified units). The user may also define the groin as ''Diffracting'' or ''Non-diffracting''. When the ''Diffracting'' option is checked, a ''Seaward Depth'' must be specified. Figure 25 illustrates the various windows associated with creating a groin.<br />
<br />
[[Image:fig20_groin.jpg|400px|thumb|left|Figure 25. Define and create a groin]]<br />
<br style="clear:both" /><br />
<br />
==T-Groins ==<br />
While a T-groin is not an option in the ''GenCade Attributes'' window, a detached breakwater and a groin can be combined to form a T-groin. If a T-groin is required, the user should first create a detached breakwater and fill in all of the information necessary for a detached breakwater in the ''GenCade Arc Attributes'' window. Then the user should create a groin that attaches to the detached breakwater. Once the conceptual model is converted to a 1D grid, it is necessary to double-check the T-groin to ensure that the shape has been retained. It is possible that the groin or detached breakwater has moved to an adjacent cell number and no longer retains the shape the user defined. The user may modify the cells for the detached breakwater or groin in the GenCade model under ''Edit Breakwaters'' or ''Edit Groins'' in the ''GenCade'' menu. If the shape of the T-groin is significantly altered, the user may want to consider decreasing the cell size for the entire grid or utilizing variable grid resolution. An example of a T-groin is shown in Figure 26. <br />
<br />
[[Image:fig21_tgroin.jpg|400px|thumb|left|Figure 26. Create a T-groin]]<br />
<br style="clear:both" /><br />
<br />
=1D Grid Setup=<br />
==Orientation, Cell Size, and Variable Grid Resolution ==<br />
After defining the shorelines and any necessary structures, the grid should be set up. To manually draw the grid frame, click on the ''Create 1-D Grid Frame''. The GenCade grid frame is purple and has an arrow at one end. If a person followed the grid from the end to the arrow, the water should always be to the left and the land should always be to the right. For example, if the GenCade grid was oriented from north to south, the water would be to the east (left) and the land would be to the west (right). The grid can be modified by clicking the ''Select 1-D Grid Frame'' and double-clicking on the square in the center of the purple grid line. Alternately, the grid options can be changed by selecting the grid frame and right-clicking Properties. The ‘’Grid Frame Properties’’ window will open, and the ''Origin X'', ''Origin Y'', ''Angle'', and ''I size'' can be modified. The ''I size'' is the length of the grid. ''Angle'' refers to the sign convention in the conceptual model which is degrees counterclockwise from the x axis. This is different from the GenCade model convention (degrees clockwise from north). Therefore, once the map is converted to a 1D grid, the ''Azimuth'' for the grid will be a different value. The cell size can be constant or variable. If the user chooses to change the cell size under ''Define cell sizes'', the number of cells will change accordingly. The grid frame set up is shown in Figure 27.<br />
<br />
[[Image:fig22_grid_frame.jpg|400px|thumb|left|Figure 27. Create and define the grid frame]]<br />
<br style="clear:both" /><br />
<br />
A constant grid resolution is reasonable for most projects. However, there are some large scale projects that would benefit from variable grid resolution. Variable grid resolution can give more detail at specific locations of interest while having coarser resolution in other areas of the grid. By utilizing variable grid resolution, the simulation will run much more quickly than a grid with a constant, finer resolution. When the map is converted to a 1D grid, one of the options under ''I Cell Options'' is ''Use refine points''. This option refers to variable grid resolution.<br />
<br />
First, it is necessary to determine which part of the grid needs a finer resolution. There are two ways to set up finer grid resolution. The user can decide to use one point or two points. For both of these options, click the ''Create Feature Point'' button. If only one feature point is created, put the point at the location of interest. Click on the ''Select Feature Point'' button and double-click on the point. The ''Refine Point'' window will open (Figure 28). Check the ''Refine grid in I direction'' and specify a base cell size. The base cell size is the size of the cells nearest to the refine point. This will be the smallest cell size in this location of the grid. Once the refine point is specified, right click on the coverage under ''Map Data'' and convert ''Map->1D Grid''. The ''Map->1D Grid'' window will open (Figure 29). Under I Cell Options, click the button to specify the ''Use refine points'' option. Type the maximum cell size and the maximum bias. The maximum cell size represents the largest cell size in the grid. Moving out from the one refine point, the cells will grow in size until a cell reaches the maximum cell size. The remaining cells in the grid will also be the maximum cell size. The maximum bias represents the amount each adjacent cell grows. For example, the default value is 1.10. This means each cell will grow 10%, so in a case with a base cell size of 10, the adjacent cells will have a size of 11. The cells will continue growing at this rate until a cell reaches the maximum cell size. In a case with only one refine point, do not select the ''Use inner growth'' option. <br />
<br />
[[Image:fig23_variable.jpg|400px|thumb|left|Figure 28. Refine the grid for variable resolution]]<br />
<br style="clear:both" /><br />
<br />
[[Image:use_refine_points.bmp|400px|thumb|left|Figure 29. Use refine points]]<br />
<br style="clear:both" /><br />
<br />
It is also possible to have a finer, constant resolution for a certain section within the grid. A groin field is a good example where a finer, constant resolution could be beneficial. For this case, select the ''Create Feature Point'' button and create points on either side of the desired finer resolution area. Click on the ''Select Feature Point'' button, double-click on each point, check the ''refine grid in I direction'' option, and choose a base cell size (make this number the same for both refine points). Once again, convert to 1D grid and select the use refine points options. Follow the same procedure as the case with only one refine point for the maximum cell size and maximum bias. If the ‘’Use inner growth’’ option is left unchecked, the cells between each refine point will be constant (at the same cell size as specified for each refine point). The cells outside of the two refine points will continue to grow up to the specified maximum bias number. If the ''Use inner growth'' option is selected, the cells will also grow between the two refine points. If the two refine points are close together, the cell size most likely will not reach the maximum cell size, but the cells between the two refine points will be larger than the base cell size.<br />
<br />
Once the ''Use refine points'' option is chosen in the ''Map->1D Grid'' window, the resulting GenCade grid will have variable resolution. After saving the project, the *.shdx file is also created. This file lists the size of each cell in the grid. This file is needed to make shoreline change or transport plots outside of SMS in cases where variable grid resolution is utilized.<br />
<br />
==Convert to 1-D Grid ==<br />
Once all of the shorelines, inlets, structures, and refine points have been added to the conceptual model, select the merged coverage, right click on the name, click on ''Convert'', and select ''Map->1D Grid'' (Figure 30). A window will open showing the origin and orientation of the GenCade grid and the different cell options. This is the same window that was opened when the grid frame was created. Once the map has been converted to a 1D grid, the data tree in the SMS will show ''GenCade Data'' and ''GenCade Grid''. If the user highlights ''GenCade Data'', the GenCade menu at the top of the interface will appear. The newly developed GenCade grid can be seen in the viewing window.<br />
<br />
[[Image:fig25_constant_cell.jpg|400px|thumb|left|Figure 30. Convert to GenCade grid with constant cell size]]<br />
<br style="clear:both" /><br />
<br />
==Wave Data ==<br />
In general, wave gauges should be defined after converting from the conceptual model to the GenCade model. After the GenCade grid has been created, highlight the coverage under ''Map Data'' to return to the conceptual model. Wave gauge data may be entered in GenCade in four conventions: shore normal, meteorological, oceanographic, and cartesian. Regardless of the convention, wave directions will be converted to shore normal convention in the *.wave files. If the waves are in meteorological or oceanographic convention, the user may define the wave gauges before converting from the conceptual model to the GenCade model. However, the shore normal option will be unavailable since the grid has not been created yet. This is the reason it is recommended that the user define the wave gauge after converting from the conceptual model to the GenCade model.<br />
<br />
There are two ways to represent wave gauges in the conceptual model. In both cases, the user needs to create and select the feature point. If the coordinates of the wave gauges are in the same coordinate system as the conceptual model, it is very easy to create a point at the location of each gauge. Drag the file with the coordinates representing the wave gauges into the SMS interface. The ''Open File Format'' window will open. Select ''Use Import Wizard'' and click ''OK''. Follow the directions for the ''File Import Wizard'' and select ''OK''. The wave gauges will be represented as scatter data. Simply select the ''Create Feature Point'' button in the conceptual model and draw a feature point directly on top of each point. Now the wave gauge locations are represented in the conceptual model. Instead of defining the feature point as a refine point, check ''Wave Gage''. The ''Options'' button will open a window where the water depth may be defined. Click on ''Data'' to open the ''Wave Events'' window (Figure 31). This window will allow the user to copy and paste data or import the wave information from a text file. Regardless of the format of the wave information, the user first needs to define the coordinate convention under ''Angle Settings''. Depending on the source, the wave information will likely be in meteorological and oceanographic convention.<br />
<br />
[[Image:fig26_wave_gauge.jpg|400px|thumb|left|Figure 31. Create and define wave gauge]]<br />
<br style="clear:both" /><br />
<br />
Before importing the wave information, double check to make sure there is no missing or incorrect data. In previous versions of the interface, the SMS could not handle wave directions from land; however, this has been corrected.<br />
<br />
If the wave information is in Microsoft Excel or a similar format, it may be easiest to directly copy and paste. There are four columns of information necessary to paste the data correctly (Figure 32). The first column represents the date (month, day, year, and time), the second is the wave height, the third column is the wave period, and the fourth column is wave direction. The date must be in MM/DD/YYYY HH:MM format. If the information is copied from a text file, the time and date must be separated by a space. If a tab is used, the SMS will read the information in five columns and the information will not be pasted correctly. Regardless of the units used in the conceptual model, Ho must be in meters. The reason the grid must be created before adding the wave information is due to the shore normal convention. It is important to note that the conceptual model and GenCade model use different sign conventions. To import the correct wave directions in shore normal coordinates, the user should go to ''GenCade->Edit Grid'' when in the GenCade Model. The ''Azimuth'' is the correct angle to determine shore normal coordinates. The ''Angle'' in the ''Grid Frame Properties'' window will list a different value since the sign convention for the conceptual model is different from the GenCade model. If the value for ''Angle'' is used to determine shore normal coordinates, the wave directions will be incorrect. After pasting the information in the ‘’Wave Events’’ window, click ‘’OK’’ in all of the open windows. Then convert to the 1D grid. To double-check the pasted wave information, go to ‘’Edit Wave Data’’ in the newly created ‘’GenCade’’ menu. The wave gauge is now assigned a cell and the water depth is listed. Click on ‘’Data’’ to open the ‘’Wave Events’’ window. All of the information in this window should be identical to the information pasted. The convention used to define the direction should be the same as the user defined. Once the project is saved, the SMS will output the *.wave files in shore normal convention. The wave directions will be converted if the information was defined in a different convention. However, if the project is reopened after saving, the user should note that regardless of the defined convention in the conceptual model, the ‘’Wave Events’’ window under ‘’Edit GenCade’’ will now list direction in shore normal convention. The ‘’Wave Events’’ window in the conceptual model will not change. For example, if the user defined the direction in meteorological convention, the directions in the ‘’Wave Events’’ window in the conceptual model will still be relative to meteorological convention.<br />
<br />
[[Image:Fig27_copy_paste_opt.jpg|400px|thumb|left|Figure 32. Format for wave gauge data using copy/paste]]<br />
<br style="clear:both" /><br />
<br />
A second way to enter the wave information is by clicking ''Import'' at the bottom of the ''Wave Events'' window. The ''Import'' function allows the user to find the text file with the wave information. Text files must have five columns representing the wave information (Figure 33). The last three columns are in the same format as the copy and paste option (wave height, wave period, and wave direction). The first column lists the date in YYYYMMDD format. The second column lists the time in HHMM format. Once the file is read by the SMS, each column must be identified (Figures 34 and 35). Once ''Finish'' is clicked, a ''Direction Angle Convention'' window should open (Figure 36). The angle convention should be the same as the projection identified under ''Angle Settings''. After pushing ''OK'', the wave information should be in the proper format under ''Wave Events''. Once all of the wave gauges are populated, the user may convert to the 1D grid. After the project is saved, the *.wave files will be created. Regardless of the specified projection, the directions in the wave file will be in shore normal convention. As with the copy/paste wave information option, the wave information in the conceptual model will remain in the specified convention.<br />
<br />
[[Image:fig28_import_wave.jpg|400px|thumb|left|Figure 33. Format for imported wave gauge data]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig29_import_wizard1.jpg|400px|thumb|left|Figure 34. Step one of file import wizard]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig30_import_wizard2.jpg|400px|thumb|left|Figure 35. Step two of file import wizard]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig31_define_angle.jpg|400px|thumb|left|Figure 36. Define angle convention]]<br />
<br style="clear:both" /><br />
<br />
=GenCade Files, Menu, Model Setup, and Execution =<br />
== GenCade Input Files ==<br />
=== Mandatory Input files ===<br />
There are three input files required to run GenCade. <br />
<br />
#GenCade control file (*.gen) lists all information related to the GenCade simulation. <br />
#Initial shoreline (*.shi) <br />
#Wave file(s) (*.wave) <br />
<br />
The .gen file records the details for structures, inlets, dredging events, beach fills, boundary conditions, wave gauges, and the model setup. This file also defines the paths for each of the input files and one of the output files, the *.prt file. '''Although the *.gen file can be opened, it is recommended that the user refrain from making any changes. '''<br />
<br />
<br />
The .shi and .wave files are also necessary to run even the simplest GenCade simulations. <br />
*A separate wave file is created for each wave gauge. <br />
<br />
<br />
=== Optional Input files ===<br />
Three other optional input files are available.<br />
<br />
#Regional contour file (*.shr)<br />
#Water level file (*.wl)<br />
#Variable resolution file (*.shdx) <br />
<br />
The water level file is only created when time-dependent wave transmission is necessary.<br />
<br />
==GenCade Menu ==<br />
Once the conceptual model is converted to the 1D grid, the ''GenCade'' menu will appear between ''Data'' and ''Web'' in the menu bar (Figure 37). This menu can be used to make minor changes to the project and to double-check that all features defined in the conceptual model are represented in the grid. An example of a minor change to make in the GenCade model is modifying the cells representing the left and right bypassing under the ''Edit Inlets'' menu. If the user is calibrating the model, it is best to return to the conceptual model to make any changes. Changes made in the conceptual model may be applied to multiple projects, but changes made to the grid itself cannot.<br />
<br />
[[Image:fig32_GenCade_menu.jpg|400px|thumb|left|Figure 37. GenCade menu in GenCade model]]<br />
<br style="clear:both" /><br />
<br />
==GenCade Model Setup ==<br />
Once the user has determined that all of the features defined in the conceptual model have been retained in the GenCade grid, the user should begin to set up the model. This is accomplished by selecting ''Model Control'' under the ''GenCade'' menu. The first tab in the ''GenCade Model Control'' window is the ''Model Setup'' (Figure 38). It is in this window that the user may specify the starting and ending date of the simulation, the time step, and the recording time step. The simulation time step must be equal to or less than the wave time step. If the wave time step is smaller than the simulation time step, an error will occur and GenCade will not run. The default time step is 1.0 hour, and the default recording time step is 168.0 hours. The user may also give the simulation a title. The bottom right of the menu states ''Print Dates''. In some cases, the user may be interested in the shoreline at a specific date not normally written in the print file (shoreline and transport information are only recorded yearly). Additional dates of interest may be added under ''Print Dates''.<br />
<br />
[[Image:fig33_model_setup.jpg|400px|thumb|left|Figure 38. Model setup window]]<br />
<br style="clear:both" /><br />
<br />
==Beach Setup ==<br />
The second tab under ''GenCade Model Control'' is the ''Beach Setup'' tab (Figure 39). The first section under this tab refers to the ''Sand and Beach Data''. Here the user may enter the ''Effective Grain Size'' (always in mm), the ''Average Berm Height'', and the ''Closure Depth''. The default ''Effective Grain Size'' is 0.2 mm. Depending on the specified units, the default ''Average Berm Height'' is 1.0 ft or 1.0 m and the default ''Closure Depth'' is 10.0 ft or 10.0 m. ''Longshore Sand Transport Calibration Coefficients'' can also be found under ''Beach Setup''. The defaults values for ''K1'' and ''K2'' are 0.5 and 0.25, respectively. These values should be adjusted during the calibration process.<br />
<br />
[[Image:fig34_beach_setup.jpg|400px|thumb|left|Figure 39. Beach setup window]]<br />
<br style="clear:both" /><br />
<br />
==Seaward BC ==<br />
The next tab under ''GenCade Model Control'' is the ''Seaward BC'' (or Boundary Condition) tab (Figure 40). The two main options in this tab are the ''Input Wave Adjustments'' section and the ''Other Options'' section. Under ''Input Wave Adjustments'', the user may modify the ''Height Amplification Factor'', ''Angle Amplification Factor'', and ''Angle Offset''. In the ''Other Options'' section, the user may define the ''Number of Cells in Offshore Contour Smoothing Window''. The default ''ISMOOTH'' value is 11, but it is suggested that this number range between 11 and 101. This is another value that must be adjusted during the calibration stage.<br />
<br />
[[Image:fig35_seaward_bc.jpg|400px|thumb|left|Figure 40. Seaward boundary condition window]]<br />
<br style="clear:both" /><br />
<br />
==Lateral BC ==<br />
The final tab under ''GenCade Model Control'' is the ''Lateral BC'' (or Boundary Condition) tab. There are three options for the ''Left Lateral BC'' and ''Right Lateral BC'': Pinned, Gated, and Moving. <br />
<br />
'''Pinned Boundary Condition'''<br />
The pinned boundary condition is the default and should be used in most cases. A boundary specified as pinned will not move from the initial shoreline. When the pinned boundary condition is selected, all other options under ''Lateral BC'' will be grayed out. The pinned lateral boundary condition is shown in Figure 41.<br />
<br />
[[Image:fig36_pinned_bc.jpg|400px|thumb|left|Figure 41. Pinned lateral boundary condition window]]<br />
<br style="clear:both" /><br />
<br />
'''Moving Boundary Condition'''<br />
If a moving boundary condition is selected (Figure 42), the boundary will move a certain distance over a time period entered by the user. When a moving boundary is selected, the ''Length of Groin from Shoreline to Seaward Tip'' will still be grayed out, but the ''Shoreline Displacement Velocity'' will be active. Under ''Shoreline Displacement Velocity'', the user should enter the shoreline displacement in the same units used to set up the grid. This shoreline displacement may occur over the entire simulation period, a day, or a time step. Shoreline displacement over the entire simulation is the most common input for a moving boundary condition, because many users have shorelines for the beginning and end of a simulation. If the user chooses to specify the shoreline displacement per time step, it should be noted that this number should be very small. For example, in an example with a time step of 0.5 hr and a shoreline displacement of 0.5 ft per time step, the total shoreline displacement during a two year simulation would be 17,520 ft.<br />
<br />
[[Image:fig37_moving_bc.jpg|400px|thumb|left|Figure 42. Moving lateral boundary condition window]]<br />
<br style="clear:both" /><br />
<br />
'''Gated Boundary Condition'''<br />
The final boundary condition available in GenCade is a gated boundary condition (Figure 43). A gated boundary condition is bounded with a groin, so this is beneficial in cases where a groin or a jetty is located near the boundary. In the case of a gated boundary condition, it is also necessary to create and define a groin at the left or right boundary in the conceptual model. If the right lateral boundary is defined as a gated boundary, the groin should have a cell number of N+1. For example, if the grid has 100 cells, the groin should be located at cell number 101. After a gated boundary condition is selected, the ''Length of Groin from Shoreline to Seaward Tip'' will be active. <br />
<br />
[[Image:fig38_gated_bc.jpg|400px|thumb|left|Figure 43. Gated lateral boundary condition window]]<br />
<br style="clear:both" /><br />
<br />
==Running GenCade ==<br />
Once the GenCade grid and all of the parameters in ''Model Control'' have been updated, it is possible to run GenCade. Please remember to save the project before running GenCade. If the project is not saved prior to running GenCade, the most recent additions to the grid will not be written in the *.gen file. To run GenCade, go to the ''GenCade'' menu and select ''Run GenCade'' (Figure 44). A window will open that will describe the simulation. This window will notify the user if an error has occurred. Although there is no time bar stating the amount of time left in the simulation, the window will show when GenCade has finished calculating each year in the time simulation. The window will alert the user when the model is finished and will prompt to exit. Generally, it does not take very long to run GenCade. For an example with a 300 ft cell size, 635 cells, and a time step of 0.1 hour, it takes only about a minute to run each year of the simulation. A smaller cell size will significantly slow down the simulation, but it should still take less than 10 minutes to run for each year in the simulation. Multiple inlets, dredging events, and beach fill can also increase the run time.<br />
<br />
[[Image:fig39_run_GenCade.jpg|400px|thumb|left|Figure 44. Run GenCade]]<br />
<br style="clear:both" /><br />
<br />
Once a GenCade grid is created, the user can choose to run the simulation outside of the SMS. Open the command prompt and move to the proper directory. The correct format to run GenCade is<br />
<br />
GenCade_v1r3.exe project.gen<br />
<br />
==GenCade Output Files ==<br />
Following a GenCade simulation, output files may be created in the assigned directory depending on the set up.<br />
*Print file (*.prt)<br />
*Shoreline position output file (*.slo)<br />
*Net transport rate file (*.qtr)<br />
*Inlet shoal volume file (*.irv) [one per inlet]<br />
*Mean net annual transport files <br />
**Mean net annual transport total (*.mqn)<br />
**Mean transport to the left (*.mql)<br />
**Mean transport to the right (*.mqr)<br />
*Offshore contour file (*.off)<br />
<br />
<br />
- The print file (*.prt) saves all of the information related to the simulation including wave heights, shorelines, and transport rates. <br />
<br />
- The shoreline position output file (*.slo) documents the shoreline position for each time step for every cell in the grid. <br />
<br />
- The net transport rate file (*.qtr) prints the net transport rate for each cell at every time step. <br />
<br />
- The inlet shoal volume file (*.irv) lists volumes for each inlet shoal for every time step. A separate inlet shoal volume file is created for each inlet represented in the simulation. If the grid does not include an inlet, the *.irv file will not be created. <br />
<br />
- All of the files except the print file may be opened and viewed in the SMS. The aforementioned files contain the majority of the information a user would need to evaluate the results of a simulation. <br />
<br />
- The mean net annual transport files (*.mqn [mean annual net transport], *.mql [mean transport to the left], and *.mqr [mean transport to the right]) list the transport for each cell for each time step. <br />
<br />
- The offshore contour for each time step for each cell is included in the offshore contour file (*.off). Additional information about GenCade output files can be found [[GenCade Output Files|here]].<br />
<br />
==Visualizing Results ==<br />
Following a simulation, several output files will be created. These were listed in the previous section. Many of these files may be opened in the SMS for visualization. The first of these files is the *.slo file, or shoreline change file. Once this file is opened in the SMS, a box with the header ''Time Steps'' will appear. An arc representing the calculated shoreline should appear in the grid window. The default color and size of the calculated shoreline may be difficult to view. Go to ''Display->Display Options'' and click on ''1D Grid'' to change the size and color of the calculated shoreline (Figure 45). The size and color of the initial shoreline, regional contour, and structures can also be changed. The default time under ''Time Steps'' is ''Relative Time''. To view the simulated dates, right click on the words ''Time Steps'' and select ''Time Settings''. Change the zero time to represent the first date in the simulation. Under ''Time Display'', change ''Relative Time'' to ''Absolute Time/Date''. The user can view the calculated shoreline at any date during the simulation and compare it with the initial shoreline or other reference line (Figure 46). <br />
<br />
[[Image:fig40_display_options.jpg|400px|thumb|left|Figure 45. Display options window]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig41_view_results.jpg|400px|thumb|left|Figure 46. Initial and calculated shorelines with regional contour]]<br />
<br style="clear:both" /><br />
<br />
Plots can also be viewed in SMS. Under ''Display'', click on ''Plot Wizard'' (Figure 47). In the first window, select ''GenCade Shoreline'' as the plot type. Keep the ''Active dataset'' under ''Dataset'' and ''Active time step'' under ''Time step'' selected and click ''Finish''. A new window will appear showing the shoreline for the selected time step (Figure 48). Once the plot has been created, simply highlight ''Rate of Change'' or ''Shoreline'' under ''GenCade Grid'' in the data tree to change the plot.<br />
<br />
[[Image:fig42_shorelines_plotwizard.jpg|400px|thumb|left|Figure 47. Plot wizard for GenCade shorelines]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig43_shoreline_plot.jpg|400px|thumb|left|Figure 48. Shoreline plot in the SMS]]<br />
<br style="clear:both" /><br />
<br />
The inlet shoal volumes over the entire simulation may also be viewed in the SMS. Go to ''Display'' to ''Plot Wizard''. Under ''Plot Type'', select ''GenCade Inlet TS'' and click ''Next'' (Figure 49). The user may select any of the inlets included in the project and may choose the entire simulation or only a few years. The user may select one shoal or many shoals. After selecting the inlet, time, and corresponding shoals, click ''Finish''. A new window with the shoal volumes over the course of the selected dates will open (Figure 50).<br />
<br />
[[Image:fig44_inlet_shoal_plot.jpg|400px|thumb|left|Figure 49. Plot wizard for inlet shoal volumes]]<br />
<br style="clear:both" /><br />
<br />
[[Image:fig45_inlet_shoal_plot2.jpg|400px|thumb|left|Figure 50. Inlet shoal volumes plot in the SMS]]<br />
<br style="clear:both" /><br />
<br />
Some users may want to plot shoreline change in Microsoft Excel or similar software. All of the information collected during the simulation was saved in the *.prt file (Figure 51). The shoreline change after each year in the simulation is located in this file. Although the shoreline change is not in column format, the format can easily be changed with a simple code. If the case uses constant resolution, the size of each cell is known and this information can easily be added to a spreadsheet. In the case of variable resolution, there is an additional input file: *.shdx. Each number in this file represents the grid cell size. The numbers in the file can also be converted to column format. Once the distance alongshore and the shoreline change have been added to Microsoft Excel or other spreadsheet software, then the shoreline change can be plotted. <br />
<br />
[[Image:fig46_results_prt.jpg|400px|thumb|left|Figure 51. Shoreline change in *.prt]]<br />
<br style="clear:both" /><br />
<br />
It is also possible to use Microsoft Excel to plot longshore transport. In the *.prt file, longshore transport can be found by searching for ''“mean net annual transport”''. This section of the *.prt file is shown in Figure 52. Please make a note of the units for transport listed in the *.prt file. The longshore transport can be plotted in Microsoft Excel in the same way as shoreline change. <br />
<br />
[[Image:fig47_results_prt2.jpg|400px|thumb|left|Figure 52. Mean net annual transport in *.prt]]<br />
<br style="clear:both" /><br />
<br />
It is slightly more difficult to compare the calculated shoreline to a measured shoreline. First, save as a new project. Open the measured shoreline in the SMS and define it as the initial shoreline (for this new saved project). Convert to 1-D grid again and save as a new project. This will save the measured shoreline as the initial shoreline. Both the measured and calculated shoreline will need to be compared to the initial shoreline. The values in the *.shi file represent the distance from the initial shoreline to the grid for each cell. The calculated shoreline can be found in the *.prt by searching for shoreline position after the total number of years in the simulation. These numbers will represent the distance offset from the GenCade grid. Shoreline change after each year in the simulation can also be found in the *.prt file. By saving the measured shoreline as the initial shoreline, this allows SMS to produce an input file for this shoreline in the same format as the initial shoreline and calculated shoreline. All of these shorelines can be converted to column format and pasted into Microsoft Excel. Subtract the initial shoreline from the measured shoreline and the calculated shoreline to get shoreline change for the measured and calculated shorelines.<br />
<br />
=Developing Alternatives =<br />
There are several reasons that a user may need to modify a GenCade grid. While calibrating the model, it may be necessary to refine the grid. Some examples of modifications necessary to develop alternatives include changing a small section of the regional contour, changing the initial shoreline, or adding new structures.<br />
<br />
==Minor Changes to the Regional Contour or Initial Shoreline ==<br />
After setting up and running the model and looking at results, it may become necessary to make a minor modification to the regional contour or initial shoreline. For example, the initial shoreline may need to be smoothed near an unstructured inlet or the regional contour may need to be adjusted to account for a large ebb shoal. <br />
<br />
To make changes to the regional contour or initial shoreline, return to the merged coverage with all of the shorelines, structures, and wave gauges under ''Map Data''. Click ''Select Feature Vertex'' and drag each vertex to the desired location (Figure 53). It is also possible to add vertices by clicking ''Create Feature Vertex'', adding the vertex, and moving it to the selected location. Extra vertices can be deleted after they are selected. Once the required updates to the regional contour or the initial shoreline are made, right click on the merged coverage and convert ''Map->1D Grid''. The initial shoreline or regional contour must be selected by clicking on the ''Select Feature Arc''. If the arc is not selected and highlighted, the old regional contour or initial shoreline will not be replaced. It should also be mentioned that only minor changes should be made to the regional contour or initial shoreline. The user should not modify the regional contour during model calibration.<br />
<br />
[[Image:fig48_modify_rc.jpg|400px|thumb|left|Figure 53. Modify the shape of the regional contour]]<br />
<br style="clear:both" /><br />
<br />
==Modify Existing Structures or Beach Fills ==<br />
For some alternatives, a beach fill or structure may need to be extended. To extend a structure, click on ''Select Feature Point''. Click on the node at the end of the structure and extend it to the desired length. Beach fills can be modified in the same way. Right click on the merged coverage and convert ''Map->1D Grid''. The modified structure must be selected (by clicking on ''Select Feature Point'') for the changes to be noted in the GenCade model. <br />
<br />
==Replace Initial Shoreline or Regional Contour ==<br />
Some projects may require analysis for several different time periods. If the structures exist during multiple time periods and the wave gauge data span many decades, it may be easiest to replace the initial shoreline in the conceptual model. The same process can be used if a new regional contour is necessary. Do not delete the existing GenCade grid. Right click on ''Map Data'', click ''New Coverage'', and select ''GenCade''. It is best to give the new coverage a specific name that can be identified easily. Right click on this new coverage and scroll down to ''Type->Models->GenCade''. Open the new shoreline or regional contour in the new coverage. Click on ''Select Feature Arc'' and define the arc. Right click on the new coverage and convert ''Map->1D Grid''. The new initial shoreline or regional contour will replace the original.<br />
<br />
==Add Structures or Beach Fills ==<br />
When a project has many different alternatives, it may be necessary to add new structures. Instead of developing a new grid for each alternative, features can be modified or added to a base grid that already has the initial shoreline, regional contour, wave gauges, and basic structures and beach fills. Right click on ''Map Data'' and select ''GenCade'' under ''New Coverage''. Right click on this coverage and confirm that the model type is ''GenCade''. In this new coverage, add new structures and beach fills by selecting the ''Create Feature Arc'' button. Specify the type of arc. Once all the new structures are included, right click on the new coverage and convert ''Map->1D Grid''. The new arcs will be added in the GenCade grid. Additional structures or beach fills can also be added directly to the merged coverage that already has the initial shoreline, regional contour, and existing structures.<br />
<br />
==Modify Wave Gauges ==<br />
The instructions above regarding adding new features can also apply to adding new wave gauges. However, sometimes the wave gauge data need to be modified. In reviewing the wave gauge information, a user may find that a few of the dates or values may be incorrect. If only a few values need to be modified, click on the merged coverage and select the wave gauge by clicking on ''Select Feature Point'' and double-click on the point representing the wave gauge. Click on ''Options'' and click on ''Data''. Manually update the incorrect wave information. Once finished, convert ''Map->1D Grid''. The wave gauge will now include the correct wave information. The steps to modify a wave gauge are shown in Figure 54.<br />
<br />
[[Image:fig49_modify_specific_wave.jpg|400px|thumb|left|Figure 54. Modify specific wave events]]<br />
<br style="clear:both" /><br />
<br />
A user may also determine that an entire set of wave gauge information may be incorrect. This can occur by selecting the wrong wave gauge when pasting values or by incorrectly manually transforming waves. This can be remedied by deleting the existing wave gauge, creating a new wave gauge, and following the steps to add information to the wave gauge.<br />
<br />
<br />
'''Useful Links'''<br><br />
<hr><br />
[[GenCade References| GenCade References]]<br><br />
[[GenCade| GenCade Home Page]]<br><br />
[[GenCade#GenCade_Documentation| GenCade Documentation Portal]]</div>Rdchlmebhttps://cirpwiki.info/wiki/GenCade_Input_Files/GEN_fileGenCade Input Files/GEN file2024-02-26T20:54:35Z<p>Rdchlmeb: </p>
<hr />
<div>Below are the presently available cards to be written to the .gen file for GenCade. Click "expand" for information about that card if there is any.<br />
<br />
Items shown in [square brackets] represent a variable contained in one of several user interface files. '''This file is still under construction.'''<br />
<br />
<hr><br />
GENCADE:<br><br><br />
<div class="mw-collapsible mw-collapsed" style="width:50%"><br />
TITLE: &emsp;[title]<div class="mw-collapsible-content"><br />
:UI file referenced: model_control_dlg.ui <br />
</div></div><br />
<nowiki>****** FILES ******</nowiki><br />
<div class="mw-collapsible mw-collapsed" style="width:50%"><br />
PROJDIR: &emsp;"<working dir>"<div class="mw-collapsible-content"><br />
:Directory that all GenCade project files are being run from.<br />
</div></div><br />
<div class="mw-collapsible mw-collapsed" style="width:50%"><br />
INIFILE: &emsp;"<proj_name>.shi"<div class="mw-collapsible-content"><br />
:<proj_name> - the name assigned by SMS and acts as a prefix to all specified filenames.<br />
:The .ini file contains the information for the initial shoreline.<br />
</div></div><br />
<div class="mw-collapsible mw-collapsed" style="width:50%"><br />
DXFILE: &emsp;"<proj_name>.shdx"<div class="mw-collapsible-content"><br />
:<proj_name> - the name assigned by SMS and acts as a prefix to all specified filenames.<br />
:The .shdx file contains the information for the variable resolution of the GenCade grid.<br />
</div></div><br />
<div class="mw-collapsible mw-collapsed" style="width:50%"><br />
REGFILE: &emsp;"<proj_name>.shr"<div class="mw-collapsible-content"><br />
:<proj_name> - the name assigned by SMS and acts as a prefix to all specified filenames.<br />
:The .<br />
</div></div><br />
<br />
<br />
<br />
<br />
<!--<br />
<br />
<div class="mw-collapsible mw-collapsed" style="width:50%"><br />
<div class="mw-collapsible-content"><br />
</div></div><br />
<br />
-></div>Rdchlmebhttps://cirpwiki.info/wiki/CMS/DredgeModule/Phase2CMS/DredgeModule/Phase22024-01-30T15:46:01Z<p>Rdchlmeb: </p>
<hr />
<div>{{DISPLAYTITLE:CMS Dredge Module - Phase 2}}<br />
{{TOC right}}<br />
This page is taken primarily from the USACE Coastal and Hydraulics Technical Note entitled "Coastal Modeling System: Dredging Module Simulation with Multiple Grain Sizes" which can be found at:<br><br />
https://erdc-library.erdc.dren.mil/jspui/bitstream/11681/33664/3/ERDC-CHL%20CHETN-I-98.pdf.<br />
<br />
= Background = <br />
The dredging and placement of multiple sediment grain-sizes are an extension of the single-grain size transport approach. In the updated Dredge Module (DM), the sediment can be represented by discrete grain size classes, and each size class is eroded, transported, and deposited independently. The grain size classes interact solely in the bed layers. The bed is represented by sediment layers of a specific thickness below the bed surface. The top or surficial upper bed layer is referred to as the mixing<br />
layer (often referred to as the active layer), which exchanges the surficial sediments with deposition from the water column. The mixing layer thickness may be set to a constant value (e.g., 0.05 meter [m]) or calculated based on the median grain size and bed form size at each cell. The critical shear stress for erosion for each grain size class in the mixing layer is determined using the<br />
hiding and exposure approach of Wu.<br />
<br />
Below the mixing layer, additional bed layers are defined and are used to track the fraction of each grain size class in the bed, referred to as the bed composition. All of the bed layers exchange sediment with each other by splitting and merging adjacent layers as their thickness evolves during a simulation due to erosion and deposition. Guidance on the implementation in SMS is available at [[CMS-Flow_Multiple-sized_Sediment_Transport | CMS-Flow_Multiple-sized_Sediment_Transport]].<br />
<br />
The CMS is a depth-averaged numerical model. Because the effects of three-dimensional processes are not included in the dredging and placement module, dredged cut and placement features are not reflective of realistic morphology around designated operation sites. Therefore, this module is suggested to be applied in cases with non-cohesive sand sized sediment where the morphological characteristics of dredging/placement need not be resolved.<br />
<br />
= Setup = <br />
[[File:DM_P2_Fig1.png|thumb|300px|Figure 1. CMS grid, bathymetry and Dredge Module information.]]<br />
[[File:DM_P2_Fig2.png|thumb|300px|Figure 2. Initial distribution of the d50 values of the bed.]]<br />
The grid, bathymetry, and dredging and placement areas for the example simulation are shown in Figure 1, which represents a typical offshore region extending 6 kilometers (km) along shore and 3 km offshore, with water depths on the order of 1.5 m in the nearshore and 9 m at the offshore extent. The bed composition is shown in Figure 2. The median grain size (d50) is 0.2 millimeters (mm) in the nearshore and increases linearly offshore, to a value of 3.0 mm.<br />
<br />
The dredging and placement areas simulated in Examples 1, 2, and 3 are illustrated in Figure 1. The dredging area is 60 m wide by 1,880 m long (area = 112,800 m<sup>2</sup>) extending from the nearshore to a depth of approximately 6.0 m. The dredged depth is specified as 6.0 m. This yields a total dredged volume of 220,465 m<sup>3</sup> of bulk material. The dredging rate is specified as 10,000 m<sup>3</sup> per day corresponding to a 22-day dredging event. The dredging is specified to start at the nearshore and proceed in the offshore direction by specifying the starting cell locations (as indicated in Figure 1). The placement area is located offshore of the dredging area and is 400 m by 520 m (area =208,000 m<sup>2</sup>). Two dredging methods were tested in Examples 1 and 2, and Example 3 applied a variation of bed layer thickness for comparison to Example 2.<br />
{{clear}}<br />
<br />
= Examples =<br />
[[File:DM_P2_Fig3.png|thumb|200px|Figure 3. Dredge definition page of the DM interface in SMS 13.0+.]]<br />
[[File:DM_P2_Fig4.png|thumb|200px|Figure 4. Placement definition page of the DM interface in SMS 13.0+.]]<br />
[[File:DM_P2_Fig5.png|thumb|200px|Figure 5. Bed surface d50 distribution after 22 days of simulation for the START_METHOD "SPECIFIED CELL" placement option.]]<br />
{| cellspacing=0 align=center cellpadding=5px width=70% style="border: 1px solid gray;"<br />
|+ Table 1. Summary of Examples<br />
|-<br />
! style="background:lightblue;color:black;border-bottom:1.5px solid black;border-right:1px solid gray" |Example<br />
! style="background:lightblue;color:black;border-bottom:1.5px solid black" |Description<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |1<br />
| style="border-bottom:1px solid gray" |SPECIFIED CELL method for dredging and placement. Starting cell must be identified for both. Dredge rate set to 10000 m<sup>3</sup>/day. Trigger method set to DEPTH of 6 meters with a Distribution method set to PERCENT. Thickness limit set to 1.1 meters.<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |2<br />
| style="border-bottom:1px solid gray" |Dredging setup is the same as example 1, however the Placement method is set to UNIFORM and instead of a Thickness limit, this example uses a Depth limit of 3.<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |3<br />
| style="border-bottom:1px solid gray" |Example 3 is identical to example 2 in the dredge module setup, the changes occur in the sediment transport mixing layer and bed layer thicknesses.<br />
|}<br />
<br />
== Example 1 ==<br />
For the first example simulation, the dredged material was removed and placed using the “SPECIFIED CELL” method in which the starting cell for each operation is specified. In this method, dredging or placement begins at the specified cell and then progresses outward. A dredging rate of 10,000 m<sup>3</sup>/day is specified. Removal continues until the trigger depth is reached, and placement continues until the fill reaches a defined upper limit thickness. The dredging and placement then moves to the next closest cell and so on. The trigger depth for dredging is set to 6.0 m, and the upper limit for placement is specified as 1.1 m. One hundred percent of the placement is assigned to the one defined placement zone. Datasets for the dredge and placement areas should be created according to the guidelines given in the initial DM technical note - [https://erdc-library.erdc.dren.mil/jspui/bitstream/11681/20266/1/ERDC-CHL%20CHETN-I-90.pdf Coastal Modeling System: Dredging Module].<br />
<br />
An interface has been added to SMS 13.0 that allows for user specification of dredge module parameters without the need to edit the CMS-Flow parameter file. Figures 3 and 4 show the Dredge Definition and Placement Definition pages for this example, respectively. Other examples require small changes to the options on these pages.<br />
<br />
The bed surface (mixing layer) sediment grain-size distribution at the end of the 22-day simulation is shown in Figure 5. In the dredging area, the sediment d50 is the same as in the initial distribution since the dredging only removes material and the lower bed layers retain their initial sediment distribution.<br />
<br />
However, there is a variation in the bed surface sediment grain-size distribution in the placement area. The median grain size is coarser with distance from the starting cell. These variations in the placement area reflect the changes in the sediment source (i.e., dredging area) as the dredging proceeds from the near shore (finer d50) to the offshore (coarser d50).<br />
{{clear}}<br />
<br />
== Example 2 ==<br />
[[File:DM_P2_Fig6.png|thumb|300px|Figure 6. Bed surface d50 distribution after 22 days of simulation for the START_METHOD "UNIFORM" placement option. The white line shows a transect used for analysis.]]<br />
[[File:DM_P2_Fig7.png|thumb|300px|Figure 7. Bed surface vertical d50 distribution after 22 days of simulation for transect shown in Figure 6.]]<br />
In the second simulation, the placement method was changed to UNIFORM with a limit of 3.0 m for depth in the placement area. The uniform method places material uniformly over every cell in the placement area until the indicated placement limit is reached. <br />
<br />
The bed surface (mixing layer) sediment grain-size distribution at the end of the 22-day simulation is shown in Figure 6. As before, the sediment d50 in the dredging area at the end of the simulation is the same as in the initial distribution.<br />
<br />
However, the d50 of the bed surface sediment grain-size distribution in the placement area has decreased and is approximately uniform (~ 1.5 mm) and reflects the distribution of sediment near the offshore extent of the dredged area. The vertical distribution of the sediment distribution is shown in Figure 7 for the transect shown in Figure 6. The bottom layers have a d50 indicative of the initial sediment composition of the bed. The d50 decreases upward and finally increases again within the top mixing layer. These vertical variations reflect the changing distribution in the source area as the dredging proceeds from the nearshore (finer d50) to the offshore (coarser d50). The discrete points (black dots) represent the top and bottom of each bed layer in each grid cell.<br />
{{clear}}<br />
<br />
== Example 3 ==<br />
[[File:DM_P2_Fig8.png|thumb|300px|Figure 8. Bed surface vertical d50 distribution after 22 days of simulation for transect shown in Figure 7 using refined bed layer thicknesses.]]<br />
[[File:DM_P2_Fig9.png|thumb|300px|Figure 9. Vertical d50 distribution after 22 days of simulation for point in center of the placement area.]]<br />
A third simulation was conducted to investigate the impact of bed layer thickness on the DM results. This simulation was identical to the second (Figure 7), except that the number of bed layers was increased from the default of 5 to 9. The mixing layer thickness was set to a constant thickness of 0.1 m, and the remaining bed layer thicknesses were set to 0.2 m.<br />
<br />
The vertical distribution of the sediment grain size in the placement area is shown in Figure 8 for the same transect in Figure 6. A plot of the vertical profile of d50 through the center of the placement area is shown in Figure 9 and demonstrates the impact of the bed layer parameters. The d50 is similar through most of the placement area deposit, which extends approximately from 6.8 to 8.1 m water depth. At the surface, the results with nine bed layers show a higher d50 than that of the five bed-layer simulation (1.7 mm vs. 1.5 mm). More notable is the difference near the base of the placement area deposit. There is a gradual increase in sediment grain size with depth for the results with five bed layers reaching the maximum d50 near a depth of 10 m. Increasing the number of bed layers to nine resulted in a highly resolved decrease in the d50 at the base of the placement area deposit with the maximum d50 reached just below a depth of 8.25 m.<br />
<br />
The “smoothing” of the d50 for the case with five bed layers is an artifact of the merging and splitting process bed layer algorithm in the CMS. These results indicate the need to test the bed layering parameter selections to assure that the desired resolution is obtained in the bed.<br />
{{clear}}<br />
<br />
= Summary = <br />
The DM was coupled with multiple grain-size non-cohesive sediment transport and implemented in the CMS. The module significantly enhances the capability of the model to support USACE dredging operations at navigation channels by directly simulating dredging and placements of poorly sorted or nonuniform sediment within a CMS simulation. The implementation of the coupled system does not require any additional input from the user other than the standard inputs that would be required for specifying a multiple grain size or dredging simulation independently. The bed layer algorithms were modified to allow for large changes in bed elevation that may occur during dredging simulations. These modifications prevent sediment mass balance violations that might otherwise occur if the bed layer thickness is too small. The implementation procedure for dredging operation and multiple grain sizes was described, and an example simulation for conditions representing an idealized offshore region has been provided to demonstrate the application of two different dredging and placement methods and their results.</div>Rdchlmebhttps://cirpwiki.info/wiki/CMS/DredgeModule/Phase1CMS/DredgeModule/Phase12024-01-30T15:42:29Z<p>Rdchlmeb: </p>
<hr />
<div>{{DISPLAYTITLE:CMS Dredge Module - Phase 1}}<br />
{{TOC left}}<br />
==Dredge Area Setup==<br />
[[File:DM_Fig3.bmp|thumb|300px|Figure 3. Test Simulation Grid Domain and Bathymetry.]]<br />
[[File:DM_Fig4.bmp|thumb|300px|Figure 4. Dredge Scenario Definitions.]]<br />
The first dredge area, "CapitolDredge" consists of a dredge source area aligned to represent a navigation channel (north-south alignment). The dredge depth was set to 7.5 meters, which created a total dredge volume of approximately 153,000 m<sup>3</sup>. The dredge rate was set to 5000 m<sup>3</sup>/day, which yielded a total time of 30 days to complete dredging. Two placement areas were defined; both near the southern edge of the grid domain, one to each side of the channel.<br />
<br />
The second dredge area, "MaintDredge" consisted of a dredge area in the northeast corner of the grid domain and resembles a sediment impoundment basin. The dredge depth was set to 8 meters yielding a dredge volume of 130,000 m<sup>3</sup>. The dredging rate was set to 6000 m<sup>3</sup>/day, yielding a dredge time of 22 days. A single placement area was defined to the south of the dredge source area.<br />
<br />
The bathymetry of the simulation grid is shown in Figure 3. The location and extent of the dredge source and placement areas for each scenario are shown in Figure 4.<br />
<br />
{{clear}}<br />
<br />
==Test Cases==<br />
{| cellspacing=0 align=center cellpadding=5px width=90% style="border: 1px solid gray;"<br />
|+ Table 1. Summary of Test Simulations<br />
|-<br />
! style="background:lightblue;color:black;border-bottom:1.5px solid black;border-right:1px solid gray" |Test Number<br />
! style="background:lightblue;color:black;border-bottom:1.5px solid black" |Description<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |101<br />
| style="border-bottom:1px solid gray" |CapitalDredge: Dredge option 2 (starting location set to north end of dredge source area), Trigger Option 1 with Threshold set to 7 m. Placement option 1 with Limit of 3m. Placement Allocation 100% for #1 and 0 % for #2.<br />
<br />
MaintDredge: Dredge option 1 (shallowest), Trigger Option 1 with Threshold set to 7.5<br />
m. Placement option 1 with Limit of 3.5 m.<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |102<br />
| style="border-bottom:1px solid gray" |CapitolDredge: Dredge Approach is changed to method 2 (shallowest cell)<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |103<br />
| style="border-bottom:1px solid gray" |CapitolDredge: Placement Allocation is changed form 100%/0% to 60%/40%.<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |104<br />
| style="border-bottom:1px solid gray" |CapitolDredge: Placement Approach is changed from 1 to 2. The CapitolDredge starting<br />
location is the northwest corner for placement area 1 and is at the northeast corner of<br />
placement area 2. The 60%/40% placement allocations used in Test 103 was<br />
applied.<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |105<br />
| style="border-bottom:1px solid gray" |CapitolDredge: Placement Areas were reduced to limit capacity and force an excess of<br />
dredge material during the simulation; placement allocation is sequential<br />
|-<br />
! style="border-bottom:1px solid gray; border-right:1px solid gray" |106<br />
| style="border-bottom:1px solid gray" |CapitolDredge: Placement Areas were reduced to limit capacity and force an excess of<br />
dredge material during the simulation; placement allocation is 80%/20%<br />
|-<br />
! style="border-bottom:1.5px solid black; border-right:1px solid gray" |108<br />
| style="border-bottom:1.5px solid black" |CapitolDredge: trigger approach is changed to option 4<br />
|}<br />
===Test 101===<br />
Examples of the simulated dredging activities for Test 101 are shown in Figure 5 through Figure 8.<br />
Figure 5 shows the final morphology changes due to the simulated dredging activities. The<br />
CapitolDredge navigation channel is apparent, as is the placement in Area 1. The capacity of Placement<br />
Area 1 was not exceeded, so the second area was not used. The changes in morphology for the<br />
MaintDredge scenario are also evident in the figure.<br />
<br />
Figure 6 shows the morphological evolution for the CapitolDredge scenario along a transect aligned<br />
with the navigation channel. The dredging begins at the specified starting location at the north end of<br />
the channel and proceeds southward. The evolution for the MaintDredge scenario is shown in Figure 7<br />
along a north-south transect passing through both the dredge source and placement areas. The<br />
dredging for the source area starts at the northern end, which is the shallowest, but quickly proceeds<br />
uniformly over the dredge source area as all cells obtain an equal depth. The placement of the material<br />
builds up uniformly over the placement area until the specified placement depth limit (3.5 m) is reached<br />
in the shallower portion of the profile. At this time, more material is placed in the deeper areas.<br />
<br />
A time series of the dredge volume for the MaintDredge Scenario is provided in Figure 8. The dredge<br />
volume starts at 130,000m<sup>3</sup> and steadily decreases during the dredging activity at 6000 m<sup>3</sup>/day and is<br />
completed at approximately 22 days (528 hours). The dredge volume placed in the MaintDredge<br />
placement area increases steadily up to 220 hours at which time the placement area capacity of 54,000<br />
m<sup>3</sup> is reached. The placement area capacity is controlled by the specified placement depth limit of 3.5m for this scenario. At 200 hours, the remaining dredge volume is assumed to be placed outside of the<br />
CMS grid domain and is tracked as the Unplaced Volume (excess).<br />
<gallery mode="packed"><br />
File:DM_Fig5.bmp|thumb|300px|Figure 5. Final Morphology Changes for Test 101.<br />
File:DM_Fig6.bmp|thumb|300px|Figure 6. Dredge Profile Evolution for Test 101, CapitolDredge Scenario.<br />
File:DM_Fig7.bmp|thumb|300px|Figure 7. Dredge Profile Evolution for Test 101, MaintDredge Scenario.<br />
File:DM_Fig8.bmp|thumb|300px|Figure 8. Dredge Source and Placement Area volume evolution for Test 101, MaintDredge Scenario.<br />
</gallery><br />
{{clear}}<br />
<br />
===Test 102===<br />
Sample results from Test 102 are shown in Figures 9 and 10. In this test case, the<br />
dredge option for the CapitolDredge scenario was changed to number 1, which causes the dredging to<br />
start at the shallowest cell. The dredge profile evolution along the navigation channel is shown in Figure<br />
9. The dredging starts at the northern shallowest end of the source area, and progress downward,<br />
extending further offshore as the depth increases. This profile contrasts the profile obtained with<br />
dredge option 2, shown in Figure 6.<br />
<br />
A time series of the dredge volume for the CapitolDredge Scenario is provided in Figure 10. The dredge<br />
volume starts at 153,000 m<sup>3</sup> and steadily decreases during the dredging activity at the rate of 5000<br />
m<sup>3</sup>/day. Dredging is completed at approximately 30 days (720 hours). The dredge volume placed in the<br />
CapitolDredge placement area increases steadily at the same rate until the dredging is completed. No<br />
excess volume is recorded since the placement area capacity is sufficient.<br />
<gallery mode="packed"><br />
File:DM_Fig9.bmp|300px|Figure 9. Dredge Profile Evolution for Test 102, CapitolDredge Scenario (transect is shown in Figure 5).<br />
File:DM_Fig10.bmp|300px|Figure 10. Dredge Source and Placement Area volume evolution for Test 102, CapitolDredge Scenario.<br />
</gallery><br />
{{clear}}<br />
<br />
===Test 103===<br />
Sample results from Test Simulation 103 are shown in Figure 11 and Figure 12. In this test case, the<br />
placement allocation between the two placement areas was changed from 100% and 0% to 60% and<br />
40%. Figure 5 shows the final morphology changes due to the simulated dredging activities. The dredge<br />
material form the CaptiolDredge source area is distributed over both placement areas. These results are<br />
in contrast to the results obtained with the 100%/0% split shown in Figure 5.<br />
<br />
A time series of the dredge volume for the CapitolDredge Scenario is provided in Figure 12. As in test<br />
Simulation 102, the dredge volume starts at 153,000m<sup>3</sup> and steadily decreases during the dredging<br />
activity and the total dredge volume placed in the CapitolDredge placement area increases steadily at<br />
the same rate. Additionally the volumes placed in areas 1 and 2 are proportioned by the specified<br />
allocation of 60% and 40%, yielding a final volume of 91,000 m<sup>3</sup> in area 1 and 62,000 m<sup>3</sup> in area 2.<br />
<gallery mode="packed"><br />
File:DM_Fig11.bmp|300px|Figure 11. Final Morphology Changes for Test 103.<br />
File:DM_Fig12.bmp|300px|Figure 12. Dredge Source and Placement Area volume evolution for Test 103, CapitolDredge Scenario.<br />
</gallery><br />
{{clear}}<br />
<br />
===Test 104===<br />
In Test Simulation 104, the dredge placement approach for the CapitolDredge scenario was changed<br />
from option 1 to option 2, which places material in the cells closest to the designated starting point first.<br />
The starting location is the northwest corner for placement area 1 and is at the northeast corner of<br />
placement area 2. The final morphology changes are shown in Figure 13. The placement areas are filled<br />
according to the specified allocation of 60% and 40%, but the filling starts at the cells closest to the<br />
designated starting locations, and are filled to the specified placement limit of 3 meters for area 1 and<br />
3.5 meters for area 2.<br />
<gallery mode="packed"><br />
File:DM_Fig13.bmp|300px|Figure 13. Final Morphology Changes for Test 104.<br />
</gallery><br />
{{clear}}<br />
===Tests 105 and 106===<br />
In Tests 105 and 106, the dredge placement approach for the CapitolDredge scenario is<br />
reduced to limit capacity and force an excess of dredge material during the simulation. For Test 105, the<br />
placement allocation is sequential and for Test 106 the placement allocation is 80%/20%. The time<br />
series of dredge and placed volumes is shown in Figure 14 for Test 105 and in Figure 15 for Test 106.<br />
<br />
The primary differences in the results are in the placed volume time series for the two cases. For Test<br />
105, the first placement area is filled at a constant rate until it reaches its capacity at about 490 hours<br />
(approximately 98,000 m<sup>3</sup>), at which time the dredge material is placed in placement area 2. When the<br />
placement area 2 capacity is reached at about 730 hours (approximately 51,000 m<sup>3</sup>), the remaining<br />
dredged material is assumed to be placed in an area off of the CMS grid domain and that volume is<br />
recorded (this amount is approximately 3,000 m<sup>3</sup>).<br />
<br />
For Test 106, both placement areas are filled steadily according to the specified ratio of 80%/20%.<br />
When the first placement area reaches capacity at about 600 hours, the total dredge volume is placed<br />
into placement area 2 and therefore the filling rate of placement area 2 increases. When the capacity of<br />
placement area 2 is reached at about 720 hours, the remaining dredged is assumed to be placed in an<br />
area off of the CMS grid domain and that volume is recorded.<br />
<gallery mode="packed"><br />
File:DM_Fig14.bmp|300px|Figure 14. Dredge Source and Placement Area volume evolution for Test 105, CapitolDredge Scenario.<br />
File:DM_Fig15.bmp|300px|Figure 15. Dredge Source and Placement Area volume evolution for Test 106, CapitolDredge Scenario.<br />
</gallery><br />
{{clear}}<br />
<br />
===Test 108===<br />
The final example provided is for Test Simulation 108, in which the CapitolDredge and MaintDredge<br />
scenarios triggering option was set to number 4. For the MaintDredge scenario, two dredge periods<br />
were specified: one from 50 to 300 hours and another from 350 to 600 hours. The time series of<br />
dredged and placed volumes for Test 108 is shown in Figure 16. The remaining dredge volume decreases <br />
steadily during the two designated periods, and remains constant during the 50 hour break between the <br />
two dredging periods. The MaintDredge Placement area is filled after 220 hours of dredging (equal to <br />
270 hours of simulation time), at which time the remaining dredged is assumed to be placed in an area <br />
off of the CMS grid domain and that volume is recorded. Between 200 and 350 hours, dredging has ceased <br />
and the dredged and placed volumes remain constant. After hour 350, dredging continues and the material <br />
is placed off the CMS grid domain.<br />
<br />
As seen previously in Test 101 (See Figure 8), the time to dredge the entire source area at 6000 m<sup>3</sup>/day<br />
is approximately 528 hours. Since the allocated dredge time for Test 108 is 500 hours, the source area<br />
volume of 130,000 m<sup>3</sup> is not completely removed. The dredge volume is limited to 125,000 m<sup>3</sup> due to<br />
the specified dredging periods and dredge rate.<br />
<gallery mode="packed><br />
File:DM_Fig16.bmp|300px|Figure 16. Dredge Source and Placement Area volume evolution for Test 108, CapitolDredge Scenario.<br />
</gallery></div>Rdchlmeb