CMS-Flow Boundary Conditions/Tidal Database Nesting: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Extracted Water Levels from a Parent Simulation=
=Extracted Water Levels from a Tidal Database=
==Example: Tidal database boundary specification==
<pre>
BOUNDARY_BEGIN
  NAME "Offshore boundary"       
  CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
  WSE_BEGIN
      OFFSET_CONSTANT  0.0 m     
  WSE_END
  VEL_BEGIN           
  VEL_END
  TIDAL_DATABASE_BEGIN
      NAME  EC2001     
      PATH  "E:\Tidal_Databases\ec2001\"
      CONSTITUENTS  4 M2 S2 K1 O1 
  TIDAL_DATABASE_END
BOUNDARY_END
</pre>


==Example 1: Tidal database water level boundary specification==
*The NAME card is optional.
*The OFFSET_CONSTANT card within the WSE_BEGIN block is optional, however the WSE_BEGIN block itself is mandatory.
*The VEL_BEGIN/VEL_END cards are optional and only used for the ADCIRC databases. Without this card, CMS does not use velocity components to the tide and simulation results may be less accurate.
 
Within the TIDAL_DATABASE_BEGIN/END block, the names for the available options are given in the column titled '''CMS Database Name''' in the next table on this page. Note that the EC2015 and ENPAC2015 database options are only available in CMS versions 5.3.6 and later.
 
 
'''Note: in a future release of SMS 13.3, the corresponding tidal database files will be downloaded directly by SMS and the save location will be written to the .cmcards parameter file.


BOUNDARY_BEGIN
:NAME      "Offshore boundary"
:CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
:WSE_BEGIN
:WSE_END
:VEL_BEGIN
:VEL_END
:TIDAL_DATABASE_BEGIN
::NAME  EC2001 !EC001 | ENPAC2003 | FES95 | FES2004 | LEPROVOST
::PATH  "E:\Tidal_Databases\ec2001\"
:TIDAL_DATABASE_END
BOUNDARY_END


==Example 2: Tidal database water level boundary specification==
==Available tidal databases in CMS==
There are several tidal databases that are available for use.  CMS can handle many of these as described in the table below.
{| class="wikitable"
|-
! Database !! CMS Database Name !! Other Info
|-
| ADCIRC (latest) || EC2015, ENPAC2015 || Available from https://adcirc.org/products/adcirc-tidal-databases/
|-
| ADCIRC (previous) || EC2001, ENPAC2003 || Replaced by newer database, but still usable.
|-
| LeProvost || LEPROVOST || Free for use
|-
| Finite Element Solution&nbsp; || FES95, FES2004 || Supported, but possibly not free to use.
|}


BOUNDARY_BEGIN
==Unavailable tidal databases==
:NAME "Offshore boundary"
Presently unsupported database options.
:CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
{| class="wikitable"
:WSE_BEGIN
|-
::OFFSET  0.1 m  !Optional
! Database !! Description
:WSE_END
|-
:VEL_BEGIN
| TPXO || Oregon State Tidal Models
:VEL_END
|-
:TIDAL_DATABASE_BEGIN
| FES2014 || Latest FES Tidal database
::NAME  EC2001 !EC2001 | ENPAC2003 | FES95 | FES2004 | LEPROVOST
|}
::PATH  "E:\Tidal_Databases\ec2001\"
::CONSTITUENTS 4 M2 S2 K1 O1    !cnum cname(1:cnum), optional
:TIDAL_DATABASE_END
BOUNDARY_END

Latest revision as of 20:00, 19 December 2023

Extracted Water Levels from a Tidal Database

Example: Tidal database boundary specification

BOUNDARY_BEGIN
   NAME "Offshore boundary"        
   CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
   WSE_BEGIN
      OFFSET_CONSTANT  0.0 m       
   WSE_END
   VEL_BEGIN            
   VEL_END
   TIDAL_DATABASE_BEGIN
      NAME  EC2001      
      PATH  "E:\Tidal_Databases\ec2001\"
      CONSTITUENTS  4 M2 S2 K1 O1   
   TIDAL_DATABASE_END
BOUNDARY_END
  • The NAME card is optional.
  • The OFFSET_CONSTANT card within the WSE_BEGIN block is optional, however the WSE_BEGIN block itself is mandatory.
  • The VEL_BEGIN/VEL_END cards are optional and only used for the ADCIRC databases. Without this card, CMS does not use velocity components to the tide and simulation results may be less accurate.

Within the TIDAL_DATABASE_BEGIN/END block, the names for the available options are given in the column titled CMS Database Name in the next table on this page. Note that the EC2015 and ENPAC2015 database options are only available in CMS versions 5.3.6 and later.


Note: in a future release of SMS 13.3, the corresponding tidal database files will be downloaded directly by SMS and the save location will be written to the .cmcards parameter file.


Available tidal databases in CMS

There are several tidal databases that are available for use. CMS can handle many of these as described in the table below.

Database CMS Database Name Other Info
ADCIRC (latest) EC2015, ENPAC2015 Available from https://adcirc.org/products/adcirc-tidal-databases/
ADCIRC (previous) EC2001, ENPAC2003 Replaced by newer database, but still usable.
LeProvost LEPROVOST Free for use
Finite Element Solution  FES95, FES2004 Supported, but possibly not free to use.

Unavailable tidal databases

Presently unsupported database options.

Database Description
TPXO Oregon State Tidal Models
FES2014 Latest FES Tidal database
Retrieved from "https://cirpwiki.info/index.php?title=CMS-Flow_Boundary_Conditions/Tidal_Database_Nesting&oldid=14275"