Basic Functions > File Formats > A.2 The Neutral File
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
A.2 The Neutral File
The key element of the neutral system is the “neutral file.” The neutral file may contain:
• An analysis model.
• A geometry model.
• A conceptual solid model.
• Any or all of the models plus the GFEG and CFEG tables relating the geometry model to the analysis model.
The neutral file is organized into small “packets” of two or more card images. Each packet contains the data for a fundamental unit of the model, such as the coordinates and attributes of a specific node or the definition of a specific finite element. The formats of the various data packets are not text for any particular analysis program, and that is the basis for the term “neutral.”
Neutral File Packet Types Supported in Patran, 725 list all data packet types (if present) in the neutral file. Each data packet type is identified by a number. Individual packets within a given type are written in order of increasing ID number.
Neutral File Applications
There are many uses for the neutral file; some are obvious, others are more subtle. The applications of which we know are described briefly in the following paragraphs. If you find an additional use, please let us know about it.
 
Finite Element Model Output
The most common use of the neutral file is to output a finite element model for analysis. In this application, the neutral file is read by an application interface which converts Patran model data into the required input format for a particular analysis program. A typical example is the PATNAS interface which translates neutral file data into a bulk data deck for input to Nastran.
Geometry Model Output
It is also possible to output a neutral file containing mathematical definitions of a geometry model. Points, parametric cubic curves, parametric bi-cubic surfaces, and parametric tri-cubic solids are the only geometry forms which can be written to a neutral file. This information can then be accessed by programs that perform such functions as automated drafting or preparation of tapes for numerically controlled milling machines.
Finite Element Model Input
Through the use of an “inverse translator”, an existing finite element model in the form of an input deck for a particular analysis program can be input to Patran. Once in the Patran database, the model can be displayed interactively, modified if necessary, and even output to a different analysis program if desired.
Geometry Model Input
Dependent upon your particular engineering application, it may be cost effective to input part of your problem's geometry via the neutral file rather than the keyboard. This is especially true if points defining your geometry can be computed using relatively simple algorithms. In this case, rather than calculating coordinates of points and typing them into Patran by hand, try writing a short computer program to compute the coordinates and output them to a file in neutral file format.
Sub-Structuring
One of the most effective techniques for modeling a large, complex structure is to break it up into its component parts. Each component part is separated by identifying the finite element node locations at each interface. Then, each part can be modeled as a separate sub-structure independent of the other parts.
If modeling time is critical, the various sub-structures can be modeled simultaneously by different individuals.
An important point here is that each modeler can use Patran's default ID number assignments for his nodes, elements and geometry items without having to worry about later conflict with other sub-structures.
When each sub-structure is finished, it will be written into its own neutral file. Then, one by one, the individual sub-structure neutral files will be read into a single database. As each sub-structure neutral file is read, its ID numbers will be offset from those already present in the database.
The offsets can be specified, or Patran will determine them automatically.
Using nodal equivalencing, the duplicate nodes at the common boundaries can be combined to form a continuous model. See Equivalence Action (Ch. 9) in the Reference Manual - Part III for more information.
Database Editing
Since the neutral file can be written in card image form, it can be edited using an interactive editor. This capability can be useful for making minor changes to your model data before analysis translation.
Archive Model
Since neutral files are upwardly compatible from release to release, it is safe to store them in the neutral file format over long periods of time. Files can be kept on tape and archived for future reference.
Neutral File Format
All information in the neutral file is contained in small units referred to as “data packets”. Each data packet consists of a one card header record followed by one or more cards containing the data for a fundamental entity of the database such as a specific node, element, line or patch.
Neutral File Packet Types Supported in Patran, 725 list all data packet types (if present) in the neutral file. Each data packet type is identified by a number. Individual packets within a given type are written in order of increasing ID number.
Neutral File Types
Neutral files created by PATRAN Plus release 2.5 may be in either text (default) or binary format. In Patran, only the text file format is supported for import and export.
Neutral File Packet Types Supported in Patran
 
Type Number
Packet Description
Import
Export
25
File title
X
X
Summary data
X
X
Finite Element Model Packets
 
Type Number
Packet Description
Import
Export
Node data
X
X
Element data
X
X
Material properties
X
X
Element properties
X
X
Coordinate frames
X
X
Distributed loads
Normal Pressures
X
Node forces
X
X
Node displacements
X
X
9
Bar element initial displacements
 
 
Node temperatures
X
X
Element temperatures
X
 
12
DOF lists
 
 
13
Mechanism entities
 
 
MPC data
X
X
Nodal heat source
X
X
Distributed heat source
 
X
Convection coefficients
X
X
Radiation emissivity values
 
 
Viewfactor Data
 
 
Named components
X
X
Geometry Model Packets
 
Type Number
Packet Description
Import
Export
Grid data
X
X
Line data
X
X
Patch data
X
X
Hyperpatch data
X
X
36
Data-line data
 
 
37
Data-patch data
 
 
38
Data-hyperpatch data
 
 
39
Field data (coefficient format)
 
 
48
Field data (PCL format)
 
 
40
LIST card
 
 
41
DATA card
 
 
GFEG/CFEG Table Packets
 
Type Number
Packet Description
Import
Export
42
GFEG table for a line
X
 
43
GFEG table for a patch
X
 
44
GFEG table for a hyperpatch
X
 
CFEG table
X
 
Trimmed Surface Solid Model Packets
 
Type Number
Packet Description
Import
Export
46
Primitive data
 
 
47
Primitive face data
 
 
End of file flag
X
X
PATRAN 2.5 Neutral File Packet Header
The header card for each data packet contains the following information:
 
Header Card
Format
(I2,8I8)
IT
ID
IV
KC
N1
N2
N3
N4
N5
 
IT
=
Packet Type
 
ID
=
Identification number. A “0” ID means not applicable (n/a)
 
IV
=
Additional ID. A “0” value means not applicable (n/a).
 
KC
=
Card Count (number of data cards after the header)
 
N1 to N5 =
Supplemental integer values used and defined as needed
The header card is followed by “KC” data card images. The meaning of the header variables for each packet type plus the content and format of its data cards are presented in PATRAN 2.5 Neutral File Contents and Format, 727. The packet types are listed in the order of their appearance (if present) in the neutral file.
PATRAN 2.5 Neutral File Contents and Format
Packet Type 25: Title Card
 
Header Card
Format
 
(I2,8I8)
25
ID
IV
KC
 
 
 
 
 
ID = 0 Not applicable
IV = 0 Not applicable
KC = 1
User Title Card
 
Format
(20A4)
h3
 
 
 
 
 
 
 
h3
= Identifying title may contain up to 80 Characters
 
 
Packet Type 26: Summary Data
 
Header Card
Format
(I2,8I8)
26
ID
IV
KC
N1
N2
N3
N4
N5
ID = 0 n/a
N1 = Number of Nodes
IV = 0 n/a
N2 = Number of Elements
KC = 1
N3 = Number of Materials
 
 
 
N4 = Number of Element Properties
 
 
N5 = Number of Coordinate Frames
Summary Data Card
Format
 
(3A4, 2A4, 3A4)
DATE
TIME
VERSION
 
 
 
 
 
DATE
= Date neutral file was created
 
 
 
TIME
= Time neutral file was created
 
 
 
 
VERSION
= Patran release number
 
 
 
 
Packet Type 01: Node Data
Header Card
Format
 
(I2,8I8)
1
ID
IV
 
KC
 
 
 
 
 
ID = Node ID
 
 
 
 
 
 
IV = 0 n/a
 
 
 
 
 
 
KC = 2
 
 
 
 
 
Data Card 2
 
Format
(I1, 1A1, I8, I8, I8, 2X, 6I1)
ICF
GTYPE
NDF
CONFIG
CID
PSPC
 
ICF* = Condensation flag (0 = unreferenced)
GTYPE = Node type
NDF* = Number of degrees-of-freedom
CONFIG = Node configuration
CID = Coordinate frame for analysis results
PSPC* = 6 permanent single point constraint flags 0 or 1
* These parameters are not currently used.
Data Card 1
 
Format
(3E16.9)
 
 
X
Y
Z
 
 
 
 
 
 
 
X = X Cartesian Coordinate of Node
 
 
 
 
Y = Y Cartesian Coordinate of Node
 
 
 
 
Z = Z Cartesian Coordinate of Node
 
 
 
Packet Type 02: Element Data
 
Header Card
Format
 
(I2,8I8)
2
ID
IV
KC
N1
N2
 
 
 
ID = Element ID
IV = Shape (2 = bar, 3 = tri, 4 = quad, 5 = tet, 7 = wedge, 8 = hex)
KC = 1 + (NODES + 9)/10 + (N1 +4)/5 (for text files)
N1 = Number of associate data values
N2 = ID of node in XY-plane (bar only)
Data Card 1
 
Format
(I8, I8, I8, I8, 3E16.9)
NODES
CONFIG
PID
CEID
θ1
θ2
θ3
NODES = Total number of nodes
CONFIG* = Element configuration
PID = Property ID (+) or material ID (-)
CEID = Congruent element ID
θ1, θ2, θ3 = Material Orientation angles (for bars, these values are the coordinates of a point in the bar X”Y-plane)
*Config is used to specify the element type needed to interpret the element data in Packet Type 04.
Data Card 2
 
Format
(10I8)
LNODES
 
 
 
 
 
 
LNODES = Element corner nodes followed by additional nodes (for bars, two additional values beyond the last node contain pin flags*).
* Pin Flags are not currently supported.
Data Card 3
 
Format
(5E16.9)
ADATA
 
 
 
 
 
 
ADATA† = Associate data values (For bars, these are coordinates of the bar ends if offset from end nodes).
†ADATA will not be present if N1 is zero
Packet Type 03: Material Properties
 
Header Card
Format
 
(I2,8I8)
3
ID
IV
KC
N1
 
 
 
 
ID = Material ID
IV = Material type* (1-13)
KC = 20 + (N1 +4)/5 (for text files)
N1 = Number of associate ply data values
Data Card 2
 
Format
(5E16.9)
DATA
 
 
 
 
 
 
DATA = 96 Material property constants**
Data Card 3
 
Format
(5E16.9)
ADATA
 
 
 
 
 
 
ADATA* = Associated ply data values (thicknesses, orientation angles, material ID’s.)
*ADATA will not be present if N1 is 0.
*Material Types:
 
1 Isotropic
4 TIS option
11 HAL option
2 2D anisotropic
5 TAN option
12 LLAM option
3 3D orthotropic
6-7 3D anisotropic
13 MIX option
**Material Property Constants.
 
1 Reference temperature (T)
2 Density (ρ)
3 Total thickness (laminate materials only)
4 Number of plies (laminate material only)
5 Offset (laminate materials only)
6 Structural damping coefficient (GE)
7 Density(ρ) S Specific heat (CP)
8 Option = material type
9-14 6 Thermal expansion coefficients (α11, α22, α33, α12, α23, α31)
15-20 6 Thermal conductivities (K11, K12, K13, K22, K23, K33)
21-26 2D thermal stress resultants for 1-degree temperature rise
(N1, N2, N12, M1, M2, M12)
27-35 9 engineering material properties (E11, E22, E33, v12, v23, v31, G12, G23, G31)
36 0 = Not applicable
37-57 21 material stiffness matrix terms (C11, C12, C13, C22, C23, C33, C44, C45, C46, C55, C56, C66, C14, C15, C16, C24, C25, C26, C34, C35, C36)
58-63 6 2D membrane stiffness matrix terms (A11, A12, A13, A22, A23, A33)
64-69 6 2D bending stiffness matrix terms (D11, D12, D13, D22, D23, D33)
70-78 9 2D membrane/bending coupling terms (B11, B12, B13, B21, B22, B23, B31, B32, B33)
79-81 Stress limits for tension, compression, and shear (ST, SC, SS)
82 Emissivity
83-88 Not applicable at present
89 Reserved
90-91 Not applicable at present
 
Packet Type 04: Element Properties
 
Header Card
Format
(I2,8I8)
4
ID
IV
KC
N1
N2
N3
N4
 
ID = Property ID N1* = Shape
IV = Material ID N2 = Nodes
KC = (N4 + 4)/5 N3* = Configuration
N4 = Number of data fields
* Definition of applicable element type (see Packet Type 02)
Data Card
 
Format
(6X,AX,6X) for Character Data,
(E16.9) for Numeric Data
DATA
 
 
 
DATA = Property data for the defined element type as required by the
analysis program. (1 to 5 property fields per record in 16 character fields.)
Packet Type 05: Coordinate Frames
 
Header Card
Format
 
(I2,8I8)
5
ID
IV
KC
 
 
 
 
 
ID = Coordinate frame ID
IV = Coordinate type (1 = rectangular, 2 = cylindrical, 3 = spherical)
KC = 4 (for text files)
Data Card 1 to 4
 
Format
(5E16.9)
A1 A2 A3 B1 B2 B3 C1 C2 C3 R(1,1) R(2,1)......R(3,3)
A1, A2, A3
B1, B2, B3,
C1, C2, C3,

Coordinates of 3 points defining the coordinate frame.
(See Chapter 9, .Cord - Coordinate Frame Directives.)
R
3 x 3 rotation matrix to transform coordinates from this frame to the global rectangular frame.
Packet Type 06: Distributed Loads
 
Header Card
Format
 
(I2,8I8)
6
ID
IV
KC
 
 
 
 
 
ID = Element ID
IV = Load Set ID
KC = 1 + NPV + 4)/5 (for text files)
Data Card 1
 
Format
(I1, I1, I1, 6I1, 8I1, I2)
6
LTYPE
EFLAG
CFLAG
ICOMP(6)
NODE(8)
NFE
 
 
LTYPE = Load type (0 = line. 1 = surface)
EFLAG = Element flag (0 or 1)
CFLAG = Node flag (0 or 1)
ICOMP = 6 load component flags (0 or 1)
NODE = 8 element node flags (0 or 1)
NFE = Edge number 1-12) or face number (1-6)
Data Card 2 to KC
Format
(5E16.9)
PDATA
 
 
 
 
 
 
 
PDATA = Non-zero load components *
* Define NC = Number of ICOMP flags on (=1)
NN = Number of NODE flags on (=1)
Then, the number of PDATA entries:
NPV = NC*(EFLAG + NN*GFLAG)
Order of PDATA is as follows:
1. NC load values at centroid of loaded region (if EFLAG = 1).
2. NC load values at each corner node on the loaded region (if GFLAG = 1).
The NODE flags correspond to the LNODES nodes in Packet type 02.
Packet Type 07: Node Forces
 
Header Card
Format
 
(I2,8I8)
7
ID
IV
KC
 
 
 
 
 
ID = Node ID
 
 
 
 
IV = Load Set ID
 
 
 
 
KC = 1 + (NDW +4)/5 (for text files)
 
 
 
 
Data Card 1
 
Format
(I8, 6I1)
CID
ICOMP(6)
 
 
 
 
 
CID = Coordinate frame ID
ICOMP = 6 force component flags (0 or 1)
Data Card 2 to KC
Format
(5E16.9)
FDATA
 
 
 
 
 
 
FDATA = Non-zero force components
NDW = Sum of ICOMP(I), I=1,6
Packet Type 08: Node Displacements
 
Header Card
Format
 
(I2,8I8)
8
ID
IV
KC
 
 
 
 
 
ID = Node ID
 
 
 
 
IV = Constraint set ID
 
 
 
 
KC = 1 + (NDW +4)/5 (for text files)
 
 
 
 
Data Card 1
 
Format
(I8, 6I1)
CID
ICOMP(6)
 
 
 
 
 
CID = Coordinate frame ID
ICOMP = 6 displacement component flags (0 or 1)
Data Card 2
Format
(5E16.9)
FDATA
 
 
 
 
 
 
FDATA = Non-blank displacement components (may be 0.0)
NDW = Sum of ICOMP(I), I=1,6
Packet Type 10: Node Temperatures
 
Header Card
Format
 
(I2,8I8)
10
ID
IV
KC
N1
N2
 
 
 
ID =Node ID N1 = Data flag 1: TEMP is temp value
IV =Temperature set ID 0: TEMP is dummy value
KC =1 N2* = User function
* This parameter is not currently used.
Data Card 1
Format
(E16.9)
TEMP
 
 
 
 
 
 
TEMP = Temperature value
Packet Type 11: Element Temperatures
 
Header Card
Format
 
(I2,8I8)
11
ID
IV
KC
N1
N2
 
 
 
ID =Element ID N1 = Data flag 1: TEMP is temp value
IV =Temperature set ID 0: TEMP is dummy value
KC =1 N2* = User function ID
* This parameter is not currently used.
Data Card 1
Format
(E16.9)
TEMP
 
 
 
 
 
 
TEMP = Temperature value
Packet Type 14: MPC Data
 
Header Card
 
Format
(I2,8I8)
 
 
 
14
ID
IV
KC
NT
NDT
 
 
 
ID = MPC ID
 
 
 
 
IV = MPC SID
 
 
 
 
KC = 2 + (NT +1)/2 (for text files)
 
 
 
 
 
NT = Total number of terms (Right side of equation)
 
NDT = Number of dependent terms (Implicit MPC)
 
 
Data Card 1
 
Format
(3A12)
DN
IN
TYPE
 
 
 
 
 
 
DN = Dependent name ID (not used)
IN = Independent name ID (not used)
TYPE = MPC or your own type name (maximum of 12 characters)
entered in option field of MPC ADD command.
Data Card 2
 
Format
(2I8, E16.9)
NID
DOF
CO
 
 
 
 
 
 
NID = Dependent node ID
DOF = Dependent degree-of-freedom
C0 = Constant term
 
Data Card 3
 
Format
2(2I8, E16.9)
NID(I),
DOF(I),
CO(I),
I = 1, NT
 
 
 
 
First NDT terms are dependent otherwise, terms are independent
NID(I) = Node ID
DOF(I) = degree-of-freedom
C0(I) = Constant coefficient
 
The form of the MPC equation is assumed to be:
where is specified by NID(I) and DOF(I) and is specified by C(I).
Packet Type 15: Nodal Heat Source
 
Header Card
Format
 
(I2,8I8)
15
ID
IV
KC
N1
N2
 
 
 
ID = Node ID N1 = Data flag 1: HEAT is heat flux value
IV = Heat Flux Set ID 0: HEAT is dummy value
KC = 1 N2* = User function ID
* This parameter is not currently used.
Data Card 1
Format
(E16.9)
HEAT
 
 
 
 
 
 
HEAT = Heat flux value
Packet Type 16: Distributed Heat Source
 
Header Card
Format
 
(I2,8I8)
16
ID
IV
KC
N1
N2
N3
 
 
ID = Element ID
N3 = Dimension code
         0  No heat flux dimension
         1  HEAT is per unit length
         2  HEAT is per unit area
         3  HEAT is per unit volume
IV = Heat Flux Set ID
KC = 1 + (NN + 4)/5 (for text files )
2                        (for binary files)
N1 = Data flag
1: HEAT is a heat flux value
0: HEAT is dummy value
 
 
 
 
N2 = User function ID
 
 
 
 
Data Card 1
Format
(I1, 1X, 8I1)
NFLAG
NODE(8)
 
 
 
 
 
NFLAG = Node flag (0 or 1)
NODE = 8 element node flags (0 or 1)
Data Card 2-KC
Format
(5E16.9)
HEAT(5)
 
 
 
 
 
 
HEAT = Distributed heat flux values*
*If N1 is zero, HEAT = 0.0 (dummy value). Otherwise:
If NFLAG = 0, one HEAT value
If NFLAG = 1, NN HEAT values
 where NN = number of NODE flags on(= 1). The NODE flags correspond to the LNODES
 corner nodes in Packet 02.
Packet Type 17: Convection Coefficients
 
Header Card
Format
 
(I2,8I8)
17
ID
IV
KC
N1
N2
 
 
 
ID = Element ID N1 = Data flag 1: CONV is a convection coefficient value
IV = Convection coefficient set ID
KC = 1 + (NN + 4)/5 (for text files) 0: CONV is dummy value
N2* = User function ID
* This parameter is not currently used.
Data Card 1
Format
(I1, 1X, 8I1)
NFLAG
NODE(8)
 
 
 
 
 
