Google Quantum, virtually

Want to try a big quantum computer, but don't have the money? Google wants to enhance your simulation game with its "Quantum Virtual Machine" which you can use for free.

At first glance, this sounds like marketing language for another quantum simulator. But if you read the article, it looks like it tries to model the effects of a real Sycamore processor, including qubit decay and phase shift, as well as gate and read errors. This forms what Google calls a "processor-like" output, meaning it's as flawed as a real quantum computer.

If you need more qubits than Google is willing to support, there are ways to add more compute using external compute nodes. Even if you have access to a real machine of sufficient size, it's convenient because you don't have to wait in a queue for time on a machine. You can solve many problems before moving to the real computer.

It could only remind us of the old days when you had to take your cards to the mainframe location and wait your turn only to find out you had made a stupid spelling mistake that cost you an hour. waiting time. At this time, we carefully “verify” a program before submitting it. This system would allow for a similar process where you test your basic logic flow on a virtual machine before incurring the wait time for a real computer to execute it.

Of course, if you really need a quantum computer, the simulation is probably too slow to be practical. But at least it might help you sort out the little issues before you tackle the whole enchilada. What will you do with a quantum computer? Tell us in the comments.

Google, of course, likes its own language, Cirq. If you want to get a head start on general concepts with a user-friendly simulator, try our series.

Google Quantum, virtually

Want to try a big quantum computer, but don't have the money? Google wants to enhance your simulation game with its "Quantum Virtual Machine" which you can use for free.

At first glance, this sounds like marketing language for another quantum simulator. But if you read the article, it looks like it tries to model the effects of a real Sycamore processor, including qubit decay and phase shift, as well as gate and read errors. This forms what Google calls a "processor-like" output, meaning it's as flawed as a real quantum computer.

If you need more qubits than Google is willing to support, there are ways to add more compute using external compute nodes. Even if you have access to a real machine of sufficient size, it's convenient because you don't have to wait in a queue for time on a machine. You can solve many problems before moving to the real computer.

It could only remind us of the old days when you had to take your cards to the mainframe location and wait your turn only to find out you had made a stupid spelling mistake that cost you an hour. waiting time. At this time, we carefully “verify” a program before submitting it. This system would allow for a similar process where you test your basic logic flow on a virtual machine before incurring the wait time for a real computer to execute it.

Of course, if you really need a quantum computer, the simulation is probably too slow to be practical. But at least it might help you sort out the little issues before you tackle the whole enchilada. What will you do with a quantum computer? Tell us in the comments.

Google, of course, likes its own language, Cirq. If you want to get a head start on general concepts with a user-friendly simulator, try our series.

What's Your Reaction?

like

dislike

love

funny

angry

sad

wow