-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade primitive result dataclasses #8100
Comments
Adding variances is a good idea 👍🏻 About renaming |
Yes, I was first considering My main issue with Maybe UPDATE: |
I close this because the discussion is obsolete |
What should we add?
In the context of
EstimatorResult
:values
field, forexpvals
. The former is not only too generic but also misleading (i.e. reminds of key-value pairs), whereas the latter is specific to statistics and directly relatable to quantum mechanics.variances
field, pulling it out of metadata. Since the result that we provide is statistical in nature, variances should have better exposure and be enforced. If calculating exact expectation values using a simulator, individual variances can always be set to zero.EstimatorResult
data structure is not related to numpy in any straightforward way, so returningndarray
seems unwarranted; since that is a mainly operational data type and what we really want here is data exchange, not performing fancy operations like vector addition. Users that need numpy can always cast.metadata
. Lists are mutable, and the dataclass hasfrozen=True
, which seems contradictory. This should also be taken into account in the previous request to remove numpy data types.The text was updated successfully, but these errors were encountered: