Main

## Main.OptionApmMaxIter History

June 09, 2017, at 12:18 AM by 10.5.113.159 -
Changed line 13 from:
See also [[Main/OptionApmIterations|ITERATIONS]]
to:
See also [[Main/OptionApmIterations|ITERATIONS]], [[Main/OptionApmMaxMemory|MAX_MEMORY]], [[Main/OptionApmMaxTime|MAX_TIME]]
June 09, 2017, at 12:16 AM by 10.5.113.159 -
Changed lines 5-6 from:
%width=50px%Attach:apm.png
to:
%width=50px%Attach:apm.png [[Main/DbsGlobal|Global Options]] | %width=30px%Attach:fv.png %width=30px%Attach:mv.png %width=30px%Attach:sv.png %width=30px%Attach:cv.png[[Main/DbsVariable|Local Options]]
Added lines 12-13:

See also [[Main/OptionApmIterations|ITERATIONS]]
June 01, 2017, at 07:38 PM by 45.56.3.173 -
Added lines 1-11:
(:title APM.MAX_ITER - APMonitor Option:)
(:keywords APM.MAX_ITER, Optimization, Estimation, Option, Configure, Default, Description:)
(:description Maximum iteration: >=1:)

%width=50px%Attach:apm.png

Type: Integer, Input
Default Value: 100
Description: Maximum iteration: >=1

MAX_ITER is the maximum number of major iterations for solution by the solver. If this number is reached, the result cannot be trusted because the equation convergence or objective minimization does not satisfy the Karush Kuhn Tucker conditions for optimality. Reaching the maximum number of iterations can happen when the problem is large, difficult, highly nonlinear or if the problem is infeasible. Increasing MAX_ITER for infeasible problems will not lead to a feasible solution but can help detect the infeasible conditions.