-
Notifications
You must be signed in to change notification settings - Fork 35
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
Ompr v1 #349
Ompr v1 #349
Conversation
This is a preparation for a new model backend.
Currently named MIPModel2. Still somewhat WIP
Dirk, I am sort of confused. So MIPModel2 is a new branch from MIPModel with MILPModel being set aside? Is there a link with MIPModel2 formulation information and examples available for MIPModel2? Thanks, SteveM |
Well, if everything works, there will be a new |
Thanks for the update. Agree about the problematic vectorized semantics in MILPModel. Ideally, an updated constraint function in MIPModel2 would accommodate sparse formulations, (row, column, value). I am not a developer, but it seems like the dplyr pivot_longer function could pre-process the sparse constraint set in rcv format and that could be passed to MIPModel2. Again, appreciate your efforts. SteveM |
It seems, everything should be backwards compatible. Doing this we can also delete a lot of old code.
It has been fixed by the new MIPModel
Fixed by new MIPModel
@sbmack can you elaborate a bit what you mean exactly? Ideally post that in the Ideas category of the discussions. Appreciate your input! |
Especially important for larger models with lots of variable instances.
First draft.
Thanks for the reply. Idea posted in the Ideas category of the Discussions section. SteveM |
Towards a new
MIPModel
. It is currently namedMIPModel2
.