Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check feasibility after a restoration failure? #436

Closed
Robbybp opened this issue Nov 23, 2024 · 1 comment
Closed

Check feasibility after a restoration failure? #436

Robbybp opened this issue Nov 23, 2024 · 1 comment

Comments

@Robbybp
Copy link
Contributor

Robbybp commented Nov 23, 2024

One of my pet peeves with Ipopt is that it returns a Restoration_Failed status code even when it fails at a feasible or almost feasible point. In many applications and algorithms, a feasible solution is fine, and Restoration_Failed makes it seem like something is seriously wrong with the termination point. I encounter this often enough that I'd like to do something about it.

IMO Ipopt should use the Feasible_Point_Found status in these cases (or a similar status for "acceptably feasible"). Barring that, we could handle "(almost) feasible restoration failures" in this interface. My proposal would be to check primal feasibility if we encounter a restoration failure and return MOI.LOCALLY_SOLVED, MOI.ALMOST_LOCALLY_SOLVED, or MOI.LOCALLY_INFEASIBLE as appropriate.

@odow
Copy link
Member

odow commented Nov 24, 2024

Closed by #435

@odow odow closed this as completed Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants