You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for the inspector show function to work properly, the import statement must be called before the sampler sample function call, followed by which the inspector show function can be called.
i.e.:
import dwave.inspector
...
sampler.sample(Q)
...
dwave.inspector.show(Q, response)
This is not entirely obvious based on context and current documentation.
The text was updated successfully, but these errors were encountered:
That is not entirely correct, since you do not have to activate the full data capture (done on import) to use show(), but it certainly makes the usage easier.
Data captured includes the problem sent to the QPU (including parameters) and the samples returned. It also captures warnings generated during embedding, and the embedding context (the map, and the chain strength).
To be clear, data capture is encouraged, because going forward it'll include much more data (like nested embeddings #40, but also other problem transformations), so we want to emphasize it our docs.
In order for the inspector show function to work properly, the import statement must be called before the sampler sample function call, followed by which the inspector show function can be called.
i.e.:
import dwave.inspector
...
sampler.sample(Q)
...
dwave.inspector.show(Q, response)
This is not entirely obvious based on context and current documentation.
The text was updated successfully, but these errors were encountered: