CMS-Flow Wave Forcing: Difference between revisions
Jump to navigation
Jump to search
(Created page with Temporally and spatially varying. * Wave forcing is generally provided by the user selecting to use the Steering Module within SMS. The mapping of wave data from wave grid t...) |
No edit summary |
||
| Line 1: | Line 1: | ||
__NOTOC__ | |||
There are two ways in which CMS-Flow uses wave information. The first is with user specified datasets. In this approach, precomputed wave height, period and direction datasets are provided to CMS-Flow. The advantage of this approach is that any wave model can be used and that the waves do not have to be recomputed for multiple CMS-Flow runs. The disadvantage is that the currents are not included in the wave model calculation (one-way coupling). The second approach is to run CMS-Flow and CMS-Wave together or in ''Steering'' mode. | |||
== User Specified Datasets == | |||
Temporally and spatially varying. | Temporally and spatially varying. | ||
* Wave forcing is generally provided by the user selecting to use the Steering Module within SMS. The mapping of wave data from wave grid to flow grid is automated during the course of the steering process. | * Wave forcing is generally provided by the user selecting to use the Steering Module within SMS. The mapping of wave data from wave grid to flow grid is automated during the course of the steering process. | ||
| Line 10: | Line 14: | ||
'''CMS-Flow cards related to wave forcing (one-way coupling)''' | '''CMS-Flow cards related to wave forcing (one-way coupling)''' | ||
{| border=1 | {| border="1" | ||
! Card !! Arguments !! Type | ! Card !! Arguments !! Type | ||
|- | |- | ||
|WAVE_RSTRESS_DATASET || File name Dataset path || character | |WAVE_RSTRESS_DATASET || "File name" "Dataset path" || character | ||
|- | |- | ||
|WAVE_HEIGHT_DATASET || File name Dataset path || character | |WAVE_HEIGHT_DATASET || "File name" "Dataset path" || character | ||
|- | |- | ||
|WAVE_PERIOD_DATASET || File name Dataset path || character | |WAVE_PERIOD_DATASET || "File name" "Dataset path" || character | ||
|- | |- | ||
|WAVE_DIRECTION_DATASET || File name Dataset path || character | |WAVE_DIRECTION_DATASET || "File name" "Dataset path" || character | ||
|- | |- | ||
|WAVE_DISSIPATION_DATASET || File name Dataset path || character | |WAVE_DISSIPATION_DATASET || "File name" "Dataset path" || character | ||
|} | |} | ||
== Steering Mode == | |||
---- | |||
[[CMS#Documentation Portal | Documentation Portal]] | |||
Revision as of 16:29, 16 January 2011
There are two ways in which CMS-Flow uses wave information. The first is with user specified datasets. In this approach, precomputed wave height, period and direction datasets are provided to CMS-Flow. The advantage of this approach is that any wave model can be used and that the waves do not have to be recomputed for multiple CMS-Flow runs. The disadvantage is that the currents are not included in the wave model calculation (one-way coupling). The second approach is to run CMS-Flow and CMS-Wave together or in Steering mode.
User Specified Datasets
Temporally and spatially varying.
- Wave forcing is generally provided by the user selecting to use the Steering Module within SMS. The mapping of wave data from wave grid to flow grid is automated during the course of the steering process.
- If a choice is made not to use the steering process, the user must provide several datasets of information which has been mapped to the flow grid geometery.
- Radiation stress gradient
- Wave height
- Wave period
- Wave direction
- Wave dissipation
CMS-Flow cards related to wave forcing (one-way coupling)
| Card | Arguments | Type |
|---|---|---|
| WAVE_RSTRESS_DATASET | "File name" "Dataset path" | character |
| WAVE_HEIGHT_DATASET | "File name" "Dataset path" | character |
| WAVE_PERIOD_DATASET | "File name" "Dataset path" | character |
| WAVE_DIRECTION_DATASET | "File name" "Dataset path" | character |
| WAVE_DISSIPATION_DATASET | "File name" "Dataset path" | character |