CMS-Flow Boundary Conditions/Tidal Database Nesting
Jump to navigation
Jump to search
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. |
Presently unsupported database options.
Database | Description |
---|---|
TPXO | Oregon State Tidal Models |
FES2014 | Latest FES Tidal database |