- Case Files (.cfx)
A case file is generated when you save a simulation in CFX-Pre. The case file contains the physics data, region definitions, and mesh information for the simulation and is used by CFX-Pre as the 'database' for the simulation setup.
A case file is a binary file and cannot be directly edited.
- CFX-Mesh Files (.gtm)
GTM files (.gtm) contain mesh regions that can be used to set up a simulation in CFX-Pre or viewed in CFD-Post.
Note: GTM files that contain mesh data should not be confused with GT-SUITE .gtm files, which are used by GT-SUITE, for example when running a CFX simulation coupled with GT-SUITE.
Limitations with a GTM File in Multiple Results Files — When loading a state file that loads multiple results files including a GTM file, load the mesh file first, and then apply the state.
- CFX-Solver Input Files (.def, .mdef)
A CFX-Solver input file is created by CFX-Pre. The input file for a single configuration simulation (.def) contains all physics and mesh data; the input file for multi-configuration simulations (.mdef) contains global physics data only (that is, Library and Simulation Control CFX Command Language specifications). An .mdef input file is supplemented by Configuration Definition (.cfg) files that:
Are located in a subdirectory that is named according to the base name of the input file
Contain local physics and mesh data.
Note: Use the
-noruncommand line option (described in Command-Line Options and Keywords for cfx5solve in the CFX-Solver Manager User's Guide) to merge global information into the configuration definition files, and produce a CFX-Solver input (.def) file that can be run by the CFX-Solver.- CFX-Solver Results Files (.res, .mres, .trn, .bak)
Intermediate and final results files are created by the CFX-Solver:
Intermediate results files, which include transient and backup files (.trn and .bak, respectively) are created while running an analysis.
Final results files for single and multi-configuration simulations (.res and .mres, respectively) are written at the end of the simulation’s execution. For multi-configuration simulations, a configuration result file (.res) is also created at the end of each configuration’s execution.
Each results file contains the following information as of the iteration or time step at which it is written:
The physics data (that is, the CFX Command Language specifications)
All or a subset of the mesh and solution data.
An alternate file format, Common Fluids Format (CFF), is also available. For details, see Common Fluids Format (CFF) Files.
- CFX-Solver Backup Results Files (.bak)
A backup file (.bak) is created at your request, either by configuring the settings on the Backup tab in Output Control in CFX-Pre, or by choosing to write a backup file while the run is in progress in the CFX-Solver Manager.
- CFX-Solver Transient Results Files (.trn)
A transient results file (.trn) is created at your request, by configuring the settings on the Output Control > Trn Results tab in CFX-Pre.
- CFX-Solver Error Results Files (.err)
An error results file (.err) is created when the CFX-Solver detects a failure and stops executing an analysis. The .err file can be loaded into CFD-Post and treated the same way as a .bak file, but if the CFX-Solver encounters another failure while writing the .err file, it may become corrupted and accurate solutions cannot be guaranteed.
- Session Files (.cse)
Session files are produced by CFD-Post and contain CCL commands. You can record the commands executed during a session to a file and then play back the file at a later date. For details, see New Session Command.
You can also modify session files in a text editor.
- State Files (.cst)
State files are produced by CFD-Post and contain CCL commands. They differ from session files in that only a snapshot of the current state is saved to a file. You can also write your own state files using any text editor. For details, see Save State Command and Save State As Command and Load State Command.
Transient Blade Row models available in Ansys CFX (described in Transient Blade Row Modeling in the CFX-Solver Modeling Guide) make it possible to obtain temporally accurate solutions of transient blade row interaction, with vastly reduced memory requirements and computational time. There are two main types of case where these transient blade row models can be applied:
Single-domain modeling, such as frozen gust (inlet disturbance (for one domain only, either rotor or stator)).
Single-stage, multi-domain modeling, such as transient rotor-stator, or any multistage model.
When a transient blade row case is loaded, CFD-Post automatically creates valid solution variables for postprocessing (see Variables Tree View).
Note:
For transient blade row cases, transient statistics for boundary-only variables (such as Force, Mass Flow, Heat Flux) are not available on the following postprocessing locators: points, lines, cut-planes, isosurfaces, and iso clips.
CFD-Post displays the global range for plots in transient blade row cases differently than in other cases. In a transient blade row case, the global range is computed and extended dynamically based on the selected domain(s) and timestep. For example if you change the definition of a plot to include another domain, or if you change the timestep, the global range in the plot's legend will be extended automatically to cover both the original and the new plot definitions.
Transient blade row cases also interact with the timestep selector; see Using the Timestep Selector with Transient Blade Row Cases for details.