-
Notifications
You must be signed in to change notification settings - Fork 21
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
Feature 70/use min gap as a constraint in penaltymodels #74
Feature 70/use min gap as a constraint in penaltymodels #74
Conversation
…parameter follow bias parameters
…st with no auxiliary for MaxGap.
…feasible with this constraint, it becomes unneccessary to search the remaining gap range
…r-specified ground states from non-zero to zero as MaxGap at the moment only handles ground states of zero
New Features ------------------- * Add min_classical_gap as a parameter in Specification. This will support min_classical_gap in the penalty models.
…nalty models to access an updated Specification object that includes min_classical_gap as a parameter
I think this might technically be backwards compatibility breaking. Because the default min-gap is 2 so models that could previously be constructed can no longer be. |
New Features ------------------ * Support a default minimum classical gap of 2 in penaltymodels
New Features ------------------ * Support a default minimum classical gap of 2
New Features ------------------ * Support a default minimum classical gap of 2
…ed up the version requirements for mip and maxgap; although this version penaltymodel_core could support the older version of mip and maxgap, the optional parameter min_classical_gap in core's specification class will be sit uselessly as it gets passed to the older mip and maxgap. This would be an unexpected behaviour, hence the version bumping.
Note changes made since last approval:
|
This is currently being blocked because there is some confusion between |
…old aspect of min_classical_gap
The |
Closes #70.