Alexander Condello
Alexander Condello
It would be useful to have mock solvers for the QPU and the leap hybrid samplers for use in testing. See Also: https://github.com/dwavesystems/dwave-cloud-client/issues/22 https://github.com/dwavesystems/dwave-system/issues/283#issuecomment-607360274
https://bugs.python.org/issue18303 We should consider putting some logic in to handle this case.
To match the DQM https://github.com/dwavesystems/dimod/blob/5d2043d0b662f38bd51e062367c2e4b703b457a1/dimod/discrete/discrete_quadratic_model.py#L767
Either checking the bounds in `CQM.check_feasible()` and/or adding an explicit `.check_bounds()`. See also: https://github.com/dwavesystems/dimod/issues/954
Consider making BQM.num_variables, BQM.num_interactions and BQM.shape methods rather than properties
Currently, `BQM.num_variables`, `BQM.num_interactions` and `BQM.shape` are all properties rather than methods. I think that it would be better to make them proper methods. Pro: * Determining `num_interactions` is an `O(num_variables)`...
Currently we have two patterns for Cython classes and it would be nice to be more consistent #### Subclass pattern Have a Cython class as a superclass of the Python...
See also https://github.com/dwavesystems/dimod/issues/1030