-
Notifications
You must be signed in to change notification settings - Fork 0
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
[RFC] Feasibility and Optimality checker #1
base: main
Are you sure you want to change the base?
Conversation
This is a significant item for JuMP 1.0, but there is debate on how to define and implement distances for different sets. See https://github.com/matbesancon/MathOptSetDistances.jl for a WIP package exploring the options. This PR also only addresses primal feasibility. See joaquimg/FeasibilityOptInterface.jl#1 for a WIP attempt at dual feasibility as well. In future, the _distance_to_set definitions will be merged into MOI. This PR is more about defining the JuMP-level interface so we can change internal details without breaking compatibility of JuMP 1.0.
This is a significant item for JuMP 1.0, but there is debate on how to define and implement distances for different sets. See https://github.com/matbesancon/MathOptSetDistances.jl for a WIP package exploring the options. This PR also only addresses primal feasibility. See joaquimg/FeasibilityOptInterface.jl#1 for a WIP attempt at dual feasibility as well. In future, the _distance_to_set definitions will be merged into MOI. This PR is more about defining the JuMP-level interface so we can change internal details without breaking compatibility of JuMP 1.0.
Codecov Report
@@ Coverage Diff @@
## main #1 +/- ##
=======================================
Coverage ? 68.23%
=======================================
Files ? 6
Lines ? 277
Branches ? 0
=======================================
Hits ? 189
Misses ? 88
Partials ? 0 Continue to review full report at Codecov.
|
This is a significant item for JuMP 1.0, but there is debate on how to define and implement distances for different sets. See https://github.com/matbesancon/MathOptSetDistances.jl for a WIP package exploring the options. This PR also only addresses primal feasibility. See joaquimg/FeasibilityOptInterface.jl#1 for a WIP attempt at dual feasibility as well. In future, the _distance_to_set definitions will be merged into MOI. This PR is more about defining the JuMP-level interface so we can change internal details without breaking compatibility of JuMP 1.0.
This is a significant item for JuMP 1.0, but there is debate on how to define and implement distances for different sets. See https://github.com/matbesancon/MathOptSetDistances.jl for a WIP package exploring the options. This PR also only addresses primal feasibility. See joaquimg/FeasibilityOptInterface.jl#1 for a WIP attempt at dual feasibility as well. In future, the _distance_to_set definitions will be merged into MOI. This PR is more about defining the JuMP-level interface so we can change internal details without breaking compatibility of JuMP 1.0.
name: TagBot | ||
on: | ||
schedule: | ||
- cron: 0 * * * * | ||
jobs: | ||
TagBot: | ||
runs-on: ubuntu-latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is an update TagBot job
ame: TagBot
on:
issue_comment:
types:
- created
workflow_dispatch:
jobs:
TagBot:
if: github.event_name == 'workflow_dispatch' || github.actor == 'JuliaTagBot'
runs-on: ubuntu-latest
steps:
- uses: JuliaRegistries/TagBot@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
ssh: ${{ secrets.DOCUMENTER_KEY }}
replaces matbesancon/MathOptSetDistances.jl#12
cc @matbesancon