Jose Pinilla

I was considering one option flag, e.g. `squeeze_info=False` which would either behave like "list" by default or "squeeze" if `True`. I see now how "drop" would allow compatibility with the...

One reason I didn't originally implement "list" is because I had to decide whether lists are always `len(samplesets)`, e.g filled with `None`, or if they only list values of existing...

`squeeze` may not be the right name since it's not the same behaviour as numpy squeeze, it only lists conflicts... so... "list-conflicts"?

About implementation for performance, if you're doing de-duplication, it's not just about having the pointers to the blobs. From what I understand, you have a pin node in `Sg`, a...

On a simpler point... regardless of moving that feature into C++ or not, I still wonder if it belongs in `_input_parser`. Adding `suspend_chains` modifies the graphs, which makes me think...

This is one detail I missed: > you can have multiple fixed chains that contain a particular qubit, but that qubit will never be used for non-fixed nodes. I'll look...

OK... so, I went on and coded an example of what I'm planning. https://github.com/joseppinilla/minorminer/tree/topo **Idea:** Create a new "flavour" of minorminer, where you provide `source_layout` and `target_layout` and that info...

Nice!! I'm very glad this is taking part of the development from your part. I like your proposal. If anything, I hope my input serves as one of the approaches...

I think this and #90 are non-issues. I found these while trying to do something similar, i.e. create a chimera graph by adding custom nodes and edges. But I don't...

The way I would do it right now is: ``` node_list = [0, 1, 4, 5, 6, 7] edge_list = [(0, 4), (0, 5), (0, 6), (0, 7), (1, 4)]...