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
We got some user feedback that essentially points to the fact that the architecture for storing PubResults inside of PrimitiveResults and trying to access specific data isn't very intuitive. One suggestion for how we could make this more clear is that we could add a diagram showing how the properties are connected to each other on the primitive input/output page: https://docs.quantum.ibm.com/guides/primitive-input-output#sampler-output.
@kaelynj suggests something like this, but other options can be explored by whoever picks this ticket up:
└── PrimitiveResult/
├── PubResult[0]/
│ ├── metadata
│ └── data/
│ ├── NAME_OF_REGISTER/
│ │ └── BitArray of count data
│ └── NAME_OF_ANOTHER_REGISTER/
│ └── BitArray of count data
└── PubResult[1]/
├── metadata
└── data/
└── NAME_OF_REGISTER/
└── BitArray of count data for second pub
The text was updated successfully, but these errors were encountered:
Closes#2650
The improvements made by #2612 I think will also help a lot with the
feedback we've been getting about confusion around the `PrimitiveResult`
data structure.
---------
Co-authored-by: abbycross <[email protected]>
We got some user feedback that essentially points to the fact that the architecture for storing PubResults inside of PrimitiveResults and trying to access specific data isn't very intuitive. One suggestion for how we could make this more clear is that we could add a diagram showing how the properties are connected to each other on the primitive input/output page: https://docs.quantum.ibm.com/guides/primitive-input-output#sampler-output.
@kaelynj suggests something like this, but other options can be explored by whoever picks this ticket up:
The text was updated successfully, but these errors were encountered: