CMS-Wave Model Parameters: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
Deleted (talk | contribs)
mNo edit summary
 
(63 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Model Control=
[[File:CMSWave Model Parameters GeneralTab V13.2.12.png|thumb|right|400px|CMS-Wave Model Control window Version 13.2.12.]]
[[Image:Shark_Fig38.PNG|thumb|right|400px|CMS-Wave Model Control window.]]
= Parameters =
To setup the model parameters for CMS-Wave:
[[File:CMS Wave Model Control V. 13.2.12.png|500px|thumb|center]]
==CMS Wave plane mode ==


1. Go to CMS-Wave, Model Control, and turn on Allow wetting and drying
===Full half plane with reverse spectra===
and Bed friction (Figure 38),
===Full plane===
In this mode, CMS-Wave performs two half-plane runs in the same grid.  The first run is in the half-plane with the principle wave direction toward the shore.  The second run is in the seaward half-plane as opposed to the first run.  Upon the completion of the second run, two half-plane results are combined to one full-plane solution (Lin et al. 2012).  Because the run time for the full-plane is approximately twice of the regular half-plane, users shall consider the full-plane mode only if the full-plane features like wave generation and propagation in a bay or around an island.
===Half Plane===


2. Users can also specify constant or varied forward and backward reflection
== Source terms ==
coefficients in Settings,
CMS-Wave is a phase-averaged model for propagation of directional irre-gular waves over complicated bathymetry and nearshore where wave re-fraction, diffraction, reflection, shoaling, and breaking simultaneously act at inlets. Wave diffraction terms are included in the governing equations following the method of Mase et al. (2005). Four different depth-limiting wave breaking formulas can be selected as options including the interaction with a current. The wave-current interaction is calculated based on the dispersion relationship including wave blocking by an opposing current (Larson and Kraus 2002). Wave generation and whitecapping dissipation are based on the parameterization source term and calibration using field data (Lin and Lin 2004a and b, 2006a). Bottom friction loss is estimated from the classical drag law formula (Collins 1972).


3. Water level and wind information are optional source as specified under
== [https://cirpwiki.info/wiki/CMS-Flow:Wave-current_Interaction Current interaction] ==
Wave Source in addition to the spectral input data,


4. File, Save As, Wave.sim (selecting the Save As Type as
== Bottom friction ==
Bottom friction could be assigned as constant or by a dataset inside SMS. To see more details, see the [https://cirpwiki.info/wiki/CMS-Flow_Model_Parameters#Bottom_and_wall_friction Bottom and wall friction of the CMS Flow].
Usually, the same roughness method used on CMS Wave is used on the CMS Flow parameters bottom friction.  
For a detail explanation of how Bottom Friction variable is used on the CMS Wave model, see [https://cirpwiki.info/wiki/Bottom_Friction Bottom Friction]


<br style="clear:both" />
==Surge Fields==
==Wind Fields==
If the spatial wind field input is required, users shall prepare a wind.dat file or *.wind (in the same format as *.cur) to provide the x- and y-component wind data corresponding to the incident wave conditions in the model grid.


= CMS-Wave Advanced Features =
==Matrix Solver==
The most recent CMS-Wave code developed is Version 3.2.  Several new capabilities and
https://cirpwiki.info/wiki/CMSFlow_Matrix_Solver
advanced features in this version include:
* Full-plane
* Automatic wave run-up calculation
* Infra-gravity wave
* Nonlinear wave-wave interaction
* Muddy bottom
* Binary file output
* Selection of multiple processors
* Permeable structure
* Spatially varied wind input
* Spatially varied spectral input
* Grid nesting
Users can use SMS11 or simply edit the existing model control file *.std to specify some of
these advanced features.
The *.std has a maximum of 24 parameters - the first 15 parameters are more the basic ones as
described in the CMS-Wave Technical Report (CHL-TR-08-13) while the remaining 9 parameters
are relatively new for advanced CMS-Wave features.


'''Table 1. CMS-Wave parameters in STD file'''
= Boundary control =
{| border="1"
[[File:CMS Wave Model Control Boundray ControlV. 13.2.12.png|500px|thumb|center]]
! Number !! Variable !! Argument Type !! Range !! Description
Water level and wind information are optional source as specified under
|-
Wave Source in addition to the spectral input data.
|  1 || iprp ||  REAL || 0 - waves and wind input in *.eng, 1 - waves only, neglect wind input in *.eng, -1 - fast mode, 2 - forced grid internal rotation
==Source==
3 - without lateral energy flux || Wave propagation mode
Spatially varied spectral input – This is simply the case as in a child grid that spatially varied wave spectra are permitted to assign at user specified locations along or near the seaward boundary of the child grid. To apply spatially varied spectra for wave input without a parent grid, users will need to prepare the wave input file with the format as described in the child grid run.
|-
| 2 || icur || REAL  || 0 - no current input, 1 - with current input *.cur, 2 -with *.cur, use only the 1st set current data || Current interaction
|}


1<sup>st</sup>      2<sup>nd</sup>    3<sup>rd</sup>    4<sup>th</sup>    5<sup>th</sup>     
https://cirpwiki.info/wiki/CMS-Wave_Input_Spectra
6<sup>th </sup>    7<sup>th</sup>      8<sup>th</sup>    9<sup>th</sup>   
10<sup>th</sup>    11<sup>th</sup>    12<sup>th</sup>  13<sup>th</sup> 
14<sup>th</sup>  15<sup>th</sup>


iprp  icur  ibk    irs    kout  ibnd  iwet  ibf    iark  iarkr  akap  bf    ark    arkr  iwvbk
==Interpolation==
16<sup>th</sup>      17<sup>th</sup>    18<sup>th</sup>      19<sup>th</sup>     
*Inverse distance weighting
20<sup>th</sup>    21<sup>st</sup>    22<sup>nd</sup>      23<sup>rd</sup>   
24<sup>th</sup>
nonln  igrav  irunup  imud  iwnd  isolv  ixmdf  iproc  iview


Among these 24 parameters in *.std, the first 6 parameters are always required in CMS-Wave and
The inverse-distance interpolation also referred to as Shepard interpola-tion is given by (Shepard 1968)
the remaining ones starting any parameter after the 6<sup>th</sup> will be assigned to the
default values if not provided in the *.std.  The more specific use and options associated with
each of these 1<sup>st</sup> to 24<sup>th</sup> parameters are given below.


iprp  =  0 (wave propagation with wind input in *.eng)
{{Equation|<math>\phi(\overrightarrow{x}) = \sum_{i=1}^N w_i \phi_i</math>|17-1}}
1 (wave propagation only, neglect wind input in *.eng)
-1 (fast mode)
2 (forced grid internal rotation)
3 (without lateral energy flux)


icur  =  0 (no current input)
where the interpolation weights are given by
1 (with current input *.cur)
2 (with *.cur, use only the 1st set current data)


ibk  = 0 (no wave break info output)
{{Equation|<math>w_i = \frac{d_i ^{-\rho_s}}{ \sum_{j} d_j^{-\rho_s}}</math>|17-2}}
1 (output breaking indices *.brk)
2 (output energy dissipation rate *.brk)


irs  = 0 (no wave radiation stress calc)
where  
1 (output radiation stress *.rad)
2 (calculate/output setup/max-water-level + *.rad)


kout = number of special wave output location, output spectrum in *.obs
<math>\rho_s</math> = real and positive power parameter [-]
and parameters in selhts.out


ibnd  = 0 (no input a parent spectrum *.nst)
d = distance between the known points <math>\overrightarrow{x_i}</math>  and the unknown interpolation points <math>\overrightarrow{x}</math>  equal to the Euclidean norm <math>d = ||\overrightarrow{x} - \overrightarrow{x}_i||</math> .  
1 (read *.nst, averaging input spectrum)
2 (read *.nst, spatially variable spectrum input)


iwet  = 0 (allow wet/dry, default)
In this interpolation, the weight of each point decreases with distance from the interpolated point. One advantage of the inverse-distance interpolation is the interpolation weights are independent of the interpolation function, and therefore only need to be calculated once and can be saved for computational efficiency.[[User_Guide_028|[1]]]
1 (without wet/dry)
-1 (allow wet/dry, output swell and local sea files)
-2 (output combined steering wav files)
-3 (output swell, local sea, and combined wav files)


ibf  = 0 (no bottom friction calc)
== Computational spectral grid==
1 (constant Darcy-Weisbach coef, c_f)
Spectral waves or wave parameters can be generated for the wave grid forcing, or wind direction and speeds can provide the necessary information for wind- wave generation. Full (directional) spectra can be imported into the SMS for the CMS-Wave, as well as simplified wave parameters (angle, wave height, and period, etc).
2 (read variable c_f file, *.fric)
3 (constant Mannings n)
4 (read variable Mannings n file, *.fric)


iark  = 0 (without forward reflection)
==Sides==
1 (with forward reflection)


iarkr = 0 (without backward reflection)
==Case data==
1 (with backward reflection)


akap  = 0 to 4 (diffraction intensity, 0 for zero diffraction, 4 for strong diffraction)
===Wind direction angle conversion===
*Cartesian
*Meteorologic
*Oceanographic
*Shore normal


bf    = constant bottom friction coef c_f or n
===Populate from Spectra===
(typical value is 0.005 for c_f and 0.025 for Mannings n)
===Set Reference Time===


ark  = 0 to 1 (constant forward reflection coef, global specification,
= Output control =
0 for zero reflection, 1 for 100% or fully reflection)
[[File:CMS Wave Model Control OutputControl. 13.2.12.png|500px|thumb|center]]
== Limit observation output ==
== Radiation stresses ==
== Sea/swell ==
==Breaking type==


arkr  = 0 to 1 (constant backward reflection coef, global specification,
= Options =
0 for zero reflection, 1 for 100% or fully reflection)
[[File:CMS Wave Model Control Options 13.2.12.png|500px|thumb|center]]
iwvbk = 0 to 3 (option for the primary wave breaking formula:
To include (trigger) either of wave run-up, infra-gravity wave, nonlinear wave-wave interaction, binary (xmdf or *.h5) output, multiple processors, muddy bed, and spatial wind field input is just a one-click step in the SMS interface. Additional files are required for the muddy bed and spatial wind field input.
0 for Goda-extended, 1 for Miche-extended,
==[https://cirpwiki.info/wiki/CMS-Flow_NUmerical_Methods:_Wetting_and_Drying Allow wetting and drying]==
2 for Battjes and Janssen, 3 for Chawla and Kirby)


nonln = 0 (none, default)  1 (nonlinear wave-wave interaction)
==Infragravity wave effect==
==[https://cirpwiki.info/wiki/CMS-Wave:Diffraction Diffraction intensity]==


igrav  = 0 (none, default) 1 (infra-gravity wave enter inlets)
==Nonlinear wave effect==
==Run up==
==Fast-mode run==
==Roller effects==
The wave roller parametric formulation is commonly applied in the wave spectral model to modify breaking wave energy dissipation nearshore to mimic better the surf zone dynamics. The wave roller effect used in CMS-Wave is based on the roller model developed by Zhang et al. (2014).


irunup = 0 (none, default) 1 (automatic, runup relative to absolute datum)
==Forward reflection==
2 (automatic, runup relative to updated MWL)
==Backward reflection==
==Muddy bed==
If the muddy bed calculation is required, users shall prepare a mud.dat file or *.mud (in the same format as *.dep) to list the spatial varying max-imum kinematic viscosity for the entire grid (recommended maximum kinematic viscosity for mud is 0.04 m2/sec).
==Wave breaking formula==
==Date format==


imud  = 0 (mud.dat, default)  1 (none)  ---- useful to users who may not want to include the mud effect when the mud.dat exists (typical maximum kinematic viscosity in mud.dat
To setup the model parameters for CMS-Wave:
is 0.04 m<sup>2</sup>/sec)


iwnd  = 0 (wind.dat, default)  1 (none)  ----  useful in steering if users decide not
1. Go to CMS-Wave, Model Control, Options and turn on Allow wetting and drying
to read the spatially varied wind field input wind.dat when the wind.dat file exists
and Bed friction


isolv  = 0 (GSR solver, default)  1 (ADI)
2. Users can also specify constant or varied forward and backward reflection
coefficients in Settings,
 
 
<br style="clear:both" />
To read more about CMS Wave defintions, see [https://cirpwiki.info/wiki/CMS-Wave_Model_Control CMS Wave Model Control Definitions]


ixmdf  = 0 (output ascii, default) 1 (output xmdf)  2 (input & output xmdf)
= CMS-Wave Model Control File formats=
The CMS-Wave Options File (*.std) can have one of 3 input formats. Click one of the options below for the format description.


iproc  = 0 (same as 1, defaultn (n processors for isolv = 0)
{|
optimum n = (total row number) /300
|-
|1. [[Wave_NoCards|No cards - order of values on one line is very important.]] || '''(Used with SMS 11.1 and previous)'''
|-
|2. [[Wave_CardFormat1|Card-based - [value] [!card name]]] || '''(Used with SMS 11.2 to 13.1)'''
|-
|3. [[Wave_CardFormat2|Card-based - [card name] [value(s)]]] || '''(Used with SMS 13.2 and after)'''
|}


iview  = 0 (half-plane, default) 1 (full-plane) --- in the full plane, users can provide additional input wave spectrum file wave.spc (same format as the *.eng) along the opposite side boundary
Later versions of SMS can generally read the older formats, however exceptions have been found with Type 1 and listed on that page.
(an imaginary origin for wave.spc at the opposite corner; users can rotate the CMS-Wave grid by 180 deg in SMS
to generate this wave.spc)


Figure 6.1 shows the CMS-Wave interface window for ''Model Control'' in SMS11.


* Full-plane – In this mode, CMS-Wave performs two half-plane runs in the same grid.  The first
[[CMS-Wave_File_Formats | Back to CMS-Wave File Formats]]
run is in the half-plane with the principle wave direction toward the shore.  The second run is in
the seaward half-plane.  Upon the completion of the second run, two half-plane results are
combined to one full-plane solution.  Because the run time for the full-plane is approximately
twice of the regular half-plane, users shall consider the full-plane mode only if the full-plane
features like wave generation and propagation in a bay or around an island. An example is to run
the Shark River wave case, 2009.sim, in the full plane (modify 2009.std).

Latest revision as of 21:24, 9 April 2025

CMS-Wave Model Control window Version 13.2.12.

Parameters

CMS Wave plane mode

Full half plane with reverse spectra

Full plane

In this mode, CMS-Wave performs two half-plane runs in the same grid. The first run is in the half-plane with the principle wave direction toward the shore. The second run is in the seaward half-plane as opposed to the first run. Upon the completion of the second run, two half-plane results are combined to one full-plane solution (Lin et al. 2012). Because the run time for the full-plane is approximately twice of the regular half-plane, users shall consider the full-plane mode only if the full-plane features like wave generation and propagation in a bay or around an island.

Half Plane

Source terms

CMS-Wave is a phase-averaged model for propagation of directional irre-gular waves over complicated bathymetry and nearshore where wave re-fraction, diffraction, reflection, shoaling, and breaking simultaneously act at inlets. Wave diffraction terms are included in the governing equations following the method of Mase et al. (2005). Four different depth-limiting wave breaking formulas can be selected as options including the interaction with a current. The wave-current interaction is calculated based on the dispersion relationship including wave blocking by an opposing current (Larson and Kraus 2002). Wave generation and whitecapping dissipation are based on the parameterization source term and calibration using field data (Lin and Lin 2004a and b, 2006a). Bottom friction loss is estimated from the classical drag law formula (Collins 1972).

Current interaction

Bottom friction

Bottom friction could be assigned as constant or by a dataset inside SMS. To see more details, see the Bottom and wall friction of the CMS Flow. Usually, the same roughness method used on CMS Wave is used on the CMS Flow parameters bottom friction. For a detail explanation of how Bottom Friction variable is used on the CMS Wave model, see Bottom Friction

Surge Fields

Wind Fields

If the spatial wind field input is required, users shall prepare a wind.dat file or *.wind (in the same format as *.cur) to provide the x- and y-component wind data corresponding to the incident wave conditions in the model grid.

Matrix Solver

https://cirpwiki.info/wiki/CMSFlow_Matrix_Solver

Boundary control

Water level and wind information are optional source as specified under Wave Source in addition to the spectral input data.

Source

Spatially varied spectral input – This is simply the case as in a child grid that spatially varied wave spectra are permitted to assign at user specified locations along or near the seaward boundary of the child grid. To apply spatially varied spectra for wave input without a parent grid, users will need to prepare the wave input file with the format as described in the child grid run.

https://cirpwiki.info/wiki/CMS-Wave_Input_Spectra

Interpolation

  • Inverse distance weighting

The inverse-distance interpolation also referred to as Shepard interpola-tion is given by (Shepard 1968)

  ϕ(x)=i=1Nwiϕi (17-1)

where the interpolation weights are given by

  wi=diρsjdjρs (17-2)

where

ρs = real and positive power parameter [-]

d = distance between the known points xi and the unknown interpolation points x equal to the Euclidean norm d=||xxi|| .

In this interpolation, the weight of each point decreases with distance from the interpolated point. One advantage of the inverse-distance interpolation is the interpolation weights are independent of the interpolation function, and therefore only need to be calculated once and can be saved for computational efficiency.[1]

Computational spectral grid

Spectral waves or wave parameters can be generated for the wave grid forcing, or wind direction and speeds can provide the necessary information for wind- wave generation. Full (directional) spectra can be imported into the SMS for the CMS-Wave, as well as simplified wave parameters (angle, wave height, and period, etc).

Sides

Case data

Wind direction angle conversion

  • Cartesian
  • Meteorologic
  • Oceanographic
  • Shore normal

Populate from Spectra

Set Reference Time

Output control

Limit observation output

Radiation stresses

Sea/swell

Breaking type

Options

To include (trigger) either of wave run-up, infra-gravity wave, nonlinear wave-wave interaction, binary (xmdf or *.h5) output, multiple processors, muddy bed, and spatial wind field input is just a one-click step in the SMS interface. Additional files are required for the muddy bed and spatial wind field input.

Allow wetting and drying

Infragravity wave effect

Diffraction intensity

Nonlinear wave effect

Run up

Fast-mode run

Roller effects

The wave roller parametric formulation is commonly applied in the wave spectral model to modify breaking wave energy dissipation nearshore to mimic better the surf zone dynamics. The wave roller effect used in CMS-Wave is based on the roller model developed by Zhang et al. (2014).

Forward reflection

Backward reflection

Muddy bed

If the muddy bed calculation is required, users shall prepare a mud.dat file or *.mud (in the same format as *.dep) to list the spatial varying max-imum kinematic viscosity for the entire grid (recommended maximum kinematic viscosity for mud is 0.04 m2/sec).

Wave breaking formula

Date format

To setup the model parameters for CMS-Wave:

1. Go to CMS-Wave, Model Control, Options and turn on Allow wetting and drying and Bed friction

2. Users can also specify constant or varied forward and backward reflection coefficients in Settings,



To read more about CMS Wave defintions, see CMS Wave Model Control Definitions

CMS-Wave Model Control File formats

The CMS-Wave Options File (*.std) can have one of 3 input formats. Click one of the options below for the format description.

1. No cards - order of values on one line is very important. (Used with SMS 11.1 and previous)
2. Card-based - [value] [!card name] (Used with SMS 11.2 to 13.1)
3. Card-based - [card name] [value(s)] (Used with SMS 13.2 and after)

Later versions of SMS can generally read the older formats, however exceptions have been found with Type 1 and listed on that page.


Back to CMS-Wave File Formats