Jessie Yu
Jessie Yu
> The `Estimator` doesn't actually provide a unified interface. If all someone wanted was expectation values then yes. But what if I want to compute expectation values and also plot...
My point was can't we improve qiskit-terra's implementation of `Estimator` to be the "simple, uniform interface" that we want? Qiskit is about more than Runtime, but the primitive interfaces live...
@rathishcholarajan Are you going to do one final release for all the new code currently in `master` before deprecating this?
Thanks!
Putting on hold label back on. Like Matthew said we shouldn't deprecate this until there is a replacement.
Yeah we talked about using `id` and `len(data)`, but this is much better. I agree with removing `id`. In fact do we even have a use case for specifying `functional=False`?
> I made a PoC to add `seed_simulator` option to`run` method and constructor. @t-imamichi We had said in the options RFC that we didn't want to pass options to `run()`...
@t-imamichi thanks for the update! I'd prefer having `default_precision` in `options` as well, since unlike `precision`, `default_precision` is not defined in the base interface. I think it's nicer to have...
> > I have a question. I used dataclass to define Options instead of using qiskit.providers.Options to allow autocompletion and expect a validation of a wrong option name. If qiskit.providers.Options...
We should check if these examples still fail since it's been a while