Open sammorley-short opened 7 years ago
Let's do it. I believe in your ability to write and submit the patch!
Since measurements need to be ordered, you probably want a list of tuples [(node, pauli), ...]
rather than a dict
. And the GraphState.parity_check
method should probably re-use a generic GraphState.measure_sequence
.
I managed the sequential measurement, but hadn't managed the multi-quint parity yet. Did you do this somewhere? I can't see a resolution to that?
Oh yeah ... please re-open!
On 08/11/16 07:54, SLesslyTall wrote:
I managed the sequential measurement, but hadn't managed the multi-quint parity yet. Did you do this somewhere? I can't see a resolution to that?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/peteshadbolt/abp/issues/13#issuecomment-259175092, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFDqb99NytjZshp0eunAczSy26DucsIks5q8Js-gaJpZM4Kk607.
It would be cool to have the native ability to perform parity measurements on qubits, e.g. make a X_1X_2 parity measurement on a Bell-state.
Program would, e.g. take a dictionary
{node: pauli for node, pauli in parity_check}
and perform the correct parity check.Also, a way to perform a list of single qubit measurements that avoids doing:
for node, pauli in measurements: gs.measure(node, pauli)
but instead e.g. takes a dictionary of{node: pauli for node, pauli in measurements}
and simply performs them sequentially.