20.4. Text and Binary Files

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:

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.

20.4.1. Program-Generated Files

The following tables list the files that the program writes:

Table 20.1:  Program-Generated Temporary Files

IdentifierTypeContents
ANOTextGraphics annotation commands (/ANNOT)
BATTextInput data copied from batch input file (/BATCH)
DOnTextDo-loop commands for nesting level n
DSPxxxxBinaryScratch files for the sparse solver
EROTBinaryRotated element matrices
EVCBinaryScratch file for PCG Lanczos eigensolver
EVLBinaryScratch file for PCG Lanczos eigensolver
LNxxBinaryScratch files for the sparse solver (x = 1-42)
LOCKBinaryPrevents more than one job with the same name from running in the same directory
LVBinaryScratch file from substructure generation pass with more than one load vector.
PAGEBinary Page file for virtual memory (database space)
PCnBinaryScratch files for PCG solver
PDABinaryScratch file for PCG solver
PMABinaryScratch file for PCG solver
SNODExxxBinaryScratch files for Supernode eigensolver
SSCRBinaryScratch 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

IdentifierTypeUpwardContents
ANFText Y ANSYS Neutral Format geometry file
ASIBinary Y Results file from a structural analysis on an FSI interface
BCSText-Stores performance information when running the sparse solver
BFINText-Interpolated body forces written as BF commands (BFINT)
CBDOText-Interpolated DOF data written as D Commands (CBDOF)
CDBText Y Text database file (CDWRITE)
CMAPText-Color map file
CMDText Y Commands written by *CFWRITE
CMSBinary Y Component Mode Synthesis file
CNDText Y Nonlinear diagnostics file that tracks contact quantities throughout the solution (NLDIAG)
CNMText Y Contact pair output data (CNTR)
DBBinary Y Database file (SAVE, /EXIT)
DBBBinary Y Copy of database file created when a nonlinear analysis terminates abnormally (used for traditional restart)
DBEBinary-Database file from VMESH failure in batch mode
DSPText-Stores performance information when running the sparse solver
DSUBBinary-Superelement DOF solution from use pass
DSPsymbBinary-Factorized stiffness matrix (also known as the triangularized stiffness matrix) from the sparse solver
ELEMText Y Element definitions (EWRITE)
EMATBinary-Element matrices
ERRText-Error and warning messages
ESAVBinary-Element saved data ESAV files created by nonlinear analyses may not be upwardly compatible
FULLBinary-Assembled global stiffness and mass matrices
GRPHText Y Neutral graphics file
GSTBinary-Graphical solution tracking file
IGESText Y IGES file from solid model data (IGESOUT)
LDHIText Y Loading and boundary conditions of load steps (used for multiframe restart)
LGWText Y Database command log file (LGWRITE)
LnnBinary Y Load case file (where nn = load case number) (LCWRITE)
LMODEBinary-Modal analysis frequencies and left mode shapes (MODOPT)
LN22Binary-Factorized stiffness matrix (also known as the triangularized stiffness matrix) from the sparse solver
LOGText Y Command input history
MAPPINGText Y Mapping data (HBMAT)
MATRIXText/Binary Y Mapping data in Harwell-Boeing format (HBMAT)
MCFText Y Modal coordinates from harmonic or transient analysis
MCOMText Y Mode combination commands from spectrum analysis
MLVBinary-Modal analysis element load vector data
MnnnBinary 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)
MNTRText-Nonlinear analysis convergence monitoring
MODEBinary-Modal analysis frequencies and mode shapes; buckling analysis load multipliers and mode shapes
MODESYMBinary-Modal analysis frequencies and mode shapes
MPText Y Material property definitions (MPWRITE)
NLHText Y Nonlinear diagnostics file that tracks results or contact quantities throughout the solution (NLHIST)
NODEText Y Node definitions (NWRITE)
NRBinary Y Stores Newton-Raphson iteration information when the nonlinear diagnostic tool is active (NLDIAG,NRRE,ON)
OSAVBinary-Copy of ESAV file from last converged substep
OUTText-Output file
PARMText Y Parameter definitions (PARSAV)
PCSText-Stores performance information when running the PCG solver
PRSBinary-Stores response spectrum (SPRS, MPRS, and DDAM) information (mode coefficients, etc.) when remote modal files are used.
PSDBinary-Stores random vibration (PSD) information (modal covariance matrices, etc.)
PVTSText-Stores pivot information when running the sparse solver
RCNBinary Y Results file for the initial contact state
RDBBinary Y Database at the start of the first substep of the first load step (used for multiframe restart)
RDnnBinary Y Database from structural analyses after nn times of rezoning
RDSPBinary-Reduced displacements
RFRQBinary-Reduced complex displacements
RMFBinaryYResults file from a static mean flow analysis
RMGBinary Y Results file from a magnetic field analysis
RnnnBinary-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)
RSnnBinary Y Results file from structural analyses after nn times of rezoning
RSTBinary Y Results file from structural and coupled-field analyses
RSTPBinary Y Results file from a linear perturbation analysis
RTHBinary Y Results file from a thermal analysis
SELDBinary-Superelement load vector data from generation pass
SnnText Y Load step files (where nn = load step number) (LSWRITE)
SORDText-Superelement name and number from use pass
STATText-Status of a batch run
SUBBinary Y Superelement matrix file from generation pass
TBText Y Hyperelastic material constants
USUBBinary Y Renamed DSUB File for input to substructure expansion pass

20.4.2. File Compression

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.


Release 18.2 - © ANSYS, Inc. All rights reserved.