REST SAPI, qubit index is shifted (by a predictable amount 🤔) on output vs. input about dwave-cloud-client HOT 5 CLOSED

Hi again, can you help me a bit w/ this? I wouldn't mind reading docs if it's there somewhere,

Thanks.

from dwave-cloud-client.

The rest api documentation is here: https://docs.dwavesys.com/docs/latest/doc_rest_api.html

let us know if you aren't able to find what you're looking for in the docs

from dwave-cloud-client.

Hi Fiona, thanks,

I am not able to find anything that has to do with the "shifting" that I observe between the submitted qubit indexes and the ones I get back in the answer of the problem,

Perhaps I'm missing something about how the solvers work behind the scenes?

from dwave-cloud-client.

My bad everyone,

The lin property on the data object contains the indexes of an enumeration of all the qubits from a solver, not the actual qubit number, for instance (qubit index) 0 -> means -> (actual qubit #) 30 on this particular topology (Advantage_system4.1).

Now that I re-read the docs, this,

One value per working qubit in the same order as solver’s qubits property

makes a lot of sense, but on a first glance I didn't get it. Perhaps it could be reworded in a more explicit way for future readers.

from dwave-cloud-client.

thanks for the suggestion

from dwave-cloud-client.