DNMY: Add support for vector-valued objective functions #968
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #968 +/- ##
==========================================
+ Coverage 95.17% 95.18% +0.01%
==========================================
Files 86 86
Lines 9205 9205
==========================================
+ Hits 8761 8762 +1
+ Misses 444 443 -1
Continue to review full report at Codecov.
|
|
Closing as stale. We can revisit this when it's time to make a push for proper multi-objective support. |
odow
added a commit
that referenced
this pull request
Jan 6, 2023
This is a re-hash of #968 The last PR lost steam because of the discussion in jump-dev/JuMP.jl#2099 My sense is that this is still the right API approach at the MOI-level, but that it's the wrong approach at the JuMP level. I'm working on a PR to JuMP, so let's hold off comments until things are working fully and we can discuss the full API, rather than the pros and cons of treating multi-criteria as vector optimization. I have a proof-of-concept solver at https://github.com/odow/MOO.jl and I'll also update Gurobi.jl to support the new API.
odow
added a commit
that referenced
this pull request
Jan 13, 2023
This is a re-hash of #968 The last PR lost steam because of the discussion in jump-dev/JuMP.jl#2099 My sense is that this is still the right API approach at the MOI-level, but that it's the wrong approach at the JuMP level. I'm working on a PR to JuMP, so let's hold off comments until things are working fully and we can discuss the full API, rather than the pros and cons of treating multi-criteria as vector optimization. I have a proof-of-concept solver at https://github.com/odow/MOO.jl and I'll also update Gurobi.jl to support the new API.
odow
added a commit
that referenced
this pull request
Jan 25, 2023
This is a re-hash of #968 The last PR lost steam because of the discussion in jump-dev/JuMP.jl#2099 My sense is that this is still the right API approach at the MOI-level, but that it's the wrong approach at the JuMP level. I'm working on a PR to JuMP, so let's hold off comments until things are working fully and we can discuss the full API, rather than the pros and cons of treating multi-criteria as vector optimization. I have a proof-of-concept solver at https://github.com/odow/MOO.jl and I'll also update Gurobi.jl to support the new API.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a DNMY branch for some work I'm doing with multi-criteria solvers.
See jump-dev/JuMP.jl#2099 for the full story.