[Ipopt-tickets] [Ipopt] #242: High computation time in IPOPT

[Ipopt]

#242: High computation time in IPOPT
----------------------------+------------------------
  Reporter:  rikrdos6       |      Owner:  ipopt-team
      Type:  clarification  |     Status:  new
  Priority:  normal         |  Component:  Ipopt
   Version:  3.11           |   Severity:  normal
Resolution:                 |   Keywords:
----------------------------+------------------------

Comment (by stefan):

 If you set the option {{{print_timing_statistics yes}}}, you should see
 more detailed information on where Ipopt has spend so much time.

 If it is the quasi-newton approximation of the Hessian, then one may want
 to check whether information on nonlinearity of variables is passed
 correctly to Ipopt, that is, whether the {{{TNLP}}} methods
 {{{get_number_of_nonlinear_variable}}} and
 {{{get_list_of_nonlinear_variables}}} (see http://www.coin-
 or.org/Ipopt/documentation/node23.html) are correctly implemented. I don't
 know how this is handled via the Matlab interface, though.

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