CFXMGR Book

ANSYS CFX-Solver Manager,
Release 10.0
Notice
This ANSYS software product and program documentation are confidential and proprietary
products of ANSYS, Inc., its subsidiaries, or licensors. The software products and
documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software
license agreement that contains provisions concerning non-disclosure, copying, length and
nature of use, warranties, disclaimers, limitations of liability, and remedies, and other
provisions. The software products and documentation may be used, disclosed, transferred,
or copied only in accordance with the terms and conditioneyps of that software license
agreement.
All product names mentioned in this document are trademarks or registered trademarks of
their respective owners.
Unauthorised use, distribution, or duplication is prohibited.
2005 ANSYS Europe Ltd. All rights reserved. Unauthorized use, distribution, or duplication
is prohibited.
ANSYS, ANSYS Workbench, CFX, AUTODYN, and any and all ANSYS, Inc. product and service
names are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in
the United States or other countries. ICEM CFD is a trademark licensed by ANSYS, Inc. CFX is
a trademark of Sony Corporation in Japan. Contains U.S. Patent No. 6,055,541 and pending
patent 10/152,543. All other trademarks or registered trademarks are the property of their
respective owners.
ANSYS, Inc. and ANSYS Europe, Ltd. are registered ISO 9001: 2000 companies.
ANSYS Canada Ltd.
554 Parkside Drive
Waterloo, Ontario
Canada
N2L 5Z4
Website: http://www.ansys.com/cfx
Any inquiries regarding copyright should be directed to:
ANSYS, Inc.
Legal/Contracts Dept.
275 Technology Drive
Canonsburg, PA 15317
or by email to cfx-info-na@ansys.com.
Table of Contents
Solver Manager Basics
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Starting ANSYS CFX-Solver Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using ANSYS Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using CFX-Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using ANSYS CFX-Pre. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Working with the Solver Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Convergence History Plots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Text Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Customising Solver Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Moving a toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Working with Solver Manager
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Define Run dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Definition file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Run definition procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Run Definition tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Partitioner tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Solver tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Specifying an Initial Values File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Run results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Parallel Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
General procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring a parallel run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Restarting a Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Reasons for restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Restart procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
ANSYS CFX-Solver Manager, Release 10.0 Page 1

Table of Contents: ANSYS CFX-Solver Files
ANSYS CFX-Solver Files
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Input Files and Initial Values Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Generated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
ANSYS CFX Results File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
ANSYS CFX Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
ANSYS CFX Output File (transient runs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
ANSYS CFX Output File (parallel runs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
ANSYS CFX Partition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
ANSYS CFX Output File (Mesh Adaption Runs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
ANSYS CFX Output File (Conjugate Heat Transfer Runs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
ANSYS CFX Output File (GGI Runs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
ANSYS CFX Output File (Combustion Runs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ANSYS CFX Output File (Radiation Runs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
List of Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Variables relevant for most CFD calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Variables relevant for turbulent flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Variables relevant for buoyant flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Variables relevant for compressible flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Variables relevant for calculations with a rotating frame of reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Variables relevant for parallel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Variables relevant for multicomponent calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Variables relevant for multiphase calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Residual Plotting
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Equation Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Convergence results and RMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Transient Residual Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Editing Definition Files
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Workflow overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Editing a Definition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Command File Editor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Menus in the Command File Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Command File Editor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Command File Editor Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Editing the Command Language (CCL) File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Command Language File Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
RULES and VARIABLES Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
VARIABLES File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
RULES File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Page 2 ANSYS CFX-Solver Manager, Release 10.0

Table of Contents: File Menu
File Menu
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Define Run command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Monitor Run in Progress command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Monitor Finished Run command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Close command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Quit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Edit Menu
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Options command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
SolverManager Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Common Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Workspace Menu
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Workspace Properties command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
General Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Monitors tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Creating Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Modifying Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Global Plot Settings tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
New Monitor command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Stop Current Run command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Restart Current Run command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Backup Run command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Arrange command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Toggle Layout Type command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Load Layout command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Save Layout command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Duplicating a plot monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
View RMS Residuals command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
View MAX Residuals command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Reset to Default Workspace command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Close command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Tools Menu
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Edit Definition File command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Export command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Export to ANSYS Multifield command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Table of Contents: Monitors Menu
Interpolate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Using the Command Line to Interpolate Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Edit Run In Progress command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Edit Current Results File command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Post-Process Results command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
View Environment command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Monitors Menu
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Help Menu
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Active Panel F1 command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
On Solver Manager command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
About Solver Manager command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
About Qt command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Help on Help command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Starting CFX-Solver from the Command Line
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Command line use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Command line arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Command line samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Start ANSYS CFX-Solver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Start ANSYS CFX-Solver Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Produce a partition file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Start ANSYS CFX-Solver in distributed parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Start ANSYS CFX-Solver from a definition file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Start ANSYS CFX-Solver in parallel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Start ANSYS CFX-Solver in parallel using MPICH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
cfx5stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
CFX-Solver Start Methods
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Direct start methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Indirect start methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
CPU and Memory Requirements
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Tetrahedral Mesh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Table of Contents: cfx5control Application
Special Solver Executables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
64-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Double Precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Chip-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Turbulence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Zero Equation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Two Equation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Reynolds Stress Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
CHT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Multicomponent Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Multiphase Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Homogeneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Inhomogeneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
N-Phase Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Additional Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Combustion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
GGI Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Transient. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
cfx5control Application
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
File Export Utility
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
ANSYS Multifield Export Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
ANSYS Element Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Output Modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Export Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Output Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Use Corrected Boundary Node Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Include Variables Only Found on Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Output Only Boundary Geometry and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Geometry Output Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Geometry Output Only (Neutral file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
FIELDVIEW Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Ensight Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
CGNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Export Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
MSC.Patran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Export Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Exporting boundary conditions to MSC.Patran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Example procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Table of Contents: File Export Utility
FIELDVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Export Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Importing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
EnSight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Export Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Importing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Custom User Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Export Executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Custom Export Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Running ANSYS CFX Export from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
Running ANSYS CFX Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Exporting a Transient Results File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Exporting Particle Tracking Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Creating an Export Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
An Example of an Export Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Example of Output Produced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Source Code for getargs.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Linking Code into ANSYS CFX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Compiler Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Using a Custom Export format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Using the ANSYS CFX-Solver Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Using the command line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Using cfx5export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Solver Manager Basics
The topics in this section include:
Introduction (p. 7 in "ANSYS CFX-Solver Manager, Release 10.0")
Starting ANSYS CFX-Solver Manager (p. 8 in "ANSYS CFX-Solver Manager, Release 10.0")
Working with the Solver Manager Interface (p. 9 in "ANSYS CFX-Solver Manager, Release
10.0")
Customising Solver Manager (p. 12 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The ANSYS CFX-Solver Manager is a graphical user interface used to:
Set attributes for a CFD calculation.
Control the ANSYS CFX-Solver interactively.
View information about the emerging solution.
As an alternative to using ANSYS CFX-Solver Manager, ANSYS CFX-Solver can be operated
from the command line. This is particularly useful for batch mode operations. For details, see
Starting CFX-Solver from the Command Line (p. 99 in "ANSYS CFX-Solver Manager, Release
10.0").
Related Documentation
The following documentation contains information relevant to CFX-Solver and ANSYS
CFX-Solver Manager.
Introduction to the ANSYS CFX Tutorials (p. 23 in "ANSYS CFX, Release 10.0: Tutorials")
Frequently Asked Questions (p. 701 in "ANSYS CFX, Release 10.0: Reference Guide")
Installation and machine-specific details can be found in:
CPU and Memory Requirements (p. 109 in "ANSYS CFX-Solver Manager, Release 10.0")
Installing ANSYS CFX on UNIX Systems (p. 31 in "ANSYS CFX, Release 10.0: Installation and
Overview")
Installing ANSYS CFX on Windows Systems (p. 47 in "ANSYS CFX, Release 10.0: Installation
and Overview")

Solver Manager Basics: Starting ANSYS CFX-Solver Manager
Starting ANSYS CFX-Solver Manager

The ANSYS CFX-Solver Manager can be started in different ways.
Using ANSYS Workbench (p. 8 in "ANSYS CFX-Solver Manager, Release 10.0")
Using CFX-Launcher (p. 8 in "ANSYS CFX-Solver Manager, Release 10.0")
Using ANSYS CFX-Pre (p. 8 in "ANSYS CFX-Solver Manager, Release 10.0")
Using the Command Line (p. 8 in "ANSYS CFX-Solver Manager, Release 10.0")
Using ANSYS Workbench

For details, see ANSYS CFX in Workbench (p. 51 in "ANSYS CFX, Release 10.0:
Reference Guide").
Using CFX-Launcher
To run ANSYS CFX-Solver Manager from the CFX Launcher, set the working directory
correctly. For details, see Working Directory Selector (p. 97 in "ANSYS CFX, Release 10.0:
Installation and Overview"). Once the working directory is set, click the ANSYS CFX-Solver
icon. ANSYS CFX-Solver Manager launches immediately and no Definition File information
is passed on. For details, see ANSYS CFX Launcher (p. 95 in "ANSYS CFX, Release 10.0:
Installation and Overview").
Using ANSYS CFX-Pre

If CFX-Pre is launched and a simulation is open, CFX-Solver Manager can be directly
launched by writing a solver file. For details, see Write Solver (.def) File command (p. 33 in
"ANSYS CFX-Pre, Release 10.0").
Using the Command Line

If using a UNIX terminal window or a Windows command window, ensure it is set up
correctly to find the ANSYS CFX commands.
1. Type cfx5solve.
2. Press Enter or Return.
ANSYS CFX-Solver Manager starts.
ANSYS CFX-Solver Manager launches immediately and no Definition File information is
passed on. Additional command line options are available. For details, see Starting
CFX-Solver from the Command Line (p. 99 in "ANSYS CFX-Solver Manager, Release 10.0").

Solver Manager Basics: Working with the Solver Manager Interface
Working with the Solver Manager Interface

ANSYS CFX-Solver Manager has a visual interface that displays a variety of results. It is
generally used to view plotted data during problem solving.
Figure 1 CFXSolver Manager Interface
Note: Throughout this documentation, additional interface images are generally displayed
as simple line drawings to guide you to a specific section of the screen, unless a full image is
required.
By default, the Convergence History Plots appear to the right or the top. The Text Output
Window appears to the left or the bottom. There is an adjustable split between the windows
which is oriented either horizontally or vertically, depending on the aspect ratio of the entire
ANSYS CFX-Solver Manager window (also adjustable).
Convergence History Plots (p. 10 in "ANSYS CFX-Solver Manager, Release 10.0")
Text Output Window (p. 11 in "ANSYS CFX-Solver Manager, Release 10.0")

Convergence History Plots

The left window displays convergence history plots. At the top of this window are tabs with
the names of displayed monitors. For details, see Monitors Menu (p. 95 in "ANSYS CFX-Solver
Manager, Release 10.0").
Figure 2 Location of Convergence History Plots
CFX Solver Manager
File Edit Workspace Tools Monitors Help
The main area of the convergence history plots show the value of each plotted variable
(typically, an RMS residual) at each timestep, according to the selected monitor (e.g.,
Momentum and Mass, Heat Transfer, etc.). Variables plotted can be selected by editing
Workspace Properties. For details, see Workspace Menu (p. 79 in "ANSYS CFX-Solver
Click any plot lines to view the value at the nearest timestep.
The legend shows the variable associated with each plot line.
Saving Images Images in the Convergence Plot History can be saved as graphics.
1. Right click in the Convergence Plot History.
2. Select Save as Image.
The Image File dialog box is displayed.
3. Select a location to export the image to.
4. Under File name, type the name for the file.
5. Under File Type, select the format to export as.
6. Click Save.
Printing Images Images in the Convergence Plot History can be printed.

2. Select Print.
3. Configure the printer as required.
4. Click Print.

Exporting Plot Data from any plot monitor can be exported. The data format for the exported file consists
Data of comma-delimited entries. This data can be used as the basis for import to another
application.
2. Select Export Plot Data.
The Export dialog box is displayed.
3. Select a location to export the data to.
4. Under File name, type the name for the file.
5. Under File Type, select the format to export as.
Files are saved with a .csv extension by default but this can be modified as required.
6. Click Save.
Text Output Window

The right window displays text output from ANSYS CFX-Solver.
Figure 3 Location of Text Output Window
CFX Solver Manager
File Edit Workspace Tools Monitors Help
The text output window lists simulation information and the progress of a solution,
including information such as physical properties, boundary conditions and various other
parameters used or calculated in creating the model. All text is written to the Output File
automatically. For details, see ANSYS CFX Output File (p. 30 in "ANSYS CFX-Solver Manager,
Release 10.0").
Saving the The current state of the output window (even when a run is in progress) can be saved to disk.
current state
1. Right-click in the text output window.
2. Select Save As.
3. Select a location to save the current state to.
4. Enter the name of the text file.
5. Click Save.
Searching for The output window can be searched for specific text.
text
1. Right-click in the text output window.
2. Select Find.
3. In Find text, enter words to search for.
4. Select or clear Match Case.

Solver Manager Basics: Customising Solver Manager
5. Click Find Previous or Find Next to search up or down from the current location.
Workspace
The Workspace drop down list shows the current run name and allows switching between
runs.
1. Click the Workspace drop down list.

2. Select a run to switch to.
Customising Solver Manager

The size and position of most windows in ANSYS CFX-Solver Manager can be changed to
customize the appearance, function and placement of objects.
Settings to be saved and loaded are stored as a Layout File (*.mst). A layout file saves
settings such as window sizes, selected plot variables and other settings specific to the
current view.
For example, by selecting a variable to be plotted and configuring the current view, a
custom display can be created. This layout can be saved and restored from the layout file at
a later time. For details, see Workspace Menu (p. 79 in "ANSYS CFX-Solver Manager, Release
10.0").
Moving a toolbar
Toolbars can be moved as required.
1. Click and drag the left edge of a toolbar to a new position.
2. Place the toolbar as desired.
The toolbar orients itself vertically if placed along the left or right side of ANSYS
CFX-Solver Manager.

Working with Solver Manager
Topics in this section include:
Define Run dialog box (p. 13 in "ANSYS CFX-Solver Manager, Release 10.0")
Specifying an Initial Values File (p. 18 in "ANSYS CFX-Solver Manager, Release 10.0")
Run results (p. 19 in "ANSYS CFX-Solver Manager, Release 10.0")
Parallel Run (p. 20 in "ANSYS CFX-Solver Manager, Release 10.0")
Restarting a Run (p. 23 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
This section describes procedures for specific types of runs.
Steps to take depend on whether an Initial Values file is required or not, and whether the
Definition File name has already been passed to the ANSYS CFX-Solver Manager.
Define Run dialog box (p. 13 in "ANSYS CFX-Solver Manager, Release 10.0")
Specifying an Initial Values File (p. 18 in "ANSYS CFX-Solver Manager, Release 10.0")
Run results (p. 19 in "ANSYS CFX-Solver Manager, Release 10.0")
Restarting a Run (p. 23 in "ANSYS CFX-Solver Manager, Release 10.0")
Define Run dialog box

Information required to define a run depends on the application. Various options can be
configured. Two types of runs can be defined.
Serial run is the default way of running a CFD simulation. During a serial run, all
computation is done by a single process running on one machine.
Parallel run divides computation into more than one process and is done on more than
one machine. For details, see Parallel Run (p. 20 in "ANSYS CFX-Solver Manager, Release
10.0").

Working with Solver Manager: Define Run dialog box
Definition file name

The name of the Definition File is automatically passed to ANSYS CFX-Solver Manager if
using the following methods:
By selecting Start Solver Manager with Definition File from Write Definition File in
ANSYS CFX-Pre.
By starting from the command line using -def. For details, see Starting CFX-Solver from
the Command Line (p. 99 in "ANSYS CFX-Solver Manager, Release 10.0").
Run definition procedure

The following process is generic to either run type.
1. If the Definition File name was passed to the Solver Manager from ANSYS CFX-Pre, the
Define Run dialog box is displayed and automatically has the Definition File selected.
An Initial Values file may still have to be specified. For details, see Specifying an Initial
Values File (p. 18 in "ANSYS CFX-Solver Manager, Release 10.0"). If the Definition File has
been passed to the Solver Manager, proceed directly to step 3.
2. Select File > Define Run.
3. Configure the run as required by modifying Run Definition, Partitioner and Solver.
Run Definition tab (p. 14 in "ANSYS CFX-Solver Manager, Release 10.0")
Partitioner tab (p. 15 in "ANSYS CFX-Solver Manager, Release 10.0")
Solver tab (p. 17 in "ANSYS CFX-Solver Manager, Release 10.0")
4. Click Start Run to begin Solver.
Run Definition tab

When defining a run, information to pass to ANSYS CFX-Solver is specified. This includes
geometry, models, boundary conditions and start-up information needed to calculate a
solution to a CFD problem.
1. In the Define Run dialog box, select Run Definition.
2. Under Definition File, click Browse and select the definition file to run.
3. If required, under Initial Values File, click Browse and select the initial values to
apply to the run.
a. If the Definition File does not require an Initial Values file, this may be left blank. For
details, see Specifying an Initial Values File (p. 18 in "ANSYS CFX-Solver Manager,
Release 10.0").
b. If an initial values file is used, select Interpolate Initial Values onto Def File Mesh.
When definition and initial results files contain dissimilar meshes, this allows initial
values to be automatically interpolated from the initial values file to the definition
file. For details, see Restarts (p. 24 in "ANSYS CFX-Solver Manager, Release 10.0").
4. If required, under Adaption Database, click Browse and select the database to use
for mesh adaption.

5. Under Type of Run, select Full or Partitioner Only.
Full runs the partitioner if applicable, and then runs Solver.
Partitioner Only is used for parallel runs only and does not run Solver. This writes a
.par file.
6. Configure the Parallel Enviroment as required.
For details, see Parallel Enviroment (p. 15 in "ANSYS CFX-Solver Manager, Release 10.0").
7. If required, under Run Environment, set the Working Folder.
8. Select Show Advanced Controls to display and configure Partitioner and Solver.
Partitioner tab (p. 15 in "ANSYS CFX-Solver Manager, Release 10.0")
Solver tab (p. 17 in "ANSYS CFX-Solver Manager, Release 10.0")
9. Click Start Run to begin the solution process.
Parallel For a Distributed Parallel setup, specify the number of partitions assigned to each host. If
Enviroment choosing a specified partition weighting (under Partitioner), click directly on the partition
weight number to edit it. There should be one weight entry per partition. For details, see
Partitioning Weighting (p. 16 in "ANSYS CFX-Solver Manager, Release 10.0").
1. Under Parallel Environment, select a Run Mode.
2. Configure the mode as required.
Run Mode determines whether the run is serial (the default when defining a run in which
a problem solved as one process), or parallel (problem split into partitions).
Serial run (the default) requires no additional configuration.
Partitioner tab
Use Partitioner settings if the mesh is to be partitioned or to use an existing partition file for
the partitioning data.
Note: An existing partition file cannot be used if the simulation involves either the Monte
Carlo or Discrete Transfer radiation models.
Partitions may be viewed prior to running ANSYS CFX-Solver. For details, see ANSYS CFX
Partition File (p. 46 in "ANSYS CFX-Solver Manager, Release 10.0").
1. In the Define Run dialog box, click the Partitioner tab.
If this is not available, ensure Show Advanced Controls is selected in the Run Definition
tab. For details, see Define Run dialog box (p. 13 in "ANSYS CFX-Solver Manager, Release
10.0").
2. If required, under Initial Partition File, click Browse and select the partition file to
load.
The *.par file is only required if a model has already been partitioned and needs to be
loaded.
3. Select a Run Priority.
Standard is the default Run Priority for partitioning.

4. Under Partitioning Detail, choose a Partition Type and configure it.
Depending on the selected Partition Type, various options must be configured. Partition
types include:
Multilevel Graph Partitioning Software - MeTiS (p. 351 in "ANSYS CFX-Solver, Release
10.0: Modelling"). When first running in parallel, it is recommended that Partition
Type be set to MeTiS.
Recursive Coordinate Bisection (p. 352 in "ANSYS CFX-Solver, Release 10.0:
Modelling")
Optimised Recursive Coordinate Bisection (p. 352 in "ANSYS CFX-Solver, Release 10.0:
Modelling")
User Specified Direction (p. 353 in "ANSYS CFX-Solver, Release 10.0: Modelling")
Radial (p. 353 in "ANSYS CFX-Solver, Release 10.0: Modelling")
Circumferential (p. 354 in "ANSYS CFX-Solver, Release 10.0: Modelling")
5. If required, configure the Partition Weighting.
For details, see Partitioning Weighting (p. 16 in "ANSYS CFX-Solver Manager, Release
10.0").
6. Configure Paritioner Memory.
For details, see Partitioner Memory (p. 17 in "ANSYS CFX-Solver Manager, Release 10.0").
Partitioning Some partition types support weighting of partitions. Partitions can be weighted in different
Weighting ways. The default setting is Automatic.
Uniform (p. 16 in "ANSYS CFX-Solver Manager, Release 10.0")
Specified (p. 16 in "ANSYS CFX-Solver Manager, Release 10.0")
Automatic (p. 17 in "ANSYS CFX-Solver Manager, Release 10.0")
Uniform
Assigns equal-sized partitions to each process.
Specified
Requires Run Definition to be configured with individual partition weights.
Partition Weights is added to the Parallel Environment. This allows partition weights to be
entered. When more than one partition is assigned to any machine, the number of partition
weight entries must equal the number of partitions. The partition weight entries should be
entered as a comma-separated list. For a distributed run like the following:
Host # of Partitions Partition Weights
Sys01 1 2
Sys02 2 2, 1.5
Sys03 1 1
Sys01 is therefore a single partition and the weight is 2. Sys02 has two partitions and they
are individually weighted at 2 and 1.5. The final system has a single partition with a weight
of 1.
If Partition Weight Factors are used, the ratio of partition weights assigned to each partition
controls the partition size.

Once started, the run progresses through the partitioning, and then into the solution of the
CFD problem. Extra information is stored in the Output File for a parallel run. For details, see
ANSYS CFX Output File (p. 30 in "ANSYS CFX-Solver Manager, Release 10.0").
Automatic
Calculates partition sizes based on the Relative Speed entry specified for each machine in
the hosts.ccl file. For details, see hosts.ccl file (p. 51 in "ANSYS CFX, Release 10.0:
Installation and Overview").
Machines with a faster relative speed than others are assigned proportionally larger
partition sizes. The entry of relative speed values is usually carried out during the ANSYS CFX
installation process, and accurate entries for relative speed can significantly optimise
parallel performance.
Windows Parallel Setup (p. 51 in "ANSYS CFX, Release 10.0: Installation and Overview")
UNIX Parallel Setup (p. 37 in "ANSYS CFX, Release 10.0: Installation and Overview")
Partitioner If ANSYS CFX-Solver fails with an Insufficient memory message, memory settings may
Memory need to be configured. This increases or decreases the amount of Partitioner Memory.
In most cases, increase memory by only a few percent. Normally, you would not set this
factor to less than 1; it is unlikely ANSYS CFX-Solver would then have enough memory to
complete the partition.
Memory Allocation Factor

1. Under Partitioner Memory, set the Memory Allocation Factor.
For example, a value of 1.05 increases memory allocation by 5% and a value of 1.1
increases memory allocation by 10%.
2. If required, under Partitioner Memory, select Detailed Memory Overrides.
For details, see Detailed Memory Overrides (p. 17 in "ANSYS CFX-Solver Manager, Release
10.0").
3. Specify Real Memory, Integer Memory, Character Memory, Double Memory and
Logical Memory as required.
Detailed Memory Overrides

If further memory control is required (e.g., a large amount of one particular type of memory
is required), select Detailed Memory Overrides. This allows explicit specification of the
amount of Real, Integer, Character, Double and Logical memory to use.
The number of words of memory can be specified, or a memory multiplier can be used. Use
a unit of M for mega-words, K for kilo-words, or X for a memory multiplier. For example, 2 X
doubles the memory allocation and 15 M means 15 million words of memory. If a value is
not specified for a particular type of memory, the value calculated by the Solver is used. If a
value is entered, it overrides the automatic estimate made by the Solver.
Solver tab
1. In the Define Run dialog box, select the Solver tab.
If this is not available ensure Show Advanced Controls in Define Run is selected. For
details, see Define Run dialog box (p. 13 in "ANSYS CFX-Solver Manager, Release 10.0").

Working with Solver Manager: Specifying an Initial Values File
2. Under Run Priority select Low, Standard or High.
Run priority may also be prioritized with a command line argument. For details, see
Starting CFX-Solver from the Command Line (p. 99 in "ANSYS CFX-Solver Manager,
Release 10.0").
3. Under Executable Settings, select or clear Double Precision.
For details, see Double Precision (p. 110 in "ANSYS CFX-Solver Manager, Release 10.0").
4. Under Solver Memory, set the Memory Allocation Factor.
For example, a value of 1.05 increases memory allocation by 5% and a value of 1.1
increases memory allocation by 10%.
For details, see Memory Allocation Factor (p. 17 in "ANSYS CFX-Solver Manager, Release
10.0").
5. If required, under Solver Memory, select Detailed Memory Overrides.
For details, see Detailed Memory Overrides (p. 17 in "ANSYS CFX-Solver Manager, Release
10.0").
6. Specify Real Memory, Integer Memory, Character Memory, Double Memory and
Logical Memory as required.
7. Under Custom Solver Options, click Browse and select a Custom Executable.
This is done when using a custom solver executable. In addition, any command line
arguments that must be supplied to the program can be entered under Solver
Arguments.
Specifying an Initial Values File

In steady state runs, initialisation data are the values of dependent variables at the start of a
steady state simulation. These can be set explicitly, read from an existing solution, or given
default values.
In transient runs, initialisation data are the values of dependent variables at the Initial Time
of a transient simulation. These can be either set explicitly, or read from an existing solution.
Initial Values files are useful in the following cases:
To restart a run after a physics change with a partially converged solution.
When restarting a run with, for example, a new turbulence model, save time and
resources by using a partially converged set of results from a previous run as the basis
for an initial guess. These initial guess values are likely to be far more accurate than using
an Automatic initial guess from the restart.
To begin a transient simulation, using the results of a steady-state simulation as the
initial guess.
Transient simulations require values to be set for all variables during initialisation.
Starting a transient run with results from a converged steady-state simulation can lead
to good convergence and solution robustness, especially if it is difficult to provide an
accurate estimate of the initial conditions.
In both cases, the geometry, topology and mesh of the definition file and initial values file
must be identical.

Working with Solver Manager: Run results
When changing node density of a mesh, use Interpolate to interpolate results from a results
file onto a new definition file. For details, see Interpolate command (p. 91 in "ANSYS
CFX-Solver Manager, Release 10.0").
Additional information on setting initial conditions is available. For details, see Setting the
Initial Conditions (p. 86 in "ANSYS CFX-Solver, Release 10.0: Modelling").
Run results
Once a run is completed, the Run name is displayed in the Workspace drop down list.
The Run name is the name of the Definition File with the extension removed and a
three-digit number added. The number is usually 001 if this is the first time ANSYS
CFX-Solver Manager is used for this Definition File. In general, it is the lowest number that
prevents files from previous runs being overwritten.
ANSYS CFX-Solver updates convergence history plots and text output windows. At first, axes
for a plot appear in the convergence history plot, and a summary of the model properties is
printed in the text output window. After a short time, tables display to indicate that ANSYS
CFX-Solver has finished initialising the problem and is ready to solve it. Each such table
corresponds to one iteration or timestep of the problem. All text which appears in the text
output window is saved in the ANSYS CFX Output File. For details, see ANSYS CFX Output File
(p. 30 in "ANSYS CFX-Solver Manager, Release 10.0").
======================================================================
OUTER LOOP ITERATION = 1 CPU SECONDS = 2.68E+00
----------------------------------------------------------------------
| Equation | Rate | RMS Res | Max Res | Location | Linear Solution |
+----------+------+---------+---------+----------+-------------------+
| U - Mom | 0.00 | 9.1E-20 | 3.3E-19 | 386 | 0.0E+00 OK |
| V - Mom | 0.00 | 3.5E+00 | 7.0E+00 | 1418 | 4.0E-03 OK |
| W - Mom | 0.00 | 1.7E-10 | 6.1E-10 | 386 | 6.8E+07 ok |
| P - Mass | 0.00 | 0.0E+00 | 0.0E+00 | 0 | 8.3 0.0E+00 OK |
+----------+------+---------+---------+----------+-------------------+
Once results for the second timestep are shown in a table (such as the one above), data is
plotted in the convergence history plots. The plot for each timestep is the normalised
residual for each of the equations that ANSYS CFX-Solver is solving. This is a measure of how
inaccurate the current solution is. These residuals should gradually decrease as the solution
progresses. They can, however, increase occasionally on some timesteps. For details, see
Residual Plotting (p. 59 in "ANSYS CFX-Solver Manager, Release 10.0").
When ANSYS CFX-Solver stops running, a message is displayed with an explanation. ANSYS
CFX-Solver stops if:
The solution reaches the level of accuracy specified.
It reaches the maximum number of timesteps specified.
It is stopped manually.
The solution diverges to the point where it causes numerical problems in the ANSYS
CFX-Solver.

Working with Solver Manager: Parallel Run
These messages (usually with more detail) are also displayed in the text output window. If
no errors occur, information on the solution itself is displayed in the text output window and
written to the output file. For details, see ANSYS CFX Output File (p. 30 in "ANSYS CFX-Solver
After a run has finished:
Define a new run by following the earlier procedure. For details, see Define Run
command (p. 75 in "ANSYS CFX-Solver Manager, Release 10.0").
Calculate more timesteps for the original run. For details, see Parallel Run (p. 20 in
"ANSYS CFX-Solver Manager, Release 10.0").
View results in ANSYS CFX-Post (provided that the ANSYS CFX-Solver produced a Results
File and did not fail). For details, see Overview of ANSYS CFX-Post (p. 7 in "ANSYS CFX-Post,
Release 10.0").
Print residual plots in the convergence history plots. For details, see Printing Images
Add comments to the saved version of the text in the text output window. For details,
see Starting CFX-Solver from the Command Line (p. 99 in "ANSYS CFX-Solver Manager,
Release 10.0").
Export results in a format suitable for post-processors other than ANSYS CFX-Post. For
details, see File Export Utility (p. 117 in "ANSYS CFX-Solver Manager, Release 10.0").
Quit ANSYS CFX-Solver Manager by selecting File > Quit. This does not stop the ANSYS
CFX-Solver calculation. Additionally, ANSYS CFX-Solver Manager can be reopened at
any time. For details, see File Menu (p. 75 in "ANSYS CFX-Solver Manager, Release 10.0").
The ANSYS CFX Tutorials describe how to use the ANSYS CFX-Solver Manager step-by-step
for several different cases. If you are a new user you are recommended to try at least the first
few of these.
Parallel Run
A tutorial is provided related to developing a parallel run. For details, see Setting Up to Run
in Parallel (p. 130 in "ANSYS CFX, Release 10.0: Tutorials").
Note: ANSYS CFX-Solver can be run in parallel only if an appropriate license has been
purchased.
Information on a parallel run is explained in more detail:

Overview (p. 20 in "ANSYS CFX-Solver Manager, Release 10.0")
General procedure (p. 21 in "ANSYS CFX-Solver Manager, Release 10.0")
Configuring a parallel run (p. 21 in "ANSYS CFX-Solver Manager, Release 10.0")
Overview
There are several parallel run modes including PVM, MPICH and several vendor specific MPI
versions available on some platforms.
PVM stands for Parallel Virtual Machine; MPI stands for Message Passing Interface. Both are
simply libraries which allow the flow solver processes to communicate with each other. PVM
is an open source library implemented at Oakridge National Labs and only works over

standard TCP/IP networks. MPICH is an open source version of MPI, implemented at
Argonne National Labs, that allows communication over standard TCP/IP networks, as well
as through shared memory. Proprietary, vendor specific versions of MPI are available on
some platforms (32 bit Linux, 64 bit Linux, HPUX and IRIX) and support a wider array of high
speed network devices, as well as Shared Memory communication.
General information on setting up a parallel run and advice on obtaining optimal parallel
performance is available. For details, see Introduction to ANSYS CFX Parallel (p. 349 in "ANSYS
CFX-Solver, Release 10.0: Modelling").
Individual users may need to be configured to run in parallel. For details, see Parallel Setup
for Individual Users (p. 64 in "ANSYS CFX, Release 10.0: Installation and Overview").
General procedure
To run ANSYS CFX-Solver in parallel, the following procedure must be followed:
1. Partition the mesh into the appropriate number of partitions.
2. Run ANSYS CFX-Solver on the partitioned problem.
These two jobs can be done either as one composite run, or as two separate jobs.
Configuring a parallel run

1. Follow the procedure for a serial run.
For details, see Run definition procedure (p. 14 in "ANSYS CFX-Solver Manager, Release
10.0").
2. Under Run Mode, select a parallel method.
Local Parallel Setup (p. 21 in "ANSYS CFX-Solver Manager, Release 10.0")
Distributed Parallel Setup (p. 22 in "ANSYS CFX-Solver Manager, Release 10.0")
3. Specify options as required.
The options differ according to the selection made.
Local Parallel Setup (p. 21 in "ANSYS CFX-Solver Manager, Release 10.0")
Distributed Parallel Setup (p. 22 in "ANSYS CFX-Solver Manager, Release 10.0")
Local Parallel Select a local parallel if running the problem with 2 or more processors on the local machine.
Setup
Any number of partitions between 2 and 512 can be selected. When running the job in the
ANSYS CFX-Solver, the computation is divided into this number of processes. For details, see
Partitioner tab (p. 15 in "ANSYS CFX-Solver Manager, Release 10.0"). Solver allows further
changes. For details, see Solver tab (p. 17 in "ANSYS CFX-Solver Manager, Release 10.0").
1. Select one of the local parallel run modes (e.g., PVM Local Parallel, HP MPI Local
Parallel or MPICH Local Parallel). Which parallel run modes you can select depends on
the hardware and operating system on which you are running.
Setting up in Parallel (p. 50 in "ANSYS CFX, Release 10.0: Installation and Overview")
Setting up MPICH for Windows (p. 57 in "ANSYS CFX, Release 10.0: Installation and
Overview")

2. Click Add Partition or Remove Partition to increase or decrease the number

of partitions.
Partitions may need to be configured based on partition weighting.
Partitioning Weighting (p. 16 in "ANSYS CFX-Solver Manager, Release 10.0")
Distributed Select a distributed parallel if running the problem with 2 or more computers.
Parallel Setup
Overview
A file named hosts.ccl must exist in the <CFXROOT>/config/ANSYS CFX directory on the
master node, and be readable by all users of the software. This file is a database containing
information about available nodes and where ANSYS CFX is installed on each of them. For
details, see hosts.ccl file (p. 51 in "ANSYS CFX, Release 10.0: Installation and Overview").
Note: If running machines as slave nodes, ensure rsh service is installed and working on
each of those machines (many Windows machines do not already have an rsh service
installed). For details, see Setting up the rsh Service (p. 54 in "ANSYS CFX, Release 10.0:
Installation and Overview"). If running MPICH on Windows, additional steps are required. For
details, see Setting up MPICH for Windows (p. 57 in "ANSYS CFX, Release 10.0: Installation and
Overview").
Important: Note that MIPCH cannot be used with a mixture of UNIX and Windows machines.
Selecting parallel hosts

Simulations can be run on parallel host machines by selecting any available host for parallel
processing. This should have been set up when CFX-5 was installed).
1. Click Insert Host .

The Select Parallel Hosts dialog box is displayed.
2. Select a host from the list of available machines.
3. Click Add.
Ensure the name of current machine is included.
4. Configure each host as required.
For details, see Configuring a host (p. 22 in "ANSYS CFX-Solver Manager, Release 10.0").
Configuring a host
Each parallel host can be configured independently.
1. In Parallel Environment, under Host Name, select the host to configure.
2. Click Add Partition or Remove Partition to increase or decrease the number

of partitions.
Partitiona may need to be configured based on partition weighting.
Partitioning Weighting (p. 16 in "ANSYS CFX-Solver Manager, Release 10.0")

Working with Solver Manager: Restarting a Run
Restarting a Run
More timesteps can be calculated on a Run that has already been sent to the ANSYS
CFX-Solver. Once a run is stopped, either restart from where it was last stopped, or change
some details of the simulation before continuing.
Reasons for restarting (p. 23 in "ANSYS CFX-Solver Manager, Release 10.0")
Restart procedure (p. 23 in "ANSYS CFX-Solver Manager, Release 10.0")
Restarts (p. 24 in "ANSYS CFX-Solver Manager, Release 10.0")
Reasons for restarting

A run may need to be restarted if:
ANSYS CFX-Solver stopped prematurely and now needs to continue running.
The solution did not converge sufficiently within the maximum number of timesteps
specified, and ANSYS CFX-Solver needs to calculate more timesteps to get better
convergence.
Instead of restarting from where the run stopped, it can be re-run with a larger maximum
number of timesteps, for example. However, restarting reduces time wasted spent
re-calculating finished results.
Some details of the physical models or parameters may need to be modified before
restarting if there are, for example:
Changes to how well converged a solution is required.
Changes to the model used (for example, as a solution emerges, it is discovered that the
model should change from laminar flow to turbulence).
Difficulties obtaining a converged solution and it is decided to run the problem with a
more robust physical model first, and then change to the physical model required after
obtaining an approximate solution to the problem.
In general, do not restart a run when the topology or mesh for the problem has changed;
rather interpolate the results into a new Definition File. For details, see Restarts (p. 24 in
Restart procedure
1. Select File > Define Run.
2. Under Run Environment, set the Working Folder to the working directory containing
the results and output files produced by the first run.
3. Select, under Definition File, the results file of the previous run.
4. Configure the Define Run dialog box as required.
5. Click Start Run.
Tip: You may also select Tools > Restart Run if you are viewing the results using the
Monitor Finished Run function. For details, see File Menu (p. 75 in "ANSYS CFX-Solver

There are slight differences in the Output File and Residuals Plots, compared to results that
would appear had the ANSYS CFX-Solver continued in the first place. The table produced for
each timestep in the Output File and Text Output Window appear similar to:
======================================================================
OUTER LOOP ITERATION = 30 ( 1) CPU SECONDS = 2.48E+02 ( 3.38E+00)
----------------------------------------------------------------------
| Equation | Rate | RMS Res | Max Res | Linear Solution |
+----------------------+------+---------+---------+------------------+
| U - Mom | 0.00 | 1.5E-04 | 1.2E-03 | 4.6E-02 OK|
| V - Mom | 0.00 | 2.1E-04 | 1.2E-03 | 3.8E-02 OK|
| W - Mom | 0.00 | 1.5E-04 | 2.1E-03 | 1.3E-02 OK|
| P - Mass | 0.00 | 3.2E-05 | 1.5E-04 | 8.3 3.4E-02 OK|
+----------------------+------+---------+---------+------------------+
| H-Energy | 0.00 | 7.7E-06 | 8.5E-05 | 9.5 9.1E-03 OK|
+----------------------+------+---------+---------+------------------+
The first line of each table contains information relevant for both the whole calculation and
for the restarted run. The whole calculation is the original run and the new restarted run
taken together. The values in brackets show information relevant to only the restarted run.
In the above table the information shows that this is the first Outer Loop Iteration or
Timestep of the restarted run, but the thirtieth iteration of the entire calculation.
The Convergence History Plots only show the residuals for the restarted run. A new output
file, which contains the information relevant for that restart, is created for each restart.
Restarts
This section deals with several types of restarts.
Runs using Mesh Adaption (p. 24 in "ANSYS CFX-Solver Manager, Release 10.0")
Runs after Physical Model or Solver Parameter changes (p. 24 in "ANSYS CFX-Solver
Manager, Release 10.0")
Runs after Topology or Mesh changes (p. 25 in "ANSYS CFX-Solver Manager, Release 10.0")
Runs using Restarting a Run which uses Mesh Adaption has no effect on the final results. If the
Mesh Adaption maximum number of adaption steps has been specified, then ANSYS CFX-Solver determines
how many adaption steps were completed in the initial run when determining how many
adaption steps remain.
Runs after Restarting a run after changing its properties is quite different from restarting without
Physical Model changing properties. To do the former, create a new Definition File with changed properties,
or Solver
and use the old Results File as an Initial Values File. In this case, only CCL and adaption
Parameter
changes parameters are read from the new Definition File. All other information, including the mesh
and topology, are read from the old Results File.
To create a new Definition File, reopen the ANSYS CFX-Pre Definition File and change the
appropriate parameters from within ANSYS CFX-Pre. Do not change the number or name of
boundary conditions (although the type can be changed), or the reference pressure, or the
name of any predefined Subdomain. If Heat Transfer Model changes from None to any other

model, it is required that the specific heat capacity at constant pressure and the thermal
conductivity of the fluid be entered. On the Initialisation form in ANSYS CFX-Pre, set the
initial values of the variables contained in the old Results File to Automatic.
ANSYS CFX-Solver can now execute the new run by setting Definition File to the
newly-created Definition File, and Initial Values File to the old Results File, in the Define
Run dialog box.
Additional information on initial conditions is available. For details, see Introduction (p. 201
in "ANSYS CFX-Pre, Release 10.0"). More details about using Initial Values File in the Define
Run dialog box in ANSYS CFX-Solver Manager is available. For details, see Run definition
procedure (p. 14 in "ANSYS CFX-Solver Manager, Release 10.0").
Runs after If the geometry, connectivity, mesh or boundary condition names or locations change an
Topology or old results file can still be used to restart a run. If a change in topology is detected, the
Mesh changes
interpolator is called automatically.
The following are examples that would change topology and/or mesh:
Recreating the mesh with different parameters, mesh controls or inflated boundaries.
Changing the underlying geometry.
Changing the connectivity of the geometry (e.g., specifying domains or subdomains
differently).
Adding a new domain or subdomain.
Changing the name or location of any boundary condition, including the Default
Boundary Condition. (However, changing the type of boundary condition will not cause
the interpolator to be called automatically.)
Changing other physics settings, such as the fluids involved, or other significant physics
changes, is not recommended.
Alternatively, call the interpolator from the Tools menu before starting the run. For details,
see Interpolate command (p. 91 in "ANSYS CFX-Solver Manager, Release 10.0").
After the interpolator has run, the residual levels will usually be different upon restarting.


ANSYS CFX-Solver Files
Input Files and Initial Values Files (p. 28 in "ANSYS CFX-Solver Manager, Release 10.0")
Generated Files (p. 28 in "ANSYS CFX-Solver Manager, Release 10.0")
List of Variables (p. 52 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The ANSYS CFX Definition File created using ANSYS CFX-Pre contains the complete
specification of the simulation, including the complete mesh.
In the ANSYS CFX-Solver, the Navier-Stokes equations are discretised over the mesh
elements to produce a set of non-linear equations for each variable at each mesh node.
These equations are solved using a coupled solver.
Steady state simulations are performed as a series of pseudo-timesteps. The timestep sizes
are determined by the timestep setting in the Solver Control in ANSYS CFX-Pre. For details,
see Solver Control (p. 217 in "ANSYS CFX-Pre, Release 10.0").
Transient simulations are performed as a series of timesteps; each timestep may consist of
several coefficient iterations. The timestep sizes are determined by the timestep setting in
Simulation Type. For details, see Editing Simulation Type (p. 135 in "ANSYS CFX-Pre, Release
10.0").
The solution process is iterative, with each iteration (in a steady-state problem) treated as a
pseudo-timestep. It stops when either:
A pre-determined convergence criterion is met, or;
The maximum number of timesteps is reached, or;
The user stops the run, using either the ANSYS CFX-Solver Manager or the cfx5stop
command.
Stop Current Run command (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0")
Starting CFX-Solver from the Command Line (p. 99 in "ANSYS CFX-Solver Manager,
Release 10.0")
Criteria for the first two of these conditions can be defined by the user in ANSYS CFX-Pre.

ANSYS CFX-Solver Files: Input Files and Initial Values Files
Input Files and Initial Values Files

The ANSYS CFX-Solver is generally run with just the Input File. The Input File is usually the
ANSYS CFX Definition File. This file can be formatted or unformatted and is
machine-independent.
The Definition File usually contains information that is required by ANSYS CFX-Solver to
complete a CFD job including:
Physical models and fluid property settings
Boundary conditions
Initial conditions
The mesh
ANSYS CFX-Solver parameter settings
However, there are occasions when the Definition File does not supply the full specification
for the simulation, and additional information is required to perform the run. For example,
if initial conditions are read from a file, the additional information must be present in an
Initial Values File, which can take the form of a previously created Definition File or Results
File. The Initial Values File data does not override any specifications defined in the Input File;
it merely supplements the run with information which is not available in the Input File.
To continue a previous run using the same specifications but for a further number of
iterations, you can select a previously created Results File and use it as the Input File.
The following table outlines available options and circumstances for Input File and Initial
Values File entries:
Input File Initial Values File Circumstance Consequence
Definition File - New Run - all information is New Results File contains
available in Definition File info from iteration #1
Definition File Results File Restarting analysis from New Results File contains
previous results info from iteration #(n+1)
Results File - Continuing analysis for a New Results File contains
further number of iterations info from iteration #(n+1)
Additional information of the conditions which a Results File must satisfy to be used as an
Initial Values File is available. For details, see Reading the Initial Guess or Initial Values from a
File (p. 95 in "ANSYS CFX-Solver, Release 10.0: Modelling").
Generated Files
The ANSYS CFX-Solver usually generates two files for a CFD calculation. These are:
ANSYS CFX Results File (p. 29 in "ANSYS CFX-Solver Manager, Release 10.0")
ANSYS CFX Output File (p. 30 in "ANSYS CFX-Solver Manager, Release 10.0")
For parallel runs of the ANSYS CFX-Solver, an additional ANSYS CFX Partition file can also be
generated.
ANSYS CFX Partition File (p. 46 in "ANSYS CFX-Solver Manager, Release 10.0")

ANSYS CFX-Solver Files: Generated Files
ANSYS CFX Results File

The ANSYS CFX Results file is produced by the ANSYS CFX-Solver and contains a full
description of the flow simulation including:
Volume mesh
Flow solution
Limitations on Results File Sizes:
In UNIX systems, the results file size is restricted only by the available disk space on the
system.
On Windows platforms, the results file size is presently limited to 2GB. If your results file
approaches 2GB in size, restart the problem on a UNIX system to continue working with
it.
The ANSYS CFX Results File is similar to the ANSYS CFX Definition File. However, in addition
to information contained in the ANSYS CFX Definition File, the Results File also contains the
calculated value of each variable at each mesh node.
In ANSYS CFX, two other types of files may contain results. Firstly, in a transient CFD
simulation, files are produced which contain the results for specified timesteps in the
Definition File. If the ANSYS CFX Results File is called file_001.res, then in the same
directory there is a subdirectory with the name file_001. Within this directory, there are
files with names such as 32.trn. These contain the results for the timestep with that
number (in this case, the 32nd timestep). Note that these files are minimal results files, as set
on the Solver Control. For details, see Transient Results tab (p. 223 in "ANSYS CFX-Pre, Release
10.0"). These contain only variable information, with no mesh. Do not try to load one of these
files directly into ANSYS CFX-Post; instead load the ANSYS CFX Results File (nam-ed
file_001.res in the example described above).
Full Results If full results files is specified in the Solver Control, files with names such as 32_full.trn
are created. These files contain the results for the timestep with the appropriate number,
and also contain the mesh. Unlike the minimal results files, these files are suitable for
restarts.
Backup Files Also in the same directory, there may be files with names such as 32_full.bak. These are
backup files, and may be present for both transient and steady-state calculations. They are
full results files and are suitable for restarts and visualisation. For details, see Backup Run
ANSYS CFX-Post The ANSYS CFX Results File may be used as input to ANSYS CFX-Post in order to view the
results and produce hard copy output. It may also be used to produce files which are
suitable for use with other post-processors by using the ANSYS CFX Export facility. For
details, see File Export Utility (p. 117 in "ANSYS CFX-Solver Manager, Release 10.0").
ANSYS The ANSYS CFX Results File may also be used as input to the ANSYS CFX-Solver. The solution
CFX-Solver is used as the initial values field from which to start a further analysis. For details, see Input
Files and Initial Values Files (p. 28 in "ANSYS CFX-Solver Manager, Release 10.0").

ANSYS CFX Output File

The ANSYS CFX Output File is a formatted text file produced by the ANSYS CFX-Solver and
contains information about your ANSYS CFX model set-up, the state of the solution during
execution of the ANSYS CFX-Solver, and job statistics for the particular run. This is the same
information written to the Text Output Area window of the ANSYS CFX-Solver Manager. For
details, see Text Output Window (p. 11 in "ANSYS CFX-Solver Manager, Release 10.0").
The file is formatted and divided into sections to allow quick and easy interpretation. The
sections which are present for any calculation may depend upon which physical models are
being used (i.e., whether the model is transient or steady-state) and whether the ANSYS
CFX-Solver is being run as several parallel processes or as a single process.
Header The header is written at the start of every ANSYS CFX Output file and contains information
regarding the command which started the job. This information is used to check which files
were used to start the run.
The Header appears similar to the following:
Starting ANSYS CFX Solver. Please wait.

This run of the ANSYS CFX, Release 10.0 Solver started at 01:23:50 on 23 Jan 2004
by user smith on tempest (sgi_r12k_irix6.5) using the command:
/network/cfx/mainset/cfx5solve -NoConsole -def
/home/smith/non_newton.def -fullname non_newton_001
Setting up ANSYS CFX Solver run ...
CFD Job This section describes the job characteristics in terms of the Run mode (sequential or
Information parallel), the machine on which the job was started, and the time and date of the start of the
run.
CFD Job Information appears similar to the following:
+--------------------------------------------------------------------+
| Job Information |
+--------------------------------------------------------------------+
Run mode: sequential run
Host computer: pesky
Job started: Mon Mar 6 11:48:00 2000
Mesh Statistics The mesh statistics show the total number of nodes and elements in the mesh, together
with number of element faces on the mesh boundaries.
Mesh Statistics appears similar to the following:
+--------------------------------------------------------------------+
| Total number of Nodes, Elements, and Faces |
+--------------------------------------------------------------------+
Domain Name : StaticMixer
Total Number of Nodes = 2291
Total Number of Elements = 11177
Total Number of Tetrahedrons = 11177
Total Number of Faces = 1376

Memory Usage Note: Allocated storage generally exceeds the required storage. 1 word = 4 bytes, 1 Kword
= 1000 words, 1 Kbyte = 1024 bytes
Memory Usage appears similar to the following:
+--------------------------------------------------------------------+
| Memory Usage Information |
+--------------------------------------------------------------------+
Data Type Kwords Kwords/Node Kbytes Kbytes/Node
Real 2767.2 1.208 10809.2 4.718
Integer 360.3 0.157 1407.4 0.614
Character 129.8 0.057 507.1 0.221
Logical 10.0 0.004 39.1 0.017
Double 16.0 0.007 62.5 0.027
Total 3283.3 1.433 12825.3 5.598
Command File The command file section describes the problem definition, including domain specification,
boundary conditions, meshing parameters and solver control.

Command File appears similar to the following:
+--------------------------------------------------------------------+
| Command File |
+--------------------------------------------------------------------+
LIBRARY:
MATERIAL: Water at RTP
Option = Pure Substance
PROPERTIES:
Option = General Fluid
Density = 9.98E2 [kg m^-3]
Dynamic Viscosity = 1.E-3 [kg m^-1 s^-1]
Specific Heat Capacity = 4.19E3 [J kg^-1 K^-1]
Thermal Conductivity = 5.91E-1 [W m^-1 K^-1]
Thermal Expansivity = 2.1E-4 [K^-1]
END # PROPERTIES
END # MATERIAL Water at RTP
END # LIBRARY
FLOW:
SOLUTION UNITS:
Mass Units = [kg]
Length Units = [m]
Time Units = [s]
Temperature Units = [K]
END # SOLUTION UNITS
SIMULATION TYPE:
Option = Steady State
END # SIMULATION TYPE
DOMAIN: StaticMixer
Coord Frame = Coord 0
Fluids List = Water at RTP
DOMAIN MODELS:
DOMAIN MOTION:
Option = Stationary
END # DOMAIN MOTION
BUOYANCY MODEL:
Option = Non Buoyant
END # BUOYANCY MODEL
REFERENCE PRESSURE:
Reference Pressure = 1.E5 [Pa]
END # REFERENCE PRESSURE
END # DOMAIN MODELS
FLUID MODELS:
TURBULENCE MODEL:
Option = Zero Equation
END # TURBULENCE MODEL
HEAT TRANSFER MODEL:
Option = Thermal Energy
END # HEAT TRANSFER MODEL
END # FLUID MODELS
BOUNDARY: in1
Boundary Type = INLET
BOUNDARY CONDITIONS:
FLOW REGIME:
Option = Subsonic
END # FLOW REGIME
MASS AND MOMENTUM:
Option = Normal Speed
Normal Speed = 2. [m s^-1]
END # MASS AND MOMENTUM
HEAT TRANSFER:
Option = Static Temperature
Static Temperature = 3.15E2 [K]

END # HEAT TRANSFER
END # BOUNDARY CONDITIONS
END # BOUNDARY in1
BOUNDARY: in2
Boundary Type = INLET
FLOW REGIME:
Option = Subsonic
END # FLOW REGIME
MASS AND MOMENTUM:
Option = Normal Speed
Normal Speed = 2. [m s^-1]
HEAT TRANSFER:
Option = Static Temperature
Static Temperature = 2.85E2 [K]
END # HEAT TRANSFER
END # BOUNDARY in2
BOUNDARY: out
Boundary Type = OUTLET
FLOW REGIME:
Option = Subsonic
END # FLOW REGIME
MASS AND MOMENTUM:
Option = Static Pressure
Relative Pressure = 0.00 [Pa]
END # BOUNDARY out
BOUNDARY: Default
Boundary Type = WALL
WALL INFLUENCE ON FLOW:
Option = No Slip
END # WALL INFLUENCE ON FLOW
WALL ROUGHNESS:
Option = Smooth Wall
END # WALL ROUGHNESS
HEAT TRANSFER:
Option = Adiabatic
END # HEAT TRANSFER
END # BOUNDARY Default
INITIALISATION:
Option = Automatic
END # INITIALISATION
END # DOMAIN StaticMixer
SOLVER CONTROL:
CONVERGENCE CONTROL:
Maximum Number of Iterations = 50
Timescale Control = Physical Timescale
Physical Timescale = 2. [s]
END # CONVERGENCE CONTROL
CONVERGENCE CRITERIA:
Residual Type = RMS
Residual Target = 1.E-4
END # CONVERGENCE CRITERIA
ADVECTION SCHEME:
Option = Upwind
END # ADVECTION SCHEME

END # SOLVER CONTROL
END #FLOW
COMMAND FILE:
Version = 5.4
END # COMMAND FILE
Initial Average These are average scales based on the initial flow field. If the initial velocity field is zero, then
Scales the initial average velocity scale will also be zero.
Initial Average Scales appears similar to the following:
+--------------------------------------------------------------------+
| Average Scale Information |
+--------------------------------------------------------------------+
Global Length = 3.2113E+00
Density = 9.9800E+02
Dynamic Viscosity = 1.0000E-03
Velocity = 0.0000E+00
Thermal Conductivity = 5.9100E-01
Specific Heat Capacity at Constant Pressure = 4.1900E+03
Prandtl Number = 7.0897E+00
Solved This section lists the dependent variables solved and the equations to which they relate as
Equations well as the estimated physical timestep if calculated automatically.
Solved Equations looks similar to the following:
+--------------------------------------------------------------------+
| The Equations Solved in This Calculation |
+--------------------------------------------------------------------+
Subsystem Name : Momentum - Mass
U - Mom
V - Mom
W - Mom
P - Mass
Subsystem Name : Energy
H-Energy
Convergence The convergence history section details the state of the solution as it progresses. Equation
History residual information at specified locations allows you to monitor the convergence.
Convergence difficulties can often be pinpointed to a particular part of the solution (e.g. the
momentum equation), and/or a particular location.
Rate - This is defined as seen in (Eqn. 1) where R n is the residual at iteration n , and R n 1 is
the residual at the previous iteration. Factors less than 1.0 indicate convergence.
R
Rate = ----n- (Eqn. 1)
R n1
RMS Res - The value of the root mean square normalised residual taken over the whole
domain.
Max Res - The value of the maximum normalised residual in the domain.

Linear Solution - the three columns in this section refer to the performance of the linear
(inner) solvers. The first column is the average number of iterations the linear solvers
attempted to obtain the specified linear equation convergence criteria (within a specified
number of iterations). The second column gives the normalised residuals for the solutions
to the linear equation. The last column can have one of four entries:
* indicates that there was a numerical floating point exception and this resulted in the
failure of the linear solvers.
F indicates that the linear solvers did not reduce the residuals (i.e., the solution was
diverging), but the linear solvers may carry on if the divergence is not catastrophic.
ok indicates that the residuals were reduced, but that the degree of reduction did not
meet the specified criteria.
OK indicates that the specified convergence criteria for the reduction of residuals was
achieved.
After the convergence criteria has been achieved, or the specified number of timesteps has
been reached, ANSYS CFX-Solver appends additional information, calculated from the
solution, to the Output File.

Convergence History appears similar to the following:
+--------------------------------------------------------------------+
| Convergence History |
+--------------------------------------------------------------------+
======================================================================
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom | 0.00 | 1.5E-10 | 5.4E-09 | 1.5E+10 ok|
| V - Mom | 0.00 | 1.6E-04 | 3.2E-03 | 6.4E+01 ok|
| W - Mom | 0.00 | 2.5E-10 | 6.4E-09 | 1.1E+10 ok|
| P - Mass | 0.00 | 2.2E-03 | 3.0E-02 | 12.0 9.5E-02 OK|
+----------------------+------+---------+---------+------------------+
| H-Energy | 0.00 | 3.6E-03 | 3.6E-02 | 5.4 8.0E-03 OK|
+----------------------+------+---------+---------+------------------+
======================================================================
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom |99.99 | 5.2E-03 | 7.5E-02 | 4.8E-02 OK|
| V - Mom |99.76 | 1.6E-02 | 1.6E-01 | 1.4E-02 OK|
| W - Mom |99.99 | 8.4E-03 | 1.2E-01 | 7.9E-02 OK|
| P - Mass | 4.26 | 9.3E-03 | 1.3E-01 | 8.3 8.4E-02 OK|
+----------------------+------+---------+---------+------------------+
| H-Energy | 0.35 | 1.3E-03 | 8.8E-03 | 9.4 2.9E-03 OK|
+----------------------+------+---------+---------+------------------+
................
................
======================================================================
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom | 0.86 | 7.7E-05 | 3.1E-04 | 5.1E-02 OK|
| V - Mom | 0.86 | 9.1E-05 | 3.7E-04 | 4.8E-02 OK|
| W - Mom | 0.86 | 1.9E-05 | 1.6E-04 | 5.0E-02 OK|
| P - Mass | 0.87 | 3.7E-05 | 1.7E-04 | 8.3 3.0E-02 OK|
+----------------------+------+---------+---------+------------------+
| H-Energy | 0.86 | 5.7E-06 | 5.5E-05 | 9.5 9.8E-03 OK|
+----------------------+------+---------+---------+------------------+
CFD Solver finished: Wed Oct 25 16:01:48 2000
Execution terminating:
all RMS residual AND global imbalance
are below their target criteria.
Computed If the Zero Equation model is used to model turbulence, the overall turbulence viscosity is
Model provided.
Constants
Computed Model Constants appears similar to the following:
+--------------------------------------------------------------------+
| Computed Model Constants |
+--------------------------------------------------------------------+
Turbulence viscosity for Turbulence Model 1 = 3.3667E+00

Global The conservation of mass, momentum and energy at the boundaries of the Fluid Domain
Conservation are calculated. This is another good check for the convergence of the solution. Small values
Statistics
of Global Imbalance indicate that conservation has essentially been maintained. The
percentage imbalance of a quantity is calculated as seen in (Eqn. 2).
Total In Total Out

% imbalance = --------------------------------------------- (Eqn. 2)
Total In
For multidomain cases, this is modified as seen in (Eqn. 3)
Domain Imbalance
% imbalance = ---------------------------------------------------------------
- (Eqn. 3)
Maximum Over All Domain
where the maximum over all domains is the maximum value of a quantity at all boundaries
and subdomain sources.
For details, see Monitoring and Obtaining Convergence (p. 340 in "ANSYS CFX-Solver, Release
10.0: Modelling").

Global Conservation Statistics appears similar to the following:
======================================================================
Boundary Flow and Total Source Term Summary
======================================================================
+--------------------------------------------------------------------+
| U - Mom |
+--------------------------------------------------------------------+
Boundary : in1 1.0456E+00
Boundary : in2 -1.1114E+00
Boundary : out -6.4836E+01
Boundary : Default 6.4653E+01
Domain : StaticMixer 0.0000E+00
-----------
Global U - Mom Balance: -2.4886E-01
Global Imbalance, in %: -0.0002 %
+--------------------------------------------------------------------+
| V - Mom |
+--------------------------------------------------------------------+
Boundary : in2 -1.2359E+04
-----------
Global V - Mom Balance: 3.2898E-01
Global Imbalance, in %: 0.0002 %
+--------------------------------------------------------------------+
| W - Mom |
+--------------------------------------------------------------------+
Boundary : in1 -5.1295E-01
Boundary : in2 -3.3912E-01
Boundary : out 1.1187E+04
Boundary : Default -1.1185E+04
-----------
Global W - Mom Balance: 1.1113E+00
+--------------------------------------------------------------------+
| P - Mass |
+--------------------------------------------------------------------+
-----------
Global P - Mass Balance: 9.9609E-02
+--------------------------------------------------------------------+

| H-Energy |
+--------------------------------------------------------------------+
-----------
Global H-Energy Balance: 1.4054E+05
Calculated Wall The ANSYS CFX-Solver calculates the pressure and viscous components of forces on all
Forces and boundaries specified as Walls. The drag force on any wall can be calculated from these
Moments
values as follows:
Lift
Pressure Forces
Parallel Forces
Direction of
flow
Drag
Lift is the net force on the body in the direction perpendicular to the direction of flow. In the
above diagram, the lift is the sum of the forces on the wall in the vertical direction, i.e., the
sum of the pressure force and the viscous force components in the y direction.
Drag is the net force on the body in the direction of the flow. In the above diagram, the drag
is the sum of the forces on the wall in the horizontal direction, i.e., the sum of the pressure
force and the viscous force components in the x direction.
It is apparent from this that viscous force is not a pure shear force since it also has a small
component in the normal direction, arising in part from a normal component in the laminar
flow shear stress.
The pressure and viscous moments are related to the pressure and viscous forces calculated
at the Wall. The pressure moment is the vector product of the pressure force vector F n and
the position vector r . The viscous moment is the vector product of the viscous force
vector F t and the position vector r . As an example, review (Eqn. 4) where M n and M t are the
pressure and viscous moments respectively.
Mn = Fn r
(Eqn. 4)
Mt = Ft r
These are summed over all the surface elements in the Wall.

It is important to note that forces do not include reference pressure effects. The pressure
force is calculated as the integral of the relative pressure over the wall area and not as the
integral of the sum of the reference and relative pressures.
You can include reference pressure effects in the force calculation by setting the expert
parameter include pref in forces = t.
Calculated Wall Forces and Moments appear similar to the following:
+--------------------------------------------------------------------+
| Pressure Force On Walls |
+--------------------------------------------------------------------+
X-Comp. Y-Comp. Z-Comp.
Default -6.5477E+01 -4.6619E+01 8.1975E+04
+--------------------------------------------------------------------+
| Viscous Force On Walls |
+--------------------------------------------------------------------+
Default 7.9935E-01 4.6327E-01 -7.9120E+01
+--------------------------------------------------------------------+
| Pressure Moment On Walls |
+--------------------------------------------------------------------+
Default -1.2028E+02 3.8079E+01 -1.5966E+05
+--------------------------------------------------------------------+
| Viscous Moment On Walls |
+--------------------------------------------------------------------+
Default 1.9096E+00 1.5574E-01 -3.0841E+02
Maximum The location and occurrence of maximum and peak residuals can help to pinpoint
Residual convergence difficulties and help to indicate the state of convergence of your solution.
Statistics
Maximum Residual Statistics appears similar to the following:
+--------------------------------------------------------------------+
| Locations of Maximum Residuals |
+--------------------------------------------------------------------+
| Equation | Node # | X | Y | Z |
+--------------------------------------------------------------------+
| U - Mom | 728 | 6.168E-01 | 5.387E-02 |-6.187E-01 |
| V - Mom | 85 | 6.136E-01 | 1.902E+00 | 6.846E-01 |
| W - Mom | 483 |-6.772E-01 | 2.826E-01 |-8.441E-01 |
| P - Mass | 413 | 7.552E-01 |-3.366E-01 |-7.821E-01 |
| H-Energy | 2083 | 6.121E-01 | 1.640E+00 | 1.178E+00 |
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
| Peak Values of Residuals |
+--------------------------------------------------------------------+
| Equation | Loop # | Peak Residual | Final Residual |
+--------------------------------------------------------------------+
| U - Mom | 2 | 5.22793E-03 | 7.67906E-05 |
| V - Mom | 2 | 1.55203E-02 | 9.05021E-05 |
| W - Mom | 2 | 8.44563E-03 | 1.87603E-05 |
| P - Mass | 2 | 9.33986E-03 | 3.72930E-05 |
| H-Energy | 1 | 3.58668E-03 | 5.74081E-06 |
+--------------------------------------------------------------------+

False Transient This is only applicable to steady-state simulations (serial and parallel). The information is
Information equation based, that is there is one line per equation solved. For each equation, the Type of
time stepping used is displayed as Auto, Physical or Local.
Both Auto and Physical run as false transients. This means that although the simulation is
steady state, a transient term with an associated timestep is used to relax the equations
during convergence. In this case, the total elapsed pseudo-time is also printed.
False Transient Information appears similar to the following:
+--------------------------------------------------------------------+
| False Transient Information |
+--------------------------------------------------------------------+
| Equation | Type | Elapsed Pseudo-Time |
+--------------------------------------------------------------------+
| U - Mom | Physical | 5.80000E+01 |
| V - Mom | Physical | 5.80000E+01 |
| W - Mom | Physical | 5.80000E+01 |
| P - Mass | Physical | 5.80000E+01 |
| H-Energy | Physical | 5.80000E+01 |
+--------------------------------------------------------------------+
Final Average These are average scales for the final flow field.
Scales
Final Average Scales appears similar to the following:
+--------------------------------------------------------------------+
| Average Scale Information |
+--------------------------------------------------------------------+
Global Length = 3.2113E+00
Density = 9.9800E+02
Dynamic Viscosity = 1.0000E-03
Velocity = 1.4534E+00
Advection Time = 2.2095E+00
Reynolds Number = 4.6581E+06
Thermal Conductivity = 5.9100E-01
Specific Heat Capacity at Constant Pressure = 4.1900E+03
Prandtl Number = 7.0897E+00
Temperature Range = 3.0008E+01
Variable Range These are the maximum and minimum values for each variable in the flow field.
Information

Variabel Range Information appears similar to the following:
+--------------------------------------------------------------------+
| Variable Range Information |
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
| Variable Name | min | max |
+--------------------------------------------------------------------+
| Velocity u | -1.65E+00 | 1.61E+00 |
| Velocity v | -2.26E+00 | 2.25E+00 |
| Velocity w | -4.13E+00 | 2.58E-01 |
| Pressure | -6.71E+02 | 1.38E+04 |
| Density | 9.98E+02 | 9.98E+02 |
| Dynamic Viscosity | 1.00E-03 | 1.00E-03 |
| Specific Heat Capacity at Constant Pressure| 4.19E+03 | 4.19E+03 |
| Thermal Conductivity | 5.91E-01 | 5.91E-01 |
| Thermal Expansivity | 2.10E-04 | 2.10E-04 |
| Eddy Viscosity | 1.89E+01 | 1.89E+01 |
| Temperature | 2.85E+02 | 3.15E+02 |
| Static Enthalpy | 1.19E+06 | 1.32E+06 |
+--------------------------------------------------------------------+
CPU CPU Requirements appears similar to the following:

Requirements
+--------------------------------------------------------------------+
| CPU Requirements of Numerical Solution |
+--------------------------------------------------------------------+
Subsystem Name Discretisation Linear Solution
(secs. %total) (secs. %total)
----------------------------------------------------------------------
Momentum - Mass 1.48E+02 65.4 % 1.71E+01 7.6 %
Energy 5.14E+01 22.8 % 9.62E+00 4.3 %
-------- ------- -------- ------
Summary 1.99E+02 88.2 % 2.67E+01 11.8 %
Job Information Job Information appears similar to the following:
Host computer: mycomputer.com

Job finished: Wed Oct 25 16:02:37 2000
Total CPU time: 2.559E+02 seconds
or: ( 0: 0: 4: 15.950 )
( Days: Hours: Minutes: Seconds )
End of solution stage.
This run of the ANSYS CFX Solver has finished.
ANSYS CFX Output File (transient runs)

For transient runs, the ANSYS CFX-Solver outputs convergence information for each
coefficient iteration.

At the completion of each timestep iteration, the following information is also written to the
Output File:
Global conservation statistics
Calculated Wall forces and moments
Maximum residual statistics
Average scale information
Convergence Convergence history appears similar to the following:

history
======================================================================
TIME STEP = 2 SIMULATION TIME = 5.00E-01 CPU SECONDS = 2.14E+01
----------------------------------------------------------------------
COEFFICIENT LOOP ITERATION = 1
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom |99.99 | 9.6E-01 | 7.7E+00 | 5.8E-04 OK|
| V - Mom |99.99 | 2.2E-01 | 2.9E+00 | 2.7E-03 OK|
| W - Mom |99.99 | 4.2E-01 | 4.4E+00 | 5.4E-04 OK|
| P - Mass | .12 | 3.0E-03 | 4.0E-02 | 12.0 4.6E-02 OK|
+----------------------+------+---------+---------+------------------+
| Smoke | .89 | 6.4E-02 | 7.3E-01 | 5.4 5.4E-05 OK|
+----------------------+------+---------+---------+------------------+
| K-TurbKE | .53 | 2.1E-01 | 5.0E-01 | 5.4 3.9E-05 OK|
+----------------------+------+---------+---------+------------------+
| E-Diss.K | .73 | 5.2E-01 | 9.5E-01 | 5.4 2.4E-05 OK|
+----------------------+------+---------+---------+------------------+
----------------------------------------------------------------------
COEFFICIENT LOOP ITERATION = 2 CPU SECONDS = 2.83E+01
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom | .14 | 1.4E-01 | 1.3E+00 | 2.0E-03 OK|
| V - Mom | .16 | 3.5E-02 | 4.9E-01 | 8.3E-03 OK|
| W - Mom | .14 | 5.8E-02 | 1.0E+00 | 1.6E-03 OK|
| P - Mass | .65 | 1.9E-03 | 3.7E-02 | 8.3 5.3E-02 OK|
+----------------------+------+---------+---------+------------------+
| Smoke | .29 | 1.9E-02 | 2.6E-01 | 5.4 5.6E-05 OK|
+----------------------+------+---------+---------+------------------+
| K-TurbKE | .17 | 3.6E-02 | 2.2E-01 | 5.4 8.2E-05 OK|
+----------------------+------+---------+---------+------------------+
| E-Diss.K | .16 | 8.3E-02 | 2.4E-01 | 5.4 6.4E-05 OK|
+----------------------+------+---------+---------+------------------+
----------------------------------------------------------------------
COEFFICIENT LOOP ITERATION = 3 CPU SECONDS = 3.50E+01
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom | .24 | 3.3E-02 | 2.8E-01 | 3.8E-03 OK|
| V - Mom | .23 | 8.0E-03 | 1.1E-01 | 1.4E-02 OK|
| W - Mom | .25 | 1.4E-02 | 2.5E-01 | 3.3E-03 OK|
| P - Mass | .68 | 1.3E-03 | 2.0E-02 | 8.3 3.6E-02 OK|
+----------------------+------+---------+---------+------------------+
| Smoke | .36 | 6.8E-03 | 1.1E-01 | 5.4 6.1E-05 OK|
+----------------------+------+---------+---------+------------------+
| K-TurbKE | .38 | 1.4E-02 | 1.2E-01 | 5.4 8.7E-05 OK|
+----------------------+------+---------+---------+------------------+
| E-Diss.K | .39 | 3.3E-02 | 1.2E-01 | 5.4 8.4E-05 OK|
+----------------------+------+---------+---------+------------------+

ANSYS CFX Output File (parallel runs)

Additional information is written to the Output File for ANSYS CFX-Solver jobs submitted in
parallel.
Partitioning If the partitioning step is run partitioning information pertaining to the current job is
Information displayed. This includes how the mesh is divided, and CPU requirements for the partitioning
process.
Partioning Information appears similar to the following:
+--------------------------------------------------------------------+
| Partitioning Information |
+--------------------------------------------------------------------+
Partitioning tool: MeTiS multilevel k-way algorithm
Number of partitions: 2
Number of graph-vertices: 3695
Number of graph-edges: 25430
Global Partitioning Information:

| Elements | Nodes (Overlap) | Faces |
------------+------------+------------------------+------------+
Full grid | 5454 | 3695 | 4012 |
------------+------------+------------------------+------------+
Part. 1 | 3119 | 1972 6.3% | 2185 |
Part. 2 | 2504 | 1973 6.3% | 1961 |
------------+------------+------------------------+------------+
Sum of part.| 5623 | 3945 6.8% | 4146 |
------------+------------+------------------------+------------+
CPU-Time requirements:
- Preparations 3.215E-01 seconds
- Low-level grid partitioning 2.539E-01 seconds
- Global partitioning information 5.607E-01 seconds
- Vertex, element and face partitioning information 1.529E-01 seconds
- Element and face set partitioning information 1.197E-01 seconds
- Summed CPU-time for grid partitioning 1.409E+00 seconds
Starting job The job information section includes master and slave partition process details.
Information
Job Information appears similar to the following:
+--------------------------------------------------------------------+
| Job Information |
+--------------------------------------------------------------------+
Run mode: parallel run
Host computer: camel

Par. Process: Master running on grid partition: 1
Job started: Wed Oct 21 10:36:07 1998
Host computer: giraffe

Par. Process: Slave running on grid partition: 2
Job started: Wed Oct 21 10:47:49 1998

Host Host Information appears similar to the following:
Information
+-----------------------------------------------------------------------+
| Host Information |
+-----------------------------------------------------------------------+
| Name | Rel. Speed | # of Proc. | # of Part | Stat. Load |
+-----------------+--------------+------------+------------+------------+
| camel | 1.00000 | 1 | 1 | 100.0 % |
| giraffe | 1.00000 | 1 | 1 | 100.0 % |
+-----------------+--------------+------------+------------+------------+
Memory Usage Memory Usage Information appears similar to the following:

Information
+--------------------------------------------------------------------+
| Memory Usage Information |
+--------------------------------------------------------------------+
Allocated storage in: WORDS

WORDS/NODE
Partition | Real | Integer | Character| Logical | Double

----------+----------+----------+----------+----------+------------
1 | 3088040 | 856354 | 200000 | 10000 | 7000
| 485.0 | 134.0 | 31.0 | 1.0 | 1.0
----------+----------+----------+----------+----------+------------
2 | 2987748 | 837506 | 200000 | 10000 | 7000
| 470.0 | 131.0 | 31.0 | 1.0 | 1.0
----------+----------+----------+----------+----------+------------
Total | 6075788 | 1693860 | 400000 | 20000 | 14000
| 507.0 | 141.0 | 33.0 | 1.0 | 1.0
Completed job Completed Job Information appears similar to the following:

Information
+--------------------------------------------------------------------+
| Job Information |
+--------------------------------------------------------------------+
Host computer: camel

Par. Process: Master running on mesh partition: 1
Job finished: Tue Apr 11 10:27:47 2000
or: ( 0: 0: 1: 22.846 )
Host computer: giraffe

Par. Process: Slave running on mesh partition: 2
Job finished: Tue Apr 11 10:27:46 2000
or: ( 0: 0: 7: 55.655 )
--> Master-Partition Nr. 1 reaches final synchronization point!

--> Slave-Partition Nr. 2 reaches final synchronization point!
End of solution stage.
This run of the ANSYS CFX Solver has finished.

ANSYS CFX Partition File

The ANSYS CFX Partition File is generated by the ANSYS CFX-Solver and used as input for a
parallel run. The Partition File is used to store information about the partitioning of the
mesh. The partition file can be used to view mesh partitions before running the ANSYS
CFX-Solver. To do this combine, the Partition File with the Definition file which was used to
produce the Partition File.
On UNIX systems, type:
cat filename.def filename_001.par > newfilename.res
On Windows systems, type:
copy /b filename.def + filename_001.par newfilename.res
This creates a results file which can be loaded in ANSYS CFX-Post and contains the variable
Real partition number.
ANSYS CFX Output File (Mesh Adaption Runs)

Mesh adaption runs display information about multiple types of output.
Convergence History (p. 46 in "ANSYS CFX-Solver Manager, Release 10.0")
Mesh Refinement (p. 46 in "ANSYS CFX-Solver Manager, Release 10.0")
Convergence The information provided during the convergence history is similar to that found in a
History non-adaptive run. However, the mesh adaption run lists the Time Step, Simulation Time and
CPU Seconds for both the current adaption step and the total ANSYS CFX-Solver run.
Convergence History appears similar to the following:
======================================================================
TIME STEP = 28 SIMULATION TIME = 2.80E-01 CPU SECONDS = 9.01E+01
(THIS RUN: 3 3.00E-02 1.59E+01)
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U - Mom | 0.80 | 9.6E-04 | 4.4E-03 | 3.2E-02 OK|
| V - Mom | 0.82 | 1.9E-04 | 2.3E-03 | 2.4E-01 ok|
| W - Mom | 0.94 | 7.4E-06 | 8.5E-05 | 1.4E+00 ok|
| P - Mass | 0.82 | 5.8E-04 | 4.2E-03 | 8.9 7.4E-02 OK|
+----------------------+------+---------+---------+------------------+
| H-Energy | 0.83 | 5.2E-04 | 1.8E-03 | 10.3 4.3E-03 OK|
+----------------------+------+---------+---------+------------------+
Mesh When a mesh adaption step is complete, the Solver Manager reports the new meshing
Refinement information, including the total number of vertices, elements and faces. The ANSYS
CFX-Solver then continues to determine a solution, using the adapted mesh.

Mesh Refinement appears simliar to the following:
+--------------------------------------------------------------------+
| |
| Mesh Refinement |
| |
+--------------------------------------------------------------------+
Adaption step 2 of 3.
Number of elements initially marked for refinement: 480
Number of elements removed because:
They already meet the minimum length criteria: 0
They are in regions not marked for refinement: 0
They are already in the deepest refinement level: 0
There are not enough nodes available to refine them: -425
----------
55
----------
Target number of nodes at end of step: 1512
Number of vertices in the final mesh: 1999

Number of elements in the final mesh: 1560
+--------------------------------------------------------------------+
| Total number of Vertices, Elements, and Faces |
+--------------------------------------------------------------------+
Domain Name : nozzle vmi
Total number of Vertices = 1999
Total number of Elements = 1560

Total number of Tetrahedrons = 146
Total number of Hexahedrons = 818
Total number of Pyramids = 596
Total number of Faces = 1702
ANSYS CFX Output File (Conjugate Heat Transfer Runs)

Thermal Energy When a solid domain is included, the Solver Manager reports the thermal energy that flows
at Solid into and out of the solid, across existing boundaries. If the solid is a source term, the total
Boundary
thermal energy added is included, along with a global imbalance.
Thermal Energy at Solid Boundary appears similar to the following:
+--------------------------------------------------------------------+
| Boundary T-Energy - 2 Flow and Total Source Term Summary |
+--------------------------------------------------------------------+
Boundary : Default Solid 0.0000E+00
Boundary : Default Fluid Solid2 -3.0742E+06
Subdomain : heater 3.0685E+06
-----------
Global T-Energy - 2 Balance: -5.6725E+03

ANSYS CFX Output File (GGI Runs)

Running the ANSYS CFX Flow Solver for cases that include GGI interfaces is similar to cases
without GGI connections. The following differences, however, will be observed:
At the start of the simulation, all GGI connection conditions are processed. This may
require the computational effort of the order of a single iteration or timestep of the flow
simulation. If a GGI connection condition is found to contain non-overlapping portions,

the percentage of the area of each side that is non-overlapping is reported. This is a
useful diagnostic, and should be reviewed to confirm that the expected amount of
non-overlapping area has been detected.
+--------------------------------------------------------------------+
| Total Number of Nodes, Elements, and Faces |
+--------------------------------------------------------------------+
Domain Name : rotor

Total Number of Hexahedrons = 33202
Domain Name : stator

Total Number of Tetrahedrons = 75265
Total Number of Prisms = 31395
Domain Interface Name : Rotor Periodic
Non-overlap area fraction on side 1 = 0.0 %

Domain Interface Name : Stator Periodic

Residual diagnostics will be reported for each domain, for example the mass and
momentum equation residuals will be reported independently for each independent
domain.
======================================================================
----------------------------------------------------------------------
+----------------------+------+---------+---------+------------------+
| U-Mom-rotor | 0.92 | 2.2E-05 | 3.6E-04 | |
| V-Mom-rotor | 0.90 | 3.6E-05 | 1.0E-03 | |
| W-Mom-rotor | 0.91 | 4.1E-05 | 9.1E-04 | |
| P-Mass-rotor | 0.94 | 1.2E-05 | 4.7E-04 | |
| U-Mom-stator | 0.89 | 2.1E-05 | 1.1E-03 | 1.3E-02 OK|
| V-Mom-stator | 0.84 | 9.9E-05 | 3.1E-03 | 3.1E-02 OK|
| W-Mom-stator | 0.86 | 7.4E-05 | 3.8E-03 | 2.6E-02 OK|
| P-Mass-stator | 0.89 | 1.4E-05 | 3.8E-04 | 10.0 6.6E-02 OK|
+----------------------+------+---------+---------+------------------+
| H-Energy-rotor | 0.92 | 7.7E-06 | 2.5E-04 | |
| H-Energy-stator | 0.88 | 5.4E-06 | 1.7E-04 | 6.1 5.4E-02 OK|
+----------------------+------+---------+---------+------------------+
| K-TurbKE-rotor | 1.62 | 1.2E-04 | 5.7E-03 | |
| K-TurbKE-stator | 0.86 | 1.1E-04 | 3.5E-03 | 6.1 9.7E-02 OK|
+----------------------+------+---------+---------+------------------+
| E-Diss.K-rotor | 2.52 | 4.0E-04 | 1.6E-02 | |

| E-Diss.K-stator | 0.87 | 1.8E-04 | 4.9E-03 | 7.5 1.5E-03 OK|
+----------------------+------+---------+---------+------------------
Flows across GGI interfaces will be reported in flow summary diagnostics. Changes in
GGI flows will occur in various situations. For example, momentum flows change as they
undergo rotation at rotational periodic GGI connections. All transport equation flows,
including the mass equation, change for the case of pitch change at a frame change GGI
connection, as well as the energy equation flows as conservation changes from absolute
frame to relative frame energy components. Pressure forces are also reported in the
momentum flow balances at contiguous and periodic GGI connections, for cases having
non-overlapping portions of the interface (from the no-slip wall that is employed).
Various quantities such as ranges of dependent variables, locations of maximum
residuals, etc., are reported at the end of the simulation on a per-domain basis.
=--------------------------------------------------------------------+
| Locations of Maximum Residuals |
+--------------------------------------------------------------------+
| Equation | Node # | X | Y | Z |
+--------------------------------------------------------------------+
| U-Mom-rotor | 5109 | 3.849E-01 | 4.761E-02 | 1.572E-01 |
| V-Mom-rotor | 4501 | 3.846E-01 | 5.065E-02 | 1.176E-01 |
| W-Mom-rotor | 3085 | 3.802E-01 | 5.029E-02 | 1.177E-01 |
| P-Mass-rotor | 3642 | 3.799E-01 | 5.260E-02 | 1.572E-01 |
| U-Mom-stator | 32356 | 4.535E-01 | 5.403E-02 | 5.000E-02 |
| V-Mom-stator | 496 | 4.541E-01 | 5.343E-02 | 4.939E-02 |
| W-Mom-stator | 496 | 4.541E-01 | 5.343E-02 | 4.939E-02 |
| P-Mass-stator | 2275 | 4.536E-01 | 5.349E-02 | 4.949E-02 |
| H-Energy-rotor | 18527 | 4.535E-01 | 5.694E-02 | 5.263E-02 |
| H-Energy-stator | 498 | 4.541E-01 | 5.352E-02 | 4.961E-02 |
| K-TurbKE-rotor | 8583 | 4.110E-01 | 4.671E-02 | 5.692E-02 |
| E-Diss.K-rotor | 8598 | 4.109E-01 | 4.667E-02 | 5.719E-02 |
| K-TurbKE-stator | 7264 | 4.540E-01 | 5.358E-02 | 4.959E-02 |
| E-Diss.K-stator | 7264 | 4.540E-01 | 5.358E-02 | 4.959E-02 |
+--------------------------------------------------------------------+

ANSYS CFX Output File (Combustion Runs)

Running a Combustion simulation in the ANSYS CFX-Solver is similar to multicomponent
fluid runs with the following differences:
For multistep reactions, only those fluid components that participate in the reaction will
be solved using the coupled scalar linear solver, while others (such as passive
components) will be solved in a segregated manner.
The flow summary for each component indicates the mass flow for each of the
components at inlet, outlet or opening boundaries, while the reported Domain value
indicates the rate of mass production(+)/consumption(-) for the component in that
domain.
+--------------------------------------------------------------------+
| CH4 |
+--------------------------------------------------------------------+
Boundary : airin 0.0000E+00
Boundary : fuelin 2.5535E-03
Boundary : out -1.1816E-07
Boundary : secairin 0.0000E+00
Domain : Combustor -2.5534E-03
-----------
Global CH4 Balance: 7.9162E-09
+--------------------------------------------------------------------+
| O2 |
+--------------------------------------------------------------------+
Boundary : airin 1.6018E-02
Boundary : fuelin 0.0000E+00
Boundary : secairin 8.5617E-04
Domain : Combustor -1.0185E-02
-----------
Global O2 Balance: 5.5227E-07
+--------------------------------------------------------------------+
| CO2 |
+--------------------------------------------------------------------+
Domain : Combustor 7.0061E-03
-----------
Global CO2 Balance: -3.0082E-07
+--------------------------------------------------------------------+
| H2O |
+--------------------------------------------------------------------+

ANSYS CFX-Solver Files: List of Variables
Domain : Combustor 5.7373E-03
-----------
Global H2O Balance: -2.5053E-07
ANSYS CFX Output File (Radiation Runs)

When the Thermal Radiation P1 model has been selected:
A new variable named I-Radiation is solved for.
It should be noticed that for heat flux specified boundaries (adiabatic, for example) the
specified heat flux can verified by adding q rad to the boundary flow in the H-Energy
flow summary.
q spec = q rad + q cond (Eqn. 5)
When the Rosseland model is selected:

No additional equation is solved. Hence, no thermal radiation flow summary will be
available.
The total heat flux is reported by the H-Energy flow summary.
q rad + q cond (Eqn. 6)
+--------------------------------------------------------------------+
| I-Radiation |
+--------------------------------------------------------------------+
Boundary : airin -1.6773E+00
Boundary : fuelin -3.1382E-01
Boundary : secairin -2.3366E+01
Domain : Combustor 3.0218E+01
-----------
Global I-Radiation Balance: 5.9579E+00
List of Variables
The following is a list of the variables which you may have defined in ANSYS CFX-Pre or are
available for viewing in ANSYS CFX-Post and exporting to other files. Many variables are only
relevant for specific physical models.
Some variables are only defined on the boundaries of the model. There are marked with a
bullet in the Boundary column. When using these variables in ANSYS CFX-Post, there are
only a limited number of useful things that you may do with these. For details, see Boundary
Value Only Variables (p. 30 in "ANSYS CFX-Post, Release 10.0").

The information given includes:
Short Name
This is the name that must be used in CEL expressions.
Dimensions
User Level
This is useful when using the ANSYS CFX Export facility. For details, see File Export Utility
(p. 117 in "ANSYS CFX-Solver Manager, Release 10.0"). Note that the ANSYS CFX-Solver
may sometimes override the user level setting depending on the physics of the
problem. In these cases, the User Level may be different to that shown in the table
below.
Boundary
This column contains a symbol if the variable only contains non-zero values on the
boundary of the model. See above for more details.
Definition
This column shows the definition of the variable.
This is not a complete list of variables. Information on obtaining details on all variables is
available. For details, see RULES and VARIABLES Files (p. 70 in "ANSYS CFX-Solver Manager,
Release 10.0").
Variables relevant for most CFD calculations

The following table contains a list of variables (with both long and short names) that can be
used when working with CFD calculations.
Long Name Short Dimensions Definition
User Level
Boundary
Name
Density density kg m^-3 1

Dynamic viscosity kg m^-1 s^-1 2 For details, see Dynamic Viscosity (p. 45 in
Viscosity "ANSYS CFX-Solver, Release 10.0:
Modelling").
Velocity* vel m s^-1 1 Velocity vector.
Velocity u u m s^-1 1 Components of Velocity.
Velocity v v
Velocity w w
Pressure p kg m^-1 s^-2 1 For details, see Modified Pressure (p. 12 in
"ANSYS CFX-Solver, Release 10.0:
Theory").
Static pstat kg m^-1 s^-2 3 For details, see Static Pressure (p. 11 in
Pressure "ANSYS CFX-Solver, Release 10.0:
Theory").
Total ptot kg m^-1 s^-2 2 For details, see Total Pressure (p. 19 in
Pressure "ANSYS CFX-Solver, Release 10.0:
Theory").
Wall Shear wall shear kg m^-1 s^-2 3 For details, see Scalable Wall-Functions
(p. 98 in "ANSYS CFX-Solver, Release 10.0:
Theory").

User Level
Boundary
Name
Volume of m^3 Volume of finite volume. For details, see

Finite Discretisation of the Governing Equations
Volume (p. 239 in "ANSYS CFX-Solver, Release
10.0: Theory").
x coordinate x m 2 Cartesian coordinate components.
y coordinate y m 2
z coordinate z m 2
Kinematic visckin kg m^2 s^-1 2 For details, see Kinematic Diffusivity (p. 29
Diffusivity in "ANSYS CFX-Solver, Release 10.0:
Modelling").
Shear Strain sstrnr s^-1 2
Rate
Specific Heat Cp m^2 s^-2 K^-1 2 For details, see Radiation Properties (p. 47
Capacity at in "ANSYS CFX-Solver, Release 10.0:
Constant Modelling").
Pressure
Specific Heat Cv m^2 s^-2 K^-1 2
Capacity at
Constant
Volume
Thermal cond kg m s^-3 K^-1 2 For details, see Thermal Conductivity
Conductivity (p. 46 in "ANSYS CFX-Solver, Release 10.0:
Modelling").
Temperature T K 1 For details, see Static Temperature (p. 14
in "ANSYS CFX-Solver, Release 10.0:
Theory").
Total Ttot K 1 For details, see Total Temperature (p. 15 in
Temperature "ANSYS CFX-Solver, Release 10.0:
Theory").
Wall Heat Qwall kg s^-3 2 For details, see Bulk Heat Flux / Heat Flux
Flux (p. 74 in "ANSYS CFX-Solver, Release 10.0:
Modelling").
Heat Transfer htc kg s^-3 K-1 2 For details, see Wall Heat Transfer (p. 74 in
Coefficient "ANSYS CFX-Solver, Release 10.0:
Modelling").
Total htot kg m^2 s^-2 For details, see The Energy Equation (p. 27
Enthalpy in "ANSYS CFX-Solver, Release 10.0:
Theory").
Static enthalpy kg m^2 s^-2 2 For details, see Heat Transfer (p. 48 in
Enthalpy "ANSYS CFX-Solver, Release 10.0:
Theory").
*. When a rotating frame of reference is used, all variables in the CFX-5 Results File are
relative to the rotating frame, unless specified as a Stn Frame variable.
. Both Pressure and Total Pressure are measured relative to the reference pressure that
you specified on the Domains panel in ANSYS CFX-Pre. Additionally, Pressure is the total
normal stress, which means that when using the k-e turbulence model, Pressure is the
thermodynamic pressure plus the turbulent normal stress. Static Pressure is the
thermodynamic pressure, in most cases this is the same as Pressure. For details, see
Reference Pressure (p. 11 in "ANSYS CFX-Solver, Release 10.0: Theory").
** Variables relevant for calculations involving energy transfer

Variables relevant for turbulent flows

used when working with turbulent flows.
User Level
Boundary
Name
Turbulence ke m^2 s^-2 1 For details, see The k-e model in ANSYS CFX
Kinetic (p. 72 in "ANSYS CFX-Solver, Release 10.0:
Energy Theory").
Turbulence ed m^2 s^-3 1 For details, see The k-e model in ANSYS CFX
Eddy (p. 72 in "ANSYS CFX-Solver, Release 10.0:
Dissipation Theory").
Turbulent tef s^-1 1
Eddy
Frequency
Eddy eddy kg m^-1 s-1 2 For details, see Eddy Viscosity Turbulence
Viscosity viscosity Models (p. 70 in "ANSYS CFX-Solver,
Release 10.0: Theory").
Reynolds rs m^2 s^-2 2 This is a tensor quantity with six
Stress components. For details, see Reynolds
Stress Turbulence Models (p. 81 in "ANSYS
CFX-Solver, Release 10.0: Theory").
Yplus yplusstd dimensionless 2 For details, see Scalable Wall-Functions
Theory").
Solver Yplus yplus dimensionless 2 For details, see Scalable Wall-Functions
Theory").
Variables relevant for buoyant flow

used when working with buoyant flows.
User Level
Boundary
Name
Thermal beta K^ -1 2 For details, see Radiation Properties (p. 47

Expansivity in "ANSYS CFX-Solver, Release 10.0:
Modelling").

Variables relevant for compressible flow

used when working with compressible flows.
User Level
Boundary
Name
Mach Mach dimensionless 1 For details, see Local Mach number, U/c
Number (p. 9 in "ANSYS CFX-Solver, Release 10.0:
Theory").
Isentropic isentropic m^-2 s^2 2
Compressibili compressi d
------
ty bility dp S
Isothermal isothermal m^-2 s^2 2
Compressibili compressi d
------
ty bility dp T
Variables relevant for calculations with a rotating frame of reference

used when working with a rotating frame of reference.
User Level
Name Boundary
Total ptotstn kg m^-1 s^-2 2 For details, see Rotating Frame Quantities
Pressure in (p. 21 in "ANSYS CFX-Solver, Release 10.0:
Stn Frame Theory").
Total Ttotstn K 2 For details, see Rotating Frame Quantities
Temperature (p. 21 in "ANSYS CFX-Solver, Release 10.0:
in Stn Frame Theory").
Total htotstn kg m^2 s^-2 2 For details, see Rotating Frame Quantities
Enthalpy in (p. 21 in "ANSYS CFX-Solver, Release 10.0:
Stn Frame Theory").
Mach Machstn dimensionless 1 For details, see Rotating Frame Quantities
Number in (p. 21 in "ANSYS CFX-Solver, Release 10.0:
Stn Frame Theory").
Velocity in velstn m s^-1 2 For details, see Rotating Frame Quantities
Stn Frame (p. 21 in "ANSYS CFX-Solver, Release 10.0:
Theory").
Variables relevant for parallel calculations

used when working with parallel calculations.
User Level
Boundary
Name
Real partition dimensionless The partition that the node was in for the
number parallel run.

Variables relevant for multicomponent calculations

used when working with multicomponent calculations.
User Level
Boundary
Name
Mass Fraction mf dimensionless 1 The fraction of a component in a

multicomponent fluid by mass.
Mass mconc kg m^-3 2 The concentration of a component.
Concentratio
n
Variables relevant for multiphase calculations

used when working with multiphase calculations.
User Level
Boundary
Name
Volume vf dimensionless 1 For details, see Volume Fraction (p. 151 in

Fraction "ANSYS CFX-Solver, Release 10.0:
Modelling").
Conservative vfc dimensionless 2 For details, see Volume Fraction (p. 151 in
Volume "ANSYS CFX-Solver, Release 10.0:
Fraction Modelling").
Superficial volflx m s^-1 1 The Fluid.Volume Fraction multiplied by
Velocity the Fluid.Velocity.


Residual Plotting
Equation Residual (p. 59 in "ANSYS CFX-Solver Manager, Release 10.0")
Convergence results and RMS (p. 60 in "ANSYS CFX-Solver Manager, Release 10.0")
Transient Residual Plotting (p. 61 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
ANSYS CFX-Solver calculates solutions to various equations. However, many cases result in
residual values. This is due to an equation not being fully satisfied. Of course, if the solution
is exact, then the residual is zero. However, since equation results only approximate physics,
the results in a solution do not always match reality.
Equation Residual
ANSYS CFX-Solver calculates the solution to various equations given the appropriate
boundary conditions and models for your particular CFD problem. For details, see Governing
Equations (p. 26 in "ANSYS CFX-Solver, Release 10.0: Theory").
At any stage of a calculation, each equation will not be satisfied exactly, and the residual
of an equation identifies by how much the left-hand-side of the equation differs from the
right-hand-side at any point in space. If the solution is exact then the residuals is zero.
Exact means that each of the relevant finite volume equations is satisfied precisely.
However, since these equations only model the physics approximately, this does not mean
that the solution exactly matches what happens in reality. If a solution is converging,
residuals should decrease with successive timesteps.
For example, assume that a given residual is 0.0005 kg s^-1. It is not obvious whether such
a residual is large or small. For instance, if the problem involves flows such that about 0.5 kg
flows into (and out of) each mesh element every second, then a residual of 0.0005 kg s^-1

Residual Plotting: Convergence results and RMS
means the equation is satisfied to within one part in a thousand, which is likely a reasonable
solution. However, if the problem involves flows of about 0.001 kg s^-1 into each mesh
element, then the residual is nearly as large as the flow, and the solution is not good.
To make the scales of the residuals meaningful, the solver normalizes values by dividing the
appropriate scales at each point. It is these Normalised Residuals that are plotted by Solver
Manager using a log (base 10) scale.
The exact details of how the residuals are normalised are involved. For details, see Residual
Normalisation Procedure (p. 252 in "ANSYS CFX-Solver, Release 10.0: Theory"). However, it is
useful to know that residuals are divided by the solution range. If linear solution diverges,
this range may be very large and the normalised residuals would be meaningless.
Convergence results and RMS

A measure of how well the solution is converged can be obtained by plotting the residuals
for each equation at the end of each timestep. For a well-converged solution, the expecation
is that the maximum residual is around 10^-3. Typically, the RMS residual will be an order of
magnitude lower than this.
The RMS (Root Mean Square) residual is obtained by taking all of the residuals throughout
the domain, squaring them, taking the mean, and then taking the square root of the mean.
This should present an idea of a typical magnitude of the residuals.
The Maximum Residuals and/or the RMS Residuals can be displayed in the convergence
history plots by selecting a specific monitor in Monitor Settings. For details, see Monitors tab
The increase of a residual after any particular timestep does not imply that the solution is
diverging. It is usual for residuals to occasionally get larger, especially at the beginning of a
Run.
Note that even though convergence is good, there are still places where the residuals
become larger temporarily.
It is also possible to have runs that do not converge at all, but simply deviate around the
same values.
If the solution fails to converge, or convergence is only happening very slowly, some tips on
how to improve the convergence are available. For details, see Monitoring and Obtaining
Convergence (p. 340 in "ANSYS CFX-Solver, Release 10.0: Modelling").
Tip: If you want to obtain Residual Plots for old Runs, select File > Monitor Finished Run
and select a file to view.

Residual Plotting: Transient Residual Plotting
Transient Residual Plotting

When monitoring a transient run with the plotting of cloop turned on, ANSYS CFX-Solver
Manager outputs the monitor data for each coefficient loop (cloop) within each timestep.
Each timestep is divided by the number of inner coefficient loops. The values are produced
for all variables in each cloop.
With the plotting selected, ANSYS CFX-Solver Manager outputs the graph of monitor data,
plotting a point for each coefficient loop evenly across the space between the previous
timestep and the current one, so that the final coefficient loop datum is plotted on the X
coordinate of the current timestep.
Note: Assume that four coefficient loops were run for timestep 39. The 1st cloop value for a
plotted variable appears at position 38.25, the 2nd at 38.5, the 3rd at 38.75, and the 4th and
final value is plotted at 39.
For details, see Global Plot Settings tab (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0").

Residual Plotting: Transient Residual Plotting

Editing Definition Files
Command File Editor Overview (p. 64 in "ANSYS CFX-Solver Manager, Release 10.0")
File Menu (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Edit Menu (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Help Menu (p. 67 in "ANSYS CFX-Solver Manager, Release 10.0")
Command File Editor Rules (p. 68 in "ANSYS CFX-Solver Manager, Release 10.0")
Command File Editor Appearance (p. 68 in "ANSYS CFX-Solver Manager, Release 10.0")
Editing the Command Language (CCL) File (p. 69 in "ANSYS CFX-Solver Manager, Release
10.0")
Command Language File Rules (p. 69 in "ANSYS CFX-Solver Manager, Release 10.0")
RULES and VARIABLES Files (p. 70 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
An existing definition (or results) file can be edited to make minor changes to a CFD model,
without having to use ANSYS CFX-Pre.

Editing Definition Files: Command File Editor Overview
Workflow overview
These modifications can be performed using either the Command File Editor in CFX-5 Solver
Manager or the cfx5cmds command from the command line, as shown in Figure 4.
Figure 4 Definition file modification workflows
Command
File Editor
Solver Solver
Manager Manager
Original Modified
Definition Definition
File File
cfx5cmds cfx5cmds
Text Editor
Editing a Definition File

The simplest method of making changes to an existing Definition File is to use the
Command File Editor. The Command File Editor provides a tree-structured representation
of a definition file. This allows modification of parameter settings and the addition of new
parameters. Existing definition files can be opened for editing as required.
Edit Definition File command (p. 90 in "ANSYS CFX-Solver Manager, Release 10.0")
The Command File Editor can also be launched to edit a run in progress or to edit the current
results file.
Edit Run In Progress command (p. 93 in "ANSYS CFX-Solver Manager, Release 10.0")
Edit Current Results File command (p. 94 in "ANSYS CFX-Solver Manager, Release 10.0")
Command File Editor Overview

The ANSYS CFX Command File Editor is a menu-driven module that facilitates the transfer of
information to and from the definition file.
The ANSYS CFX Command Language file uses a hierarchy to make accessing information
easier.

Editing Definition Files: Menus in the Command File Editor
The Command File Editor can be invoked in multiple ways and each way provides a different
function:
Tools > Edit Definition File
For details, see Edit Definition File command (p. 90 in "ANSYS CFX-Solver Manager,
Release 10.0").
Tools > Edit Run In Progress
For details, see Edit Run In Progress command (p. 93 in "ANSYS CFX-Solver Manager,
Release 10.0").
Tools > Edit Current Results File
For details, see Edit Current Results File command (p. 94 in "ANSYS CFX-Solver Manager,
Release 10.0").
Menus in the Command File Editor

The Command File Editor has three menus:
File Menu (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Edit Menu (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Help Menu (p. 67 in "ANSYS CFX-Solver Manager, Release 10.0")
File Menu
The File menu contains:
Save Command (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Validate Command (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Exit Command (p. 65 in "ANSYS CFX-Solver Manager, Release 10.0")
Save Command Saves the file and returns the ANSYS CFX Command Language file information to the ANSYS
CFX Definition File.
Validate Checks the format of the ANSYS CFX Command Language file for necessary content and
Command reports any errors. Validation of units is performed each time a parameter is edited.
Exit Command Closes the Command File Editor. A prompt is displayed if there are unsaved changes.
Edit Menu
The Edit menu contains:
Add Parameter Command (p. 66 in "ANSYS CFX-Solver Manager, Release 10.0")
Edit Parameter Command (p. 66 in "ANSYS CFX-Solver Manager, Release 10.0")
Delete Parameter Command (p. 67 in "ANSYS CFX-Solver Manager, Release 10.0")
Add Expert Parameter Section Command (p. 67 in "ANSYS CFX-Solver Manager, Release
10.0")
Find Command (p. 67 in "ANSYS CFX-Solver Manager, Release 10.0")
Find Next Command (p. 67 in "ANSYS CFX-Solver Manager, Release 10.0")

Add Parameter Some categories (e.g. the FLOW > SOLVER CONTROL > CONVERGENCE CONTROL section)
Command allow additional parameters that are not shown by default.
The Add Parameter option is used to:
Add a new parameter to a category when the category is selected.
Add an expert parameter to the ANSYS CFX Command Language file after the Expert
Parameter Section has been created. For details, see Add Expert Parameter Section
Command (p. 67 in "ANSYS CFX-Solver Manager, Release 10.0").
If a parameter can be added to a section, a dialog box displays with a drop-down list of
available parameters. Ensure that parameters being added make sense and use correct units
as required.
1. Select a parameter that allows additional parameters to be added.
2. Select Edit > Add Parameter.
3. In the drop down list select a parameter.
4. Under Value, enter specific information about the parameter.
For details, see Command File Editor Rules (p. 68 in "ANSYS CFX-Solver Manager, Release
10.0").
5. Click OK.
Edit Parameter The Edit Parameter option allows changes to an existing expert parameter in the ANSYS CFX
Command Command Language file.
When the Command File Editor is first opened, the Root is displayed. It contains three
categories: LIBRARY, EXECUTION CONTROL (seen only when editing version 5.5 or later . res
files) and FLOW.
In .def files, only two categories are displayed: LIBRARY and FLOW.
Note: Parameters that can be edited display the Value in green. Other parameters cannot be
changed from the Command File Editor.
Expanding categories
Additional information about a category can be seen by expanding it.
1. Click the plus/minus boxes to expand or reduce the category selection.
Tip: Right-click to expand the category and all of its sub-categories.
Editing entries
Important: Editing the ANSYS CFX Command Language file changes the ANSYS CFX
Definition File, but does not make changes to the ANSYS CFX-Pre Case file. In other words,
changes made by the Command File Editor are used by the ANSYS CFX-Solver but do not
appear when the case file is reopened in ANSYS CFX-Pre.
A sample of this procedure is available. For details, see Supersonic Flow Over a Wing (p. 169
in "ANSYS CFX, Release 10.0: Tutorials").
1. Expand the Name of the entry until a Value in green or orange is displayed.
Editable values display in green or in orange.
2. Double click the value to edit.
The Edit Parameter dialog box is displayed.

3. Edit the value as required.
In some parameters this may require edits to text and in others a selection in a
dropdown list box. For details, see Command File Editor Rules (p. 68 in "ANSYS
4. Click OK.
5. When all modifications have been made, save the file.
Changes made to the ANSYS CFX Command Language file are written in the definition
file.
Delete The Delete Parameter option is used to remove an expert parameter from the ANSYS CFX
Parameter Command Language file.
Command
Add Expert The Add Expert Parameter Section provides access to the expert parameters in ANSYS CFX.
Parameter An Expert Parameter Section must be created before adding expert parameters to the
Section
ANSYS CFX Command Language file.
Command
Before adding any expert parameters to the ANSYS CFX Command Language file, first add
an Expert Parameters section to the tree structure displayed in the Command File Editor.
1. Select Edit > Add Expert Parameter Section.
The EXPERT PARAMETERS: section is added to the bottom of the FLOW branch of the
tree.
2. Expand FLOW.
3. Select EXPERT PARAMETERS.
4. Add parameters as required.
For details, see Add Parameter Command (p. 66 in "ANSYS CFX-Solver Manager, Release
10.0").
Once the value for an Expert Parameter has been set, it can be edited as needed. For details,
see Edit Parameter Command (p. 66 in "ANSYS CFX-Solver Manager, Release 10.0").
Find Command Allows searching of the ANSYS CFX Command Language file for a keyword or keywords.
Find Next Finds the next occurrence of the keyword or keywords.

Command
Help Menu
The Help menu contains:
On ANSYS CFX Definition File Editor Command (p. 67 in "ANSYS CFX-Solver Manager,
Release 10.0")
On Expert Parameters Command (p. 68 in "ANSYS CFX-Solver Manager, Release 10.0")
On ANSYS CFX The help associated with the Command File Editor is launched.
Definition File
Editor
Command

Editing Definition Files: Command File Editor Rules
On Expert The CFX-Solver Expert Control Parameters help is launched.
Parameters
Command
Command File Editor Rules

If unsure as to an appropriate value to enter, select Help > On Expert Parameters from the
main Command File Editor window to view a description and valid values for the
parameters.
The following rules apply when using the Command File Editor:
Everything is case-sensitive. Use care to distinguish upper case letters from lower case
letters.
Parameter names must start with a letter (not a number or symbol). Subsequent
characters can be letters, numbers, spaces or tabs.
Spaces appearing before or after a name are not considered to be part of the name.
Multiple spaces and tabs appearing inside a name are treated as a single space.
For parameters requiring a logical value, enter T or t for true, and F or f for false. For many
parameters requiring an integer value only a few integer values are valid.
These rules should suffice for simple editing operations. To perform more complicated
editing operations, consider editing the command file directly. For details, see Editing the
Command Language (CCL) File (p. 69 in "ANSYS CFX-Solver Manager, Release 10.0").
Command File Editor Appearance

Some of the file information under Name and Value headings may be truncated when the
tree structure is expanded. The amount of space allocated to the name or the value can be
configured.
1. Position the mouse cursor between the Name and Value headings.
That is, place the cursor over the line that separates the two headings. The cursor
appears as a double line with an arrow to the left and the right.
2. Click and drag to expand or contract the width of the column.
Tip: For lengthy lines (i.e. those that contain lists) double-click on the line. This opens the
line in a configurable dialog box for viewing and editing.

Editing Definition Files: Editing the Command Language (CCL) File
Editing the Command Language (CCL) File

In some circumstances, more significant changes may be required to the definition file than
the Command File Editor allows. ANSYS CFX allows the use of a text editor to edit the ANSYS
CFX Command Language file.
Note: This feature is for expert users only. Extreme care must be taken when editing a ANSYS
CFX Command Language file. Changes made to the ANSYS CFX Command Language file are
reflected in the definition file and may have negative effects on the model. It is strongly
advised that original files are backed up before edits are made to them.
To generate the ANSYS CFX Command Language file, use the cfx5cmds command in a
UNIX terminal or a Windows command line. Ensure this is set up correctly to run ANSYS CFX
commands. For details, see Command Line (p. 99 in "ANSYS CFX, Release 10.0: Installation
and Overview").
Command Language File Rules

The following rules apply when using a text editor to change a ANSYS CFX Command
Language file:
We do not recommend changing the Solution Units outside of ANSYS CFX-Pre. For
details, see Solution Units (p. 130 in "ANSYS CFX-Pre, Release 10.0").
Everything apart from Expert Parameter names is case-sensitive. Use care to distinguish
upper case letters from lower-case letters. It is recommended that lower case letters are
used for Expert Parameter names to match those shown in the Command File Editors
Expert Parameters section.
The name of any variable must start with a letter (not a number or symbol). Subsequent
characters can be letters, numbers, spaces, or tabs.
Spaces appearing before or after a name are not considered to be part of the name.
Multiple spaces and tabs appearing inside a name are treated as a single space.
Nothing is sensitive to indentation. Indentation is used only to make the appearance of
the text clearer.
The comment character is the pound, or number sign (#). Anything appearing to the
right of this character is ignored. For instance:
PARAMETER = 3.2 # This text is ignored
The line continuation character is the backslash (\). To break a long line of text into two
or more lines, insert a backslash character at the end of the first line. For instance, both
of the following lines are handled the same way:
NAME = default temperature used in the first simulation

NAME = default temperature used in the first simulation
A line containing ANSYS CFX Expression Language must be no more than 256 characters
long. Other lines can be of any length.

Editing Definition Files: RULES and VARIABLES Files
The Rules and Variables files can be a useful guide when editing a CCL file. For details, see
RULES and VARIABLES Files (p. 70 in "ANSYS CFX-Solver Manager, Release 10.0").
Some objects in the CCL file can be defined with a default value and then overridden by local
values. For example, the SOLVER CONTROL section of a CCL file may look like:
SOLVER CONTROL :
CONVERGENCE CONTROL :
Maximum Number of Iterations = 100
Physical Timescale = 5.E-1 [s]
END
EQUATION CLASS : momentum
CONVERGENCE CONTROL :
Physical Timescale = 1.E-1 [s]
END
END
CONVERGENCE CRITERIA :
Residual Type = RMS
Residual Target = 1.E-4
END
ADVECTION SCHEME :
Option = Upwind
END
DYNAMIC MODEL CONTROL :
Global Dynamic Model Control = No
END
END
The first CONVERGENCE CONTROL object defines values that apply to all equation classes.
The Physical Timescale is then locally overridden for the momentum equation class. Other
objects, including the ADVECTION SCHEME, can be locally overridden in the same way. The
order in which objects appear is not important, so an object can be assigned an override
before its default has been set. Only some parameters may be set to a different local value;
for example, it does not make sense to set the Maximum Number of Iterations locally.
RULES and VARIABLES Files

The RULES and VARIABLES file can be useful when editing a CCL file. They provide
information on valid options, variables and dependencies. Both files are located in
<CFXROOT>/etc/ and can be viewed in any text editor.
Note: In some cases, the RULES and VARIABLES files contain information about variables,
parameters, models and options that are not yet fully supported in the ANSYS CFX-Solver.
Use caution with features that are not documented elsewhere as these may cause the
ANSYS CFX-Solver to fail or produce invalid results.

VARIABLES File
The VARIABLES file lists all the variables available in the ANSYS CFX-Solver. Information
provided for each variable appears similar to the following:
VARIABLE: vel
Option = Definition
MMS Name = VEL
Long Name = Velocity
Tensor Type = VECTOR
Quantity = Velocity
Status = P
User Level = 1
Output to Jobfile = No
Output to Postprocessor = Yes
Component Short Names = \
u, \
v, \
w
Component Long Names = \
Velocity u, \
Velocity v, \
Velocity w
Component MMS Names = \
VEL-1, \
VEL-2, \
VEL-3
General Availability = ADAPTION, RESULTS, CEL
Variable Description = Velocity
Variable Scope = PHASE
END
The following information can be identified:

The name appearing immediately after VARIABLE: (in this case vel) is the ANSYS
CFX-Solver name or short name for the variable.
For scalar quantities (Tensor Type = SCALAR), the name appearing after VARIABLE:
is the name that must be used in any CEL expressions. The MMS Name and Long Name
are not valid names to use for this purpose.
For vector and tensor quantities (Tensor Type = VECTOR and Tensor Type =
SYMTEN2), the Component Short Names (u, v and w in this case) are names that must
be used in any CEL expressions.
The User Level setting controls when the variable is seen. Variables of
User Level = 1 will appear in drop-down variable selection menus in ANSYS
CFX-Post. Variables with User Level = 2 or User Level = 3 will only appear in the
full list of variables.
The Output to Postprocessor setting controls if the variable is written to the results
file for use in ANSYS CFX-Post. A variable must be involved in the simulation before is
has the potential to be written out.
The General Availability field determines when a variable can be used. Only
variables whose General Availability includes CEL can be used in CEL expressions.
The names of all VARIABLE, EQUATION DEFINITION and FUNCTION objects are
reserved names. These names should not be used as the name for any CEL expressions,
Additional Variables, User Routines or User Function,s etc.

The end of the VARIABLES file contains a section listing call back definitions. Using call
backs which are not documented, or using them on locations other than those documented
will produce invalid results. For details, see Additional CEL functions in ANSYS CFX-Pre/ANSYS
CFX-Solver (p. 71 in "ANSYS CFX, Release 10.0: Reference Guide").
RULES File
The RULES file contains information about which models and parameters are valid options.
This includeds SINGLETON, OBJECT and PARAMETER items.
RULES The first items in the RULES file list the top level SINGLETON objects. All other items are
children of these optional top level objects.
RULES: This could be used to modify the list of allowed options. This should always be
done locally.
LIBRARY: Includes libraries for materials, reactions, CEL and user routines. Add new
materials and reactions using a local library.
FLOW: Contains the current problem definition.
USER: Where user parameters may be stored for later retrieval through User Fortran.
COMMAND FILE: Contains the command file version number.
EXECUTION CONTROL: Contains information about the parallel setup and other settings
controlled in the ANSYS CFX-Solver Manager.
Details about models that are not available can also be found through the user interface. For
example, the SINGLETON: ADVECTION SCHEME item includes the QUICK scheme.
SINGLETON A SINGLETON object is permitted to appear once as the child of a parent object. For this
reason SINGLETON objects do not have names associated with them, for example:
LIBRARY :
CEL :
EXPRESSIONS :

Each of these three items is a SINGLETON object. The LIBRARY SINGLETON may only have
one CEL SINGLETON, and the CEL SINGLETON may only have one EXPRESSIONS
SINGLETON. Parameters and child definitions do not need to be grouped for a SINGLETON
into a single location; this is done automatically by the ANSYS CFX-Solver. For example, the
following is valid:
LIBRARY :
CEL :
EXPRESSIONS :
myexp1 = 1 [ m ]
END
END
END
...
LIBRARY :
CEL :
EXPRESSIONS :
myexp2 = 2 [ m ]
END
END
END
OBJECT An OBJECT is similar to a SINGLETON except that more than one can appear as the child of
a parent object. For this reason each OBJECT must have a name, for example:
FLOW :
DOMAIN : domain1
...
END
DOMAIN : domain2
...
END
END
Two OBJECT items of type DOMAIN have been defined with names domain1 and domain2.
These are children of the FLOW SINGLETON.
PARAMETER A PARAMETER consists of a name, followed by the = character, followed by a value. Many
parameters in the RULES file cannot be set in a CCL file and therefore cannot be altered.
The Parameter Type tells you the type of values the parameter is allowed to take. It
could be Real, Real List, Integer, Integer List, String or String List. When a list is valid,
items should be comma separated.
Some parameters contain an Allowed String List. This containes valid strings that
can be used for that parameter.
Each PARAMETER that you can set has a Dependency List which lists the variables the
PARAMETER can depend upon. XYZ refers to the x, y and z coordinates. XYZT refers to the
x, y and z coordinates and time. The CCL file can be edited based on the dependencies
listed here.
If a PARAMETER contains the item Dynamic Reread Item = Yes, then it can be
modified while a run is in progress. Some SINGLETON objects also contain this item. For
details, see Edit Run In Progress command (p. 93 in "ANSYS CFX-Solver Manager, Release
10.0").


File Menu
Define Run command (p. 75 in "ANSYS CFX-Solver Manager, Release 10.0")
Monitor Run in Progress command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Monitor Finished Run command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Close command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Quit command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
There are a variety of options that can be used to perform actions related to the software.
The File menu contains:
Define Run command (p. 75 in "ANSYS CFX-Solver Manager, Release 10.0")
Monitor Run in Progress command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Monitor Finished Run command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Quit command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0")
Define Run command

The information required to define a run depends on the application and options can be
configured. For details, see Define Run dialog box (p. 13 in "ANSYS CFX-Solver Manager,
Release 10.0").

File Menu: Monitor Run in Progress command
Monitor Run in Progress command

Used when Solver Manager has been closed and the display of a run currently underway in
the Solver needs to be re-opened.
1. Select File > Monitor Run in Progress.
The Select a Run Directory (.dir) dialog box is displayed.
2. Browse to the directory containing the current run.
3. Select the current run.
4. Click OK.
Data up to the current timestep is loaded.
Monitor Finished Run command

Used when the residual plots of a finished run are to be viewed.
1. Select File > Monitor Finished Run.
The Monitor Finished Run dialog box is displayed.
2. Under File Type, select the type of files to view.
3. Browse to the directory containing the finished run.
4. Select the run to view.
If required, select a different file
5. Click OK.
The data is loaded.
Close command
Used to close all windows related to the current run. Any other runs that were open are not
affected, and the last open run prior to the current run is displayed. If the Solver was in
progress on the current run, it continues to operate in the background, and the run can be
re-monitored. For details, see Monitor Run in Progress command (p. 76 in "ANSYS CFX-Solver
Quit command
Used to exit ANSYS CFX-Solver Manager. Closing CFX-Solver Manager does not stop
CFX-Solver jobs which are currently running. CFX-Solver Manager can be re-opened to take
control of these jobs again simply by opening CFX-Solver Manager and selecting Monitor
Run in Progress. For details, see Monitor Run in Progress command (p. 76 in "ANSYS
1. Select File > Quit.
2. Click Quit or Cancel.

Edit Menu
Options command (p. 77 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The Edit menu is used to specify options for the ANSYS CFX-Solver Manager.
The Edit menu contains:
Options command (p. 77 in "ANSYS CFX-Solver Manager, Release 10.0")
Options command
1. Select Edit > Options.
The Options dialog box is displayed.
2. Set SolverManager and Common options as required.
For details, see SolverManager Options (p. 77 in "ANSYS CFX-Solver Manager, Release
10.0").
For details, see Common Options (p. 78 in "ANSYS CFX-Solver Manager, Release
10.0").
SolverManager Options
SolverManager options include Miscellaneous settings and Monitor settings.
Miscellaneous 1. Under SolverManager, select Miscellaneous.

2. Select or deselect Warn on large out files.
a. If selected, set a Warning Threshold as the minimum file size for warnings. The
default limit is about 10 MB (10,000,000 bytes).
b. If selected, specify a Default Layout Mode to specify what mode monitors are
presented when starting a new run.
3. Select or deselect Show Original Variable Names.

Edit Menu: Options command
4. If selected, all variable names being shown display in the CFX 5.6 format.Select or clear
Dont write Backup file on Edit Run In Progress.
By default, a backup file is written. For details, see Edit Run In Progress command (p. 93 in
Monitor Multiple options exist that can be monitored as required.

The visibility for each type of residual can be toggled on or off. Settings take effect the
next time a run is started, or the next time a results file is viewed.
If visibility is disabled for all residuals in a plot monitor, the monitor will not be created.
For details, see Customising Solver Manager (p. 12 in "ANSYS CFX-Solver Manager,
Release 10.0").
Monitor options are available to specify global residual display preferences. Settings chosen
on the form apply for all future solver runs and override default display settings for monitors.
Monitors can still be created using the Workspace menu. For details, see New Monitor
1. Under SolverManager, select Monitor.
2. Select or deselect an option.
Common Options
Common options are the same between applications. For details, see Common (p. 45 in
"ANSYS CFX-Pre, Release 10.0").

Workspace Menu
The topics in this section include
Workspace Properties command (p. 80 in "ANSYS CFX-Solver Manager, Release 10.0")
New Monitor command (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0")
Restart Current Run command (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0")
Backup Run command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Arrange command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Toggle Layout Type command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Load Layout command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Save Layout command (p. 87 in "ANSYS CFX-Solver Manager, Release 10.0")
View RMS Residuals command (p. 88 in "ANSYS CFX-Solver Manager, Release 10.0")
View MAX Residuals command (p. 88 in "ANSYS CFX-Solver Manager, Release 10.0")
Reset to Default Workspace command (p. 88 in "ANSYS CFX-Solver Manager, Release
10.0")
Introduction
The Workspace menu controls layout, plots and text windows which are visible in the
viewer. The current run can also be backed up, restarted or stopped.
Properties for the current workspace can be changed, and new monitors created for
simulations.
You can switch between multiple windows and tabbed GUI layout using the Toggle Layout
menu option. Run control can also be carried out using the workspace menu. As well as
stopping and restarting runs, you can back up a simulation which is currently running.
You can switch between viewing RMS and Maximum residual values at any time during or
after a run.

Workspace Menu: Workspace Properties command
The Workspace menu contains:
New Monitor command (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0")
Restart Current Run command (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0")
Backup Run command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Arrange command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Toggle Layout Type command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Load Layout command (p. 86 in "ANSYS CFX-Solver Manager, Release 10.0")
Save Layout command (p. 87 in "ANSYS CFX-Solver Manager, Release 10.0")
View RMS Residuals command (p. 88 in "ANSYS CFX-Solver Manager, Release 10.0")
View MAX Residuals command (p. 88 in "ANSYS CFX-Solver Manager, Release 10.0")
Reset to Default Workspace command (p. 88 in "ANSYS CFX-Solver Manager, Release
10.0")
Workspace Properties command

By default, appropriate monitors are automatically created by ANSYS CFX-Solver Manager
for the particular type of simulation you are running. The type and/or number of plots that
appear can be changed by using Workspace Properties. Not all of the default plots relevant
to the solution are displayed: you can choose them in the Monitors menu. For details, see
Monitors Menu (p. 95 in "ANSYS CFX-Solver Manager, Release 10.0").
When loading a results file or start a Solver run, ANSYS CFX-Solver Manager checks the type
of run before creating the correct plots. For example, a Volume Fraction plot will be created
for multiphase simulations.
Workspace properties include:
General Settings tab (p. 80 in "ANSYS CFX-Solver Manager, Release 10.0")
Monitors tab (p. 80 in "ANSYS CFX-Solver Manager, Release 10.0")
Global Plot Settings tab (p. 85 in "ANSYS CFX-Solver Manager, Release 10.0")
General Settings tab

Out File displays the path and name of the output file from Solver.
Directory displays the path and name of the directory created by Solver.
These files cannot be edited and are for information about the workspace. The locations can
be set in the Working Folder option when defining the run. For details, see Define Run
Monitors tab
Monitors allow customisation of the Solver Manager viewer and text windows. Three types
of monitors exist: Plot Monitors, Residual Monitors and Text Monitors.

Monitor related information includes:
Filter (p. 81 in "ANSYS CFX-Solver Manager, Release 10.0")
Creating Monitors (p. 81 in "ANSYS CFX-Solver Manager, Release 10.0")
Modifying Monitors (p. 81 in "ANSYS CFX-Solver Manager, Release 10.0")
Deleting Monitors (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0")
Plot Monitor (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0")
Residual Monitor (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0")
Text Monitor (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0")
Monitor Properties (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0")
Filter Filter allows specification of the monitors to display.

1. Under Filter, select All, Plot Monitor, Residual Monitor or Text Monitor.
All displays every available monitors. Details on other settings are also available.
For details, see Plot Monitor (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0").
For details, see Residual Monitor (p. 82 in "ANSYS CFX-Solver Manager, Release
10.0").
For details, see Text Monitor (p. 82 in "ANSYS CFX-Solver Manager, Release 10.0").
Creating Monitors
Monitors can be created within Workspace Properties. However, they can also be created
directly from the Workspace menu by selecting New Monitor.
1. Select Workspace > Workspace Properties.
2. Select Monitors.
3. Click New .
The New Monitor dialog box is displayed.
4. Under Name, type the name of the new monitor.
5. Under Type, select Plot Monitor, Residual Monitor or Text Monitor.
6. Click OK.
The Monitor Properties dialog box is displayed.
7. Configure the monitor as required.
Range Settings tab (p. 83 in "ANSYS CFX-Solver Manager, Release 10.0")
Plot Lines tab (p. 83 in "ANSYS CFX-Solver Manager, Release 10.0")
Modifying Monitors
1. Select Workspace > Workspace Properties.
2. Select Monitors.
3. Select the monitor to modify.
4. Click Edit .
The Monitor Properties dialog box is displayed.

5. Configure the monitor as required.
Deleting 1. Select Workspace > Workspace Properties.

Monitors
2. Select Monitors.
3. Select the monitor to delete.
4. Click Delete .
Plot Monitor Plot monitors show the values of expressions versus time step. Monitors can be modified if
required. For details, see Modifying Monitors (p. 81 in "ANSYS CFX-Solver Manager, Release
10.0").
Residual Residual monitors show the values of residuals for equation variables versus time step.
Monitor Monitors can be modified if required. For details, see Modifying Monitors (p. 81 in "ANSYS
Text Monitor Text monitors show the contents of text files that are updated as the run proceeds. Monitors
can be modified if required. For details, see Modifying Monitors (p. 81 in "ANSYS CFX-Solver
Monitor Monitor properties differ depending on the type of monitor. Up to three tabs are available
Properties to configure monitor properties.
General Settings tab

1. Under Window Label, type the name to display for the monitor.
2. If working with a Text monitor:
a. Under Text File Name, click Browse and select a file containing the definition
for the text monitor.
This can be any .out file.
b. Select or clear Disable this Monitor.
If selected, the monitor is disabled.
3. If working with a Plot Monitor or a Residual Monitor:
a. Under Background Colour, click Colour Selector and set the background
colour.
b. Select or clear Display Legend.
If selected, the legend is displayed in the monitor.
c. Under Grid Mode select Both, X, Y or None.
This determines if grid lines appear along the X or Y axis, on both or not at all.
d. Under Grid Colour, click Colour Selector and set the grid colour.

4. Select or clear Visibility.
If selected, the monitor is displayed.
Range Settings Range settings allow multiple timestep range options to be configured.
tab
1. Under Timestep Range Option, select Display All, Most Recent, Fixed or This Run
Only.
Display All displays values for every iteration. If viewing a restarted run, results from
the previous run are also visible .
Most Recent displays the current iteration and a number of previous iterations.
Fixed displays a beginning and end iteration which is always displayed, regardless
of the current iteration number.
This Run Only displays the range for the current run. If the run is a restart, previous
runs are not included in the range.
2. Under Variable Axis, select or clear Use Logarithmic Scale.
If selected, Set Manual Scale (Log) is automatically selected.
3. Under Set Manual Scale (Log) or Set Manual Scale (Linear) set the Upper Bound and
Lower Bound values for the variable axis.
4. Complete the Timestep configuration based on the Timestep Range Option selected.
Most Recent requires a value fo Timestep Window Size.
Fixed requires values for First Timestep and Last Timestep.
Plot Lines tab While not all variable types are available at any given time, the following is a complete list of
all variable types available.
ACCUMULATED TIMESTEP (p. 83 in "ANSYS CFX-Solver Manager, Release 10.0")
BALANCES (p. 83 in "ANSYS CFX-Solver Manager, Release 10.0")
FLOW (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
FORCE (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
NEG ACCUMULATION (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
RESIDUAL (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
SOURCE (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
TIMESTEP (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
USER (p. 84 in "ANSYS CFX-Solver Manager, Release 10.0")
Plot lines can be displayed as required. For details, see Configuring Plot Lines (p. 84 in "ANSYS
Further details on the output of the solver are available. For details, see ANSYS CFX-Solver
Files (p. 27 in "ANSYS CFX-Solver Manager, Release 10.0").
ACCUMULATED TIMESTEP
The accumulated timestep values are plotted.
BALANCES
These are the normalised sum of the flows (i.e. % imbalance), for a given equation, on a
particular domain. The absolute flow is normalised by the maximum flow, calculated by
looking at flows on all domains, for that particular equation.

FLOW
The flows listed in the solver manager are the absolute amounts of a variable transported
through a boundary condition patch. For example, the flow for the continuity (P-Mass)
equation is the mass flow of a particular phase through the boundary patch. The flow for
the energy (H-Energy) equation is the energy flow per unit time through the patch.
FORCE
For details, see Calculated Wall Forces and Moments (p. 39 in "ANSYS CFX-Solver Manager,
Release 10.0").
NEG ACCUMULATION
Negative accumulation is the transient term contribution to the balance equation. See the
information under BALANCES for further details.
RESIDUAL
For details, see Residual Plotting (p. 59 in "ANSYS CFX-Solver Manager, Release 10.0").
SOURCE
Sources are the amount of a variable created or consumed in a particular three dimensional
region of a domain. The region might be user defined, if user defined source terms were set
up, or the region might be the entire domain. SOURCE values which are defined for the
entire domain are automatically computed by the solver, and vary depending on the
models which are being used. For example, automatically computed SOURCE values will
appear in the turbulent kinetic energy equation which represent the production and
dissipation of turbulence.
TIMESTEP
The timestep values are plotted.
USER
If monitor points have been created, a USER category is available. This can be expanded to
select the monitor points to plot. For details, see Monitor tab (p. 225 in "ANSYS CFX-Pre,
Release 10.0").
Configuring Plot Lines

Plot line variables can be configured as required.
1. Expand a plot line variable by clicking + next to it.
Categories are displayed.
2. Expand a category by clicking + next to it.
3. Select or clear specific plot line variables.
4. If working with a Residual Monitor, under Residual Mode, select RMS or MAX.
Residual Mode acts as a visibility filter for variables of Residual type seelcted by default.
If a variable of type Residual is not selected by default it is plotted even if its type does
not match the Residual Mode setting.
5. Click Apply.

Workspace Menu: New Monitor command
Global Plot Settings tab

Plotting of coefficient loop/cloop data is turned off by default.
For Transient runs, this selects or deselects plotting of cloop data for each inner loop. This is
in addition to plotting data for each outer loop/timestep. For details, see Transient Residual
Plotting (p. 61 in "ANSYS CFX-Solver Manager, Release 10.0").
Note: As turning on the cloop setting results in a three to seven times increase in the size of
the monitor data file, it affects the performance of the ANSYS CFX-Solver Manager.
1. Select Workspace > Workspace Properties > Global Plot Settings.

2. Select or clear Plot Coefficient Loop Data.
3. Under Plot Data By select Time Step or Simulation Time.
Variables are plotted against accumulated Time Step (the default) or against
Simulation Time. The latter is useful when using non-uniform time steps.
New Monitor command

This menu allows a shortcut to the creation of new monitors. However, if other properties
associated with a workspace need to be defined, full Workspace Properties should be
viewed. Monitors can then be created as required.
Monitors tab (p. 80 in "ANSYS CFX-Solver Manager, Release 10.0")
Stop Current Run command

Stopping the current run is only available when the current run is in the running state. When
ANSYS CFX-Solver stops, the run is labelled as Finished, and a message displays. This
message names the run and specifies it has terminated at the users request. Additional
information about the run is also listed.
Once manually terminated a run can be manipulated in the same way that a completed run
can.
1. Select Workspace > Stop Current Run or click Stop Current Run .
ANSYS CFX-Solver stops at the end of the next iteration or timestep.
Tip: If running ANSYS CFX-Solver from the command line, imitate the Stop button by
using the command cfx5stop. For details, see Starting CFX-Solver from the Command
Line (p. 99 in "ANSYS CFX-Solver Manager, Release 10.0").
Restart Current Run command

Restarting the current run is only available when a run is finished or stopped. It allows a run
to be restarted. There are numerous ways a run can be set up to restart. For details, see
Restarting a Run (p. 23 in "ANSYS CFX-Solver Manager, Release 10.0").

Workspace Menu: Backup Run command
Restarting a run start the run with the same settings as the previous run, including Parallel
settings.
1. Select Workspace > Restart Current Run or click Restart Current Run .
Backup Run command

Backing up a run creates a backup file of the results at the end of the timestep that is
currently calculating. This file contains sufficient information for restarting a run of for
visualisation. Backup files should be generated if a solution may be diverging and an
intermediate solution needs to be retained.
The backup file is stored in a subdirectory within the working directory. This subdirectory is
given the same name as the current run.
1. Select Workspace > Backup Run or click Backup Run .
Arrange command
Arranging the workspace deletes all monitors that are currently showing, regenerates them,
and redisplays them by optimizing the display based on available screen space. This has no
impact on the display if the layout type has been toggled to display multiple overlapping
tabs. For details, see Toggle Layout Type command (p. 86 in "ANSYS CFX-Solver Manager,
Release 10.0").
1. Select Workspace > Arrange or click Arrange Workspace .
Toggle Layout Type command

Two layout modes exist. One is set up with multiple overlapping tabs used to switch
between Monitors and the other displays each Monitor in its own window. These may be
toggled as required.
1. Select Workspace > Toggle Layout Types or click Toggle Layout Types .
Load Layout command

Layouts can be loaded as required. Before loading a layout, there must be layouts that have
been saved. For details, see Save Layout command (p. 87 in "ANSYS CFX-Solver Manager,
Release 10.0").
1. Select Workspace > Load Layout or click Load Layout .

The Layout File dialog box is displayed.

Workspace Menu: Save Layout command
2. Select the location containing the file to load.
3. Select the file to load.
4. Click Open.
As the new workspace replaces the existing one Solver Manager requires confirmation
that the new workspace should overwrite the existing one.
5. Click Yes.
The new layout is loaded.
Save Layout command

Once a layout has been configured to display preferred settings views, it can be saved. Once
saved, layouts can be loaded as required. For details, see Load Layout command (p. 86 in
This is useful when carrying out different runs for the same problem. For example, there may
be a layout with preferred settings after changing a boundary condition value. Another
layout may be preferred for viewing a turbulence model. By saving and loading a layout, it
is simple to switch between these views.
The saved layout fully restores settings only for problems with the same domain and
boundary names as the problem that was selected in the when the layout was saved. If the
saved layout is loaded when the current problem has different domain and/or boundary
names, variables to plot must be reselected. For details, see Duplicating a plot monitor (p. 87
in "ANSYS CFX-Solver Manager, Release 10.0").
1. Configure the current layout to the appearance to save.
That is, display various monitors, position them, set up the layout type and so on.
2. Select Workspace > Save Layout.
The Layout File dialog box is displayed.
3. If required, set the path location to a different folder.
4. Under Filename, type the name of the file to save.
5. Click Save.
If the name already exists, a warning dialog box is displayed.
Overwrite replaces the old file with the new document.
Re-select returns to the Layout File dialog box.
Cancel closes the open dialog boxes.
Duplicating a plot monitor

Rather than creating plot monitors manually, an existing one can be duplicated and
modified.

Workspace Menu: View RMS Residuals command
The easiest way to create your own plot monitor is to copy the definition of an existing
monitor and edit it to include the new variables. The default monitor files can be found in
the <CFXROOT>/etc/ANSYS CFX/ directory. For example, if you wish to view turbulence
data on the same plot as mass and momentum you could enter the following:
^RESIDUAL,RMS,.*-Mom;^RESIDUAL,RMS,.*-Diss.K; \
^RESIDUAL,RMS,.*-TurbKE;
As stated previously, the string for which a search is made can be found from the variable
lists in the Plot Lines panel of the Monitors form. For details, see Plot Lines tab (p. 83 in
View RMS Residuals command

Selecting this option displays the RMS values of the residuals. For details, see Residual
1. Select Workspace > View RMS Residuals.
View MAX Residuals command

Selecting this option displays the MAX values of the residuals. For details, see Residual
1. Select Workspace > View Max Residuals.
Reset to Default Workspace command

Resets the default workspace to the state it was in immediately after the run was started, or
after a finished run was loaded. This can be useful when retrieving plots that have been
accidentally deleted, or when reloading the original plots after a change to their definition.
Note: Resetting the default workspace deletes any custom monitors.
1. Select Workspace > Reset to Default Workspace.

2. Click Yes.
Close command
For details, see Close command (p. 76 in "ANSYS CFX-Solver Manager, Release 10.0").

Tools Menu
Export command (p. 90 in "ANSYS CFX-Solver Manager, Release 10.0")
Export to ANSYS Multifield command (p. 91 in "ANSYS CFX-Solver Manager, Release 10.0")
Interpolate command (p. 91 in "ANSYS CFX-Solver Manager, Release 10.0")
Post-Process Results command (p. 94 in "ANSYS CFX-Solver Manager, Release 10.0")
View Environment command (p. 94 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The Tools menu controls layout, plots and text windows which are visible in the viewer. The
current run can also be backed up, restarted or stopped.
Properties for the current workspace can be changed, and new monitors created for
simulations.
The Tools menu contains:
Export command (p. 90 in "ANSYS CFX-Solver Manager, Release 10.0")
Export to ANSYS Multifield command (p. 91 in "ANSYS CFX-Solver Manager, Release 10.0")
Interpolate command (p. 91 in "ANSYS CFX-Solver Manager, Release 10.0")
Post-Process Results command (p. 94 in "ANSYS CFX-Solver Manager, Release 10.0")
View Environment command (p. 94 in "ANSYS CFX-Solver Manager, Release 10.0")

Tools Menu: Edit Definition File command
Edit Definition File command

The command file section of a definition file can be modified. This allows modifications to a
definition file without the need to use ANSYS CFX-Pre. The most useful application of this is
in the modification of a simulation when re-running the simulation may be too time
consuming.
When a definition file is selected for modification, the Command File Editor is launched. For
details, see Editing Definition Files (p. 63 in "ANSYS CFX-Solver Manager, Release 10.0").
1. Select Tools > Edit Definition File.
2. Browse to the directory containing the definition file to edit.
3. Select the definition file.
4. Click Open.
The Command File Editor is launched.
Export command
If using tools other than ANSYS CFX-Post for post-processing, data needs to be exported to
a Results File in a supported format. The ANSYS CFX Export utility can also be run from the
command line.
File Export Utility (p. 117 in "ANSYS CFX-Solver Manager, Release 10.0")
Running ANSYS CFX Export from the Command Line (p. 129 in "ANSYS CFX-Solver
There must be a results file to reference before exporting.
1. Select Tools > Export.
The Export dialog box is displayed.
2. Under Results File, click Browse and select a results file for export.
3. If required, under Export File, click Browse and modify the default output path and
name.
4. Under Domain Name, select the domain to export.
Where multiple domains exist, select the domain(s) to export.
5. Under Export Type select CGNS, MSC.Patran, FIELDVIEW, EnSight or Custom User
Export.
CGNS (p. 121 in "ANSYS CFX-Solver Manager, Release 10.0")
MSC.Patran (p. 123 in "ANSYS CFX-Solver Manager, Release 10.0")
FIELDVIEW (p. 126 in "ANSYS CFX-Solver Manager, Release 10.0")
EnSight (p. 127 in "ANSYS CFX-Solver Manager, Release 10.0")
Custom User Export (p. 128 in "ANSYS CFX-Solver Manager, Release 10.0")
6. Under Export Options, configure options as required.
The options are dependent on the Export Type. For details, see File Export Utility (p. 117
in "ANSYS CFX-Solver Manager, Release 10.0").

Tools Menu: Export to ANSYS Multifield command
7. Click Export.
Once completed, a message is displayed. Click OK to close it.
Export to ANSYS Multifield command

This option is used to produce files for use in Fluid Structure Interaction cases. For details,
see ANSYS Multifield Export Options (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0").
1. Select Tools > Export to ANSYS Multifield.
The Export to Multifield Solver dialog box is displayed.
3. If required, under Export File, click Browse and modify the default output path and
name.
4. Under Domain Name, select the domain to export.
Where multiple domains exist, select the domain(s) to export.
5. If required, under Boundary, select the boundaries to export.
6. Under Export Options, configure options as required.
The options are dependent on the Export Type. For details, see ANSYS Multifield Export
Options (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0").
7. Click Export.
Once completed a message is displayed. Click OK to close it.
Interpolate command
Interpolation allows imposition of a solution from a results file produced using one mesh,
into a Definition File containing another mesh.
The major benefit of interpolation is the ability to use the solution from a simple model as a
good initial guess for a more complex model. Therefore, the likelihood of converging a
complex model increases.
Interpolate can be used to slightly modified geometry or boundary conditions and so on to
facilitate rapid parametric design studies.
ANSYS CFX-Solver uses an automatic interpolation feature that automatically calls the
interpolator when meshes are not identical. This can be enabled by selecting Interpolate
Initial Values onto Def File Mesh when defining a run. For details, see Define Run command
Interpolating from one results file into another overwrites the results stored in the
destination file. If these results are important, make a copy of the file and interpolate into
that.
The cfx5interp script uses conservative values when interpolating results.

Tools Menu: Interpolate command
There may be situations where the shape of the model has changed and the solution set no
longer maps exactly onto the model grid. If the solution grid does not provide values for all
of the nodes in the new grid, then the cfx5interp script extrapolates values for the
extraneous points, based on the given solution set.
1. Select Tools > Interpolate.
The Interpolation dialog box is displayed.
ANSYS CFX Results file can be interpolated onto either an existing ANSYS CFX Definition
file, or onto another ANSYS CFX results (*.res) file.
3. Under Mesh File, click Browse and select a mesh file for interpolation.
4. Select or clear Calculate differences.
If selected, interpolator generates a comparison of the two files. The comparison is
stored as additional variables with the prefix Difference. These variables can be used in
ANSYS CFX-Post to determine regions where the solution has changed significantly.
5. Click Interpolate.
The output window displays details of the interpolation process.
Once completed, a message is displayed. Click OK to close it.
Note: To save the results to a text file, right click in the results and select Save As.
Using the Command Line to Interpolate Results

In some instances, the cfx5interp script can be used from the command line to initiate an
interpolation.
To use the cfx5interp script, enter the following in the command line:
cfx5interp -def <interpolate to file> -res <interpolate from file>
This command produces the same results as running the interpolate function within ANSYS
CFX-Solver Manager.
A -difference argument can be passed which forces the interpolator to produce difference
datasets when both files contain results. It calculates the differences between an original set
of fields, specified with the -from switch, and a new set specified with -destination.
The cfx5interp script is also capable of producing a text file of results for specific locations
within the fluid domain. This is particularly useful if there is experimental data to validate.
To produce a results text file, first create a text file containing the particular coordinates of
interest. The vertex text file should be of the following format:
x(1) y(1) z(1)
x(2) y(2) z(2)
. . . .
x(n) y(n) z(n)
Once the vertex file is created, run the following cfx5interp script:
cfx5interp -vtx <vertex file> -res <results file>
The script creates a third file entitled <vertex file>.new. This new text file contains the
coordinates specified in the vertex file, as well as the results at these locations.

Tools Menu: Edit Run In Progress command
If there exists a set of coordinates that lie outside of the solution grid, values of 0.0E0 will be
interpolated for all variables at this location. The cfx5interp script will not extrapolate
results to a vertex file.
A sample file, with variable descriptions, is shown below:
1 : Coordinates + variables for vertex
0.000000E+00 0.000000E+00 -2.000000E+00 Vertex coordinates
3 : G/PRESGRD 1.552757E+02 -1.102330E+02 -1.906295E+03 Pressure (x, y, z)
1 : G/DENSITY 1.000000E+03 Density
1 : G/CONDUCT 6.200000E-01 Conductivity
1 : G/VISCDYN 1.140000E-03 Dynamic Viscosity
3 : G/VEL -9.742797E-03 3.445983E-03 -3.966365E+00 Velocity
1 : G/SPHEATP 4.190000E+03 Specific Heat
1 : G/ENTH 1.256984E+06 Enthalpy
1: G/TEMP 2.999962E+02 Temperature
1 : G/PRES 4.147881E+01 Pressure
1 : G/TEMPTOT 2.999981E+02 Total Temperature
1 : G/PRESTOT 7.966394E+03 Total Pressure
0 : END OF VARIABLES
Note: Some of the values obtained using the cfx5interp script may differ slightly from the
values obtained using Data Export in ANSYS CFX-Post. These minor discrepancies result
from different methods of calculation. Discrepancies are more likely to occur at points which
lie very close to the edge of the mesh elements or in regions of prism and hexahedral
elements. Inconsistencies are likely to be more significant where gradients are large,
particularly in the boundary layer.
Edit Run In Progress command

You can edit the CCL definition of a Definition File while the solver is running. The changes
you make take effect when saved and the modifed CCL is preprocessed for the flow solver.
The modifed CCL may take several iterations to be updated depending on system load,
hardware and problem size.
Theses changes apply only to the run in progress, and do not affect the Definition File that
was used to begin the run (if one was used). Before the next outer loop iteration begins, a
backup file named <iteration number>.bak is written to the working directory. The
backup file can be used to restart the run from the point at which the CCL definition was
changed, if needed.
Only selected CCL parameters can be dynamically changed. A list of these parameters is in
the RULES file. For details, see RULES File (p. 72 in "ANSYS CFX-Solver Manager, Release
10.0").
The Command File Editor can also be used to make changes to the CCL contained in a
Definition File. Changes, when saved, affect the edited Definition File only, not any run in
progress. For details, see Editing Definition Files (p. 63 in "ANSYS CFX-Solver Manager,
Release 10.0").
1. Select Tools > Edit Run In Progress or click .

The Command File Editor is launched.

Tools Menu: Edit Current Results File command
Edit Current Results File command

Edit the results file in the current workspace (if available). This feature is available when a
results file in the current workspace that has finished. For details, see Editing Definition Files
1. Select Tools > Edit Current Results File or click .

The Command File Editor is launched and the current results opened.
Post-Process Results command

Loads the ANSYS CFX-Post post-processor. For details, see Overview of ANSYS CFX-Post (p. 7 in
"ANSYS CFX-Post, Release 10.0").
1. Select Tools > Post-Process Results.
The Start CFX-Post dialog box is displayed.
3. Select or clear Shut down Solver Manager.
If selected Solver Manager is shut down before CFX-Post is launched.
4. Click OK.
View Environment command

Used to display a complete list of environment variables associated with the ANSYS
CFX-Solver Manager and their settings.
1. Select Tools > View Environment.
The Solver Manager Environment dialog box is displayed.
2. Click Save to export the content to a text file.

Monitors Menu
The topic(s) in this section include:
Introduction
The Monitors menu sets the display options for plots of your simulation.
Each menu option has a submenu. This is used to specify display options for a given
category. Selected options will display the related plot.
Residuals are combined by default in the ANSYS CFX-Solver Manager. Residuals for each
domain can be displayed as required by selecting the residuals by Domain in the submenu
for each residual type.

Monitors Menu: Introduction

Help Menu
Active Panel F1 command (p. 97 in "ANSYS CFX-Solver Manager, Release 10.0")
On Solver Manager command (p. 97 in "ANSYS CFX-Solver Manager, Release 10.0")
About Solver Manager command (p. 98 in "ANSYS CFX-Solver Manager, Release 10.0")
About Qt command (p. 98 in "ANSYS CFX-Solver Manager, Release 10.0")
Help on Help command (p. 98 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The Help menu contains options for navigation to sections of the online documentation.
The help menu contains:
Active Panel F1 command (p. 97 in "ANSYS CFX-Solver Manager, Release 10.0")
On Solver Manager command (p. 97 in "ANSYS CFX-Solver Manager, Release 10.0")
About Solver Manager command (p. 98 in "ANSYS CFX-Solver Manager, Release 10.0")
About Qt command (p. 98 in "ANSYS CFX-Solver Manager, Release 10.0")
Help on Help command (p. 98 in "ANSYS CFX-Solver Manager, Release 10.0")
Active Panel F1 command

The help associated with the active panel is launched. This is used to launch
context-sensitive help for the current aspect of the application.
For example, if the Viewer is selected as the active window, selecting Active Panel (or
pressing F1) opens a help window with information about the Viewer.
On Solver Manager command

The ANSYS CFX-Solver Manager help is launched.

Help Menu: About Solver Manager command
About Solver Manager command

Lists information about ANSYS CFX-Solver Manager including version number and
copyright information.
About Qt command
Lists information about Qt.
Help on Help command

Opens a document explaining how to navigate through online help in ANSYS CFX using
different methods.

Starting CFX-Solver from the
Command Line
Command line use (p. 99 in "ANSYS CFX-Solver Manager, Release 10.0")
Command line arguments (p. 101 in "ANSYS CFX-Solver Manager, Release 10.0")
Command line samples (p. 103 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The ANSYS CFX-Solver is a separate module of ANSYS CFX which has no graphical user
interface. It is launched from the command line. For details, see Using the Command Line
If using ANSYS CFX-Solver Manager to start ANSYS CFX-Solver, some details of a solution can
be seen as it emerges. The graphical user interface of the ANSYS CFX-Solver Manager allows
various options to be set and easier control over the process. However, to run ANSYS
CFX-Solver in batch mode, start it from the command line, as described in this section.
Command line use

ANSYS CFX-Solver Manager can be launched from the command line in a UNIX terminal or
a Windows command line.
1. Launch a UNIX shell or a DOS prompt.
2. Type cfx5solve.
3. Press <Return> or <Enter>.
For details, see Command Line (p. 99 in "ANSYS CFX, Release 10.0: Installation and
Overview").

Starting CFX-Solver from the Command Line: Command line use
ANSYS CFX-Solver can be launched from the command line in a UNIX terminal or a Windows
command line.
1. Launch a UNIX shell or a DOS prompt.
2. Type cfx5solve -def <file>
<file> should be replaced with the name of your Definition File.
3. Press Return or Enter.
For details, see Command Line (p. 99 in "ANSYS CFX, Release 10.0: Installation and
Overview").
There are various options that can be used with the cfx5solve command. There are two
alternative forms: one which starts ANSYS CFX-Solver and one which starts ANSYS
CFX-Solver Manager (check these for the latest changes by typing cfx5solve -help):
cfx5solve -def <file> [-help] [-initial <file>]

[-double] [-single]
[-nosave|-save] [-name <name>] [-size #]
[-solver <executable>] [-partition <#partitions>]
[-parallel] [-hstfile <file>] [-parfile <file>] [-serial]
[-verbose]
or
cfx5solve [-interactive [-definition <file>]]

[-display <display>] [-help] [-noautohelp]
[-solver <executable>] [-verbose]
where [] denotes an optional argument, | separates mutually exclusive arguments and <
> denotes that substitution of a suitable value is required. All other arguments are keywords,
some of which have a short form.

Starting CFX-Solver from the Command Line: Command line arguments
Command line arguments

Some of the various arguments are briefly described below; execute cfx5solve -help to
view a full list of available arguments.
Argument Alternative form Usage
-batch Run ANSYS CFX-Solver in batch mode (i.e. without
starting the ANSYS CFX-Solver Manager). This is the
default mode.
-ccl <file> Reads additional Command Language from the
named file. Overrides any ANSYS CFX Command
Language specified in the Definition File.
-definition <file> -def <file> Use <file> as the input file, which may be a ANSYS
CFX Definition File or a Results File for a restart. The
file specified is used in the same way as the Input File
on the Define Run dialog box. For details, see Define
Run command (p. 75 in "ANSYS CFX-Solver Manager,
Release 10.0").
-display <display> (UNIX only) Use the X11 server <display> instead
of the X11 server defined by the DISPLAY
environment variable.
-double Runs the double precision version of ANSYS
CFX-Solver. See -single.
-example <file> -eg <file> Runs the ANSYS CFX-Solver on one of the ANSYS CFX
Example Definition Files provided with the product.
The option StaticMixer is currently available.
-help -h Displays help information.
-initial <file> -ini <file> Use the initial values in the ANSYS CFX Results File
<file>. This option may only be used together with
a ANSYS CFX Definition File which was created with
the Automatic or Automatic with Value
initialisation settings. The file specified is used in the
same way as the Initial Values File in the Define Run
dialog box. For details, see Define Run command
-interactive -int Run the interactive ANSYS CFX-Solver Manager to
-manager start a new run and/or manage or monitor an existing
run.
-monitor <file> When starting Solver Manager, monitor the run
represented by <file>, which may be a ANSYS CFX
Results File or Output File.
-name <name> Choose names for the exported files and temporary
directory based on the problem name <name>
instead of the Definition File name unless other
names are explicitly defined.
This name cannot be set when using the ANSYS
CFX-Solver Manager to start the ANSYS CFX-Solver.
-parallel -par Runs the solver in parallel mode. This option can be
combined with -partition for a partitioning run.
-par-local Allows fast setup of a parallel run on the local host
only.
-par-dist Allows fast setup of a distributed parallel run. See the
examples below.

Starting CFX-Solver from the Command Line: Command line arguments

-par-host-list When running in parallel, do not use the list of hosts
<host1>,[<host2>,...] in the host file passed in through the -hstfile
argument. Instead, use the list from this argument. If
the -hstfile argument is also given, host details are
taken from that file if possible, if the -hstfile argument
is not given, or if any of the specified hosts are not
available in the file so named, details are read from
hosts.ccl file which is also used by Solver Manager.
-parfile-read <parfile> Specifies the name of an input partition file used to
set up a partitioning or parallel run.
-parfile-write Specifies the name of a partition file to write to,
<parfile> containing the information from a partitioning run.
-partition -part <#partitions> Runs the solver in partitioning mode. The specified
<#partitions> <#partitions> must also be specified as a dummy
value if a par-file is also specified and the required
number of partitions is taken from this file.
-partitioner Run <executable> instead of the standard
<executable> partitioner.
-part-only <# of Runs the solver in partitioning mode only. This is
partitions> normally equivalent to -part, but may be necessary if
partitioning a results file from a previous run.
-part-mode <mode> Sets the partitioning mode to use when running the
partitioner. Valid options are metis-kway, metis-rec,
rcb
Finer control over the partitioning method is
available through the Command Language.
-priority <number> -pri <number> Allows the specification of a job priority to a solver
run. Priority 2 is the default priority setting, with
priority 1 being lower than the default. High priorities
can be set with 3 and 4.
-save Do not delete any temporary files after the run.
Normally the standard temporary files created by
ANSYS CFX-Solver are deleted automatically after
each run.
-serial If restarting from a results file produced by a parallel
run, this forces the run to be done in serial.
-single Runs the single-precision version of the ANSYS
CFX-Solver. This is the default, but is provided for
overriding any information which might be stored in
the CFX Command Language dataset in a file from a
previous run. See -double.
-size <factor> -s <factor> Change memory estimates used by the ANSYS
CFX-Solver by a factor of <factor>. Memory estimates
are sometimes inaccurate and this option needs to be
used to increase the memory allocated. For example,
using -size 1.05 increases memory allocated by
5%. This option provides the same functionality as set
in Solver Memory. For details, see Solver tab (p. 17 in
Further options for controlling the ANSYS CFX-Solver
memory allocation are available. Execute
cfx5solve -help for full details.

Starting CFX-Solver from the Command Line: Command line samples

-size-part <factor> -sizepar <factor> Change the memory estimates used by the
partitioner by a factor of <factor>. See also -size.
Further options for controlling the partitioner
memory allocation are available. Execute
cfx5solve -help for full details.
-size-nr <size> -nr <size> These flags are for advanced users to change the
-size-ni <size> -ni <size> memory allocation parameters for the solver.
-size-nd <size> -nd <size> Usually, you should use the -size argument instead.
<size> is the desired memory allocation in words,
-size-nc <size> -nc <size>
and may have K or M appended for kilo- or mega-.
-size-nl <size> -nl <size>
-size-part-nr <size> -nrpar <size> This is the same as the -size-* arguments, but gives
-size-part-ni <size> -nipar <size> the sizes needed for partitioner rather than solver.
-size-part-nd <size> -ndpar <size>
-size-part-nc <size> -ncpar <size>
-size-part-nl <size> -nlpar <size>
-solver <executable> Run <executable> instead of the standard solver.
-solver-arch <arch> Specifies an architecture string, which is used to
locate the ANSYS CFX-Solver version to run the
optimised solver. The <arch> should be a valid
ANSYS CFX architecture string, and the software
expects to find a version of solver.exe in
<CFXROOT>/bin/<version>/<arch>/solver.exe
-start-method Use the named start method to start the solver. This
<name> option allows you to use different parallel methods,
as listed in the Solver Manager GUI, instead of the
defaults. For parallel runs, you also need to provide
the -part or -par-dist arguments.
-verbose -v Specifying this option may result in additional output
being sent to the standard Output File (normally the
screen).
Command line samples

To help clarify the use of the command line several examples are provided:
Start ANSYS CFX-Solver (p. 104 in "ANSYS CFX-Solver Manager, Release 10.0")
Start ANSYS CFX-Solver Manager (p. 104 in "ANSYS CFX-Solver Manager, Release 10.0")
Produce a partition file (p. 104 in "ANSYS CFX-Solver Manager, Release 10.0")
Start ANSYS CFX-Solver in distributed parallel (p. 104 in "ANSYS CFX-Solver Manager,
Release 10.0")
Start ANSYS CFX-Solver from a definition file (p. 104 in "ANSYS CFX-Solver Manager,
Release 10.0")
Start ANSYS CFX-Solver in parallel (p. 105 in "ANSYS CFX-Solver Manager, Release 10.0")
Start ANSYS CFX-Solver in parallel using MPICH (p. 105 in "ANSYS CFX-Solver Manager,
Release 10.0")
cfx5stop (p. 105 in "ANSYS CFX-Solver Manager, Release 10.0")

Start ANSYS CFX-Solver

To start the ANSYS CFX-Solver running from the Definition File model.def, type:
cfx5solve -def model.def
Start ANSYS CFX-Solver Manager

To start the ANSYS CFX-Solver Manager, passing it the name of the Definition File, type:
cfx5solve -interactive -def model.def
Produce a partition file

To produce a partition file model.par with the MeTiS partitioning method and 7 partitions,
but NOT run ANSYS CFX-Solver to solve for the solution, make sure that no file model.par
exists in the working directory and type:
cfx5solve -def model.def -partition 7
Note: If the file model.par exists in the working directory, then the Partition Type (MeTiS,
RecCoordBis or SpecDir) is read from this file, even if you havent specified the file
model.par. Because this could potentially be confusing, you are advised to use the ANSYS
CFX-Solver Manager to set up a partitioning run, unless you are certain that either there is
no file model.par, or that the partitioning method specified in the model.par file is what
you require.
Start ANSYS CFX-Solver in distributed parallel

For this example to work, the hosts Sys01, Sys02 and Sys03 must be defined in the central
hosts.ccl file.
To run the CFX-5 Solver in distributed parallel, starting from the Definition File model.def,
and using 1 processor on Sys01, 1 processor on Sys02 and 2 processors on Sys03, type:
cfx5solve -def model.def -par-dist Sys01,Sys02,Sys03*2
Start ANSYS CFX-Solver from a definition file

To run the CFX-5 Solver in parallel, starting from the Definition File model.def and running
only on the local machine with 2 partitions, type:
cfx5solve -def model.def -par-local -partition 2
Note: This method does not require you to create a hst file.

If you have already created a file model.par (for instance, by using the command
cfx5solve -def model.def -partition 7), then you can run the parallel ANSYS
CFX-Solver by typing:
cfx5solve -def model.def -parallel -parfile model.par
Start ANSYS CFX-Solver in parallel

To start the ANSYS CFX-Solver in parallel with four partitions on two hosts:
cfx5solve -def file.def -par-dist 'hosta*2,hostb*2'
Start ANSYS CFX-Solver in parallel using MPICH

To start the ANSYS CFX-Solver in parallel, with two partitions, using MPICH local parallel on
a Windows machine (this command should be given as a single line):
cfx5solve -def file.def -start-method "MPICH Local Parallel for Windows" -part 2
cfx5stop
After ANSYS CFX-Solver is running, stop it by typing cfx5stop at the command line.
Suppose a Run is called mixer_001 in the current directory. There will be a temporary
directory called mixer_001.dir in the current directory while that run is actually running. To
stop the Run, enter the following command line:
cfx5stop -directory mixer_001.dir


CFX-Solver Start Methods
Topics in this section include:
Direct start methods (p. 107 in "ANSYS CFX-Solver Manager, Release 10.0")
Indirect start methods (p. 108 in "ANSYS CFX-Solver Manager, Release 10.0")
Example (p. 108 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
ANSYS CFX-Solver Methods define allowable parameters and command-line arguments
used by ANSYS CFX-Solver Manager and CFX Solver Script to launch the CFX solver
executable and perform a CFD run. The definition of the Solver Start Methods is available to
expert users to customize solver start-up for specific parallel or batch queuing
environments.
The default Start Methods for a CFX installation are contained in the
<CFXROOT>/etc/start-methods.ccl file. The default start method can be over-ridden by
placing a custom version of this file in the same location as the site or user CFX configuration
files.
Direct start methods

Solver Start methods which directly run the CFX Solver executable are known as Direct start
methods, and are commonly used for defining solver execution in serial or parallel on local
networks. Definition of Solver Start Methods for specific parallel environments can be made
following the various available PVM and MPI methods in the file.

CFX-Solver Start Methods: Indirect start methods
Indirect start methods

Solver Start methods can also be used to launch a user-defined script or program, which can
perform system interaction before re-executing a cfx5solve command under a different
environment or system. These are known as Indirect start methods, and are commonly used
for executing ANSYS CFX-Solver run on remote or batch queuing systems. Use of Indirect
start methods requires knowledge of a system scripting language (e.g., bash or Perl) to
customize the solve start-up process for your specific environment.
Example
An example of the use of Indirect Solver Start methods to run a cfx5solve command within
a PBS-based batch queueing system is provided in the CFX distribution. For details, please
see the Submit to PBS Queue start method in start-methods.ccl, and the qcfx5solve.pl script
in the <CFXROOT>/extras/ directory.

CPU and Memory
Requirements
Tetrahedral Mesh (p. 109 in "ANSYS CFX-Solver Manager, Release 10.0")
Special Solver Executables (p. 110 in "ANSYS CFX-Solver Manager, Release 10.0")
Turbulence (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0")
Energy (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0")
CHT (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0")
Multicomponent Flows (p. 112 in "ANSYS CFX-Solver Manager, Release 10.0")
Multiphase Flows (p. 112 in "ANSYS CFX-Solver Manager, Release 10.0")
Additional Variables (p. 113 in "ANSYS CFX-Solver Manager, Release 10.0")
Combustion (p. 113 in "ANSYS CFX-Solver Manager, Release 10.0")
Radiation (p. 113 in "ANSYS CFX-Solver Manager, Release 10.0")
GGI Interfaces (p. 113 in "ANSYS CFX-Solver Manager, Release 10.0")
Transient (p. 113 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
This section provides information on typical increases in CPU (central processing unit) time
and memory requirements incurred by some simulations and physical models.
Tetrahedral Mesh
The ratio of elements to nodes is approximately 5:1 for a tetrahedral mesh. For example, if 5
million tetrahedral elements are in a mesh, then there are approximately 1 million nodes.
This is in contrast to a hexahedral mesh where the ratio of elements to nodes approaches
1:1 as the grid becomes large.

CPU and Memory Requirements: Special Solver Executables
Memory required for a tetrahedral mesh is about 0.4 times the memory required for a hex
mesh of the same number of elements. Alternatively a tetrahedral mesh has about 2 times
the required memory of a hexahedral mesh with the same number of nodes.
Special Solver Executables

On all systems there are default Solver executables. On some systems, there are additional
solver executables. There are three classes of special executables: 64-bit, double precision
and chip-specific. Not all of these special executables are offered on all systems. For details,
see Supported Platforms (p. 18 in "ANSYS CFX, Release 10.0: Installation and Overview").
64-bit (p. 110 in "ANSYS CFX-Solver Manager, Release 10.0")
Double Precision (p. 110 in "ANSYS CFX-Solver Manager, Release 10.0")
Chip-specific (p. 110 in "ANSYS CFX-Solver Manager, Release 10.0")
64-bit
Used on all 64-bit platforms, and permit individual solver processes in excess of 2 gigabytes
(although some platforms are still 32-bit platforms, which are limited to at most 2 gigabytes
of RAM, or slightly less depending on the computer vendor). There is generally no RAM
penalty or CPU time penalty with 64-bit executables (the basic floating point numbers are
still stored using 32 bit words, only the addressing of data involves 64 bit addresses).
Double Precision
Double Precision Solver executables store basic floating point numbers as 64 bit words.
These executables are available to permit more accurate numerical mathematical
operations. Double precision accuracy might be needed if the computational domain
involves a huge variation in grid dimension, aspect ratio, pressure range, etc.
When double precision is used, the computer memory used for a given problem and grid
size is double that of the default (single precision) solver executable. Stated another way:
the maximum problem size to run on a given computer for the double precision Solver
executable is half that of the default single precision solver executable.
Chip-specific
Chip-specific Solver executables have been compiled taking specific advantage of a
computer chip architecture (e.g. a Pentium III chip set only). In contrast, the default solver
executables are compiled in such a way as to run on a family of chip sets (e.g. all Pentium
class chips). There is no penalty in terms of memory with the chip-specific Solver
executables, and generally they provide a performance improvement of at least 25%
compared to the default solver executables. No user choice is required. If a chip-specific
solver is available for the hardware being used it automatically is detected and used.

CPU and Memory Requirements: Turbulence
Turbulence
The following topics will be discussed:
Zero Equation Model (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0")
Two Equation Models (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0")
Reynolds Stress Model (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0")
Zero Equation Model

The use of this model incurs a small increase in CPU time and memory requirements
compared to laminar flow.
Two Equation Models

Two additional scalar equations are solved when using two equation turbulence models.
The SST model has a slight additional cost over other two equation models since a wall scale
equation is also solved.
Consider the case of single phase, single component laminar flow in which the U-Mom,
V-Mom, W-Mom and P-Mass equations are solved. Expect a CPU cost increase on the order
of 50% by the addition of a two-equation turbulence model. Memory requirement increases
are small.
Reynolds Stress Model

This model adds six scalar equations for each of the Reynolds Stresses as well as the Eddy
Dissipation equation. It is approximately 2.5 times more expensive than the two equation
turbulence models.
Consider the case of single phase, single component laminar flow in which the U-Mom,
V-Mom, W-Mom and P-Mass equations are solved. Expect a CPU cost increase on the order
of 120% by the addition of a Reynolds Stress turbulence model. Memory requirement
increases are small.
Energy
Both the Thermal and Total Energy models require the solution of an additional scalar
equation. The solution of the energy equation typically requires 1/3 of the CPU required for
the U-Mom, V-Mom, W-Mom and P-Mass equations. Memory requirement increases are
small.
CHT
Only the energy equation is solved in CHT regions, so compared to the same number of
nodes in a fluid region CPU costs much less (U-Mom, V-Mom, W-Mom and P-Mass are not
solved).

CPU and Memory Requirements: Multicomponent Flows
Multicomponent Flows
Each additional component adds an extra scalar equation. Therefore, as the number of
components increase, CPU time required to solve the Mass Fraction equation increases
linearly. Expect each component to add approximately 25% to the CPU required for the
U-Mom, V-Mom, W-Mom and P-Mass equations.
Multiphase Flows
The following topics will be discussed:
Homogeneous (p. 112 in "ANSYS CFX-Solver Manager, Release 10.0")
Inhomogeneous (p. 112 in "ANSYS CFX-Solver Manager, Release 10.0")
N-Phase Flow (p. 112 in "ANSYS CFX-Solver Manager, Release 10.0")
Homogeneous
For two-phase flow using the Homogeneous model expect memory requirements to
increase by a factor of 1.5 and CPU time to increase by a factor of 1.7 over the same
single-phase simulation. Enabling free surface does not significantly alter CPU or memory
requirements.
Inhomogeneous
For two-phase flow using the Particle or Mixture models expect memory requirements to
increase by a factor of 2.15 and CPU time to increase by a factor of 2.25. Enabling free surface
does not significantly alter CPU or memory requirements.
N-Phase Flow
As the number of fluids increase, expect memory and CPU requirements to increase
approximately linearly for small N. Tetrahedral meshes have more of a linear increase than
hexahedral meshes. The table below gives approximate memory increase factors for up to
5 phases when compared to the same single-phase simulation on a hexahedral mesh.
# of Phases Memory Increases
(Hex Mesh) (Tet Mesh)
1 1 1.80
2 2.15 3.40
3 3.50 5.70
4 5.15 8.05
5 7.00 10.60
Expect the CPU factor to be slightly less than the corresponding memory factors, but the
trend is the same.

CPU and Memory Requirements: Additional Variables
Additional Variables
This adds a single scalar equation for each additional variable. Expect a CPU cost increase of
approximately 20% for each additional variable over the solution of the U-Mom, V-Mom,
W-Mom and P-Mass equations for a single-phase single-component case. Increases in
memory requirements are small.
Combustion
Modelling combustion incurs a slight cost compared to multicomponent flow with the
same number of components. For multi-step reactions each component is solved using the
coupled solve. This incurs additional CPU time which does not increase linearly with the
number of components.
Radiation
This adds a single scalar equation. Cost increases are similar to those of the Energy equation.
For details, see Energy (p. 111 in "ANSYS CFX-Solver Manager, Release 10.0").
GGI Interfaces
An intersection algorithm which is performed at the start of a simulation to connect each
side of a GGI connection incurs a one-time cost.
Each GGI connection means approximately 5% more CPU time and memory is required. This
number can vary greatly, as it is a function of the number of nodes involved in a GGI
connection, compared to the number of nodes that are not involved in the GGI connection.
There is also a dependence on the geometric complexity of the GGI connection.
Transient
Each coefficient loop requires approximately the same CPU time as the equivalent steady
state iteration.

CPU and Memory Requirements: Transient

cfx5control Application
The topic(s) in this section include:
Introduction
The cfx5control application can be used to dynamically control the ANSYS CFX-Solver. The
features available include:
Stopping the solver.
Instructing the solver to write a backup results file.
Editing the Command Language during a run.
Reading Command Language from a file and implementing it on the fly.
Full details can be found by running the executable with the option -help at the command
line.
For example:
<CFXROOT>/bin/cfx5control -help
where <CFXROOT> is the path to your installation of ANSYS CFX.

cfx5control Application: Introduction

File Export Utility
ANSYS Multifield Export Options (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0")
CGNS (p. 121 in "ANSYS CFX-Solver Manager, Release 10.0")
MSC.Patran (p. 123 in "ANSYS CFX-Solver Manager, Release 10.0")
FIELDVIEW (p. 126 in "ANSYS CFX-Solver Manager, Release 10.0")
EnSight (p. 127 in "ANSYS CFX-Solver Manager, Release 10.0")
Custom User Export (p. 128 in "ANSYS CFX-Solver Manager, Release 10.0")
Creating an Export Program (p. 133 in "ANSYS CFX-Solver Manager, Release 10.0")
Introduction
The ANSYS CFX Results File contains the details of the mesh used and details of the variables
which have been calculated. For details, see List of Variables (p. 52 in "ANSYS CFX-Solver
To post-process using software other than ANSYS CFX-Post, the mesh and variables can be
extracted from the ANSYS CFX Results File. This can be written out in a number of alternative
formats by using a utility called ANSYS CFX Export.
The export file formats available in ANSYS CFX Export are suitable for direct input into the
following software systems:
ANSYS Multifield
All systems that support CGNS file import.
MSC.Patran, from the MacNeal-Schwendler Corporation.
FIELDVIEW, from Intelligent Light.
EnSight, from Computational Engineering International, Inc.
Custom User Export. Write custom export programs to view results in other
post-processors.

File Export Utility: ANSYS Multifield Export Options
To export use the Tools menu. For details, see Export command (p. 90 in "ANSYS CFX-Solver
Manager, Release 10.0"). Alternatively, exports may be run directly from the command line.
For details, see Running ANSYS CFX Export from the Command Line (p. 129 in "ANSYS
ANSYS Multifield Export Options

The CFX to ANSYS Data Transfer Tool is an application that exports results from ANSYS CFX
simulations into ANSYS .cdb files. These can then be opened in ANSYS for further analysis. A
related tutorial is available. For details, see Conjugate Heat Transfer in a Heating Coil (p. 253
in "ANSYS CFX, Release 10.0: Tutorials").
Note: Prior to configuring this option, the Export to ANSYS Multi-field dialog box must be
displayed. For details, see Export to ANSYS Multifield command (p. 91 in "ANSYS CFX-Solver
ANSYS Element Type

Selections correspond to the type of ANSYS element to export. The choices are 3D Thermal
(element type 70), 2D Thermal (element type 152), and 2D Stress (element type 152). Please
refer to the ANSYS documentation for a description of these element types.
Output Modifiers
The following scaling and offset factors can be used to change the units of the solution. The
factors can be applied when you need to convert the units that are written to the ANSYS CFX
into those that you wish to use in ANSYS.
Modifiers include:
Offset Flow (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0")
Offset Values (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0")
Scale Flow (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0")
Scale Values (p. 118 in "ANSYS CFX-Solver Manager, Release 10.0")
Offset Flow Requires a real number corresponding to the offset value applied to solution flows. The
default value is 0.
Offset Values Requires a real number corresponding to the offset value applied to solution values. The
default value is 0.
Scale Flow Requires a real number corresponding to the scaling factor applied to solution flows. The
default value is 1.
Scale Values Requires a real number corresponding to the scaling factor applied to solution values. The
default value is 1.

File Export Utility: Export Options
Export Options
Prior to configuring for export, the Export dialog box must be displayed. For details, see
Export command (p. 90 in "ANSYS CFX-Solver Manager, Release 10.0").
Note: If exporting for use with ANSYS Multi-field, use the Export to ANSYS Multi-field menu.
For details, see Export to ANSYS Multifield command (p. 91 in "ANSYS CFX-Solver Manager,
Release 10.0").
There are numerous export options used. These include:

Output Level (p. 119 in "ANSYS CFX-Solver Manager, Release 10.0")
Use Corrected Boundary Node Data (p. 119 in "ANSYS CFX-Solver Manager, Release 10.0")
Include Variables Only Found on Boundaries (p. 120 in "ANSYS CFX-Solver Manager,
Release 10.0")
Output Only Boundary Geometry and Results (p. 120 in "ANSYS CFX-Solver Manager,
Release 10.0")
Format (p. 120 in "ANSYS CFX-Solver Manager, Release 10.0")
Geometry Output Only (p. 120 in "ANSYS CFX-Solver Manager, Release 10.0")
Geometry Output Only (Neutral file) (p. 120 in "ANSYS CFX-Solver Manager, Release 10.0")
FIELDVIEW Version (p. 120 in "ANSYS CFX-Solver Manager, Release 10.0")
Ensight Version (p. 121 in "ANSYS CFX-Solver Manager, Release 10.0")
Output Level
This options defaults to 1 and is available to CGNS, MSC.Patran, FIELDVIEW and EnSight
export types.
Ouput level selects which subset of variables to export. Each variable is given a user level.
For details, see List of Variables (p. 52 in "ANSYS CFX-Solver Manager, Release 10.0").
1 outputs a small subset of basic variables such as velocity and pressure, which have user
level 1.
2 outputs all variables which are of user levels 1 and 2.
3 outputs all variables stored in the ANSYS CFX Results File.
Use Corrected Boundary Node Data

This option defaults to selected and is available to CGNS, MSC.Patran, FIELDVIEW and
EnSight export types.
The values of some variables on the boundary nodes (i.e. on the edges of the geometry) are
not precisely equal to the specified boundary conditions when ANSYS CFX-Solver finishes
calculations.
For instance, the value of velocity on a node on the wall will not be precisely zero, and the
value of temperature on an inlet may not be precisely the specified inlet temperature. For
visualisation purposes, it can be more helpful if the nodes at the boundary contain the
specified boundary conditions and so Use Corrected Data on Boundary Nodes should be
turned on for these cases.

File Export Utility: Export Options
Corrected boundary node values are obtained by taking the results produced by the ANSYS
CFX-Solver (called conservative values) and overwriting the results on the boundary nodes
with the specified boundary conditions. This ensures velocity is displayed as zero on no-slip
walls and equal to the specified inlet velocity on the inlet, for example. Using corrected
boundary node values is identical to selecting Use Surface Data on Boundary Nodes as
described in more detail.
For details, see MSC.Patran (p. 123 in "ANSYS CFX-Solver Manager, Release 10.0").
For details, see Hybrid and Conservative Variable Values (p. 29 in "ANSYS CFX-Post,
Release 10.0").
Include Variables Only Found on Boundaries

This option defaults to cleared and is available to CGNS, MSC.Patran, FIELDVIEW and EnSight
export types.
If selected, the export of variables that exist on boundaries only (such as y+ values) is
allowed.
Output Only Boundary Geometry and Results

This option defaults to cleared and is available to CGNS and MSC.Patran export types.
If selected, only the data for nodes on the boundaries is output. This can be used to allow
results from CFD calculations to provide boundary conditions for other analysis.
Format
This option defaults to Unstructured Binary and is available to FIELDVIEW and EnSight
export types.
Choose whether to export in binary or ASCII (text) format. The ASCII format is
human-readable but larger than the binary format.
Geometry Output Only

This option defaults to cleared and is available to CGNS export types.
If selected, details of the geometry and mesh, but not of variables, is exported.
Geometry Output Only (Neutral file)

This option defaults to cleared and is available to MSC.Patran export types.
If selected, details of the geometry and mesh, but not of variables, is exported to a Neutral
file. For more details about MSC.Patran Neutral files, refer to your documentation from
MSC.Patran.
FIELDVIEW Version
This option defaults to 8 and is available to FIELDVIEW export types.
The selection specifies the FIELDVIEW release number to conform to on export. Supported
versions for export include 6, 7 and 8.

File Export Utility: CGNS
Ensight Version
This option defaults to 7 and is available to EnSight export types.
The selection specifies the EnSight release number to conform to on export. Supported
versions for export include 5, 6 and 7.
CGNS
The CFD General Notation System (CGNS) system is designed to facilitate the exchange of
data between sites and applications, and to help stabilise the archiving of data. The data is
stored in a compact, binary format.
Note: Prior to configuring this option the Export dialog box must be displayed. For details,
see Export command (p. 90 in "ANSYS CFX-Solver Manager, Release 10.0"). Configuration of
the dialog box uses numerous common export options. For details, see Export Options
This section contains:

Overview (p. 121 in "ANSYS CFX-Solver Manager, Release 10.0")
Export Files (p. 121 in "ANSYS CFX-Solver Manager, Release 10.0")
Import Files (p. 122 in "ANSYS CFX-Solver Manager, Release 10.0")
Overview
CGNS consists of a collection of conventions for the storage and retrieval of CFD data. The
system consists of two parts:
A standard format for recording the data.
Software that reads, writes and modifies data in that format.
Export Files
The exported file set consists of either a single file for non-transient results, or multiple files
for transient results. Each contains a complete mesh and flow solution. By default all files are
generated with a .cgns extension. Import into a program that reads CGNS files should be
done according to the importing programs instructions.
ANSYS CFX-Export is capable of writing CGNS Version 2.3 files. These CGNS files can be read
by third parties if they support the features we write and are using CGNS Version 2.0 and
above.
Note: A CGNS valid file can be written in ADF or HDF5 format. ANSYS CFX currently only
supports ADF base files. When HDF5 becomes standard practise, it is hoped both versions
will be supported and identified seamlessly.

File Export Utility: CGNS
Import Files
There is a wide range of products that can import CGNS files. Consult user documentation
for the product being used for further information.
Note: An issue was detected while reading a CGNS file in TecPlot. If a similar problem is
encountered, set the environment variable CFX5_EXPORT_CGNS_TECPLOT to a value of 1,
restart ANSYS CFX and export the CGNS file again.
Reading Files Method

written by Mesh and solution data contained within ANSYS CFX results files can be wirtten as CGNS files
ANSYS from the ANSYS CFX-Solver Manager.
CFX-Export
To create a CGNS file, open the Solver Manager and select Export... from the Tools menu.
The default format to export data to should be CGNS. If it is not, change the Export Type to
CGNS. Select the Results File to create the CGNS file from and the options to use and click on
the Export button to perform the operation.
Further information on exporting files is contained within the standard documentation.
Preliminary notes
The file produced contains Grid and Solution data. It does not contain problem setup
(Physics) information.
The amount of solution data and the type of grid written to the CGNS file is user controllable
either on the command line or via the GUI. What is seen in the CGNS file reflects what the
user requests. There are files that when written using some options may not be able to be
reread into CFX-Pre. Caution must therefore be used if the original ANSYS CFX 10.0 solution
files are deleted, as it may not be possible to recover all information.
Names of variables, zones and boundary conditions are always CGNS compliant. The name
seen within the ANSYS CFX 10.0 application may have to be changed to achieve this.
When creating a CGNS file using CFX-Export, the following structure is written.
Base (Base_t)
A single base is written to each CGNS file.
Its name is not significant.
It is always written with a cell_dimension of 3 (i.e. 3D)
If a transient file is being written a simulation type (SimulationType_t) of TimeAccurate
is specified below the base node.
A state (ReferenceState_t) is also written below the base node with a description of
where the file was generated from and what it represents.
Zones (Zone_t)
A single zone is written under each Base_t node for each zone requested by the user and is
always unstructured in nature.
Coordinates of node data are always written in double precision. Due to the nature of the
grid being unstructured, there is no implicit ordering in how the grid is written.

File Export Utility: MSC.Patran
Elements (Elements_t)
Element Sections are written on a one per domain/subdomain basis as well as a one per
boundary condition basis. Due to the nature of CFX data a single element cannot appear in
more than one Element Section. Element numbering is unique and consecutive.
The user can control whether volume mesh (with surface mesh) or a surface mesh is written
to the file.
Boundary Conditions (BC_t)

Boundary Conditions are written. The location of each boundary condition is specified as set
of 2D elements (faces) or a set of nodes. The former is generally preferred as the later can
have some restrictions for the program that reads the file.
No properties of the boundary condition are written other than its type.
Solution Data (FlowSolution_t)

Solution data is written where requested. Names are mapped to be CGNS compliant. No
discrete data is currently written. Where Wall Only data is present missing solution data
is written as 0.0.
Transient Data
Transient data is written by writing the Grid and Solution data for each ANSYS CFX 10.0
transient file available to the CFX-Export process, to a separate CGNS file.
MSC.Patran
MSC.Patran is a general purpose CAE simulation tool.
Note: Prior to configuring this option the Export dialog box must be displayed. For details,

Import Files (p. 124 in "ANSYS CFX-Solver Manager, Release 10.0")
Exporting boundary conditions to MSC.Patran (p. 124 in "ANSYS CFX-Solver Manager,
Release 10.0")
Example procedure (p. 125 in "ANSYS CFX-Solver Manager, Release 10.0")
Export Files
The file set for this export option consists of three files:
File Name File Type
<basename>.out PATRAN Neutral File
<basename>.nod PATRAN 2.5 Nodal Results File
<basename>.results_tmpl PATRAN Results Template File

ANSYS CFX Export uses ASCII files and a subset of record types to be found in the full
definition of the PATRAN file formats. The full definition of the PATRAN file formats can be
found in the MSC.Patran documentation.
Faces associated with the ANSYS CFX boundaries and elements associated with subdomains
are transferred into PATRAN named components. The boundary/subdomain components
are named using their ANSYS CFX name.
Exported nodes are only associated with the PATRAN default_group, unless -nodes is used
when CFX-5 Export is used from the command line.
Import Files
The following procedure should be followed for successfully import of results into
MSC.Patran Version 2001r2. However, this may need to be adapted depending on what
MSC.Patran is used for. For more details about importing, please see the MSC.Patran
documentation.
Note: An MSC.Patran warning may appear when importing the Neutral file that reads No
element type could be found for element property set <P_SET.1>. No action needs to be taken.
1. Prepare the required PATRAN files.

Run ANSYS CFX Export on the ANSYS CFX Results File, either using the ANSYS CFX-Solver
Manager or directly from the command line.
2. Start PATRAN and create a new database.
Use File > New to create a new database. Click on Enable NFS access (on UNIX systems
only). Enter a new database name and press OK.
In New Model Preferences, choose the appropriate Analysis Code option for the
analysis.
3. Import ANSYS CFX mesh and results.
Use File > Import to access Import. Set Object/Source to Model/Neutral. Enter the
name of the Neutral file produced by ANSYS CFX Export and click Apply. Acknowledge
the first pop-up and answer Yes to the second to continue.
Use Import again with Object/Source set to Results/PATRAN2.nod, to read the nodal
results file produced by ANSYS CFX Export. Template for PATRAN 2.5 Import Results
displays. Enter the name of the template file produced by ANSYS CFX Export, and click
OK. Enter the nodal results file name in Import and click Apply.
4. Continue to use MSC.Patran as required.
Exporting boundary conditions to MSC.Patran

ANSYS CFX can be utilized to provide data to be used as boundary conditions for other types
of analysis in MSC.Patran.
MSC.Patran allows models to be prepared for several different kinds of analysis. It also has
facilities for using imported data to define data fields suitable for interpolating loads and
boundary conditions onto the geometry or the mesh of a new model.
A description of the relevant PATRAN facilities, in particular the Fields function and its
applications, can be found in the MSC.Patran documentation.

Example procedure
Here we outline some guidelines for one possible procedure for incorporating ANSYS CFX
results into a PATRAN model. ANSYS CFX temperature predictions will be used to define a
temperature distribution on a geometry surface of a new model. Details about any of the
options can be found in the MSC.Patran documentation.
Points to note in this example are:
ANSYS CFX Export files should be read into a new database first before any PATRAN
model grid. This ensures that the node numbers of the Neutral file, as well as the nodal
result file remain in correspondence. The nodes and elements in the new model mesh
will be numbered or renumbered to follow on from those in the ANSYS CFX data.
The ANSYS CFX model should, of course, not be included in the new model analysis, but
the ANSYS CFX data must not be deleted until the boundary values have been
interpolated onto the new grid.
The new model mesh can either be created or imported as part of step 6. or in a later
step, without affecting the procedure, since in this example the boundary condition is
defined on geometry surfaces.
The example assumes exported results include the Temperature variable.
1. Prepare PATRAN Neutral and Nodal Results files containing boundary data only.
Run ANSYS CFX Export on the ANSYS CFX Results File, either using the ANSYS CFX-Solver
Manager or directly from the command line. Toggle Boundary Data Output Only on if
using the ANSYS CFX-Solver Manager, or use the -boundary option if using ANSYS CFX
Export from the command line.
2. Start PATRAN and create a new database.
Use File > New to create a new database. Click on Enable NFS access (on UNIX systems
only). Enter a new database name and click OK.
On New Model Preferences, choose the appropriate Analysis Code option, for
example, PATRAN 2 NF.
3. Import ANSYS CFX mesh and results.
Use File > Import. Set Object/Source to Model/Neutral. Enter the name of the Neutral
file produced by ANSYS CFX Export and click Apply. Acknowledge the pop-up to
continue.
Use Import again with Object/Format set to Results/PATRAN2.nod, to read the nodal
results file produced by ANSYS CFX Export. Template for PATRAN 2.5 Import Results
appears. Enter the name of the template file produced by ANSYS CFX Export, and click
OK. Enter the nodal results file name and click Apply.
4. Display temperature results as a fringe plot.
Select Group/Post to post just the group containing the boundary condition nodes to
use. Select Results. On Results, select the temperature results, and click Apply.
5. Create a continuous FEM field from the displayed variable.
Select the Fields radio button. Set Action/Object/Method to Create/Spatial/FEM. Enter
a new name under Field Name. Click the Continuous radio button. Select the relevant
group under Mesh/Results Group Filter. Click Apply.

File Export Utility: FIELDVIEW
6. Add the geometry for the new model.
Post the default_group and make it current using Group/Post. Use the toolbar icons to
ensure the display will be in wireframe mode rather than in hidden line mode. Then
either create a geometry for the new PATRAN model using the Geometry radio button
to open the Geometry form or import the geometry from a previously prepared
database using File > Import with Object/Source set to Model/ MSC/PATRAN DB.
7. Define a temperature boundary condition on new geometry surfaces.
Select the Load/BCs radio button. Set Action/Object/Type to
Create/Temperature/Nodal. Enter a name under New Set Name. Click Input Data.
Select the field in the Spatial Fields box and click OK. Under Load/Boundary
Conditions, click Select Application Region to display Select Application Region.
Click the Geometry radio button under Geometry Filter. In Select Geometric Entities,
pick the surfaces to apply the boundary condition to. Click Add and then OK. In
Load/Boundary Conditions, click Apply. A temperature distribution should now be
visible on the relevant geometry surfaces, in the form of values shown at the
intersections of the surface display lines.
8. Complete the PATRAN model.
FIELDVIEW
FIELDVIEW is a standalone CFD post processor.
Note: Prior to configuring this option, the Export dialog box must be displayed. For details,

Importing Files (p. 126 in "ANSYS CFX-Solver Manager, Release 10.0")
Export Files
The file set for this export option consists of one file:
File Name File Type
<basename>.fv FIELDVIEW File
ANSYS CFX Export uses a subset of record types to be found in the full definition of the
FIELDVIEW file formats which can be found in the FIELDVIEW documentation.
Importing Files
The following procedure allows importing results into FIELDVIEW Version 6, 7 and 8.
FIELDVIEW reads the version number from within the input file.

File Export Utility: EnSight
Results files may need modification, depending on how they are to be used with FIELDVIEW.
For more details about importing, see the FIELDVIEW documentation.
1. Select Data Files > Unstructured Data Input from the menu bar. In File Selection,
select the file created using ANSYS CFX Export and then click OK. In Function Subset
Selection, select All and click OK. Click Exit in Unstructured Data Input.
2. The results can now be analyzed as required.
EnSight
EnSight is a suite of tools for engineering and scientific simulation.
Note: Prior to configuring this option, the Export dialog box must be displayed. For details,
Importing Files (p. 127 in "ANSYS CFX-Solver Manager, Release 10.0")
Export Files
The file set for this export option consists of the following files:
File Name File Type
<basename>.geom Ensight Geometry File
<basename>.results Ensight Results File (version 5)
<basename>.s01 (etc.) Ensight Variable Files for scalar variable
<basename>.v03 (etc.) Ensight Variable Files for vector variables
<basename>.case Ensight case files (Ensight 6 and 7).
Note: Each subdomain and boundary condition is exported as one EnSight part.
Note: ANSYS CFX variable aliases have to be modified to create valid EnSight variable
names, by leaving out spaces and special characters and limiting their length.
ANSYS CFX Export uses a subset of record types to be found in the full definition of the
EnSight file formats, which can be found in the EnSight documentation.
Importing Files
Files can be imported to EnSight 5, 6 and 7 as required.
Ensight 5 (p. 128 in "ANSYS CFX-Solver Manager, Release 10.0")
Ensight 6 and 7 (p. 128 in "ANSYS CFX-Solver Manager, Release 10.0")

File Export Utility: Custom User Export
Ensight 5 The following procedure allows importing results into EnSight 5. Results files may need
modification, depending on how they are to be used with EnSight. For more details about
importing, see the EnSight documentation.
1. Select File > Data (Reader). In File Selection, click the name of the geometry file created
using ANSYS CFX Export, and then click on (Set) Geometry.
2. Click on the name of the EnSight results file. Click (Set) Result and then click Okay.
3. In Data Part Loader, click Load All, and then click Close.
4. The results can now be analyzed as required.
Ensight 6 and 7 The following procedure allows importing results into EnSight 6 or 7. Results files may need
modification, depending on how they are to be used with EnSight. For more details about
importing, see the EnSight documentation.
1. Select File > Data Reader.
2. Select the Format as Case.
3. Choose the case file which has been exported. All files produced by the ANSYS
CFX-Solver Manager are automatically loaded.
Custom User Export

Files can be exported using a custom format from the ANSYS CFX-Solver Manager or from
the command line. To do so, it is required that a custom export program be created.
Creating an Export Program (p. 133 in "ANSYS CFX-Solver Manager, Release 10.0")
Export Executable
Browse to the name of your compiled executable (you must first create and compile your
user export program). For details, see Creating an Export Program (p. 133 in "ANSYS
Custom Export Settings

Enter any options for a customised program (such as would be entered as command line
flags).
Mesh and results contained within a ANSYS CFX Results File can be exported in many
formats, ready for input into post-processing software other than ANSYS CFX-Post,
MSC/PATRAN, EnSight and Fieldview. However, this is only recommended for advanced
users, since it involves at least some knowledge of C or C++ programming language.
Once an export format has been defined, it can be used by any number of users; so if other
ANSYS CFX users at a site regularly use a different post-processor, it may be worth
contacting a system administrator to find out if such a format has already been defined at a
given site.

File Export Utility: Running ANSYS CFX Export from the Command Line
To define a new format, use the Export Application Programming Interface (API). The
general steps to follow are:
1. Create a file which contains instructions needed to build the format in C.
This is most easily done by editing the template file provided (which is written in C). For
details, see An Example of an Export Program (p. 133 in "ANSYS CFX-Solver Manager,
Release 10.0").
2. Link the C file into the ANSYS CFX code.
For details, see Linking Code into ANSYS CFX (p. 150 in "ANSYS CFX-Solver Manager,
Release 10.0").
3. Use the program.
For details, see Using a Custom Export format (p. 151 in "ANSYS CFX-Solver Manager,
Release 10.0").
Numerous keywords are required for development and use of custom export files. For
details, see Keyword Descriptions (p. 130 in "ANSYS CFX-Solver Manager, Release 10.0").
Running ANSYS CFX Export from the Command Line

In the following code, [] denotes an optional argument, and <> and # denote that
substitution of a suitable value is required. All other arguments are keywords, some of which
may have a short form.
Note: -cgns, -ensight, -fieldview, -patran or -custom should be the first option on the
command line.
-ensight, creates export files suitable for input into the EnSight post-processor.
-patran, creates export files suitable for input into the MSC/PATRAN post-processor.
-fieldview, creates export files suitable for input into the FIELDVIEW post-processor.
-custom should be used if there is a need for custom defined export formats. For details,
see Export Options (p. 119 in "ANSYS CFX-Solver Manager, Release 10.0").
For all standard options (-cgns, -patran, -fieldview and -ensight), the compulsory file <file>
is the same file as would be specify under Tools > Export > Results File in the ANSYS
CFX-Solver Manager. The optional file entered as -name <file> is the same filename as would
be specify under Tools > Export > Export File.
Running ANSYS CFX Export

To run ANSYS CFX Export from the command line, type one of the following commands into
a UNIX terminal or a suitable Windows command line and press Return or Enter. For details,
see Command Line (p. 99 in "ANSYS CFX, Release 10.0: Installation and Overview").
cfx5export -cgns [-boundary] [-corrected] [-Combine] [-domain <number>] [-geometry]

[-help] [-name <file>] [-summary] [-timestep <number>] [-user <level>] [-verbose]
<file>

or
cfx5export -ensight [-5|-6|-7] [-absolute] [-ascii|-binary] [-corrected] [-domain

<number>] [-help] [-include] [-long] [-name <file>] [-summary] [-timestep <number>]
[-user <level>] [-verbose] <file>
or
cfx5export -fieldview [-6|-7|-8] [-absolute] [-ascii] [-corrected] [-domain <number>]

[-include] [-name <file>] [-summary] [-timestep <number>] [-user <level>] [-verbose]
<file>
or
cfx5export -patran [-absolute] [-boundary] [-corrected] [-domain <number>] [-geometry]

[-help] [-include] [-name <file>] [-nodes] [-summary] [-timestep <number>] [-user
<level>] [-verbose] <file>
or
cfx5export [-exec <executable>] -custom [<options>]
Keyword Descriptions
A basic description of the keywords is given below.
Argument Alternative Usage
form
-6 Write out an EnSight Version 6 case file instead of an
EnSight Version 5 results file.
Write a FieldView version 6 file instead of a FieldView
version 7 file.
-7 Write an EnSight version 7 case file instead of an Ensight
version 5 results file.
Write a FieldView version 7 file (default)
-8 Write a FieldView version 8 file instead of a FieldView
version 7 file.
-ascii -s Write the output file in ASCII format, rather than
unstructured binary format.
-binary Write the output file in unstructured binary format.
-boundary -b Boundary data only. Using this argument corresponds to
selecting the option Boundary Data Output Only when
using CFX-5 Export from the CFX-5 Solver Manager.
-cgns Export data in the CGNS format
-corrected -c Use corrected boundary node values. This corresponds to
selecting Use Surface Data on Boundary Nodes to be
ON when using CFX-5 Export from the CFX-5 Solver
Manager.
-Combine Indicates that all timesteps should be saved into one
CGNS file.


form
-custom <options> Use custom export program defined by the
CFX_EXPORT_EXEC variable. If this option is specified no
further argument checking is done and all remaining
options on the command line are passed straight to the
export program. For details, see Export Options (p. 119 in
-domain <number> -d <number> Specifies the domain of interest. If <number> is non-zero,
CFX5export will export just the given domain. If
<number> is zero, the data is combined and exported as
a single domain. The default value is 0.
-ensight Export data for use with EnSight.
-exec <executable> Because environment variables are not read under
Windows NT, this option provides an alternative way of
specifying the custom export executable dynamically,
without having to create a cfx5rc file. Note that it must
appear before the -custom switch.
-fieldview -fv Export data for use with FIELDVIEW.
-geometry -g Geometry data only (no results). Using this option
corresponds to choosing Geometry Output Only
(Neutral File) when using ANSYS CFX Export from the
ANSYS CFX-Solver Manager.
-help -h Print this information.
-include -i Include boundary node only data. If you specify this
option, then variables such as Yplus (which only have
meaningful values on the boundary nodes) will be
exported.
-long Use long variable names
-name <base> -output <base> Set the basename for the output files to <base> instead
-out <base> of the name of the input file. If you do not use this option,
the exported files will be written in the same directory as
the input file. You need to take care when selecting this
name to avoid your ANSYS CFX Results File being
over-written.
-nodes -n Use nodes when exporting packet 21 data (groups).
-patran Export data for use with MSC/PATRAN.

File Export Utility: Exporting a Transient Results File

form
-summary -f Displays a summary of the domains and timesteps
contained in the ANSYS CFX Results File.
-timestep <number> -time <number> If the <number> is non-zero, data for the given timestep
-t <number> in a transient run is exported. If <number> is -1, data from
all timesteps is exported. If the -timestep switch is not
given, data from the last timestep will be exported.
-user <level> -u <level> User level of interest: <level> should be a number 1, 2
or 3, and this corresponds to selecting Output Level 1, 2
or 3 when using ANSYS CFX Export from the ANSYS
CFX-Solver Manager.
-verbose -v Specifying this option may result in additional output
being sent to the standard output file (normally the
screen).
<file> Name of ANSYS CFX Results File from which data is to be
exported. The names of the file(s) created depends on the
format being written.
Ensight geometry will be written to <file>geom, the
results file to <file>.res, and the variables to
<file>.s## or <file>.v## where ## is the variable
number and s indicates a scalar and v a vector unless the
-name option is used.
Patran geometry will be written to <file>.out as a
Neutral file, the results template to <file>.res_tmpl,
and the nodal results to <basename>.nod unless the
name option is used.
Fieldview geometry will be written to <file>.fv unless
the -name option is used.
Note: The files will be created in the same directory as the
original files, not necessarily in the current working
directory.
Terminology
Boundary Node If you choose to use boundary node only data, then variables such as Yplus (which only take
Only Data meaningful values on the boundary nodes) will be exported.
Region Regions are defined as groups of nodes or faces which are located on the external
boundaries of the domain.
Exporting a Transient Results File

If you have completed a transient run, you have several options for exporting the results.
You can elect to:
Export the results file, which contains the solution to the final timestep.
Export one or more of the preliminary timestep solutions.
Export all of the timesteps.

File Export Utility: Exporting Particle Tracking Data
You can use either the ANSYS CFX-Solver Manager or the cfx5export script to export a
transient file.
Export Options (p. 119 in "ANSYS CFX-Solver Manager, Release 10.0")
File Format
If you elect to export the results file, which contains the solution to the final timestep, the
format will be:
filename.ext
where .ext is based on the format being written.
However, if you elect to export a different timestep, then the export file will have the
following format:
filename_t#.ext
where # is the value of the timestep exported.
Note: Ensight transient files will be sequentially numbered, regardless of the timestep value.
For example, if timesteps of 1s, 5s and 7s are exported, they will have the filenames
filename_t1.ext, filename_t2.ext and filename_t3.ext.
Exporting Particle Tracking Data

Export of particle tracking data is not supported in the current release of ANSYS CFX.
Creating an Export Program

Custom Export APIs can be created using C. An existing Export source routine can be used
as the basis of a custom export program.
An Example of an Export Program

The following is an annotated listing of the C source code for a reasonably simple example
of a customised Export program. The full source code is available for use as a template and
is located in ANSYS CFX/examples/ExportTemplate.c, where ANSYS CFX is the directory in
which ANSYS CFX is installed. For details, see Specific Directory Names (p. 9 in "ANSYS CFX,
Release 10.0: Installation and Overview").
The example program is a reasonably simple example of an export program, which opens a
ANSYS CFX Results File, outputs a geometry file (ignoring pyramid elements) and several
files containing results. After the program listing, a sample of the output produced is shown.
File Header The file header uses several #include entries. The first set include standard header files.
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <io.h>

File Export Utility: Creating an Export Program
The second set include ANSYS CFX Export header files.
#include "cfxExport.h"
#include "getargs.h"
Optaining ANSYS CFX Export header files is described in more detail. For details, see Linking
Code into ANSYS CFX (p. 150 in "ANSYS CFX-Solver Manager, Release 10.0").
Allowed The definition of allowed options appears as:

Arguments static char options[] = "u:d:t:cif";
The following piece of code simply defines the message which is printed if the user enters
incorrect options to the program.
static char *usgmsg[] = {

"usage: ExportTemplate [options] res_file [basename]",
" options are:",
" -u<level> = user level of interest",
" -d<domain> = domain of interest (default is 0 - all the domains",
" are combined into a single domain)",
" -t<timestep> = timestep of interest (if set to -1, all timesteps",
" are exported)"
" -c = use corrected boundary node data",
" -i = include boundary node only data",
" -f = get info on the res_file (No output is created)",
" <basename> is the base filename for Template file output.",
"If not specified, it defaults to res_file. The Template",
"geometry file will be written to <basename>.geom, the",
"results file to <basename>.res, and the variables to",
"<basename>.s## or <basename>.v## where ## is the variable",
"number and s indicates a scalar and v a vector.",
NULL
};
Main Program Initialisation

As is standard, the variables argc and argv are the number of arguments and a pointer to
the argument list. The variable cfxCNT_SIZE and the types cfxNode and cfxElement are
defined in the header file cfxExport.h as are all variables and functions starting with the
letters cfx. For details, see ANSYS CFX, Release 10.0 Mesh and Results Export API (p. 105 in

"ANSYS CFX, Release 10.0: Reference Guide"). The variables level, zone, alias, bndfix
and bnddat are used for setting the default values for the various parameters which can be
set on the command line of the program.
void main (int argc, char *argv[])

{
char *pptr;
char baseFileName[256], fileName[256], errmsg[256];
int i, n, counts[cfxCNT_SIZE], dim, length, namelen;
int nnodes, nelems, nscalars, nvectors, nvalues;
int level = 1, zone = 0, alias = 1, bndfix = 0, bnddat = 0;
int timestep = -1, infoOnly = 0;
int ts, t, t1, t2;
int nTimeDig = 1; /* number of digits in transient file suffix */
char zoneExt[256]; /* zone extension added to the base filename */
int isTimestep = 0;
float timeVal = 0.0; /* time value in the single timestep mode */
char *wildcard = { "******" }; /* used in transient file specification */
FILE *fp;
cfxNode *nodes;
cfxElement *elems;
float *var;
The variable cfxCNT_SIZE and the types cfxNode and cfxElement are defined in the
header file cfxExport.h as are all variables and functions starting with the letters cfx. For
details, see ANSYS CFX, Release 10.0 Mesh and Results Export API (p. 105 in "ANSYS CFX,
Release 10.0: Reference Guide"). The variables level, zone, alias, bndfix and bnddat are
used for setting the default values for the various parameters which can be set on the
command line of the program.
The following line prints an error message if there are not enough arguments to proceed.
if (argc < 2)
cfxUsage (usgmsg, NULL);

The following piece of code reads the specified options and assigns values to certain
variables accordingly. If an invalid or incomplete option is specified, then getargs prints an
error message and the export program stops.
while ((n = getargs (argc, argv, options)) > 0) {

switch (n) {
case u:
level = atoi (argarg);
break;
case d:
zone = atoi (argarg);
break;
case t:
timestep = atoi (argarg);
isTimestep = 1;
break;
case c:
bndfix = 1;
break;
case i:
bnddat = 1;
break;
case f:
infoOnly = 1;
break;
}
}
After this, the level variable contains the user level specified. All results are output if they
are of this user level or below it. The zone variable contains the domain number that you
specified. For details, see Region (p. 132 in "ANSYS CFX-Solver Manager, Release 10.0"). The
variable alias determines whether the variables are referred to by their long names or
short names. The default here is for short names to be used since some post-processors
need variable names to contain no spaces, but you are encouraged to use long variable
names wherever possible. The variable bndfix determines whether the variables are
exported with corrected boundary node values - if bndfix is set to 1, then corrected values
are used. Finally, bnddat determines whether variables which only contain meaningful
values on the boundary (such as Yplus) are exported or not - if bnddat is set to 1, then these
variables are exported.
Checking File Names

The following code checks to make sure that a ANSYS CFX Results File has been specified,
and that it can be read by the export program. If this is not the case, the export program
exits.
/* CFX-5 results file */

if (argind >= argc)
cfxUsage (usgmsg, "CFX-5 results file not specified");
if (access (argv[argind], 0)) {
fprintf (stderr, "result file <%s> does not exist\n", argv[argind]);
exit (1);
}

The following code writes the basename specified to the character array baseFileName. If
one was not specified, then it defaults to the name of the Results File specified. A basename
name may be specified in another directory (e.g. ../template/output). However, later in the
code this basename without the preceding directory information is required (in this
example output); and so the pointer pptr is assigned to point to the first character of this
name.
/* base file name */

if (argind + 1 < argc)
strcpy (baseFileName, argv[argind+1]);
else
strcpy (baseFileName, argv[argind]);
if (NULL != (pptr = strrchr (baseFileName, /)))
pptr++;
else if (NULL != (pptr = strrchr (baseFileName, \\)))
pptr++;
else
pptr = baseFileName;
The following code checks that the results file that will be produced by the export program
wont overwrite an existing results file.
/* dont overwrite results file */

sprintf (fileName, "%s.res", baseFileName);
if (0 == strcmp (argv[argind], fileName)) {
fprintf (stderr, "Template res file would overwrite ANSYS CFX results file\n");
fprintf (stderr, "Need to select new Template output base file name\n");
exit (1);
}
Opening the ANSYS CFX Results File

The following code prints a message to the screen telling you that the program is reading
the Results File. It then calls cfxExportInit, which must always be called before any of the
other export routines. The variable n is set to equal the number of zones in the Results File.
If the -f option has been selected, information about the Results File will be displayed. The

number of domains to be exported is also determined so that the format of the exported file
includes the appropriate suffix. Finally, a check is made to make sure that the zone (if any)
that you specified in the program options is a valid zone for this Results File.
/* open CFX-5 results file */

printf ("\nreading ANSYS CFX results from <%s>\n", argv[argind]);
n = cfxExportInit (argv[argind], NULL);
if (infoOnly) {
int nt;
printf("\n%d domains:\n", n);
for(i = 1; i <= n; i++)
printf(" %d %s\n", i, cfxExportZoneName(i));
nt = cfxExportTimestepCount();
printf("%d timesteps:\n", nt);
if(nt) {
for(i = 1; i <= nt; i++)
printf(" %d\n", cfxExportTimestepNumGet(i));
}
cfxExportDone();
exit (0);
}
/* determine the zone suffix for the export files */
strcpy(zoneExt, "");
if(zone == 0) {
printf ("processing all domains\n");
cfxExportSetVarParams(bndfix, level);
}
else {
printf ("processing domain %d\n", zone);
if(n != 1) {
float f;
int nZoneDig = 0;
/* count number of digits needed to fit any zone number */
f = (float) n;
while((f /= 10) >= 1) nZoneDig++;
sprintf(zoneExt, "_d%*.*d", nZoneDig, nZoneDig, zone);
}
}
if (cfxExportZoneSet (zone, counts) < 0)
cfxExportFatal ("invalid zone number");
The following code is ignoring any pyramid elements (elements with 5 nodes) and
decreases nelems by the number of pyramid elements. It then checks to make sure that
neither the number of nodes nor the number of elements is zero; if so, the program exits
with return code -1.
The first two lines focus on the number of nodes in the zone and the number of elements in
the zone.
nnodes = cfxExportNodeCount();
nelems = cfxExportElementCount();
if (counts[cfxCNT_PYR]) {
printf ("%d pyramid elements found - they are being ignored\n",
counts[cfxCNT_PYR]);
nelems -= counts[cfxCNT_PYR];
}
if (!nnodes || !nelems)
cfxExportFatal ("no nodes and/or elements");

Timestep Setup
The following code determines whether all of the timesteps, a specific timestep or the final
timestep (steady-state) have been selected for export.
if(isTimestep && timestep == -1 && !cfxExportTimestepCount()) {

isTimestep = 0;
}
if(isTimestep) {
int i;
float f;
if(timestep == -1) {
printf("processing all timesteps\n");
t1 = 1;
t2 = cfxExportTimestepCount() + 1;
}
else {
int isFound = 0;
printf("processing timestep %d\n", timestep);
for(i = 1; i <= cfxExportTimestepCount() + 1; i++)
if(cfxExportTimestepNumGet(i) == timestep) {
timeVal = cfxExportTimestepTimeGet(i);
t1 = t2 = i;
isFound = 1;
break;
}
if(!isFound) {
sprintf(errmsg, "\nTimestep %d not found. "
"Use -f to see the list of valid timesteps.\n", timestep);
cfxExportFatal (errmsg);
}
}
/* count number of digits needed to fit any timestep number */
f = (float) cfxExportTimestepCount();
while((f /= 10) >= 1) nTimeDig++;
}
else {
timeVal = cfxExportTimestepTimeGet(cfxExportTimestepCount() + 1);
timestep = cfxExportTimestepNumGet(cfxExportTimestepCount() + 1);
t1 = t2 = cfxExportTimestepCount() + 1;
}
Geometry File Output

The following code opens the geometry file basename.geom, printing an error if it cant be
opened for any reason. A message is then displayed informing the user that the application
is writing the geometry file.
/* Template geometry output */

sprintf (fileName, "%s.geom", baseFileName);
if (NULL == (fp = fopen (fileName, "w+"))) {
sprintf (errmsg, "cant open <%s> for output", fileName);
}
printf ("writing Template Geometry file to <%s>\n", fileName);

The header of this file is shown after the program listing.
/* write header */
fprintf( fp, "Template Geometry file exported from ANSYS CFX\n");
fprintf( fp, " \n");
fprintf( fp, "node id given\n");
fprintf( fp, "element id off\n");
The following code writes first the word coordinates and the number of nodes which will
be written. The pointer nodes is initialised to point at the data for the first node and the node
data is written into the geometry file. For each node, a node number is written, followed by
the three coordinates of that node. Note that n ranges between 0 and nnodes-1. This
program adds 1 to each node number so that the nodes in the geometry file are numbered
between 1 and nnodes. When it has finished, the cfxExportNodeFree routine frees the
memory that was used to store the node data, and finally the word done is printed on the
screen to alert you that it has finished writing the node data.
/* write nodes */
fprintf( fp, "coordinates\n");
fprintf( fp, "%8d\n", nnodes );
nodes = cfxExportNodeList();
printf (" writing %d nodes ...", nnodes);
fflush (stdout);
for (n = 0; n < nnodes; n++, nodes++) {
fprintf( fp, "%8d %12.5e %12.5e %12.5e\n", n + 1, nodes->x,
nodes->y, nodes->z );
}
cfxExportNodeFree();
printf (" done\n");
Next, the data for each element must be written.

Firstly, some general information is written. Then the data for each element type is written
in turn.
/* write elements */
fprintf( fp, "part 1\n" );
fprintf( fp, "volume elements\n");
printf (" writing %d elements...", nelems);
fflush (stdout);
For tetrahedral elements, the word tetra4 is written to the file, followed by the number of
tetrahedral elements written.
/* tets */
fprintf( fp, "tetra4\n");
fprintf( fp, "%8d\n", counts[cfxCNT_TET] );
The following code is only executed if the number of tetrahedral elements is non-zero.
Assuming this, elems is set to point to the list of elements stored in the Results File. The
index n loops over all the elements. For each element, the following step is carried out: If

the element is a tetrahedron, then loop over its four vertices and write their node numbers
to the geometry file, then start a new line (ready for the next set of data).. The output
produced can be seen in the examples of the exported files in the next section.
if (counts[cfxCNT_TET]) {
elems = cfxExportElementList();
for (n = 0; n < nelems; n++, elems++) {
if (cfxELEM_TET == elems->type) {
for (i = 0; i < elems->type; i++)
fprintf (fp, "%8d", elems->nodeid[i]);
putc (\n, fp);
}
}
}
For wedges (triangular prisms) and hexahedral elements, the same procedure is followed.
However, there is a slight difference in the way that the fprintf line is written for
hexahedral elements. This is because the order that the element nodes are written to the
geometry file is different to the order in which they were read from the Results File. This may
need to be done if a post-processor has a different convention for node order than the one

which the ANSYS CFX Export node routines have. Which order the nodes are written in will
affect which node is connected to which. The following diagrams show the order of the
nodes and connections that ANSYS CFX uses.
3 4
0
2 3
0
1 2
1
Pyramid element
Tethrahedral element
6
5
3 4 7
5
4
2
2
0 0 3
1 1
Wedge (prism) element Hexahedral element
/* wedges */
fprintf( fp, "penta6\n");
fprintf( fp, "%8d\n", counts[cfxCNT_WDG] );
if (counts[cfxCNT_WDG]) {
if (cfxELEM_WDG == elems->type) {
for (i = 0; i < elems->type; i++)
fprintf (fp, "%8d", elems->nodeid[i]);
}
putc (\n, fp);
}
}
/* hexes */
fprintf( fp, "hexa8\n");
fprintf( fp, "%8d\n", counts[cfxCNT_HEX] );
if (counts[cfxCNT_HEX]) {
if (cfxELEM_HEX == elems->type)
fprintf (fp, "%8d%8d%8d%8d%8d%8d%8d%8d\n",
elems->nodeid[0], elems->nodeid[1],
elems->nodeid[7], elems->nodeid[6]);
}
}

Then the geometry file is closed and the memory occupied by the element data is freed.
printf (" done\n");

fclose (fp);
cfxExportElementFree();
The Template Results File

Despite its name, the Template results file does not contain any actual values of results. It
simply contains information about how many variables there are and in which file each is
stored.
The first job is to make sure that there are some results for export. Firstly, the code checks
that there is a non-zero number of variables which have the specified user level. Then it
counts the number of scalar and vector variables which will be exported. To be exported, a
variable must:
1. Have a dimension of 1 (scalar variable) or 3 (vector variable) and,
2. Either be a variable with useful values everywhere in the zone or be a variable which
only has values on the boundaries (in which case it will only be exported if you asked to
include boundary node only data by specifying the option -i when starting the export
program, which translated to setting bnddat = 1 when the arguments were
processed).
Review the cfxExportVariableSize routine if this logic is unclear. For details, see
cfxExportVariableSize (p. 116 in "ANSYS CFX, Release 10.0: Reference Guide").
Once results are identified, the code calculates the variable namelen, which is the length of
the longest variable name to be exported (the alias variable was set when processing the
arguments passed to the export program, and depends upon whether you wanted to use
long names or short names). If there are no vector or scalar variables to be exported, the
export program exits.
/* output results file */

nscalars = nvectors = namelen = 0;
if ((nvalues = cfxExportVariableCount(level)) > 0) {
for (n = 1; n <= nvalues; n++) {
cfxExportVariableSize (n, &dim, &length, &i);
if ((1 != dim && 3 != dim) ||
(length != nnodes && length != bnddat))
continue;
if (1 == dim)
nscalars++;
else
nvectors++;
i = strlen (cfxExportVariableName (n, alias));
if (namelen < i)
namelen = i;
}
}
if (0 == (nscalars + nvectors)) {
cfxExportDone ();
exit (0);
}

The following code checks that the results file can be opened for writing to, and exits if not.
The number of scalar and vector variables are written to the file, followed by some numbers
(which EnSight, for example, requires) which are always the same for any export of this kind.
sprintf (fileName, "%s.res", baseFileName);

sprintf (errmsg, "cant open <%s> for writing", fileName);
}
printf ("writing Template results file to <%s>\n", fileName);
fflush (stdout);
fprintf( fp, "%d %d 0\n", nscalars, nvectors );
fprintf( fp, "%d\n", t2 - t1 + 1 );
for(i = t1; i <= t2; i++) {
fprintf( fp, "%13.4e", cfxExportTimestepTimeGet(i));
if(!(i % 6)) fprintf( fp, "\n");
}
fprintf( fp, "\n");
if(isTimestep && t1 != t2)
fprintf( fp, "0 1\n");
Next, for each scalar variable, a line is written which contains the filename where the scalar
will be written, and then the name of the variable. Note that the filename is not the
basename, but the basename with all the directory structure (if any) stripped off the front.
For details, see Checking File Names (p. 136 in "ANSYS CFX-Solver Manager, Release 10.0").
This is done because these file will be written in the same directory as this Template results
file, so there is no need for directory information.
if ( nscalars ) {
if (1 == dim && (length == nnodes || length == bnddat))
if(!isTimestep)
fprintf (fp, "%s%s.s%2.2d %s\n", pptr, zoneExt,
n, cfxExportVariableName(n, alias));
else if(t1 == t2)
fprintf (fp, "%s%s_t%d.s%2.2d %s\n", pptr, zoneExt,
cfxExportTimestepNumGet(t1), n,
cfxExportVariableName(n, alias));
else
fprintf (fp, "%s%s_t%*.*s.s%2.2d %s\n", pptr, zoneExt,
nTimeDig, nTimeDig, wildcard, n,
}
}

The same information is then written for each vector variable and the Template results file
is closed.
if ( nvectors ) {
if (3 == dim && (length == nnodes || length == bnddat))
if(!isTimestep)
fprintf (fp, "%s%s.v%2.2d %s\n", pptr, zoneExt,
n, cfxExportVariableName(n, alias));
else if(t1 == t2)
fprintf (fp, "%s%s_t%d.v%2.2d %s\n", pptr, zoneExt,
cfxExportTimestepNumGet(t1), n,
else
fprintf (fp, "%s%s_t%*.*s.v%2.2d %s\n", pptr, zoneExt,
nTimeDig, nTimeDig, wildcard, n,
}
}
fclose( fp );
Creating Files with Results for Each Variable

The results for each variable are written to a separate file, called <basename>.s01,
<basename>.s02, <basename>.v03, for example. Each file with an extension containing a
letter s contains a scalar variable, and each with a v contains a vector variable. Which
variable is written to each file is tabulated in the Template results file which has just been
written.
The following code reads the information for each variable, after you decide that it should
be exported - the logic is very similar to that used when counting the relevant variables
when creating the Template results file. The marked if loop executes if the variable needs
to be exported. It checks to make sure that the variable information can be read, and
(assuming it can) then builds the filename and checks to see if it can be opened. Continuing,
it writes to the screen where it is putting the variable, and then loops through all the values,
writing them to the file, inserting a new line every six values. After each variable, the memory
used to store that variable is restored.

After all the variable files have been written, the program calls the cfxExportDone routine,
which close the ANSYS CFX Results File, and frees up any remaining memory. This routine
must be the last call to any of the cfx routines. The program then exits.
Note: This program makes no use of any of the region routines, which allow access to
boundary condition data, nor the volume routines which allow access to the subdomains
which are defined for a problem.
Region routines (p. 114 in "ANSYS CFX, Release 10.0: Reference Guide")
Volume routines (p. 113 in "ANSYS CFX, Release 10.0: Reference Guide")
/* output each timestep to a different file */

for(t = t1; t <= t2; t++) {
ts = cfxExportTimestepNumGet(t);
if(cfxExportTimestepSet(ts) < 0) {
continue;
}
/* build file name and open file */
if(!isTimestep)
sprintf( fileName, "%s%s.%c%2.2d", baseFileName, zoneExt,
1 == dim ? s : v, n);
else if(t1 == t2)
sprintf( fileName, "%s%s_t%d.%c%2.2d", baseFileName, zoneExt,
ts, 1 == dim ? s : v, n);
else
sprintf( fileName, "%s%s_t%*.*d.%c%2.2d", baseFileName, zoneExt,
nTimeDig, nTimeDig, t-1, 1 == dim ? s : v, n);
sprintf (errmsg, "cant open <%s> for writing\n", fileName);
}
printf (" %-*s -> %s ...", namelen,
cfxExportVariableName(n, alias), fileName);
fflush (stdout);
fprintf( fp, "%s\n", cfxExportVariableName(n, alias));
length = nnodes * dim;
for ( i = 0; i < length; i++, var++ ) {
fprintf( fp, "%12.5e ", *var );
if ( i && 5 == (i % 6) )
putc (\n, fp);
}
if ( 0 != ( nvalues % 6 ) )
putc( \n, fp );
fclose( fp );
cfxExportVariableFree (n);
printf (" done\n");
}
}
} /* loop for each timestep */
cfxExportDone();
exit (0);
}
Example of Output Produced

If the above program is correctly compiled and run, the following output is obtained. For
details, see Using a Custom Export format (p. 151 in "ANSYS CFX-Solver Manager, Release
10.0").

In this example, the ANSYS CFX Results File contains three variables at user level 1: pressure,
temperature and velocity. This is in a file named file.res. No timesteps or domains were
specified, and the basename was specified as an example.
The following is displayed on screen:
reading ANSYS CFX results from <file.res>

processing all domains
writing Template Geometry file to <example.geom>
writing 2365 nodes ... done
writing 11435 elements... done
writing Template results file to <example.res>
writing variable output files
Pressure -> example.s01 ... done
Temperature -> example.s02 ... done
Velocity -> example.v03 ... done
Five files are produced: the geometry file example.geom, the Template results file
example.res, and three variable files called example.s01, example.s02 and
example.v03, which contain the results for pressure, temperature and velocity,
respectively.
example.geom (p. 148 in "ANSYS CFX-Solver Manager, Release 10.0")
example.res (p. 148 in "ANSYS CFX-Solver Manager, Release 10.0")
example.s01 (p. 148 in "ANSYS CFX-Solver Manager, Release 10.0")

example.geom The content of this file appears as:
Template Geometry file exported from ANSYS CFX
node id given
element id off
coordinates
2365
1 2.00000e+00 0.00000e+00 0.00000e+00
2-2.00000e+00-6.51683e-07 0.00000e+00
3 2.00000e+00 0.00000e+00 2.00000e+00
4-2.00000e+00-6.51683e-07 2.00000e+00
5 3.00000e+00 1.00000e+00 5.00000e-01
....
....
....
2362-1.13337e+00 2.18877e-01 4.02491e-01
2363-1.12115e+00-3.66598e-01 2.22610e-01
2364 1.36924e+00 4.78359e-01 1.22588e-01
2365-3.30703e-01 1.38487e+00 2.23515e+00
part 1
volume elements
tetra4
11435
754 230 12 145
755 216 8 122
756 212 125 215
....
....
....
2365 496 475 474
penta6
0
hexa8
0
example.res The content of this file appears as:
2 1 0
1
0.0
0 1
example.s01 Pressure
example.s02 Temperature
example.v03 Velocity
example.s01 The content of this file appears as:
Pressure
1.42748e+04 1.42621e+04 1.43425e+04 1.43350e+04 1.44118e+04 1.44777e+04
1.38639e+04 1.37352e+04 1.44130e+04 1.44755e+04 1.37733e+04 1.37626e+04
....
....
....
1.39092e+04 1.40699e+04 1.24139e+04 1.34786e+04 1.34859e+04 1.37959e+04

Source Code for getargs.c

The following code is the C code which defines the functions cfxUsage and getargs, both
of which are called by the example listing above. You do not need to include this code with
your custom export program (it is automatically linked in if you use the compiler as
described in the next section).
#include <stdio.h>
#include <string.h>
#include <ctype.h>
#include "getargs.h"
/*---------- usage --------------------------------------------------

* display usage message and exit
*-------------------------------------------------------------------*/
void cfxUsage (
#ifdef PROTOTYPE
char **usgmsg, char *errmsg)
#else
usgmsg, errmsg)
char **usgmsg, *errmsg;
#endif
{
int n;
if (NULL != errmsg)
fprintf (stderr, "ERROR: %s\n", errmsg);
for (n = 0; NULL != usgmsg[n]; n++)
fprintf (stderr, "%s\n", usgmsg[n]);
exit (NULL != errmsg);
}
/*---------- getargs ---------------------------------------------------

* get option letter from argument vector or terminates on error
* this is similar to getopt()
*----------------------------------------------------------------------*/
int argind = 0; /* index into argv array */

char *argarg; /* pointer to argument string */
int getargs (
#ifdef PROTOTYPE
int argc, char **argv, char *ostr)
#else
argc, argv, ostr)
int argc;
char **argv, *ostr;
#endif
{
int argopt;
char *oli;
static char *place;
static int nextarg;
/* initialisation */
if (!argind)
nextarg = 1;
if (nextarg) { /* update scanning pointer */
nextarg = 0;
/* end of arguments */
if (++argind >= argc || - != argv[argind][0])
return (0);

File Export Utility: Linking Code into ANSYS CFX
place = argarg = &argv[argind][1];
}
/* check for valid option */
if ((argopt = *place++) == : ||
(oli = strchr (ostr, argopt)) == NULL) {
fprintf (stderr, "invalid command line option `%c\n", argopt);
exit (1);
}
/* check for an argument */
if (*++oli != :) { /* dont need argument */
argarg = NULL;
if (!*place)
nextarg = 1;
}
else { /* need an argument */
if (!*place) {
if (++argind >= argc) {
fprintf (stderr, "missing argument for option `%c\n", argopt);
exit (1);
}
place = argv[argind];
}
argarg = place;
nextarg = 1;
}
return (argopt); /* return option letter */
}
Linking Code into ANSYS CFX

In order to build an export utility routine, it must be linked with the Export API library. The
library is named libmeshexport.a.
Compiler Flags
The following compiler flags are necessary for successful compilation on the listed
platforms:
Platform Flag
hpux (pa-2) +DS2.0W +DA2.0W
hpux-ia64 +DD64
linux (32 bit) <none>
linux-ia64 <none>, but use ecc compiler
irix -64
solaris -xarch=v9
aix -q64 (the linker may also need -b64)
osf <none>
UNIX
On most UNIX systems, build the executable with the command:
cc export.c -o export.exe -IANSYS CFX/include/ -o export -LANSYS CFX/lib/ -lmeshexport

-lcclapilt -lio -lm -lc

File Export Utility: Using a Custom Export format
where ANSYS CFX is the directory in which ANSYS CFX is installed and ANSYS CFX is the
architecture of the machine that you are running on (e.g. one of solaris, irix, hpux,
hpux-ia64, aix, linux, linux-ia64,osf). The ANSYS CFX for your installation can be
identified. For details, see Specific Directory Names (p. 9 in "ANSYS CFX, Release 10.0:
Installation and Overview"). The ANSYS CFX for your machine can be identeified. For details,
see Operating System Names (p. 10 in "ANSYS CFX, Release 10.0: Installation and Overview").
In this example, your own export program is named expo.c and the executable file will be
called export.exe. Please note the compiler flags listed above.
Windows
On Windows systems, using the Microsoft Developer Studio which comes with Visual C++,
build the executable as follows.
1. Open the .c file for the import routine (for example export.c) in Microsoft Developer
Studio.
2. Specify the libraries which need to be linked in, by selecting Project > Add to Project >
Files. Add Library Files libio.lib, libmeshexport.lib and libcclapilt.lib
from the ANSYS CFX\lib\winnt directory, whereANSYS CFX is the directory in which
ANSYS CFX is installed.
3. Select Project > Settings, and select Settings for All Configurations and ANSYS
CFX\include.
4. Under Project Settings, click the Link tab and enter C, LIBCD in Ignore Libraries.
5. Click the C/C++ tab, select Code Generation from the Category option menu, and
select Multithreaded DLL from Use run-time Library.
6. To build the executable, select Build > Build <program_name>.exe, where
<program_name> is the name of the project.
Using a Custom Export format

There are multiple ways in which an export program can be used once it has been compiled.
Using the ANSYS CFX-Solver Manager GUI (p. 151 in "ANSYS CFX-Solver Manager, Release
10.0")
Using the command line (p. 152 in "ANSYS CFX-Solver Manager, Release 10.0")
Using cfx5export (p. 152 in "ANSYS CFX-Solver Manager, Release 10.0")
Using the ANSYS CFX-Solver Manager GUI

Using this method, supply the name of the program and any associated options (such as
would be entered at the command line). The cfx5export command will be run using the
program and with the associated arguments included.
This can also run directly from the command line. For the purposes of describing the
procedure, assume the executable file is called myexport and is contained in the directory
/home/user/export/ (UNIX) or c:\user\export (Windows). Specify the results file
called file.res in the same directory and make the basename example.

File Export Utility: Using a Custom Export format
Using the command line

You may also run directly from the command line. For the purposes of describing what you
can do, we will assume that the executable file is called myexport and is contained in the
directory /home/smith/export/ (UNIX) or c:\smith\export (Windows). We want to
specify the results file called file.res in the same directory and make the basename
example.
UNIX To run the program directly on a UNIX system, call it using:
./myexport file.res example
assuming that the current directory is /home/user/export/.
Windows On a Windows machine, run the program by opening a command window, changing
directory to c:\user\export, and typing:
myexport file.res example
Note: Just double-clicking on the name of the program in the Windows Explorer, or using
the Execute myexport.exe option in Microsoft Developer Studio does not readily give you
the option to enter command line arguments.
Using cfx5export
To run the program using the cfx5export -custom command, add the following line to
the .cfx5rc file:
CFX_EXPORT_EXEC="<executable_path>"
where <executable_path> is the full path and name of the executable (e.g.
/home/user/export/myexport or c:\user\export\myexport as appropriate). For
details, see Resources Set in cfx5rc Files (p. 69 in "ANSYS CFX, Release 10.0: Installation and
Overview").
The cfx5export command can be used with the -custom argument for the given
example. Type:
cfx5export -custom file.res example
into a UNIX terminal or a suitable Windows NT command line and press Return or Enter. For
details, see Command Line (p. 99 in "ANSYS CFX, Release 10.0: Installation and Overview").

Index
A convergence history 34
adaption 46
additional variables 113 transient 43
allowed arguments 134 cpu requirements 42
false transient information 41
final average scales 41
global conservation statistics 37
B
header 30
host information (parallel) 45
boundary initial average scales 34
corrected node values 130 job information 42
node only data 131, 132 linear solution 35
value only variables 53 maximum residual 34, 40
boundary conditions CFX-5 output file
in user export 146 job information 30
memory usage 31
memory usage (parallel) 45
C mesh adaption 46
mesh refinement 46
capacity, specific heat 54 mesh statistics 30
CFD (computational fluid dynamics) partitioning information (parallel) 44
job information 30 rate 34
CFX-5 rms residual 34
command file solved equations 34
editing 69 starting job information (parallel) 44
generating 69 thermal energy (solid) 47
structure 69 wall forces and moments 39
commands CFX-5 Solver Manager
cfx5cmds 69 starting 8
cfx5export 129 changing
cfx5interp 92
appearance of definition file editor 68
export
checking file names 136
with transient results 132
coefficient, heat transfer 54
output file
combustion 113
command file 31
completed job information command file 31
(parallel) 45 Command File Editor 64
computed model constants 36 completed job information 45
conjugate heat transfer 47 computed model constants 36
Page 153
Index: D
conductivity, thermal 54 F
convergence
history 34, 43, 46 false transient information 41
corrected boundary node values 130 fieldview
CPU requirements 42 post-processing 117
custom export settings 128 file
customising format 133
solver manager 12 header 133
rules 70
variables 70
D flux, heat 54
define run command 75

define run form 13 G
definition file
editor GGI
rules 68 interfaces 113
dissipation, turbulence eddy 55
distributed parallel
setup 22 H
heat flux 54
E heat transfer
coefficient 54
eddy viscosity 55 hexahedral element 142
edit history, convergence 34
CCL file 69
element
hexahedral 142 I
prism 142
pyramid 142 importing results
tetrahedral 142 to Fieldview 126
wedge 142 information, false transient 41
energy interpolating results 91
turbulence kinetic 55
EnSight
options 127 K
post-processing 117
using exported files 127 kinematic diffusivity 54
enthalpy 54
equations, Navier-Stokes 27
expansivity, thermal 55 L
export
boundary conditions to linking
MSC/Patran 124 code into CFX-5 150
executable 128 export programs 150
linking programs 150
plot data 11
transient results file 132 M
mach number 56
Page 154
Index: N
mesh S
refinement 46
statistics 30 shear strain rate 54
mesh interpolation 91 specific heat capacity 54
using command line 92 static
monitor points enthalpy 54
plotting 84 structure of .mst file 87
monitors subdomain
general settings 82 in user export 146
plot lines 83
range settings 83
MSC/Patran T
options 123
post-processing 117 temperature 54
tetrahedral element 142
thermal conductivity 54
N thermal expansivity 55
timestep
Navier-Stokes equations 27 setup 139
total
enthalpy 54
P pressure 53
temperature 54
partitioning transient information, false 41
information 44 transient simulations
viewing 46 exporting data from 132
post-processing turbulence eddy dissipation 55
EnSight 117 turbulence kinetic energy 55
fieldview 117
MSC/Patran 117
pressure U
total 53
printing user
to a printer 10 export 128
prism element 142 level of variables 53
pyramid element 142
V
R
variables
rate, shear strain 54 boundary value only 53
residual plot definition 53
obtaining for old runs 60 file 70
Residual Plotting list of all 52
Transient 61 short names 53
residual, definition 59 user level 53
restarting a run 23 viscosity
results file 29 dynamic 53
results, interpolating 91 eddy 55
rules file 70 volume of finite volume 54
Page 155
Index: W
W
wall heat flux 54

wall shear 53
wedge element 142
Yplus 55
Page 156

CFXMGR Book

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CFXMGR Book

Hochgeladen von

Copyright:

Verfügbare Formate

ANSYS CFX-Solver Manager,

Working with Solver Manager

ANSYS CFX-Solver Manager, Release 10.0 Page 1

Editing Definition Files

Page 2 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX-Solver Manager, Release 10.0 Page 3

Starting CFX-Solver from the Command Line

CFX-Solver Start Methods

CPU and Memory Requirements

Page 4 ANSYS CFX-Solver Manager, Release 10.0

File Export Utility

ANSYS CFX-Solver Manager, Release 10.0 Page 5

Page 6 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX-Solver Manager, Release 10.0 Page 7

Starting ANSYS CFX-Solver Manager

Using ANSYS Workbench

Using ANSYS CFX-Pre

Using the Command Line

Page 8 ANSYS CFX-Solver Manager, Release 10.0

Working with the Solver Manager Interface

ANSYS CFX-Solver Manager, Release 10.0 Page 9

Convergence History Plots

Printing Images Images in the Convergence Plot History can be printed.

Page 10 ANSYS CFX-Solver Manager, Release 10.0

Text Output Window

ANSYS CFX-Solver Manager, Release 10.0 Page 11

1. Click the Workspace drop down list.

Customising Solver Manager

Page 12 ANSYS CFX-Solver Manager, Release 10.0

Define Run dialog box

ANSYS CFX-Solver Manager, Release 10.0 Page 13

Definition file name

Run definition procedure

Run Definition tab

Page 14 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX-Solver Manager, Release 10.0 Page 15

Page 16 ANSYS CFX-Solver Manager, Release 10.0

Memory Allocation Factor

Detailed Memory Overrides

ANSYS CFX-Solver Manager, Release 10.0 Page 17

Specifying an Initial Values File

Page 18 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX-Solver Manager, Release 10.0 Page 19

Information on a parallel run is explained in more detail:

Page 20 ANSYS CFX-Solver Manager, Release 10.0

Configuring a parallel run

ANSYS CFX-Solver Manager, Release 10.0 Page 21

2. Click Add Partition or Remove Partition to increase or decrease the number

Selecting parallel hosts

1. Click Insert Host .

2. Click Add Partition or Remove Partition to increase or decrease the number

Page 22 ANSYS CFX-Solver Manager, Release 10.0

Reasons for restarting

ANSYS CFX-Solver Manager, Release 10.0 Page 23

Page 24 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX-Solver Manager, Release 10.0 Page 25

Page 26 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX-Solver Manager, Release 10.0 Page 27

Input Files and Initial Values Files

Page 28 ANSYS CFX-Solver Manager, Release 10.0

ANSYS CFX Results File

ANSYS CFX-Solver Manager, Release 10.0 Page 29

ANSYS CFX Output File