Skip to content
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

Conversation

m3ller
Copy link
Contributor

@m3ller m3ller commented Jan 7, 2019

Closes #70.

  • Made changes so that min classical gap can now be added as a direct constraint in each penalty model (MIP, MaxGap, LP)
  • Add corresponding unit tests to verify that the min classical gap parameter works

m3ller added 25 commits January 3, 2019 14:00
…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
@arcondello arcondello self-requested a review January 8, 2019 16:02
@arcondello arcondello self-assigned this Jan 8, 2019
@arcondello
Copy link
Member

arcondello commented Jan 8, 2019

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.

m3ller added 11 commits January 9, 2019 11:28
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.
@m3ller
Copy link
Contributor Author

m3ller commented Jan 10, 2019

Note changes made since last approval:

  • Made code changes to penaltymodel-cache
  • Bumped up version numbers

@m3ller m3ller changed the title Feature 70/use min gap as a constraint in penaltymodels WIP: Feature 70/use min gap as a constraint in penaltymodels Jan 10, 2019
@m3ller
Copy link
Contributor Author

m3ller commented Jan 14, 2019

This is currently being blocked because there is some confusion between classical_gap and min_classical_gap.

@m3ller m3ller changed the title WIP: Feature 70/use min gap as a constraint in penaltymodels Feature 70/use min gap as a constraint in penaltymodels Jan 15, 2019
@m3ller
Copy link
Contributor Author

m3ller commented Jan 15, 2019

The min_classical_gap and classical_gap issue will be taken care of by the refactoring issue #78

@m3ller m3ller merged commit b34b781 into dwavesystems:master Jan 16, 2019
@m3ller m3ller deleted the feature-70/use-min-gap-as-a-constraint-in-penaltymodels branch January 16, 2019 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants