HyperXtrude creates the following files during the analysis and post-processing.
File name |
Description |
File type |
||||
Jobname_000.out |
Standard output with convergence history. This is the key output file you should inspect to understand the run and its diagnostics. |
ASCII |
||||
#autosave.phx |
HyperXtrude save file with results from previous nonlinear iteration. This file can be used to restart the analysis, especially when the run ends/crashes for some reason. This file will be automatically deleted unless the pset parameter SavePHXfileYesNo is set to yes. |
Binary |
||||
Jobname.save.phx |
HyperXtrude results file created once the solution is converged. This file also contains solutions from mesh refinement steps and time steps. This file will be automatically deleted unless the pset parameter SavePHXfileYesNo is set to yes. |
Binary |
||||
Jobname.mod |
Finite element mesh that can be imported into HyperMesh. This is not often used. To enable this output, add these commands to the TCL file:
|
ASCII |
||||
Jobname.res |
Results file that can be imported into HyperMesh. This is not often used. To enable this output, add these commands to the TCL file:
|
Binary |
||||
Jobname.h3d |
Results file in HyperView format. This is the main output file for post-processing the results. |
Binary |
||||
Jobname.pth |
Solution along a particle path line. |
ASCII |
||||
Jobname.fem |
OptiStruct input deck for tool deflection and fatigue analysis |
ASCII |
||||
Jobname.rtm |
This file will be written for metal extrusion analysis and it contains information needed by the automatic report generator |
ASCII |
||||
Jobname.srf |
Boundary fluxes and forces |
ASCII |