Skip to content

Separate Specification from PenaltyModel Class #78

Description

@m3ller

Current Problem
Currently, the Specification class is a super class of PenaltyModel. This is a bit confusing as Specification objects get passed to penaltymodel-mip, -maxgap, and -lp in order to generate a PenaltyModel object.

This also leads to issues between classical_gap and min_classical_gap in PR #74. (Most notably that the subclass classical_gap arg gets passed to the super's min_classical_gap).

Proposed Solution
Refactor the code so that PenaltyModel is a subclass of BQM

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions