|
Note: This postprocess mesh format requires GiD version 6.0 or higher.
Comments are allowed and should begin with a '#'. Blank lines are also allowed.
To enter the mesh names and result names in another encoding, just write # encoding your_encoding
for example:
# encoding utf-8
Inside this file one or more MESHes can be defined, each of them should:
MESH "mesh_name" dimension my_dimension Elemtype my_type Nnode my_number
where
- MESH, dimension, elemtype, nnode: are keywords that are not case-sensitive;
"mesh_name":
is an optional name for the mesh;
my_dimension:
is 2 or 3 according to the geometric dimension of the mesh;
my_type:
describes the element type of this MESH. It should be one of the following;Point, Linear, Triangle, Quadrilateral, Tetrahedra, Hexahedra, Prism, Pyramid, Sphere, Circle
;
my_number:
the number of nodes of my_type element:
- Point: 1 node,
Point connectivity:
![]()
- Linear: 2 or 3 nodes,
Line connectivities:
![]()
![]()
- Triangle: 3 or 6 nodes,
Triangle connectivities:
![]()
![]()
- Quadrilateral: 4, 8 or 9 nodes,
Quadrilateral connectivities:
![]()
![]()
![]()
- Tetrahedron: 4 or 10 nodes,
Tetrahedron connectivities:
![]()
![]()
- Hexahedron: 8, 20 or 27 nodes.
Hexahedron connectivities:
![]()
![]()
![]()
- Prism: 6 or 15 nodes,
Prism connectivities:
![]()
![]()
- Pyramid: 5 or 13 nodes,
Pyramid connectivities:
![]()
![]()
- Sphere: 1 node and a radius
- Circle: 1 node, a radius and a normal (x, y, z)
Note: For elements of order greater than linear, the connectivities must written in hierarchical order, i.e. the vertex nodes first, then the middle ones.
# color 127 127 0
In this way different colours can be specified for several meshes, taking into account that the # color line must be between the MESH line and the Coordinates line.
coordinates
1 0.0 1.0
3.0 . . .1000
-2.5 9.3 21.8
end coordinates
where
- the pair of keywords coordinates and end coordinates are not case-sensitive;
- between these keywords there should be the nodal coordinates of all the MESHes or the current one.
Note: If each MESH specifies its own coordinates, the node number should be unique, for instance, if MESH "mesh one" uses nodes 1..100, and MESH "other mesh" uses 50 nodes, they should be numbered from 101 up.
elements
#el_num node_1 node_2 node_3 optional_material_number
1 1 2 3 215
. . .
1000 32 48 23 215
end elements
where
- the pair of keywords elements and end elements are not case-sensitive;
- between these keywords there should be the nodal connectivities for the my_type elements.
Note: On elements of order greater than linear, the connectivities must written in hierarchical order, i.e. the vertex nodes first, then the middle ones;
- There is optionally a material number.
- For Sphere elements :
Element_number Node_number Radius [ optional_material_number]
- For Circle elements :
Element_number Node_number Radius [optional_normal_x optional_normal_y optional_normal_z] [optional_material_number]
If the normal is not written for circles, normal ( 0.0, 0.0, 1.0) will be used.
|
This example clarifies the description:
#mesh of a table
MESH "board" dimension 3 ElemType Triangle Nnode 3
# color 127 127 0
Coordinates
# node number coordinate_x coordinate_y coordinate_z
1 -5 3 -3
2 -5 3 0
3 -5 0 0
4 -2 2 0
5 -1.66667 3 0
6 -5 -3 -3
7 -2 -2 0
8 0 0 0
9 -5 -3 0
10 1.66667 3 0
11 -1.66667 -3 0
12 2 2 0
13 2 -2 0
14 1.66667 -3 0
15 5 3 -3
16 5 3 0
17 5 0 0
18 5 -3 -3
19 5 -3 0
end coordinates
#we put both material in the same MESH,
#but they could be separated into two MESH
Elements
# element node_1 node_2 node_3 material_number
5 19 17 13 3
6 3 9 7 3
7 2 3 4 3
8 17 16 12 3
9 12 16 10 3
10 12 10 4 3
11 7 9 11 3
12 7 11 13 3
13 2 4 5 3
14 5 4 10 3
15 19 13 14 3
16 14 13 11 3
17 3 7 4 3
18 17 12 13 3
19 13 12 8 4
20 13 8 7 4
21 7 8 4 4
22 4 8 12 4
end elements
MESH dimension 3 ElemType Linear Nnode 2
Coordinates
#no coordinates then they are already in the first MESH
end coordinates
Elements
# element node_1 node_2 material_number
1 9 6 5
2 19 18 5
3 16 15 5
4 2 1 5
end elements