# Pennylane statevector results different from qiskit statevector? issue

**URL:** <https://discuss.pennylane.ai/t/pennylane-statevector-results-different-from-qiskit-statevector-issue/1072>\
**Category:** PennyLane Help\
**Created:** [May 31, 2021, 5:28am UTC](https://discuss.pennylane.ai/t/pennylane-statevector-results-different-from-qiskit-statevector-issue/1072 "2021-05-31T05:28:32Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![josh](https://yyz2.discourse-cdn.com/flex012/user_avatar/discuss.pennylane.ai/josh/32/100_2.png) [@josh](https://discuss.pennylane.ai/u/josh)\
**Post date:** [May 31, 2021, 9:38am UTC](https://discuss.pennylane.ai/t/pennylane-statevector-results-different-from-qiskit-statevector-issue/1072/5 "2021-05-31T09:38:24Z")

</div>

Thanks @Amandeep!

I had a look, and this is to be expected. It is because PennyLane and Qiskit use **different** conventions for the underlying statevector ordering.

For more details, see here:

> [@Probability() usage](http://discuss.pennylane.ai/t/probability-usage/284/12):
>
> Hi @Miguel_Fernandez, as odd as it looks, I believe PennyLane and Qiskit are returning the exact same result. The disagreement results from Qiskit not implementing the same convention as commonly seen in quantum information papers and textbook; typically, the top qubit (labelled 0) in a circuit is the leftmost integer within the ket; |q\_0 q\_1 \cdots q\_{n-1} q\_n\rangle. For example, for a 2-qubit system originally in the ground state |00\rangle, applying an X gate to qubit 0 in this convention…

In this particular case, if you want to get the Qiskit results to match the PennyLane results, you can simply reshape and transpose the statevector:

```python

def f_statevector(theta):
    qc = construct_circuit(theta, 0)
    statevector = backend_statevector.run(qc).result().get_statevector(qc)
    statevector = statevector.reshape([2] * qubits).T.flatten()

```

---

_[View the full topic](https://discuss.pennylane.ai/t/pennylane-statevector-results-different-from-qiskit-statevector-issue/1072)._