SMS:PTM Boundary Condition File: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 4: Line 4:
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.
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.


==Related Topics==
*[[SMS:PTM Files|PTM Files]]





Revision as of 19:15, 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.

Related Topics