SMS:Wave Gages: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Hide in print|{{GenCade Menubox}}
[[Image:GenCade Wave Gages.png|thumb|200 px|GenCade ''Wave Gages'' table]]
}}
Wave gages provide boundary condition information to a GenCade simulation. The wave height, period and direction influence the transport of material on the shoreline and the shoreline morphology.  The GenCade model allows defining multiple wave gages, providing for spatially varied driving force.


Wave gages provide boundary condition information to a GenCade simulation. The wave height, period and direction influence the transport of material on the shoreline and the shoreline morphology.  The GenCade model allows the user to define multiple wave gages, providing for spatially varied driving force.
The wave gage is created either as an ''Attribute'' on a feature point in the GenCade coverage, which will be mapped to a specific cell in the grid, or it may be specified directly on the grid.  For each wave gage, specify a depth and wave events.  Each wave event has a date and time, a H0, a period, and a direction.  The model computes the wave conditions for each cell in the grid by interpolating the data from the neighboring wave gages.
 
The wave gage is created either as an "Attribute" on a feature point in the GenCade coverage, which will be mapped to a specific cell in the grid, or it may be specified directly on the grid.  For each wave gage the user also specifies a depth and wave events.  Each wave event has a date and time, a H0, a period, and a direction.  The model computes the wave conditions for each cell in the grid by interpolating the data from the neighboring wave gages.


Wave gages specified in a GenCade coverage will be displayed at the feature point in the coverage, and will appear when the 1D grid (not grid frame) is created on the associated cell in the grid.   
Wave gages specified in a GenCade coverage will be displayed at the feature point in the coverage, and will appear when the 1D grid (not grid frame) is created on the associated cell in the grid.   


If the user changes attributes of a wave gage on a feature point, these changes do not impact the simulation unless teh attributes are mapped to the grid again (Map → 1D grid).  Wave gages can be edited using the "Edit Wave Data.." option from the GenCade menu after the grid is created and still take effect.
If attributes of a wave gage are changed on a feature point, these changes do not impact the simulation unless the attributes are mapped to the grid again ('''Map → 1D grid''').  Wave gages can be edited using the '''Edit Wave Data..''' option from the ''GenCade'' menu after the grid is created and still take effect.


==Wave Events==
==Wave Events==
Line 14: Line 12:


The direction of a wave, for a given wave event, for a given wave gage may be specified in a meteorological, oceanographic, or Cartesian convention.  Also, the wave direction can be specified in a shore normal convention as long as a 1D grid or 1D grid frame is present in the coverage which contains the wave gage.  The default convention for wave gages is meteorological.
The direction of a wave, for a given wave event, for a given wave gage may be specified in a meteorological, oceanographic, or Cartesian convention.  Also, the wave direction can be specified in a shore normal convention as long as a 1D grid or 1D grid frame is present in the coverage which contains the wave gage.  The default convention for wave gages is meteorological.
[[File:Wave Event.png|thumb|none|left|500 px|Example of a ''Wave Event'' dialog.]]


==Wave Data for GenCade==
==Wave Data for GenCade==
Wave conditions, including significant wave height, peak period, and direction, drive the transport forces that impact coastal morphology. GenCade requires wave data for at least one location in the domain, and supports options for the user to specify wave data at multiple locations in the domain. Each wave gage includes:  
Wave conditions, including significant wave height, peak period, and direction, drive the transport forces that impact coastal morphology. GenCade requires wave data for at least one location in the domain, and supports options for specifying wave data at multiple locations in the domain. Each wave gage includes:  
* A location – (X,Y) coordinate as a feature point and Cell ID as an input to the model.  
* A location – (X,Y) coordinate as a feature point and Cell ID as an input to the model.  
* A depth – the water depth at the gage.  
* A depth – The water depth at the gage.  
* A time series of wave data events – The user obtains these events either from a buoy or from a local wave transformation model.  
* A time series of wave data events – Obtain these events either from a buoy or from a local wave transformation model.  
Issuing the command to edit wave data invokes the ''Wave Gages'' dialog. This dialog lists the gauge cell IDs and the depths. It also includes a button for each gage to view/edit the wave data at that gage.  
Issuing the command to edit wave data invokes the ''Wave Gages'' dialog. This dialog lists the gauge cell IDs and the depths. It also includes a button for each gage to view/edit the wave data at that gage.  


