Skip to content

Support MOI.FEASIBILITY_SENSE #80

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.

Sign up for GitHub

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

Jump to bottom
Closed
rschwarz opened this issue Jan 6, 2019 · 2 comments
Closed

Support MOI.FEASIBILITY_SENSE #80

rschwarz opened this issue Jan 6, 2019 · 2 comments

Comments

@rschwarz
Copy link
Collaborator

rschwarz commented Jan 6, 2019

Currently (after merging #76), setting MOI.FEASIBILITY_SENSE is a no-op.
We coud clear the objective coefficients of all variables, but then they could not be recovered when the objective sense is set to maximize or minimize.

To support this properly, we would have to store both the sense and the objective coefficients separately in the MOI wrapper (SCIP.Optimizer).
@rschwarz rschwarz mentioned this issue Jan 6, 2019
Merged
@rschwarz
Copy link
Collaborator Author

Together with this change, we could also support SingleVariable objective functions (and remember that it was this function type?).

@rschwarz rschwarz mentioned this issue Jan 12, 2019
Closed
@rschwarz
Copy link
Collaborator Author

Another related missing feature is the attribute MOI.ObjectiveFunctionType. This is used, e.g., by JuMP to show the model in the REPL, so it currently errors with a direct SCIP.Optimizer.

@matbesancon matbesancon mentioned this issue Apr 29, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rschwarz @matbesancon