NFLAG = Node flag (0 or 1)
NODE = 8 element node flags (0 or 1)
Data Card 2
Format
(5E16.9)
CONV(5)
 
 
 
 
 
 
CONV = Convection coefficient values*
*If N1 is zero, CONV = 0.0 (dummy value). Otherwise:
If NFLAG = 0, one CONV value
If NFLAG = 1, NN CONV values
 where NN = number of NODE flags on(= 1) The NODE flags correspond to the LNODES
 corner nodes in Packet 02.
Packet Type 18: Radiation Emissivity Values
 
Header Card
Format
 
(I2,8I8)
18
ID
IV
KC
N1
N2
 
 
 
ID = Element ID N1 = Data flag
IV = Convection coefficient set ID 1: EMIS is a emissivity value
0: EMIS is dummy value
KC = 1 + (NN + 4)/5 (for text files )
N2 = User function ID
Data Card 1
Format
(I1, 1X, 8I1)
NFLAG
NODE(8)
 
 
 
 
 
NFLAG = Node flag (0 or 1)
NODE = 8 element node flags (0 or 1)
Data Card 2
Format
(5E16.9)
EMIS(5)
 
 
 
 
 
 
EMIS = Convection coefficient values*
*If N1 is zero, EMIS = 0.0 (dummy value). Otherwise:
If NFLAG = 0, one EMIS value
If NFLAG = 1, NN EMIS values
 where NN = number of NODE flags on(= 1). The NODE flags correspond to the LNODES
 corner nodes in Packet 02.
Packet Type 19: Viewfactor Data
 
Header Card
Format
 
(I2,8I8)
18
ID
IV
KC
N1
N2
 
 
 
ID = Element ID N1 = Not used
IV = Enclosure ID N2 = User function ID
KC = 1
Data Card 1
        Format
(6I8,2X,8I1)
NODE1
NODE2
CVSID
OBSTR
DYN
SURF
NODE(8)
NODE1 = First Reference Node ID
NODE2 = Second Reference Node ID
CVSID = Convex Surface ID
OBSTR = Non-obstruction Flag
(0 = potential obstruction, 1 = non-obstruction)
DYN = Dynamic Flag (0 or 1)
SURF = Surface (0 = top, 1 = bottom)
NODE(8) = 8 element node flags (0 or 1)
 
* This parameter is not currently used.
Packet Type 21: Named Components
 
Header Card
Format
 
(I2,8I8)
21
ID
IV
KC
 
 
 
 
 
ID = Component number
IV = 2 times the number of data pairs
KC = 1 + (IV + 9)/10 (for text files)
1 + (IV + 509)/510 (for binary files)
Data Card 1
Format
(A12)
NAME
 
 
 
 
 
 
NAME = Component Name
Data Card 2
Format
 
(10I8)
   NTYPE(1)*
ID(1)
NTYPE(2)
ID(2)
........
NTYPE(5)
ID(5)
 
 
(NTYPE(i), ID(i)) = Data pairs defining type and ID number of each item in this
(I = 1, IV/2) component.
*NTYPE meanings:
 
1 grid#
  8 quadrilateral
2 line
  9 tetrahedron
3 patch
11 wedge
4 hyperpatch
12 hexahedron
5 node
19 coordinate frame
6 bar
22 multi-point constraints
7 triangle
 
 
 
NTYPEs 6-12 may have 100 or 200 added to the basic NTYPE. The number of hundreds is usually the number of midside nodes.
Packet Type 31: Grid Data
 
Header Card
Format
 
(I2,8I8)
31
ID
IV
KC
 
 
 
 
 
ID = Grid ID
IV = 0 not/applicable
KC = 1
Data Card 1
 
Format
(3E16.9)
X
Y
Z
 
 
 
 
 
 
X,Y,Z = Cartesian coordinates of Grid
Packet Type 32: Line Data
 
Header Card
Format
 
(I2,8I8)
32
ID
IV
KC
 
 
 
 
 
ID = Line ID
IV = 0 not/applicable
KC = 3 (for text files)
Data Card 1 to 3
 
Format
(5E16.9/5E16.9/2E16.9,2I8)
B(1,1),
B(2,1)
B(3,1)
.....
 
 
B(4,3)
IG1
IG2
B(I,J) = 4 x 3 matrix of geometric format line coefficients
IG1, IG2 = End point grid ID’s
Packet Type 33: Patch Data
 
Header Card
Format
 
(I2,8I8)
33
ID
IV
KC
 
 
 
 
 
ID = Patch ID
IV = 0 not/applicable
KC = 10 (for text files)
Data Card 1 to 10
 
Format
9(5E16.9/5), 3E16.9/2E16.9,4I8
B(1,1),
B(2,1)
B(3,1)
.....
 
 
 
B(16,3)
IG(4)
B(I,J) = 16 x 3 matrix of geometric format patch coefficients
IG = 4 corner grid ID’s
Packet Type 34: Hyperpatch Data
 
Header Card
Format
 
(I2,8I8)
34
ID
IV
KC
 
 
 
 
 
ID = Hyperpatch ID
IV = 0 not/applicable
KC = 40 (for text files)
Data Card 1 to 40
 
Format
38(5E16.9/), 3E16.9/,8I8
B(1,1),
B(2,1)
B(3,1)
.....
 
 
 
B(64,3)
IG(8)
B(I,J) = 64 x 3 matrix of geometric format hyperpatch coefficients
IG = 8 corner grid ID’s
Packet Types 42, 43 or 44: GFEG Table for Line, Patch or Hyperpatch 1
(when created from a GFEG command)
 
Header Card
Format
 
(I2,8I8)
IT
ID
IV
KC
N1
N2
 
 
 
IT = 42, 43, or 44
ID = Line, patch or hyperpatch ID
IV = Number of nodes contained in region
KC = 5 +IV (for text files)
N1 = 1 (signifies this packet is 2.0 format)*
* This parameter is not currently used.
Header Card
 
Format
(I8, 3I8, I8, 5I8)
IDELTA
N1
N2
N3
MAXMAG
IFACE
 
IDELTA* = Integer parametric mesh increment
N1, N2, N3* = Number of nodes in ζ1, ζ2 and ζ3 directions
MAXMAG* = Maximum magnification power
IFACE* = Face degeneracy flags (faces 1 through 5)
* This parameter is not currently used.
Data Card 2
 
Format
(I8, I8, 7X, 1A1, 7I8)
IFACE NCONDF NGTYPE NDF NCONF GCID PS NGDAT ISTMID ICFLAG
IFACE* = Face degeneracy flag (face 6)
NCONDF* = Condensation flag (0 = unreferenced)
NGTYPE* = Node type
NDF* = Number of degrees-of-freedom
NCONF* = Configuration number
GCID* = Analysis coordinate frame ID
PS* = Permanent single point constraint
NGDATA* = Pointer to auxiliary data
ISTMID* = Location of first added midnode
IGFLAG = Type of GFEG table: 0 = table created by GFEG
* This parameter is not currently used.
Data Card 3
 
Format
(3E16.9)
STRTCH
 
 
 
 
 
 
 
STRTCH(3) = Mesh ratios
Data Card 4
 
Format
(3E16.9)
AUXC
 
 
 
 
 
 
 
AUXC = Auxiliary mesh constants
Data Card 5
 
Format
(8I8, I8, I8)
IDUM(8)
IOLD
NACTUL
 
 
 
 
IDUM(8) = Reserved for future use
IOLD = Table format flag (for database conversion)
NACTUL = Number of existing nodes
 
 
Data Cards 6 to KC
 
Format
(3E16.9, I8, I8)
XI(3)
NFLAG
NID
 
 
 
 
 
Node data
XI(3) = Real parametric coordinates in ζ1, ζ2 and ζ3 directions
of parent line, patch or hyperpatch
NFLAG = Flag word
NID = Node ID number
+ if specified by user,
- if assigned by Patran
Packet Type 42, 43 or 44: GFEG Table for Line, Patch or Hyperpatch (when created from a MESH command)
 
Header Card
Format
 
(I2,8I8)
IT
ID
IV
KC
N1
N2
 
 
 
IT = 42, 43, or 44
ID = Line, patch or hyperpatch ID
IV = Number of nodes contained in region
KC = 5 +IV (for text files)
N1 = 1 (signifies this packet is 2.0 format)*
* This parameter is not currently used.
Data Card 1
 
Format
(I0I8)
NL1
NL2
NL3
NL4
NL5
IFACE
 
 
NL1,..NL4 = Number of elements on edges 1 through 4
NL5 = Number of elements through thickness (for hyperpatch)
IFACE* = Face degeneracy flags (faces 1 through 5)
* This parameter is not currently used.
Data Card 2
 
Format
(I8, I8, 7X, 1A1, 7I8)
IFACE NCONDF NGTYPE NDF NCONF GCID PS NGDAT ISTMID ICFLAG
IFACE* = Face degeneracy flag (face 6)
NCONDF* = Condensation flag (0 = unreferenced)
NGTYPE* = Node type
NDF* = Number of degrees-of-freedom
NCONF* = Configuration number
GCID* = Analysis coordinate frame ID
PS* = Permanent single point constraint
NGDATA* = Pointer to auxiliary data
ISTMID* = Location of first added midnode
IGFLAG = Type of GFEG table: >0 = table created by GFEG
* This parameter is not currently used.
 
Data Card 3
 
Format
(3E16.9)
STRTCH
 
 
 
 
 
 
 
STRTCH = Mesh ratios for edges 1, 2 and 3
Data Card 4
 
Format
(3E16.9)
STRTCH
 
 
 
 
 
 
 
STRTCH = Mesh ratios for edge 4 and ζ3 direction (followed by one word
reserved for future use)
Data Card 5
 
Format
(8I8, I8, I8)
IDUM(8)
IOLD
NACTUL
 
 
 
 
IDUM(8) = Reserved for future use
IOLD = Table format flag (for database conversion)
NACTUL = Number of existing nodes
Data Cards 6 to KC
 
Format
(3E16.9, I8, I8)
XI(3)
NFLAG
NID
 
 
 
 
 
Node data
XI(3) = Real parametric coordinates in ζ1, ζ2 and ζ3 directions
of parent line, patch or hyperpatch
NFLAG = Flag word
NID = Node ID number
+ if specified by user,
- if assigned by Patran
Packet Type 45: CFEG Table
 
Data Card 1
 
Format
(6I8)
LPH
ID
LSHAPE
DGFLAG
MINID
MIAXID
LPH = Type of region (2=line, 3=patch, 4=hyperpatch)
ID = ID of line, patch, or hyperpatch
LSHAPE = Element shape (2=bar, 3=tri, 4=quad, 5=tet, 7=wedge, 8=hex)
DGFLAG* = Degenerate element flag (1 indicates one or more degenerate
elements are present in this CFEG)
MINID = Minimum element ID
MAXID = Maximum element ID
* This parameter is not currently used.
Data Card 2
 
Format
(6I8)
NDIM
LSHAPE
NODES
ICONF
LPH
ID
LPROP
NPROP
 
NDIM = Number of words per element record
LSHAPE = Element shape
NODES = Number of nodes per element
ICONF* = Element configuration
LPH = Type of region
ID = ID of region
LPROP* = Property ID flag (0 = PID, 1 = MID)
 
NPROP* = Property ID (+ = PID, - = MID)
 
* This parameter is not currently used.
Data Card 2 to KC
Format
(10I8)
LCON(10)
 
 
 
 
 
 
LCON(10) = Element data (NELS records with NDIM words per second)
Words 1 through NODEs = Element Nodes*
Word NDIM =Element ID number
+ if specified by user
- if assigned by Patran
*These are local node ID numbers corresponding to record numbers in the associated GFEG table.
Packet Type 99: End of Neutral File
 
Header Card
Format
 
(I2,8I8)
45
ID
IV
KC
N1
N2
 
 
 
ID = CFEG sequence number
IV = Number of elements contained in region (NELS)
KC = 2 + ((IV * NDIM) + 9)/10
N1* = Reserved
* This parameter is not currently used.
Header Card
 
Format
(I2, 8I8)
99
ID
IV
 
KC
 
 
 
 
ID = 0 not/applicable
IV = 0 not/applicable
KC = 1
1 The format of the GFEG tables changed with Patran release 2.0.