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
In iteration 13: Column 167 becomes basic, and column 168 becomes nonbasic
In Iteration 14: Column 168 becomes basic, and column 167 becomes nonbasic
The solution was to Highs::clearSolver, and then Highs::run again.
However, it is also important to state that HIGHS essentially solved the problem as the new solve leads to the same objective and the primal and dual infeasibilities are almost satisfied.
End of backstory
One suggestion that came up in private communications was:
Add some message (possibly combined with some documentation) that encourages the user to look at the maximum primal and dual infeasibility and decide whether they accept the problem as being solved OR re-solve after clearing the solver.
A follow-up question, related to JuMP would be:
Is it easy to query such infeasibilities or should the user query solutions and check themselves?
Backstory:
The following LP solution log came from a sequence of solves of LP's changing the RHS.
A rare event of cycling was spotted:
In iteration 13: Column 167 becomes basic, and column 168 becomes nonbasic
In Iteration 14: Column 168 becomes basic, and column 167 becomes nonbasic
The solution was to
Highs::clearSolver
, and thenHighs::run
again.However, it is also important to state that HIGHS essentially solved the problem as the new solve leads to the same objective and the primal and dual infeasibilities are almost satisfied.
End of backstory
One suggestion that came up in private communications was:
Add some message (possibly combined with some documentation) that encourages the user to look at the maximum primal and dual infeasibility and decide whether they accept the problem as being solved OR re-solve after clearing the solver.
A follow-up question, related to JuMP would be:
Is it easy to query such infeasibilities or should the user query solutions and check themselves?
cc @odow
The text was updated successfully, but these errors were encountered: