Alexander Condello

Hi @scorpioares, thanks for the report! Would it be possible to share the CQM that you submitting? You can save it by running ```python import shutil with cqm.to_file() as src_f:...

Agree that inheriting may make sense, but be careful if you do - it's important that you not accidental require a connection to SAPI.

Could even use the existing one https://github.com/dwavesystems/dwave-system/blob/d043ddc834f99e7c5f3f5b82f1836a08ed3de2db/dwave/embedding/exceptions.py#L18

I know that @randomir has been suggesting a `dwave.common` package or similar. Unfortunately, there is no nice way to populate a namespace from multiple packages (or at least none that...

The `EmbeddingComposite` and the `DWaveSampler` only accept BQMs, not CQMs or DQMs. If you want to solve CQMs you should use the `LeapHybridCQMSampler`. We should probably raise a better error...

Should be closed by https://github.com/dwavesystems/dwave-system/pull/317 in the sense that it should only pick up QPUs.

How about ``` sampler = DWaveSampler() tiles = find_tiles(sampler.structure, 2, 2, 4) bqm = dimod.BQM.empty('SPIN') for tile in tiles: bqm.update(dimod.ran_r(1, tile)) sampleset = sampler.sample(bqm) ``` if we exposed the `find_tiles`...

Yes, though it finds the regions in a pretty naive/greedy way so it can miss a lot of realestate.

I think this is because the way we find the tiles is not deterministic. I assume that for a single instantiated tiling composite sampler the order will be consistent. Anyway,...

I took a closer look and realized that I am not sure what the expected behaviour is. The method to find the tiles is deterministic ([link](https://github.com/dwavesystems/dwave-system/blob/2fe8941831ca2bd9e94b338d38960ec8003627bc/dwave/system/composites/tiling.py#L167)). And it uses `dimod.concatenate`...