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 (or upward) compatible, so they can be created in a previous release and used in a more recent version. For a list of those files, see Table 19.2: Program-Generated Permanent Files.
The following tables list the files that the program writes:
Table 19.1: Program-Generated Temporary Files
| Identifier | Type | Contents |
|---|---|---|
| ANO | Text | Graphics annotation commands (/ANNOT) |
| BAT | Text | Input data copied from batch input file (/BATCH) |
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) |
Pnn | Binary | Scratch files for matrix assembly procedure |
PCn | Binary | Scratch files for PCG solver and matrix assembly procedure |
| PDA | Binary | Scratch file for PCG solver and matrix assembly procedure |
| PMA | Binary | Scratch file for PCG solver and matrix assembly procedure |
SNODExxx | Binary | Scratch files for Supernode eigensolver |
| SSCR | Binary | Scratch file from substructure generation pass |
| vtA0Q | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
| vtAQ0 | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
| vtAQ1 | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
| vtFQ | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
| vtQ | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
| vtWrk | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
| vtdX | Binary | Scratch files for harmonic analysis using the VT method and/or certain eigensolvers |
Many permanent files are forward compatible. Files that can generally be used by future program releases have a Y in the Forward column.
Table 19.2: Program-Generated Permanent Files
| Identifier | Type | Forward | Contents |
|---|---|---|---|
| ANF | Text | Y | Ansys Neutral Format geometry file |
| ASI | Binary | Y | Results file from a structural analysis on an FSI interface |
| BCLV | Binary | Y | Superelement static correction vectors from the generation pass |
| 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 forward compatible |
| FULL | Binary | - | Assembled global stiffness and mass matrices |
| GST | Text | - | 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 | Y | 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) |
NDXXX | Text | - | Element IDs violating criteria |
| NLH | Text | Y | Nonlinear diagnostics file that tracks results or contact quantities throughout the solution (NLHIST) |
| NODE | Text | Y | Node definitions (NWRITE) |
NRXXX | Text | 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. |
| PSAV | Binary | - | Copy of OSAV file from last substep (used only for semi-implicit analysis) |
| 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 |
| RMSH | Text | - | Remeshing activity monitor file for mesh nonlinear adaptivity 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 |
| RSM | Binary | - | Radiosity mapping data file for radiosity surface elements (SURF251, SURF252) |
| 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 |
| SECF | Text | - | Stores output quantities associated with result sections (OUTPR,RSFO) |
| SELD | Binary | Y | 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.
The /FCOMP command enables you to control compression of the results files, database files, certain restart files (.rnnn), and certain files created during a nonlinear analysis (.osav) while they are being written. This command offers two different ways to do compression:
Compression based on a sparsification scheme (default).
The average file compression is 10-50 percent. The solution time and time reading the results file or database file are not significantly increased and may decrease due to reduced I/O size requirements.
Compression based on the zlib algorithm; you control the level of compression by inputting a number from 0 (no compression) to 5.
The average file will compress about 25 percent at the cost of added solution time (more so if running in distributed-memory parallel mode) or time to save the database. The time to read the results (for example, the SET command) or resume the database is also increased.
Compressing the files 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.
Note that results files from modal analyses will compress
very little if the stresses are written to the MODE file
(MSUPkey = YES on MXPAND).