Clicking on the ''Data ...'' button for any of the gages brings up the ''Wave Events'' dialog. This dialog displays the time, height, period and direction (in shore normal coordinates) for the gage. The data is in a spread sheet, so it may be copied and pasted from other spread sheet data. There is also an "Import" button that can be used bring up the [[SMS:File Import Wizard|import wizard]] to bring in wave events data stored in a text file.  The data is saved and passed to the model in the wave file.
Clicking on the '''Data ...''' button for any of the gages brings up the ''Wave Events'' dialog. This dialog displays the time, height, period and direction (in shore normal coordinates) for the gage. The data is in a spread sheet, so it may be copied and pasted from other spread sheet data. There is also an '''Import''' button that can be used bring up the [[SMS:File Import Wizard|''Import Wizard'']] to bring in wave events data stored in a text file.  The data is saved and passed to the model in the wave file.
==Modify 1D Wave Line==
Used with CGWAVE, the paramters must first be defined in the [[SMS:CGWAVE Model Control|''CGWAVE Model Control'']] dialog.
[[File:CGWAVE Modift1DWave.png|thumb|none|450 px|The ''Modify 1D Wave Line'' dialog]]


==Related Topics==
==Related Topics==
Line 29: Line 32:


{{Template:Navbox SMS}}
{{Template:Navbox SMS}}
[[Category:GenCade]]
[[Category:GenCade Dialogs]]

Latest revision as of 14:21, 15 July 2019

GenCade Wave Gages table

Wave gages provide boundary condition information to a GenCade simulation. The wave height, period and direction influence the transport of material on the shoreline and the shoreline morphology. The GenCade model allows defining multiple wave gages, providing for spatially varied driving force.

The wave gage is created either as an Attribute on a feature point in the GenCade coverage, which will be mapped to a specific cell in the grid, or it may be specified directly on the grid. For each wave gage, specify a depth and wave events. Each wave event has a date and time, a H0, a period, and a direction. The model computes the wave conditions for each cell in the grid by interpolating the data from the neighboring wave gages.

Wave gages specified in a GenCade coverage will be displayed at the feature point in the coverage, and will appear when the 1D grid (not grid frame) is created on the associated cell in the grid.

If attributes of a wave gage are changed on a feature point, these changes do not impact the simulation unless the attributes are mapped to the grid again (Map → 1D grid). Wave gages can be edited using the Edit Wave Data.. option from the GenCade menu after the grid is created and still take effect.

Wave Events

Wave events can be edited by clicking on the Data... button when editing the wave gage. This can be done for either a gage on a 1D grid, or a gage at a feature point.

The direction of a wave, for a given wave event, for a given wave gage may be specified in a meteorological, oceanographic, or Cartesian convention. Also, the wave direction can be specified in a shore normal convention as long as a 1D grid or 1D grid frame is present in the coverage which contains the wave gage. The default convention for wave gages is meteorological.

Example of a Wave Event dialog.

Wave Data for GenCade

Wave conditions, including significant wave height, peak period, and direction, drive the transport forces that impact coastal morphology. GenCade requires wave data for at least one location in the domain, and supports options for specifying wave data at multiple locations in the domain. Each wave gage includes:

  • A location – (X,Y) coordinate as a feature point and Cell ID as an input to the model.
  • A depth – The water depth at the gage.
  • A time series of wave data events – Obtain these events either from a buoy or from a local wave transformation model.

Issuing the command to edit wave data invokes the Wave Gages dialog. This dialog lists the gauge cell IDs and the depths. It also includes a button for each gage to view/edit the wave data at that gage.

Clicking on the Data ... button for any of the gages brings up the Wave Events dialog. This dialog displays the time, height, period and direction (in shore normal coordinates) for the gage. The data is in a spread sheet, so it may be copied and pasted from other spread sheet data. There is also an Import button that can be used bring up the Import Wizard to bring in wave events data stored in a text file. The data is saved and passed to the model in the wave file.

Modify 1D Wave Line

Used with CGWAVE, the paramters must first be defined in the CGWAVE Model Control dialog.

The Modify 1D Wave Line dialog

Related Topics