Iterative

An alternative to the iterative linear system solvers is given by direct linear system solvers, which are handled via the Direct attribute node. Although several attribute subnodes for solving linear systems can be attached to an operation node, only one can be active at any given time.

The iterative solver iterates until a relative tolerance is fulfilled. You specify this tolerance in the field of the operation node to which this attribute belongs.

Also see The Iterative Solvers, Iterative Solver Types, and Selecting a Preconditioner for an Iterative Linear System Solver for more details about the settings under .

This section contains settings for choosing an iterative linear system solver and for specifying the type of preconditioning and some settings for the error norm and error estimation.

Use the list to select an iterative linear system solver. Select:

•

to use the active preconditioner attached to this node as the linear system solver. This solver uses the settings for and from the section of the corresponding node.

If or is selected, specify the that the solver performs until it restarts (the default is 50). There is no guarantee that a restarted GMRES converges for a small restart value. A larger restart value increases the robustness of the interactive procedure, but it also increases memory use and computational time. For large problems, the computational cost to produce a preconditioner of such quality that the termination criteria are fulfilled for a small number of iterations and for a small restart value is often large. For those problems, it is often advantageous to set up a preconditioner with a somewhat lesser quality and instead increase the restart value or iterate more steps. Doing so typically increases the condition number for the preconditioned system, so an increase in the error-estimate factor might be needed as well.

If any other linear system solver than is selected, specify whether you are the linear system matrix from the or . Normally, this setting does not significantly influence the convergence behavior of the selected solver. The default choice is left preconditioning. Normally, for GMRES, the two versions of GMRES have similar convergence behavior (see Ref. 17). If the preconditioner is ill-conditioned, there could, however, be differences in the behavior. For the conjugate gradient method, this choice only affects the convergence criterion and not the algorithm itself.

If you use left preconditioning, a residual tolerance is available in the field (default: 0.01). You can use this setting to obtain extra accuracy. If you for some reason do not want that extra accuracy, set the relative tolerance to one (1).

If you use preconditioning, select the check box to allow termination of the linear iterative methods using a criterion other than the standard ones (that is, norm checks of the relative preconditioned residual or the relative residual). The nonlinear-based error norm is foremost used for time-dependent studies (enabled per default), where the (initial) residual can be very small for certain time steps and the requirements become too strict. The nonlinear-based error norm normalizes the preconditioned residual with the scales from the solution instead of the initial residual. This method is more reliable when the scales for (size of) the solution have saturated. This is the reason for having a level, which you can specify as a relative error norm value in the field (default: 0.1 for stationary solvers and 1 for time-dependent solvers). For Stationary studies it is not common that the initial residual is small, so this functionality is not enabled per default. Also, if is selected and left preconditioning is used, the check box is available and selected so that the termination of the iterative solver use nonlinear scales. This setting corresponds to the termination behavior in earlier versions.

The stopping criteria for the iterative solvers are based on an error estimate, which checks if the relative residual times a stability constant ρ is less than a tolerance. This tolerance is specified in the field of the operation node to which this attribute belongs. Use the field to set ρ, which serves as a safety factor to avoid premature termination of the iterations due to, for example, ill-conditioning of the matrix A or poor preconditioning (default: 400). A larger value of ρ increases the number of iterations but decreases the chance that the iteration is terminated too early. To avoid false termination, the main solver continues iterating until the error check passes or until the step size is smaller than about 2.2·10−14.

	For information about the convergence criteria used by the iterative solvers, see Convergence Criteria for Linear Solvers

If is selected, the check box is selected by default. GCRO-DR is a method for Krylov subspace recycling. It can be useful while solving sequences of linear systems arising from, for example, nonlinear problems. The idea behind the GCRO-DR method is to retain the subspace determined while solving previous systems and use it to reduce the cost of solving the next system. This method reuses and improves the basis when GMRES is restarting. However, because the GCRO-DR method stores left and right vectors for the Krylov space (similar to FGMRES), the memory requirements are about twice as high for the iteration data stored by the GCRO-DR method compared to GMRES. GCRO-DR is therefore activated only when GMRES reaches its restart length.

When the check box is selected, you can specify the following settings:

•

Use the options in the list to control if the subspace is stored or deleted between iterations. If you choose , the subspace is always deleted. This means that GMRES will be called again in the next nonlinear or parametric iteration. If you choose , the subspace is always stored. By default, the storage is selected, and it means that the subspace is deleted if you get quick convergence, because in that case, GMRES can be expected to converge quickly in the next nonlinear or parametric iteration.

•

In the field, which is available when is set to , you can specify a minimum value for the number of restarts (default: 5). Using this setting can be useful to control when the subspace should be cleared between solver calls in cases when a subspace exists between solver calls — for instance, in a frequency sweep. The GCRO-DR method might then requires more cycles than usual to converge.

•

Select the check box to force the subspace storage whenever GMRES converges in more than k iterations (set in the field). In that case, the size of the stored subspace is equal to the fraction of GMRES iterations controlled by the value (larger than 0, maximum 1) in the field.

Use the field to enter a maximum number of iterations that the iterative solver is allowed to take (default: 10,000 iterations). When this number of iterations has been performed without reaching the specified tolerance, the solver stops with an error message.

The error handling mechanism in the linear iterative solvers is intended to contribute to a general robustness of the computation. For example:

Use the field to manually set the constant ρ. The default is 400. See Convergence Criteria for Linear Solvers for more information.

You can control the accuracy of the solution of the linear system from the list:

•

The default is , meaning that the main solver is responsible for error management. The solver checks for errors for every linear system that is solved. To avoid false termination, the main solver continues iterating until the error check passes or until the step size is smaller than about 2.2·10−14. With this setting, linear solver errors are either added to the error description if the nonlinear solver does not converge, or added as a warning if the errors persist for the converged solution. The nonlinear solver continues when it reaches the maximum number of iterations. Use the field to control the efforts spent in each linear solver call (default: 100 iterations).

•

Choose to check for errors for every linear system that is solved. If an error occurs in the main solver, warnings originating from the error checking in the direct solver appear. The error check asserts that the relative error times a stability constant ρ is sufficiently small. This setting is useful for debugging problems with singular or near singular formulations.