You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Behavior
The NLP PIPS-NLP solver does not converge for some extreme-scale problems (thousands+ scenarios and million+ variables/constraints). The manifestation of this issue includes any of the following:
PIPS-NLP returns with message "Problem may be locally infeasible. Feasibility Restoration Phase is needed [...]"
a large number of iterations (>100) without much decrease in "Inf_pr", "Inf_du", "Comp", "lg(mu)" convergence metrics
Cause
This issue almost always occurs when the problem is numerically ill-posed in some sense, either the constraint Jacobian is rank-deficient or the problem is badly scaled.
While PIPS-NLP has mathematical mechanisms to cope with these, namely primal and dual regularization strategies, a couple of things can go wrong. Very often the inertia needed for these regularizations is not accurate because the diagonal KKT blocks of the problems are severely ill-conditioned or even singular and the linear solvers used by PIPS-NLP under the hood return incorrect inertias for these blocks. We stress that this is caused by the ill-conditioning of the problem and the linear solvers are fine. In other cases, these linear solvers do not detect rank deficiency and solve singular linear systems, which result in "garbage" search directions inside PIPS (you will see "AugSysErr" > 1e-4 in PIPS-NLP's output and/or very large ||d||).
Fix
The ultimate fix is to improve the numerical formulation of the problem by ensuring full-rank Jacobians and/or good scaling of the problem. When this is not possible, we recommend a couple of workarounds/possible fixes using PIPS-NLP.
Fine tuning PIPS-NLP
Here are a couple of potential PIPS-based fixes for the issue.
Switch between MA27 and MA57 (options 'SymLinearSolver 0' and 'SymLinearSolver 1', respectively)
Use 'DoIR_Aug 1' option (iterative refinement for the augmented linear system) and also do 1.
Use 'DoIR_Full 1' option (iterative refinement for the entire linearized KKT system) and also do 1.
Provide a good initial (primal) starting point, for example by solving the problem with a small number of scenarios and "port" the solution to the problematic problem that has a larger number of scenarios. This strategy proved to be quite robust for SC-ACOPF problems.
Use inertia-free regularization approaches: options 'dWd_test 1' or 'dWd_test 2'. These regularization strategies are not as robust as the inertia-based regularization, but you're running out of options if you reached this step.
Relevant information about what's going on internally in PIPS during the numerical solve can be obtained by running with option 'prtLvl 2'.
These options should be provided in the pipsnlp.parameter file (place this in the directory you're running PIPS or StructJuMP).
Still does not work?
Submit an issue describing your experience and attach the PIPS-NLP's output obtained by running with option 'prtLvl 3' + the necessary files we need to run your problem.
The text was updated successfully, but these errors were encountered:
Behavior
The NLP PIPS-NLP solver does not converge for some extreme-scale problems (thousands+ scenarios and million+ variables/constraints). The manifestation of this issue includes any of the following:
Cause
This issue almost always occurs when the problem is numerically ill-posed in some sense, either the constraint Jacobian is rank-deficient or the problem is badly scaled.
While PIPS-NLP has mathematical mechanisms to cope with these, namely primal and dual regularization strategies, a couple of things can go wrong. Very often the inertia needed for these regularizations is not accurate because the diagonal KKT blocks of the problems are severely ill-conditioned or even singular and the linear solvers used by PIPS-NLP under the hood return incorrect inertias for these blocks. We stress that this is caused by the ill-conditioning of the problem and the linear solvers are fine. In other cases, these linear solvers do not detect rank deficiency and solve singular linear systems, which result in "garbage" search directions inside PIPS (you will see "AugSysErr" > 1e-4 in PIPS-NLP's output and/or very large ||d||).
Fix
The ultimate fix is to improve the numerical formulation of the problem by ensuring full-rank Jacobians and/or good scaling of the problem. When this is not possible, we recommend a couple of workarounds/possible fixes using PIPS-NLP.
Fine tuning PIPS-NLP
Here are a couple of potential PIPS-based fixes for the issue.
Relevant information about what's going on internally in PIPS during the numerical solve can be obtained by running with option 'prtLvl 2'.
These options should be provided in the pipsnlp.parameter file (place this in the directory you're running PIPS or StructJuMP).
Still does not work?
Submit an issue describing your experience and attach the PIPS-NLP's output obtained by running with option 'prtLvl 3' + the necessary files we need to run your problem.
The text was updated successfully, but these errors were encountered: