-
Notifications
You must be signed in to change notification settings - Fork 53
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
Implement a clean API to decide whether or not to extract solver values #163
Comments
I think I see what it is that you want. However it seems like it will always depend a lot on the specific application whether it is "okay" to get the values from a particular type of non-optimal solution? |
Or is it just this |
It would be a start. Just wanted to start a discussion on whether that's the way it should be handled or if we look at alternative ways that solve the problem in a bit more general fashion. For example, a while back we introduced the property |
Just to be sure: Is it a question of whether it's technically possible to get the values from the solver, or is it a question of whether it's meaningful to do so? If it's the former, I agree that it would make sense to have e.g. a |
@cdiener can probably explain this better than I do. The question is about the latter. We don't always expect it to be a valid solution at that point but looking at the values can still be informative as to why the solver failed. |
@KristianJensen It would be the first (whether it's technically possible). This is to be able to inspect a non-optimal solution. For instance |
Please see the source of this issue in opencobra/cobrapy#714. Basically, we would like a clean way to decide whether or not it is okay to extract primals (and duals).
The text was updated successfully, but these errors were encountered: