Although PAM-STAMP might provide its own input file format, the oSP3D PAM-STAMP import interface only imports PAM-STAMP output files. Because Ansys has no access to documentation about the PAM-STAMP data file format, it has used customer-generated output as the reference data file format specification.
A typical file extension for a PAM-STAMP data file might be .asc. The file specification is given as follows:
Lines 1 and 2 are skipped. They may or may not be empty.
Words in a line are separated by one or more spaces.
Line 3 is expected to contain at least two words. The first word is skipped. The remaining words in the line are interpreted as the data identifier.
Lines 4 through 6 are skipped.
Line 7 is expected to contain two words. The first word is skipped. The second word is either
NODE
orELEMENT
, which instructs the interface to expect either nodal or element data.Lines 8 and 9 are skipped.
The remaining lines are read word-by-word until the end of the file is encountered. Exactly two words per line are expected. The first word must be of the data type
integer
and is interpreted as either a nodal or element identifier. The second word is interpreted as the associated scalar data value. An exception is a line with a zero entry only in the first column, which signals an imminent end of file. If valid data lines follow, they are still imported until the end of file is encountered.
PAM-STAMP Data File Example
114734 bend 8 Run_name Contour bend Unit NONE Dimension 1 Type SCALAR Entity ELEMENT State State 4/end : Time = 0.000000 Number 2 953005 -5.30040e-004 953006 2.08850e-004 0