-
Notifications
You must be signed in to change notification settings - Fork 2
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
Use this package more generally? #7
Comments
Hi @dourouc05 Sorry, I have been quite busy, so I will try an extensive answer later. The answer is yes on principle, even though I would need to check the exact implications (for instance are the involved packages all registered etc). We have a Constraint Programming stream on julia's Zulip btw. Talk to you soon (we can schedule an online meeting to make things smoother too). |
Hi @dourouc05 |
@Azzaare Regarding dependencies, this package only depends on MOI, and it is also registered. (Unlike CPLEXCP, a wrapper for CPLEX CP Optimizer, which has heavier dependencies…) Thanks for pointing at Zulip, I didn't know it existed! (And I now subscribed, of course!) For meeting, we could have a BoF or equivalent at JuliaCon or the next JuMP workshop? @Wikunia MOI forces you to implement |
Thanks @dourouc05 If it registered I am fine with it. We were considering BoF, but we have little time left to submit ... I will try to have a better look at BoF submissions. It should not be too complicated. As for the dimension related thing, there is a workaround that was given to me on JuMP-dev (@odow I think), which allows us to skip the dimension in JuMP syntax (but not in MOI). For my solver, providing the dimension is just extra noise. What about making the dimension optional? |
At the MOI level, you should explicitly state the dimension. We can make nicer syntax at the JuMP level |
Hi there! Also, there is a new kid in town with https://github.com/corail-research/SeaPearl.jl It seems we have some critical mass. Should we try to have some meeting? |
This package started with jump-dev/JuMP.jl#2227. Its goal is to be the official extension to MOI for constraint programming. It is now in a useable state, and allows to wrap most of the CPLEX CP Optimizer solver: it should be relatively stable, except for new features (unlike the first versions, which broke compatibility every now and then).
In the Julia ecosystem, there are two other packages for constraint programming, but they focus on solving problems: https://github.com/Wikunia/ConstraintSolver.jl and https://github.com/JuliaConstraints. For now, these packages have different MOI sets to represent the same constraints. The goal of the present package is to provide these MOI sets, so that users can easily switch from one solver to another (and to ease writing new solvers/wrappers for existing solvers). It may be integrated into MOI in the future.
I mapped the constraints supported in each package to those in CP: ConstraintSolver.jl and JuliaConstraints.
@Wikunia @Azzaare Is there anything missing in this package? Would you have designed things differently? Would you be ready to use this package as a dependency for your own solvers (instead of your custom sets), until it migrates into MOI?
The text was updated successfully, but these errors were encountered: