17.01.2015 Views

GPS-X Technical Reference

GPS-X Technical Reference

GPS-X Technical Reference

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Miscellaneous 424<br />

STEADY-STATE SOLVER<br />

The steady-state solver used in <strong>GPS</strong>-X is a robust routine based on a direct search algorithm (that<br />

is, no gradients are used). Sometimes, the steady-state convergence appears slow or diverges due<br />

to a problem in the way that the model is set up. For example, if the underflow rate from a settler<br />

is too low, that settler will begin to fill up with solids. Since the concentration ranges of solids in<br />

the ten layers become large, the changes in these layers between loops of the steady-state solver<br />

also become large which may cause slow convergence or divergence.<br />

In all cases of poor convergence, the user should closely examine all the unit processes for proper<br />

specification. The easiest way to do this is to examine the dsum# variable associated with each<br />

unit process where # represents the overflow stream label. You can do this by issuing the display<br />

command in the Command line of the Simulation Control window. The sum of the individual<br />

dsum values equals the dsum value displayed in the Log window. Having done that, there are a<br />

number of parameters associated with the steady-state solver that can be fine-tuned.<br />

The forms shown in Figure 15-9 and Figure 15-10 are accessed by selecting<br />

General Data > System > Parameters > Steady-State. The parameters in these forms are<br />

described below.<br />

The first menu item, number of retries on iteration indicates the number of times the steadystate<br />

solver will try to reach convergence if it fails.<br />

The error limit on individual variables is a tolerance below which the steady-state ignores a<br />

variable. If the steady-state solver is making changes to a state variable that become smaller than<br />

this tolerance, the solver will ignore the variable, assuming it is at steady-state.<br />

When the solver achieves a sum of state variable derivatives below the iteration termination<br />

criteria, a steady-state convergence is triggered. The default value is 10.0, but in some systems it<br />

may need to be increased when in single precision.<br />

The contract constant and expand constant refer to the step size made by the steady-state solver<br />

between iterations. A larger step is taken if an improvement is found, while a smaller step is taken<br />

if no improvement is found. The performance of the steady-state solver can be greatly affected by<br />

these parameters. The expansion factor is limited to the maximum step size in one iteration.<br />

This maximum step size is dampened as the steady-state solution is reached. The damping factor<br />

on final approach will control the damping effect. A zero value means no damping; while a<br />

value of 1.0 means that the maximum step size is limited to one tenth of the maximum step size.<br />

The initial step size that the steady-state solver takes is governed by the initial perturbation<br />

parameter. This number is normally set smaller than the maximum step size to prevent a poor<br />

initial guess by the solver.<br />

<strong>GPS</strong>-X <strong>Technical</strong> <strong>Reference</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!