Supported Output File Types

The following file types are generated by HyperLife.

  • Session file
  • Result output
  • Rainflow/Damage matrix results
  • Run Setup file
  • ASCII format results file for Rainflow information of the Queried Element
  • Log file

HyperLife Session File (*.hlf)

Details related to the Fatigue Setup are stored in this file. It is automatically written to the working directory on completion of the fatigue evaluation.

Type of Fatigue Analysis, Material Assignment, Events created, and the calculated fatigue results are stored in this file.

Session file can be reloaded to:
  • Retrieve the setup
  • Rerun of the retrieved setup
  • Review of calculated results

HyperLife Result Output (*.hwascii)

Hwascii lists the fatigue results of each element.

Results from hwascii can also be reviewed in HyperLife by loading the input result file used for the fatigue calculation (.h3d, .op2, and so on).

Rainflow/Damage Matrix results (.h5)

The Damage/Rainflow Matrix result for each element will be stored in a *.h5 file.

Rainflow/Damage Matrix will not be displayed in HyperLife if Display rainflow data is disabled in preferences.

HyperLife ASCII Format Results File for Rainflow Information of the Queried Element (3DMatrixInfo_ELe<ID>.rfout)

This file is created in the working directory on click of the export option above the Damage/Rainflow Matrix. Tabulated data written to the file can vary based on the Fatigue solution evaluated.

Run Setup File (*.xml)

The xml file is generated via export from Evaluate or is automatically written to the working directory on completion of an evaluation.

The file can be imported to configure the HyperLife Fatigue setup or to submit a Batch run from the session.

Log File (*.log)

A log file outputs the HyperLife evaluation summary for a particular run.

The log file is activated from preferences. This feature is activated by default for a run submitted via Batch.