Main

APM.MAX_TIME - APMonitor Option

Main.OptionApmMaxTime History

Hide minor edits - Show changes to output

June 09, 2017, at 12:19 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]], [[Main/OptionApmMaxIter|MAX_ITER]], [[Main/OptionApmMaxMemory|MAX_MEMORY]]
June 01, 2017, at 07:39 PM by 45.56.3.173 -
Added lines 1-11:
(:title APM.MAX_TIME - APMonitor Option:)
(:keywords APM.MAX_TIME, Optimization, Estimation, Option, Configure, Default, Description:)
(:description Maximum run time in seconds:)

%width=50px%Attach:apm.png

 Type: Floating Point, Input
 Default Value: 1.0e20
 Description: Maximum run time in seconds

MAX_TIME is the maximum amount of clock time in seconds that the solver should continue. Solutions forced to terminate early by this constraint do not satisfy the Karush Kuhn Tucker conditions for optimality. Even with this constraint, the application may fail to terminate at the required time because there are limited checks within the solvers. If a solver is stuck in a single major iteration when the time limit is reached, the program will terminate once that major iteration is completed. A supervisory application at the operating system level should generally be used to terminate applications that exceed a maximum desired amount of clock or CPU time.