dwave-hybrid icon indicating copy to clipboard operation
dwave-hybrid copied to clipboard

Hybrid Asynchronous Decomposition Sampler prototype framework.

Results 29 dwave-hybrid issues
Sort by recently updated
recently updated
newest added

1. Is it possible to execute a qubo problem execution with hybrid solver on CPU only? 2. Is it possible to divide large problem into small sub problems and execute...

I have a problem with an unembeddable number of variables. I can obtain a solution with SimulatedAnnealingSampler and I would like to start from that final state and execute reverse...

Currently, `SampleSet.info['timing']` as returned by the QPU sampler is discarded by our QPU hybrid samplers (like `QPUSubproblemAutoEmbeddingSampler` and others). It would be useful to expose/store this info in hybrid sampler's...

feature
good first issue

Currently, `max_subproblem_size=50` for Kerberos samplers. Why not let it default to double that size for Advantage QPUs?

Compared to the BQM solver in HSS, ParallelTempering is very slow. I've attached a Python program for observing this, including a DQM from Accenture. ``` import hybrid from dimod import...

Initially, `hybrid.Lambda` was made to bind `hybrid.Lambda` instance as `self` in `next`/`error`/`init` calls. That allowed runnable implementations via `hybrid.Lambda` to have access to a persistent state (like any other runnable...

feature
breaks compatibility

`Map` can easily be generalized to support non-bijective mapping, at least in surjective sense (dropping some outputs). The same can be achieved with `map | filter` flow, but sometimes non-emitting...

feature

One option is to add general conditional execution (i.e. an `If` block), but then to support probabilistic execution we need to have uniform sampler, threshold condition, if block, etc. Proposal:...

feature

After #201 and #202 are implemented, add a version of `Map` that executes each mapping operation (or each branch here) with a certain probability. Implementing this as `map | filter`...

feature

While other composing runnables take children runnables as positional arguments (children-accepting: `Branches`, `Parallel`, `Race`; child-accepting: `Loop`, `Map`, `Unwind`), `Branch` takes its children in a single argument, `components`. Although there are...

breaks compatibility