Depending on how files are used, the program writes them in text (ASCII) form or binary form. For example, ERR and LOG files are text, while DB, EMAT, and RST files are binary. In general, files that you may need to read (and edit) are written in text form, and all other files are written in binary form.
Below are some tips for using binary files:
When transferring files via FTP (File Transfer Protocol), you must set the BINARY option before doing the transfer.
Most binary files must have write permission to be used, even if the data is only being read from the file. However, the database files (file.DB) and results files (file.RST, file.RTH, etc.) can be read-only. When you save a read-only file.DB, the existing read-only file is saved to a file.DBB. You cannot save the read-only file.DB a second time, however, because it will attempt to overwrite the file.DBB file.
Binary files are not backward-compatible with previous releases. You cannot use binary files generated by the current release with an earlier release. Some files are forward-compatible. For a list of those files, see Table 20.2: Program-Generated Permanent Files.
The following tables list the files that the program writes:
Table 20.1: Program-Generated Temporary Files
| Identifier | Type | Contents |
|---|---|---|
| ANO | Text | Graphics annotation commands (/ANNOT) |
| BAT | Text | Input data copied from batch input file (/BATCH) |
DOn | Text | Do-loop commands for nesting level
n |
DSPxxxx | Binary | Scratch files for the sparse solver |
| EROT | Binary | Rotated element matrices |
| EVC | Binary | Scratch file for PCG Lanczos eigensolver |
| EVL | Binary | Scratch file for PCG Lanczos eigensolver |
LNxx | Binary | Scratch files for the sparse solver (x = 1-42) |
| LOCK | Binary | Prevents more than one job with the same name from running in the same directory |
| LV | Binary | Scratch file from substructure generation pass with more than one load vector. |
| PAGE | Binary | Page file for virtual memory (database space) |
| PCn | Binary | Scratch files for PCG solver |
| PDA | Binary | Scratch file for PCG solver |
| PMA | Binary | Scratch file for PCG solver |
SNODExxx | Binary | Scratch files for Supernode eigensolver |
| SSCR | Binary | Scratch file from substructure generation pass |
Many permanent files are upwardly compatible. Files that can generally be used by future program releases have a Y in the Upward column.
Table 20.2: Program-Generated Permanent Files
| Identifier | Type | Upward | Contents |
|---|---|---|---|
| ANF | Text | Y | ANSYS Neutral Format geometry file |
| ASI | Binary | Y | Results file from a structural analysis on an FSI interface |
| BCS | Text | - | Stores performance information when running the sparse solver |
| BFIN | Text | - | Interpolated body forces written as BF commands (BFINT) |
| CBDO | Text | - | Interpolated DOF data written as D Commands (CBDOF) |
| CDB | Text | Y | Text database file (CDWRITE) |
| CMAP | Text | - | Color map file |
| CMD | Text | Y | Commands written by *CFWRITE |
| CMS | Binary | Y | Component Mode Synthesis file |
| CND | Text | Y | Nonlinear diagnostics file that tracks contact quantities throughout the solution (NLDIAG) |
| CNM | Text | Y | Contact pair output data (CNTR) |
| DB | Binary | Y | Database file (SAVE, /EXIT) |
| DBB | Binary | Y | Copy of database file created when a nonlinear analysis terminates abnormally (used for traditional restart) |
| DBE | Binary | - | Database file from VMESH failure in batch mode |
| DSP | Text | - | Stores performance information when running the sparse solver |
| DSUB | Binary | - | Superelement DOF solution from use pass |
| DSPsymb | Binary | - | Factorized stiffness matrix (also known as the triangularized stiffness matrix) from the sparse solver |
| ELEM | Text | Y | Element definitions (EWRITE) |
| EMAT | Binary | - | Element matrices |
| ERR | Text | - | Error and warning messages |
| ESAV | Binary | - | Element saved data ESAV files created by nonlinear analyses may not be upwardly compatible |
| FULL | Binary | - | Assembled global stiffness and mass matrices |
| GRPH | Text | Y | Neutral graphics file |
| GST | Binary | - | Graphical solution tracking file |
| IGES | Text | Y | IGES file from solid model data (IGESOUT) |
| LDHI | Text | Y | Loading and boundary conditions of load steps (used for multiframe restart) |
| LGW | Text | Y | Database command log file (LGWRITE) |
| Lnn | Binary | Y | Load case file (where nn = load case number) (LCWRITE) |
| LMODE | Binary | - | Modal analysis frequencies and left mode shapes (MODOPT) |
| LN22 | Binary | - | Factorized stiffness matrix (also known as the triangularized stiffness matrix) from the sparse solver |
| LOG | Text | Y | Command input history |
| MAPPING | Text | Y | Mapping data (HBMAT) |
| MATRIX | Text/Binary | Y | Mapping data in Harwell-Boeing format (HBMAT) |
| MCF | Text | Y | Modal coordinates from harmonic or transient analysis |
| MCOM | Text | Y | Mode combination commands from spectrum analysis |
| MLV | Binary | - | Modal analysis element load vector data |
Mnnn | Binary | Y | Modal displacements, velocities, and accelerations records and solution commands for a single substep of a load step (used for multiframe restart of a mode-superposition transient analysis) |
| MNTR | Text | - | Nonlinear analysis convergence monitoring |
| MODE | Binary | - | Modal analysis frequencies and mode shapes; buckling analysis load multipliers and mode shapes |
| MODESYM | Binary | - | Modal analysis frequencies and mode shapes |
| MP | Text | Y | Material property definitions (MPWRITE) |
| NLH | Text | Y | Nonlinear diagnostics file that tracks results or contact quantities throughout the solution (NLHIST) |
| NODE | Text | Y | Node definitions (NWRITE) |
| NR | Binary | Y | Stores Newton-Raphson iteration information when the nonlinear diagnostic tool is active (NLDIAG,NRRE,ON) |
| OSAV | Binary | - | Copy of ESAV file from last converged substep |
| OUT | Text | - | Output file |
| PARM | Text | Y | Parameter definitions (PARSAV) |
| PCS | Text | - | Stores performance information when running the PCG solver |
| PRS | Binary | - | Stores response spectrum (SPRS, MPRS, and DDAM) information (mode coefficients, etc.) when remote modal files are used. |
| PSD | Binary | - | Stores random vibration (PSD) information (modal covariance matrices, etc.) |
| PVTS | Text | - | Stores pivot information when running the sparse solver |
| RCN | Binary | Y | Results file for the initial contact state |
| RDB | Binary | Y | Database at the start of the first substep of the first load step (used for multiframe restart) |
| RDnn | Binary | Y | Database from structural analyses after nn times of rezoning |
| RDSP | Binary | - | Reduced displacements |
| RFRQ | Binary | - | Reduced complex displacements |
| RMF | Binary | Y | Results file from a static mean flow analysis |
| RMG | Binary | Y | Results file from a magnetic field analysis |
Rnnn | Binary | - | Element saved records, solution commands, and status for a single substep of a load step (used for multiframe restart of static and full transient analyses) |
| RSnn | Binary | Y | Results file from structural analyses after nn times of rezoning |
| RST | Binary | Y | Results file from structural and coupled-field analyses |
| RSTP | Binary | Y | Results file from a linear perturbation analysis |
| RTH | Binary | Y | Results file from a thermal analysis |
| SELD | Binary | - | Superelement load vector data from generation pass |
Snn | Text | Y | Load step files (where nn
= load step number) (LSWRITE) |
| SORD | Text | - | Superelement name and number from use pass |
| STAT | Text | - | Status of a batch run |
| SUB | Binary | Y | Superelement matrix file from generation pass |
| TB | Text | Y | Hyperelastic material constants |
| USUB | Binary | Y | Renamed DSUB File for input to substructure expansion pass |
Many file compression utilities exist for Linux (such as gzip) and Windows (such as WinZip). The program cannot read compressed files. You can compress your models to save space when archiving, so long as you uncompress them before trying to read them into the program.
You can also compress the results file while it is being written by issuing the
/FCOMP command. The average results file will compress about
25 percent, at the cost of added solution time (more so if running distributed
parallel) and more time to read the results (for example, SET
command). Note that results files from modal analyses will compress very little if
the stresses are written to the MODE file (MSUPkey = YES
on MXPAND). Compressing the results file is useful for speeding
up file transfers (for example when solving on a network cluster) or reducing the
disk space required to archive the analysis data.