22.1.1. Basic Settings: Common

22.1.1.1. Advection Scheme

For details, see Advection Scheme Selection in the CFX-Solver Modeling Guide.

22.1.1.2. Transient Scheme

The Transient Scheme settings are available for steady-state simulations and for transient blade row cases that use the Harmonic Balance transient method. For details, see Transient Scheme in the CFX-Solver Modeling Guide.

22.1.1.3. Turbulence Numerics

The Turbulence Numerics options are First Order and High Resolution. The First Order option uses Upwind advection and the First Order Backward Euler transient scheme. The High Resolution option uses High Resolution advection and the High Resolution transient scheme.

For details, see Advection Scheme Selection in the CFX-Solver Modeling Guide and Transient Scheme in the CFX-Solver Modeling Guide.


Note:  The settings on the Equation Class Settings Tab will override the Turbulence Numerics settings.


22.1.1.4. Convergence Criteria

For details, see Monitoring and Obtaining Convergence in the CFX-Solver Modeling Guide.

22.1.1.5. Elapsed Wall Clock Time Control

Select the Maximum Run Time option if you want to stop your run after a maximum elapsed time (wall clock time).

If you select this option the flow solver will automatically attempt to estimate the time to complete the next timestep or outer loop iteration. The estimated time is the average time that it takes to solve a previous iteration (includes the time to assemble and solve the linear equations, radiation and particle tracking) plus the average time it is taking to write any Standard backup or transient files. The time estimate currently does not include the time used by processes external to the flow solver. This includes mesh refinement, interpolation and FSI with Mechanical.

22.1.1.6. Interrupt Control

Interrupt control conditions are used to specify criteria for stopping a solver run independently of any specified Elapsed Wall Clock Time Control settings.

You can set Option to:

  • Any Interrupt

    This option causes a solver run to terminate if the specified convergence conditions (specified under Convergence Conditions) are met or if any of the user-defined interrupts (specified under User Interrupt Conditions) are triggered.

  • All Interrupts

    This option causes a solver run to terminate only if the specified convergence conditions are met and all user-defined interrupts are triggered.

The Convergence Conditions settings indicate which of the convergence criteria constitute an interrupt condition:

  • Default Conditions

    With this option, the convergence criteria selected are those normally used for the type (steady-state, transient, harmonic balance) of run.

  • Selected Conditions

    With this option, you can manually select the convergence criteria from a list.

User-defined interrupt control conditions are specified using logical expressions. These expressions are evaluated by CFX-Solver and are reported in the CFX-Solver Output file. After executing each iteration (of a steady-state case) or time step (of a transient case), the solver evaluates all internal termination conditions and all user-defined interrupt control conditions. If any or all (depending on the interrupt control option) of these conditions are true, then solver execution stops and the outcome is written to the CFX-Solver Output file.

Typically, interrupt control conditions are defined by single-valued logical expressions. However, single-valued mathematical expressions can also be used. In this case, a single-valued mathematical expression is considered to be true if and only if the result of the expression is greater than or equal to 0.5. Otherwise it is deemed to have a value of false. For a discussion on logical expressions, see CFX Expression Language Statements in the CFX Reference Guide.

You should consider setting interrupt control conditions if you expect your case to exhibit transient convergence behavior. For details and an example, see Using Interrupt Control in Cases with Transient Convergence Behavior in the CFX-Solver Modeling Guide.


Note:
  • To prevent a steady-state run from being interrupted before reaching the intended minimum number of iterations, each interrupt condition should include a requirement that the minimum number of iterations has been completed. For example, an interrupt condition could begin with "aitern>5 && " in order to require that a minimum number of 5 iterations has been reached before the interrupt control condition can evaluate to true.

  • Interrupt control is ignored in a System Coupling analysis. For details, see Supported Capabilities and Limitations in the CFX-Solver Modeling Guide.


22.1.1.6.1. List Box

The list box is used to select interrupt control conditions for editing or deletion. Interrupt control conditions can be created or deleted with icons that appear beside the list box.

22.1.1.6.1.1. [Interrupt Condition Name]

Enter a logical expression to specify an interrupt control condition.

22.1.1.7. Junction Box Routine

If you have created any Junction Box Routine objects, select those to include in this Solver run.

For details, see User Junction Box Routines in the CFX-Solver Modeling Guide.