SMS:PTM Boundary Condition File: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
(Created page with "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...")
 
No edit summary
Line 3: Line 3:


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 that some users may not have the ADCIRC interface enabled, or may have an existing mesh that they don't want to replace.
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 that some users may not have the ADCIRC interface enabled, or may have an existing mesh that they don't want to replace.
{{Template:Navbox SMS}}

Revision as of 15:35, 15 November 2012

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 that some users may not have the ADCIRC interface enabled, or may have an existing mesh that they don't want to replace.