Interfacing with PAM-CRASH 2G

This section discusses how the HyperGraph applications interface with the PAM-CRASH 2G solver.

HyperGraph hgdaisy External Reader

Description	Supports	Does Not Support
Reads PAM-CRASH and PAM-CRASH 2G DSY files (results files generated by the solver) into HyperGraph. The PAM-CRASH DSY reader is enhanced to handle higher version result files. No ESI license is required to use this reader.	NODES Displacements Velocities Accelerations BEAMS and BARS FAXI Axial force FSSH Transverse S Shear force FTSH Transverse T shear force MTOR Torsion moment MSN1 S moment at n1 MTN1 T moment at n1 MSN2 S moment at n2 MTN2 T moment at n2 SHELLS MXX Local bending moment about x-axis MYY Local bending moment about y-axis MXY Local twisting moment in xy plane EPMA Maximum plastic strain over thickness EPMI Minimum plastic strain over thickness NXX Local membrane stress resultant in x-direction NYY Local membrane stress resultant in y-direction NXY Local in-plane shear membrane stress resultant THIC Resultant shell thickness SOLIDS SXX Stress in X-direction SYY Stress in Y-direction SZZ Stress in Z-direction SXY Shear stress in XY-direction SYZ Shear stress in YZ-direction SZX Shear stress in ZX-direction EPLE Equivalent plastic strain TOOLS THIC Resultant shell thickness	Stamp options.

Description

Supports

Does Not Support

Reads PAM-CRASH and PAM-CRASH 2G DSY files (results files generated by the solver) into HyperGraph.

The PAM-CRASH DSY reader is enhanced to handle higher version result files.

No ESI license is required to use this reader.

NODES

Displacements

Velocities

Accelerations

BEAMS and BARS

FAXI: Axial force
FSSH: Transverse S Shear force
FTSH: Transverse T shear force
MTOR: Torsion moment
MSN1: S moment at n1
MTN1: T moment at n1
MSN2: S moment at n2
MTN2: T moment at n2

SHELLS

MXX: Local bending moment about x-axis
MYY: Local bending moment about y-axis
MXY: Local twisting moment in xy plane
EPMA: Maximum plastic strain over thickness
EPMI: Minimum plastic strain over thickness
NXX: Local membrane stress resultant in x-direction
NYY: Local membrane stress resultant in y-direction
NXY: Local in-plane shear membrane stress resultant
THIC: Resultant shell thickness

SOLIDS

SXX: Stress in X-direction
SYY: Stress in Y-direction
SZZ: Stress in Z-direction
SXY: Shear stress in XY-direction
SYZ: Shear stress in YZ-direction
SZX: Shear stress in ZX-direction
EPLE: Equivalent plastic strain

TOOLS

THIC: Resultant shell thickness

Stamp options.

Usage

To run from the command prompt to convert PAM-CRASH or PAM-CRASH 2G DSY files into Altair Binary Files (ABF files):

-hgdaisy dsyfile outfile.

To run in HyperGraph:

By default this reader is registered. If it is not, please register it before reading DSY files. It is located in the HWDIR\externalreaders\bin\$PLATFORM\plot directory. After registering the reader, you can read DSY files directly into HyperGraph.

HyperGraph hgthp Result Reader

Description	Supports
Reads PAM-CRASH and PAM-CRASH 2G THP binary files (time history files generated by the solver) into HyperGraph. Also reads ASCII files generated by exporting curves from PAMVIEW. hgthp can be run from the command prompt to convert THP files into Altair Binary Files (ABF files). The PAM-CRASH THP reader is enhanced to handle higher version result files. No ESI license is required to use this reader.	The PAM-CRASH and PAM-SAFE options. Solid Elements Only the first seven variables of Table A in the PAM-CRASH Notes Manual, Plot Output 5, (output qualifiers SXYZ and EPLE). Shell and Membrane Elements Only the first fourteen variables of Table A in the PAM-CRASH Notes Manual, Plot Output 7, (output qualifiers MXYZ to STRA). Beam and Bar Elements Only the first fourteen variables of Table A in the PAM-CRASH Notes Manual, Plot Output 13, (output qualifiers FAXI to RTN2). Results for nodal time histories, transmission sections, airbags, airbag chambers, airbag walls, materials, contacts, and rigid walls are also supported. A new data type, shell_user, is added to display the results for user-defined shell materials.

Description

Supports

Reads PAM-CRASH and PAM-CRASH 2G THP binary files (time history files generated by the solver) into HyperGraph.

Also reads ASCII files generated by exporting curves from PAMVIEW.

hgthp can be run from the command prompt to convert THP files into Altair Binary Files (ABF files).

The PAM-CRASH THP reader is enhanced to handle higher version result files.

No ESI license is required to use this reader.

The PAM-CRASH and PAM-SAFE options.

Solid Elements: Only the first seven variables of Table A in the PAM-CRASH Notes Manual, Plot Output 5, (output qualifiers SXYZ and EPLE).

Shell and Membrane Elements: Only the first fourteen variables of Table A in the PAM-CRASH Notes Manual, Plot Output 7, (output qualifiers MXYZ to STRA).

Beam and Bar Elements: Only the first fourteen variables of Table A in the PAM-CRASH Notes Manual, Plot Output 13, (output qualifiers FAXI to RTN2).; Results for nodal time histories, transmission sections, airbags, airbag chambers, airbag walls, materials, contacts, and rigid walls are also supported.; A new data type, shell_user, is added to display the results for user-defined shell materials.

Usage

To run from the command prompt:

–hgthp thpfile outfile.

To run in HyperGraph:

By default this reader is registered. If not, please register it before reading THP files. It is located in the HWDIR\externalreaders\bin\$PLATFORM\plot directory. After the reader is registered you can read THP files or PAM-CRASH ASCII files directly into HyperGraph.

HyperGraph erfh5 Result Reader

HyperGraph and HyperView uses same ERFH5 result reader to support ERF (HDF5) results.

HyperGraph reader supports Femzip ERF (HDF5) results, femzip library version 6.1.2019.

The PAM-CRASH ERF (HDF5) reader is enhanced to handle higher version result files.

PAM-CRASH ERF reader support ERF (HDF5) results that use modular input definition.

Entity pools are also used to handle duplicate IDs shared across different modules in the same model. These entities will be represented by their module IDs along with their parent entity module IDs.