HyperCrash

.mesh File

.mesh File

 Previous topic Next topic Expand/collapse all hidden text  

.mesh File

 Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

For each physical part declared in the .mcrash file, there will be a corresponding .mesh file.

In each .mesh file the declarations of the nodes, elements will be preceded by a header, which will contain the name of the part, the material name, the mesh class, the CAD design date, and the thickness.

The format of this header is described as follows: The name of a physical part file will be normalized. It will be of the following form:

NAME.mesh

Where NAME is the name of the part in the .mcrash file (no blank character in the name).

Header Format

First line:

#HyperCrash_PART

Where:

 

Type

Unit
•#HyperCrash_PART

is a keyword. This keyword is left justified.

Keyword

No

After this line, all lines beginning with a # are comment lines.

Parts

For each block describing one part, information will be contained here:

/HPART/part_id/nb_subpart/dd_mmm_yyyy/NAME/Class

Where:

 

Type

Unit
•HPART

is a keyword

Keyword

No
•part_id

is the identifier number of the part

Integer

No
•nb_subpart

is the number of subpart

Integer

No
•dd_mmm_yyyy

is the reference date defined with :

•dd: day (01 < Integer < 32)
•mmm: month

jan

January

feb

February

mar

March

apr

April

may

May

jun

June

jul

July

aug

August

sep

September

oct

October

nov

November

dec

December
•yyyy: year

Keyword

No
•NAME

is the name of the part

String

No
•Class

is the class of the part which can:

•0: special (several class en the same time) – default value.
•1: fine mesh
•2: fine mesh
•3: medium mesh
•4: coarse mesh

Integer

No

/SUBPART/subpart_id/subpart_name

Where:

 

Type

Unit
•SUBPART

is a keyword

Keyword

No
•subpart_id

is the identifier number of the subpart

Integer

No
•subpart_name

is the name of subpart

String

No

Card 1:

1

2

3

4

5

6

7

8

9

10

PID

MID

Class

 

 

 

 

 

 

 

Where:

 

Type

Unit
•PID

is a keyword

Keyword

No
•MID

is a keyword

Keyword

No
•Class

is the class of the part which can:

•0: special (several class at the same time) – default value.
•1: fine mesh
•2: fine mesh
•3: medium mesh
•4: coarse mesh

Integer

No

/MID/Mat_id/Mat_name

Where:

 

Type

Unit
•MID

is a keyword

Keyword

No
•Mat_id

is the identifier number of the material

Integer

No
•Mat_name

is the file name of the material which will be read in the $MCRASHDIR/mat (String with less than 9 characters).

String

No

The name of the material is the same as the file name of the same material in the database.

/PID/type/prop_id/thickness/unit

Where:

 

Type

Unit
•PID

is a keyword

Keyword

No
•type

is keyword to defined the type of property which can be:

•SHELL

Keyword

No
•prop_id

is the identifier number of the property

Integer

No
•thickness

is the thickness value of the part

Real

Length
•unit

is a keyword which defined the unit and can be:

•mm
•cm
•dm
•m
•inch
•ft

Keyword

No
hmtoggle_plus1Example

#HyperCrash_PART

/HPART/8/0/30_jul_1999/MEMBER_ENG_CRADLE/1

/MID/1/HST440

/PID/SHELL/1/2.00000/mm

#--1---|---2---|---3---|---4---|---5---|---6---|---7---|---8---|---9---|--10---|

 

#HyperCrash_PART

/HPART/76/2/SEATRAIL6S5AAV0_L/2

/SUBPART/1/shell19_jul_1999

      1       1       1

/MID/1/SP

/PID/SHELL/1/2.00000/mm

/SUBPART/2/beam

      2       2       0

/MID/2/SP

/PID/SHELL/2/1.20000/mm

#--1---|---2---|---3---|---4---|---5---|---6---|---7---|---8---|---9---|--10---|

 

Nodes

/NODE/unit

Where:

 

Type

Unit
•NODE

is a keyword

Keyword

No
•unit

is a keyword which defined the unit and can be:

•mm
•cm
•dm
•m
•inch
•ft

Keyword

No

Card 1:

1

2

3

4

5

6

7

8

9

10

NODID

XCOOR

YCOOR

ZCOOR

 

 

 

Where:

 

Type

Unit
•NODID

is the identifier number of the node

Integer

No
•XCOOR

is the node coordinate value in the first global coordinate system

Real

Length
•YCOOR

is the node coordinate value in the second global coordinate system

Real

Length
•ZCOOR

is the node coordinate value in the third global coordinate system

Real

Length
hmtoggle_plus1Example

#--1---|---2---|---3---|---4---|---5---|---6---|---7---|---8---|---9---|--10---|

/NODE/mm

      3      1072.15028      -146.71306        92.20811

      4      1072.15028      -162.30000        92.20811

      5      1083.68673      -162.30000        90.99558

      6      1095.22224      -162.30000        89.78315

#--1---|---2---|---3---|---4---|---5---|---6---|---7---|---8---|---9---|--10---|

 

Elements

/SH3N/Part_id

Where:

 

Type

Unit
•SH3N

is a keyword

Keyword

No
•Part_id

is the identifier number of the part or subpart of 3 node shell elements.

Integer

No

Card 1:

1

2

3

4

5

6

7

8

9

10

SH3N_ID

NOD1

NOD2

NOD3

 

 

 

 

 

 

Where:

 

Type

Unit
•SH3N_ID

is the identifier number of the 3 node shell element.

Integer

No
•NODi

are the identifier numbers of the node connectivity of the element.

Integer

No

/SHELL/part_id

Where:

 

Type

Unit
•SHELL

is a keyword

Keyword

No
•part_id

is the identifier number of the part or subpart of 4 node shell elements.

Integer

No

Card 1:

1

2

3

4

5

6

7

8

9

10

SHELL_ID

NOD1

NOD2

NOD3

NOD4

 

 

 

 

 

Where:

 

Type

Unit
•SHELL_ID

is the identifier number of the 4 node shell element.

Integer

No
•NODi

are the identifier numbers of the node connectivity of the element.

Integer

No
hmtoggle_plus1Example

#--1---|---2---|---3---|---4---|---5---|---6---|---7---|---8---|---9---|--10---|

/SH3N/1

     13      21       1      10

     15      23      13      14

     21      32      28      33

     22      29      28      34

/SH3N/2

     24      16      31      19

     25      17      18      32

     29      21      38      20

     30      35      37      39

     36      42      43      41

/SHELL/1

      1      11       5       6       7

      2      11       3       4       5

/SHELL/2

      3      12       8       9      10

      4       2       3      11      12

#--1---|---2---|---3---|---4---|---5---|---6---|---7---|---8---|---9---|--10---|

 

Note: SH3N and SHELL may not share the same ID and can only refer to nodes, parts and/or subparts defined in the same file.

End of the file

End of input data is signalled with:

/END

Where:

 

Type

Unit
•END

Keyword to finish the input.

Keyword

No

Go to

Specific HyperCrash Input Files