Add function in interfaces to get the solver's method#426
Closed
cvanaret wants to merge 4 commits into
Closed
Conversation
amontoison
force-pushed
the
main
branch
5 times, most recently
from
5a5ca03 to
21482ad
Compare
Owner
Author
|
Superseded by #719 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a function
uno_get_solver_method()in C/Fortran/Python interfaces for the user to check which method is used by the solver, based on the strategy combination.This is especially useful because some special cases in the ingredient instantiation exist (e.g., if unconstrained, Uno automatically picks merit function + no relaxation).
Fixes #421