SMS:PTM Boundary Condition File: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
PTM_BC CMS-PTM v2.1.025 | PTM_BC CMS-PTM v2.1.025 | ||
When SMS reads the keyword (PTM_BC) in the header, it will then convert the file into a MIF/MID file, and read it into the GIS module. Blue is used to indicate open boundaries, and brown for closed boundaries. The reason for reading the file into the PTM interface and not the ADCIRC is | When SMS reads the keyword (PTM_BC) in the header, it will then convert the file into a MIF/MID file, and read it into the GIS module. Blue is used to indicate open boundaries, and brown for closed boundaries. The reason for reading the file into the PTM interface and not the ADCIRC is in case the ADCIRC interface is not enabled or if there is an existing mesh. | ||
Revision as of 19:14, 1 February 2016
This file follows the ADCIRC fort.14 format. The only difference is that the header line will identify the file as a PTM_BC file with a version number. Here is an example:
PTM_BC CMS-PTM v2.1.025
When SMS reads the keyword (PTM_BC) in the header, it will then convert the file into a MIF/MID file, and read it into the GIS module. Blue is used to indicate open boundaries, and brown for closed boundaries. The reason for reading the file into the PTM interface and not the ADCIRC is in case the ADCIRC interface is not enabled or if there is an existing mesh.
SMS – Surface-water Modeling System | ||
|---|---|---|
| Modules: | 1D Grid • Cartesian Grid • Curvilinear Grid • GIS • Map • Mesh • Particle • Quadtree • Raster • Scatter • UGrid |  |
| General Models: | 3D Structure • FVCOM • Generic • PTM | |
| Coastal Models: | ADCIRC • BOUSS-2D • CGWAVE • CMS-Flow • CMS-Wave • GenCade • STWAVE • WAM | |
| Riverine/Estuarine Models: | AdH • HEC-RAS • HYDRO AS-2D • RMA2 • RMA4 • SRH-2D • TUFLOW • TUFLOW FV | |
| Aquaveo • SMS Tutorials • SMS Workflows | ||
