eldo_user

Optimization
Final Diagnostic Conditions
• MONIT_VAL=ERRMAX or MONIT_VAL=ERRMIN, the printed value will be:
The maximal constraint violation Max k {v
(k)
l + v (k) u } or the minimal constraint violation
Min k {v
(k)
l + v (k) u }.
Related Topics
Monitoring Goal Value Objectives
Monitoring Minimize and Maximize Objectives
Optimization Methods
Final Diagnostic Conditions
When the optimizer has finished, a status code is printed in the optimization results. It is
essential to check the value of this code (and its associated message) and the effective results of
optimization (design variables and objectives).
The final diagnostics indicate the final status of the optimizer before it exits. These messages
and their meaning are described in Table 13-3:
Table 13-3. Optimization Result Status Code
Code Message and meaning
0 The optimization seems to be successful. The required accuracy has been achieved.
The iterates have converged to a point that satisfies the optimality conditions to
the accuracy requested by the optional parameters TOL_OPT or TOL_GRAD and
TOL_FEAS (refer to “Optimization Methods” on page 622). The user should
verify whether the following two conditions have been satisfied:
• The final values of Optimality are significantly small.
• The final values of Feasibility are significantly small. This is set to zero if there
are no equality or inequality constraints.
1 Optimization was not successful. The maximum number of simulation runs has
been reached.
The limiting number of iterations, determined by the optional parameter
MAX_ITER has been reached.
Check the iteration log contained in the .otm file. If the optimizer appears to be
making progress, MAX_ITER may be too small. If so, increase its value and rerun
the optimizer, possibly using the values of the design variables obtained so far (this
can be considered as a warm start).
656
Eldo® User's Manual, 15.3