-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add constraint to Model<Solved> #118
Comments
@mmghannam Thanks for the clarification. Would it be possible to implement that in my own code using traits, like described in the readme? If it works I could create a fork and open a PR to add that |
That would be great @egaban, feel free to ask here or email me if you have any questions. Good luck, looking forward to your PR! |
I think I was complicating it too much, an easier way would be to add access to the SCIP This sounds like a more tangible goal, @egaban are you still interested in working on this? |
Hi @mmghannam! I apologize for not having enough time to work on that earlier, but I'm still interested in contributing. The alternative approach you suggested sounds easier to implement, though the Constraint Handlers might be a more robust solution. Maybe we can do the I've started learning about Rust FFI, but the main challenge for the Constraint Handlers now is figuring out how to do that in SCIP's C interface (I've never done that in C before), and in a generic way (unknown ConsData type). I estimate that I'll be ready to start working on this in about a month, if that's ok. |
No apologies needed! I'm happy to hear you're still interested. Let me know if I you need any help :) |
That's great! Thanks for the update |
I couldn't find in the documentation if there's a safe way to add a constraint after the model was solved
This could be useful for solving a TSP with lazy constraint generation, for instance
The text was updated successfully, but these errors were encountered: