[Ipopt] mumps out of memory
Saqib Ilyas
msaqib at gmail.com
Tue Jul 20 14:13:18 EDT 2010
Hi all
I download the Windows binary for IpOpt. I didn't have enough time to
compile from source or to download and compile not-included solvers. I have
an AMPL model that, when I try to solve with IpOpt, it gives the following
error. Any clues what is going on? I have 2 GB RAM on a Windows XP machine.
I tried to fiddle with the alleged "mump_mem_percent option" but ipopt came
back to me saying that was not a recognized option. Error dump follows:
******************************************************************************
This program contains Ipopt, a library for large-scale nonlinear
optimization.
Ipopt is released as open source code under the Common Public License
(CPL).
For more information visit http://projects.coin-or.org/Ipopt
******************************************************************************
NOTE: You are using Ipopt by default with the MUMPS linear solver.
Other linear solvers might be more efficient (see Ipopt
documentation).
This is Ipopt version 3.8.0, running with linear solver mumps.
Number of nonzeros in equality constraint Jacobian...: 0
Number of nonzeros in inequality constraint Jacobian.: 30888
Number of nonzeros in Lagrangian Hessian.............: 617760
MUMPS returned INFO(1) =-13 - out or memory.
In some cases it helps to decrease the value of the option
"mumps_mem_percent".
Total number of variables............................: 32175
variables with only lower bounds: 0
variables with lower and upper bounds: 32175
variables with only upper bounds: 0
Total number of equality constraints.................: 0
Total number of inequality constraints...............: 936
inequality constraints with only lower bounds: 0
inequality constraints with lower and upper bounds: 0
inequality constraints with only upper bounds: 936
iter objective inf_pr inf_du lg(mu) ||d|| lg(rg) alpha_du
alpha_pr ls
0 2.7042410e+002 0.00e+000 1.46e+001 -1.0 0.00e+000 - 0.00e+000
0.00e+00
0 0
MUMPS returned INFO(1) =-13 - out or memory.
In some cases it helps to decrease the value of the option
"mumps_mem_percent".
WARNING: Problem in step computation; switching to emergency mode.
Restoration phase is called at point that is almost feasible,
with constraint violation 0.000000e+000. Abort.
Number of Iterations....: 0
(scaled) (unscaled)
Objective...............: 2.7042410056253124e+002 2.7042410056253124e+002
Dual infeasibility......: 1.4603015700000002e+001 1.4603015700000002e+001
Constraint violation....: 0.0000000000000000e+000 0.0000000000000000e+000
Complementarity.........: 9.9000001999999998e-001 9.9000001999999998e-001
Overall NLP error.......: 1.4603015700000002e+001 1.4603015700000002e+001
Number of objective function evaluations = 1
Number of objective gradient evaluations = 1
Number of equality constraint evaluations = 0
Number of inequality constraint evaluations = 1
Number of equality constraint Jacobian evaluations = 0
Number of inequality constraint Jacobian evaluations = 1
Number of Lagrangian Hessian evaluations = 1
Total CPU secs in IPOPT (w/o function evaluations) = 0.828
Total CPU secs in NLP function evaluations = 0.172
EXIT: Restoration Failed!
Ipopt 3.8.0: Restoration Phase Failed.
suffix ipopt_zU_out OUT;
suffix ipopt_zL_out OUT;
ampl:
--
Muhammad Saqib Ilyas
PhD Student, Computer Science and Engineering
Lahore University of Management Sciences
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.coin-or.org/pipermail/ipopt/attachments/20100720/b0fc95c5/attachment.html
More information about the Ipopt
mailing list