HIN File

The HIN file allows you to call a user defined failure criteria for your analysis.

With the HIN file, you can control the damage initiation and evolution schemes used in the analysis. You may also specify additional variables to track throughout the analysis. Place the HIN file in the same directory as the input file and use the same name as the input file with a .hin extension. Currently, the following routines support user properties:

UDMGINI2
UDMGINI3
UDMGEVO2

The HIN file should follow the basic structure below for user specified damage criteria:

*MATERIAL, NAME=<name of composite>
*DAMAGE INITIATION, TYPE=USER
*DAMAGE EVOLUTION, TYPE=USER
*DEPVAR, NUM=<# of additional variables to track>
*USER PROPERTIES
<numerical inputs>

Any keywords specified in the HIN file will take precedence over the user material constants supplied in the input file.

Unidirectional Composite Materials

*MATERIAL, NAME=: Must match the name of the composite material used in the analysis. This keyword must precede the other keywords.

*DAMAGE INITIATION, TYPE=USER: This will tell Helius PFA to use the damage initiation criteria specified by the UDMGINI2 subroutine.

*DAMAGE EVOLUTION, TYPE=USER: This will tell Helius PFA to use the damage evolution criteria specified by the UDMGEVO2 subroutine.

*DEPVAR, NUM=: This keyword specifies the number of solution dependent state variables to track out of the total number requested in the input file. For example, if the input file requests 9 solution dependent variables and the HIN file requests *DEPVAR, NUM=2, two of the nine solution dependent variables would be set aside for the user defined failure criteria. It is good practice to increase the number of solution dependent variables requested in the input file by the number specified in the HIN file to ensure minimum requirements are met.

*USER PROPERTIES: The line(s) that follow this keyword can be used to define any numerical inputs required by the user specified failure criteria. There is no restriction on the number of entries per line or the number of lines.

Woven Composite Materials

*MATERIAL, NAME=: Must match the name of the composite material used in the analysis. This keyword must precede the other keywords.

*DAMAGE INITIATION, TYPE=USER: This will tell Helius PFA to use the damage initiation criteria specified by the UDMGINI3 subroutine.

*DAMAGE EVOLUTION, TYPE=DISCRETE MPFS, FPFS: User specified damage evolution is not supported for woven materials. Only discrete damage evolution is supported. You may specify the post-failure stiffness ratios where MPFS is the matrix post-failure stiffness ratio and FPFS is the fiber post-failure stiffness ratio.

*DEPVAR, NUM=: This keyword specifies the number of solution dependent state variables to track out of the total number requested in the input file. For example, if the input file requests 9 solution dependent variables and the HIN file requests *DEPVAR, NUM=2, two of the nine solution dependent variables would be set aside for the user defined failure criteria. It is good practice to increase the number of solution dependent variables requested in the input file by the number specified in the HIN file to ensure minimum requirements are met.

*USER PROPERTIES: The line(s) that follow this keyword can be used to define any numerical inputs required by the user specified failure criteria. There is no restriction on the number of entries per line or the number of lines.

Example HIN File

**
*MATERIAL, NAME=AS4_3502
*DAMAGE INITIATIION, TYPEE=USER
*DAMAGE EVOLUTION, TYPE=USER
*DEPVAR, NUM=2
*USER PROPERTIES
0.89
0.12, 0.03
**
*MATERIAL, NAME=AS4-6K_3502_5HS
*DAMAGE INITIATION, TYPE=USER
** user damage evolution not supported for weaves
*DAMAGE EVOLUTION, TYPE=DISCRETE
0.001, 0.006
*DEPVAR, NUM=2
*USER PROPERTIES
0.90
**