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
Add the possibility to extract the statevector after a partial measurement of the quantum circuit.
Context:
Qiskit's Aer simulator allows extracting the statevector after measuring a subset of the qubits in the quantum circuit. Since the measurement outcome is random, it will pick one possible outcome of the partial measurement at random and return the resulting statevector after the measurement.
The output DDSIM Statevector will always be $1/\sqrt{2} (|00\rangle + |11\rangle)$. The output Aer Statevector will alternate between $|00\rangle$ and $|11\rangle$ since these are the possible statevectors after the first qubit was measured.
Describe the solution you'd like
Since there is no one and only "correct" way, how the statevector should look like in the above scenario, I'd propose allowing both possbilities s.t. users can chose depending on their application area. So it might be possible to add a flag (maybe at the time of initializiation of the backend) that chooses the behavior.
The text was updated successfully, but these errors were encountered:
One thing that is also not quite clear is how Qiskit chooses which statevector to return: Either by the measurement probability or with equal probability.
What's the problem this feature will solve?
Add the possibility to extract the statevector after a partial measurement of the quantum circuit.
Context:
Qiskit's Aer simulator allows extracting the statevector after measuring a subset of the qubits in the quantum circuit. Since the measurement outcome is random, it will pick one possible outcome of the partial measurement at random and return the resulting statevector after the measurement.
Small example that illustrates this behavior:
The output$1/\sqrt{2} (|00\rangle + |11\rangle)$ . The output $|00\rangle$ and $|11\rangle$ since these are the possible statevectors after the first qubit was measured.
DDSIM Statevector
will always beAer Statevector
will alternate betweenDescribe the solution you'd like
Since there is no one and only "correct" way, how the statevector should look like in the above scenario, I'd propose allowing both possbilities s.t. users can chose depending on their application area. So it might be possible to add a flag (maybe at the time of initializiation of the backend) that chooses the behavior.
The text was updated successfully, but these errors were encountered: