MSC Fatigue Output Files

Table 1‑3
File	Description
name.db	This is the database containing the FE model and its results created by Pre & Post or MSC Patran.
jobname.fin	This is the job control file that is written by Pre & Post or MSC Patran when you click the Apply button in the Job Control... form. The following Actions create this form: Full Analysis, Partial Analysis, Translate Only, Save Job Only. If you take a look at this file it contains Parameter=keyword entries. It defines the analysis set up as specified when you fill out the various forms. You can read this file in under the Job Control... form also when the Action is set to Read Saved Job.
jobname.fes	This is the fatigue analysis input file. It is a binary file and contains all information necessary to run a complete fatigue analysis using the FEFAT analyzer. It is created by the PAT3FAT and FATTRANS translators which read the jobname.fin file and the FE results information from the database name.db. You can view the contents of this file with the Utilities... option in FEFAT. The Action, Translate Only on the Job Control... form will create this file and then stop.
jobname.fpp	This binary file is created by FEFAT after preprocessing. It is the result of the rainflow cycle count. The Action, Partial Analysis on the Job Control... form will create all files up to this point and then stop.
jobname.fef	This is the results file of a fatigue analysis created by FEFAT when a Full Analysis is requested. It is an ASCII file and can be read back into Pre & Post or MSC Patran to create life contour plots. It is also read by the MSC Fatigue module PFPOST to do tabular listings of results. A jobname.fef_tmpl file is also created which is a template used when read back into Pre & Post or MSC Patran defining the meaning of each column of results data in the jobname.fef file.
jobname.msg	This is the message file containing all messages during an analysis. If a job does not run properly for some reason, this is the file to look in first to find clues as to the problem.
jobname.sta	This is a one line status file read by the Monitor action from the Job Control Form... which is updated constantly as the analysis proceeds.

Table 1‑3

File

Description

name.db

This is the database containing the FE model and its results created by Pre & Post or MSC Patran.

jobname.fin

This is the job control file that is written by Pre & Post or MSC Patran when you click the Apply button in the Job Control... form. The following Actions create this form: Full Analysis, Partial Analysis, Translate Only, Save Job Only. If you take a look at this file it contains Parameter=keyword entries. It defines the analysis set up as specified when you fill out the various forms. You can read this file in under the Job Control... form also when the Action is set to Read Saved Job.

jobname.fes

This is the fatigue analysis input file. It is a binary file and contains all information necessary to run a complete fatigue analysis using the FEFAT analyzer. It is created by the PAT3FAT and FATTRANS translators which read the jobname.fin file and the FE results information from the database name.db. You can view the contents of this file with the Utilities... option in FEFAT. The Action, Translate Only on the Job Control... form will create this file and then stop.

jobname.fpp

This binary file is created by FEFAT after preprocessing. It is the result of the rainflow cycle count. The Action, Partial Analysis on the Job Control... form will create all files up to this point and then stop.

jobname.fef

This is the results file of a fatigue analysis created by FEFAT when a Full Analysis is requested. It is an ASCII file and can be read back into Pre & Post or MSC Patran to create life contour plots. It is also read by the MSC Fatigue module PFPOST to do tabular listings of results. A jobname.fef_tmpl file is also created which is a template used when read back into Pre & Post or MSC Patran defining the meaning of each column of results data in the jobname.fef file.

jobname.msg

This is the message file containing all messages during an analysis. If a job does not run properly for some reason, this is the file to look in first to find clues as to the problem.

jobname.sta

This is a one line status file read by the Monitor action from the Job Control Form... which is updated constantly as the analysis proceeds.