Jessie Yu
Jessie Yu
> The time to transition from "pending - not accepting new jobs" to closed is what changes in the new API, which takes longer time to move to the close...
> [@jyu00](https://github.com/jyu00) something has change drastically in the estimator option configuration since the writing of the tutorial on [krylov-quantum-diagonalization](https://quantum.cloud.ibm.com/docs/en/tutorials/krylov-quantum-diagonalization). using the experimental path makes the tutorial work in the intended...
I think we should just deprecate passing a string for `backend`. Today you can do `Session(backend="ibm_osaka")`, which would actually call `QiskitRuntimeService()` (i.e. use your default account setting) under the cover....
> running in local simulation mode with mitigation turned on silently ignores these options. It [should](https://github.com/Qiskit/qiskit-ibm-runtime/blob/1f6922c7fd21f2f9f4a14e9953d7d5e4809fe48e/qiskit_ibm_runtime/fake_provider/local_service.py#L242-L243) already raise a warning if an unsupported option is used.
@InnocenzoFulginiti can you elaborate more on which timing information you are looking for? For example, if you have a circuit ``` if (c[0] == 0) { x $0; } else...
> > We want fake backends to undergo ISA checks, but not simulators. > > Why not? The simulators have a set of basis gates as well that must be...
The field after `pub_result.data` is the name of the classical register used. In the [code example](https://docs.quantum.ibm.com/guides/get-started-with-primitives#2-create-a-circuit) above, it uses `circuit.measure_all()`, which by default name the classical register `meas`. Now it's...
@srdtrk the names of the classical registers depend on how you construct your circuit (in this case, your `qcEx1`). For example, if I do ```python from qiskit import QuantumCircuit qc...
The section on `Multiple circuits in the same job` is incorrect. If you submit a large job, it may get divided into smaller jobs and thus interleave with cal jobs....