Implement callback support for Xpress#5231
Open
djunglas wants to merge 1 commit into
Open
Conversation
We implement full support for the callback in Xpress. The Xpress implementation supports all events and all features of the ortools callbacks. We also added a "solution source" attribute to the callback data in case of the MIP_SOLUTION event because we think this can be useful. In general the Xpress callback is much richer than what the ortools callback offers but we did not want to add too many things that could be Xpress-specific and might not be available with other solvers. Co-authored-by: Francesco Cavaliere <francescocavaliere@fico.com>
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
2 participants
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.
We implement full support for the callback in Xpress. The Xpress implementation supports all events and all features of the ortools callbacks. We also added a "solution source" attribute to the callback data in case of the MIP_SOLUTION event because we think this can be useful. In general the Xpress callback is much richer than what the ortools callback offers but we did not want to add too many things that could be Xpress-specific and might not be available with other solvers.