[Ipopt-tickets] [Ipopt] #286: Using "acceptable_obj_change_tol".

[Ipopt]

#286: Using "acceptable_obj_change_tol".
----------------------------+------------------------
  Reporter:  alexho         |      Owner:  ipopt-team
      Type:  clarification  |     Status:  closed
  Priority:  normal         |  Component:  Ipopt
   Version:  3.12           |   Severity:  normal
Resolution:  fixed          |   Keywords:
----------------------------+------------------------
Changes (by stefan):

 * status:  new => closed
 * type:  defect => clarification
 * resolution:   => fixed


Comment:

 acceptable_obj_change_tol is only one parameter in a whole group that
 steers stopping at an acceptable point. Have a look at parameter
 acceptable_tol and related ones: https://www.coin-
 or.org/Ipopt/documentation/node42.html#SECTION000112070000000000000

 I think next to the obj_change_tol, a number of other criteria on primal
 and dual feasibility need to be satisfied for at least 15
 (=acceptable_iter) iterations to make Ipopt stop.

--
Ticket URL: <https://projects.coin-or.org/Ipopt/ticket/286#comment:1>
Ipopt <http://projects.coin-or.org/Ipopt>
Interior-point optimizer for nonlinear programs.