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

Order of solutions #1372

Closed
blegat opened this issue May 25, 2021 · 1 comment · Fixed by #1375
Closed

Order of solutions #1372

blegat opened this issue May 25, 2021 · 1 comment · Fixed by #1375
Labels
Type: Documentation This issue requires changes to the documentation
Milestone

Comments

@blegat
Copy link
Member

blegat commented May 25, 2021

When the termination status is OPTIMAL, do the solver need to guarantee that the optimal solution is the first one ?
If this is the case, then this is a bug: jump-dev/MosekTools.jl#66
In fact, we kind of assume it the tests already since we only ever test with the first solution.
Is this in the documentation somewhere ?
I remember we discussed about that, see e.g. jump-dev/JuMP.jl#2512 (comment)

@blegat blegat added the Type: Documentation This issue requires changes to the documentation label May 25, 2021
@odow
Copy link
Member

odow commented May 25, 2021

When the termination status is OPTIMAL, do the solver need to guarantee that the optimal solution is the first one ?

Yes. If this is not documented, it should be. It's the only reasonable thing to do.

@odow odow added this to the v0.10 milestone May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Documentation This issue requires changes to the documentation
Development

Successfully merging a pull request may close this issue.

2 participants