Analysis Settings

The Analysis Settings field has the following properties:

Suggested best practices for analysis settings are discussed in Analysis Settings Best Practices.

Analysis Type

This option is used to define the overall coupling type for the analysis.

The available options are:

  • General

    • This is the only available option when one or more of the coupling participants is executing steady or static analyses. Note that mixed steady/static and transient analyses are not currently possible.

  • Transient

    • This is the only available option when all of the coupling participants are executing transient analyses.

Initialization Controls

This option is used to define the initialization controls available for all coupling types.

Coupling Initialization

The available options are:

  • Program Controlled

    • For initial runs (that is, not restart runs), the initial time and step are each set to 0.

    • For restart runs, the initial time and step are set to the values obtained from the latest valid restart point.

  • Restart Points (indicated by Step and Time)

    • The system coupling simulation can have multiple restart points when Intermediate Restart Data Output is selected for either all coupling steps or for a set of coupling step intervals. The next coupled analysis will be started based on the restart point that you have selected.

For more information regarding restarts, see Restarting a System Coupling Analysis.


Important:  Program controlled or explicitly specified restart points only affect the coupling step and/or time used to restart the coupling service. Appropriate restart points must also be specified for the co-simulation participants that are part of the coupled analysis. For more information about coupling participants, see Restarting a System Coupling Analysis.


Duration Controls

This option is used to define the duration for the analysis.

Duration Defined By

The options available to define the duration of a coupled analysis are:

  • End Time

    • Available only when the Analysis Type is Transient

    • When the End Time option is used, the coupling service will execute coupling steps until the specified end time is reached. In a transient analysis, each coupling step is a time step (with the time interval specified by the step size). Note that the final coupling step size is reduced automatically, if needed, so that the specified end time is respected.

    • Some of the participant systems, such as ANSYS Mechanical, require the end time specified in their setup to be respected. When a coupled analysis involves one or more participants that require their setup’s end time be respected, then the maximum allowable end time for the coupled analysis is the minimum of the end times reported by such participants. In this case, a validation error will be reported if the coupled analysis’ specified end time is greater than the minimum identified.

      Other participant systems, such as Fluent, can run past the end time specified. These participant systems have no effect on the allowable end time of the coupled analysis.

  • Number of Steps

    • Available only when the Analysis Type is General.

    • When this option is used, the coupling service will execute coupling steps until the specified number of steps is reached.

Step Controls

The duration of the coupled analysis is broken into a sequence of coupling steps. Data transfers between the coupled solvers occur at the beginning of each coupling iteration within a coupling step. Coupling steps are always indexed. During the analysis, each new coupling step is started when:

  • The coupling analysis duration has not been reached, and

  • Either the maximum number of coupling iterations has been reached or the coupling step is converged.

The available options are:

  • Step Size

    • If the coupling is defined in terms of time (a transient analysis), then a coupling step is associated with a time interval. The Step Size option specifies the time interval associated with each coupling step (in seconds). The final coupling step size is reduced automatically, if needed, so that the specified end time is respected. This reduction does not occur if the analysis duration is set by the Number of Steps.

    • The coupling step size is fixed for the duration of the System Coupling analysis, but it can be changed when restarting the analysis.

  • Minimum Iterations

    • This option allows specification of the fewest number of coupling iterations (at least 1) that could be executed per coupling step.

    • The specified minimum number of coupling iterations will be executed even if all measures of convergence are realized in fewer iterations.

  • Maximum Iterations

    • This option allows specification of the greatest number of coupling iterations that could possibly be executed per coupling step.

    • The specified maximum number of coupling iterations may not be executed if the analysis converges prior to the maximum iteration step being reached.

Analysis Settings Best Practices

This section provides information about best practices for the following analysis settings:

General Analysis Type

With a General analysis type, accurate coupled solutions can be achieved using different combinations of coupling step and coupling iteration specifications. The two cases described below are: when an analysis is solved using one coupling step, and when an analysis is solved using many coupling steps. Your choice of the combination of coupling steps and coupling iterations will:

  • determine when result and/or restart data is able to be written, as the restart points can only be written at the end of a coupling step,

  • allow you to balance the required file storage space and your need for analysis restarts,

  • determine how you can use system coupling’s under relaxation factor (see Under-Relaxation Algorithm) and ramping (see Ramping Algorithm), as these only apply to coupling iterations and cannot be applied over coupling steps.

For more information about restarting your coupled analysis, see Restarting a System Coupling Analysis.

Coupled Analysis solved using only one Coupling Step

A coupled analysis can be solved using only one coupling step. In this case, the coupling step is made up of many coupling iterations, and the solution is complete at the end of this one step. The analysis will continue executing until either the solution converges, or the specified maximum number of coupling iterations is completed. Only the end of a coupling step can be used as a restart point. When only one coupling step is used, results and restart data is generated only at the end of the solution. The analysis can be terminated as usual, but because intermediate restart data is not generated, the coupled analysis cannot be restarted if it terminates abnormally (due to an error, power interruption, etc.) or if you terminate it before the coupling step is completed. Using only one coupling step within a coupled analysis minimizes file storage space at the expense of the ability to restart the analysis. Interrupting the analysis will not affect the analysis, because System Coupling will complete the current coupling step (and so complete the solution) before stopping the analysis. Ramping and under-relaxation can be applied across coupling iterations within the single coupling step.

Coupled Analysis solved using many Coupling Steps

A coupled analysis can be solved using many coupling steps. In this case, the coupling steps are made up of one or more coupling iterations. The analysis will continue executing until the specified number of coupling steps is completed. The transition from one coupling step to the next will occur when either the solution converges or the specified maximum number of coupling iterations is completed. Only the end of a coupling step can be used as a restart point (you are able to specify which steps are used). Results and restart data is generated at the specified restart points. If the analysis should terminate abnormally within a coupling step, you can restart the analysis from the previous restart point. By using more coupling steps with fewer coupling iterations per step, as opposed to one coupling step with many coupling iterations, more points at which restarts can be done are created. For difficult or complex analyses, which might experience abnormal terminations, more restart points allow restarts of the analysis (saving time and computational effort) at the expense of file storage space. System Coupling’s ramping and under-relaxation can be used across coupling iterations, but cannot be used across coupling steps, so System Coupling always transfers the full data transfer value at the end of each coupling step. Participant solvers may ramp data received from System Coupling at the coupling steps.

Transient Analysis Type

In a transient analysis, a coupling step is associated with a time interval by specifying the coupling step size (in seconds). With a time specified, a coupling step is the same as a time step within the transient analysis. The coupling step size used should reflect the time scales of the physics being studied. Note that unless sub-stepping is supported by the co-simulation participants being coupled, the coupling step size will typically be limited by the finest/smallest time scale of the co-simulation participants. If the analysis duration is specified using an End Time, then care should be taken to ensure that an integral number of coupling steps can be executed between the (re)start time and the specified end time. If this is not done, then the final coupling step size will be reduced to respect the specified end time, and this may introduce temporal discretization error into the coupled analysis.

The minimum number of coupling iterations may be set to a value larger than one (one is the default). If the data transfers have been under relaxed, you want to ensure a minimum number of coupling iterations is performed so that you iterate out the effect of the under-relaxation. Note that the data transfer convergence criteria would usually make this unnecessary.

The maximum number of coupling iterations should be set to allow complete convergence within each coupling step. Failure to fully converge within a given coupling step will modify the transient behavior from that step onward.


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