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
During one of the demos (king face-off in game 1 of quantum chess quarter finals), a bad qubit caused an embarrassing situation. It would be good if we could have some sanity checking before important demos to check qubits and adjust the device to remove bad/misbehaving qubits.
Currently, the device proto files need to be specified (contact dstrain115 or cantwellc for an example) so the qubits have to manually pruned from the file. It would be good if we could easily remove them in a better way.
During one of the demos (king face-off in game 1 of quantum chess quarter finals), a bad qubit caused an embarrassing situation. It would be good if we could have some sanity checking before important demos to check qubits and adjust the device to remove bad/misbehaving qubits.
Currently, the device proto files need to be specified (contact dstrain115 or cantwellc for an example) so the qubits have to manually pruned from the file. It would be good if we could easily remove them in a better way.
Also, the existing sanity check just does a simultaneous readout of all qubits. It might be better to run an actual quantum chess circuit as well. See existing readout tester here:
https://github.com/quantumlib/ReCirq/blob/master/recirq/quantum_chess/readout_tester.py
The text was updated successfully, but these errors were encountered: