AI Generated Video Summary
1. Introduction to Stuart Smith's VR Journey
Hi, I'm Stuart Smith. I've been part of the virtual reality community for quite some time now. I got involved in web VR back when building web-based virtual reality meant asking Brandon Jones over at Google for custom builds of Chromium. I released Space Rocks, a personal tribute to Atari's 1979 classic Asteroids, but in VR, of course. I also wrote HandyJS for both recording and recognizing hand poses on the fly. I've made a lot of work outside of VR, too. I'm educated as a graphic designer and artist. I've worked as a commissioned artist and had artwork exhibited in various galleries and museums. I'm also a lifelong mediocre-to-terrible musician.
I got involved in web VR back when building web-based virtual reality meant asking Brandon Jones over at Google for custom builds of Chromium. The medium felt really fresh and exciting. And around that time, I wrote the VR controller library for 3JS. It provided an easy, generic way for your web VR app to support a bunch of different hand controllers without having to write custom code for each one. So back then, that meant, you know, the first Vive controllers, Microsoft Mixed Reality controllers, Rift Touch, Daydream, and remember Gear VR? And all that stuff.
Over at the Google Data Arts team, we used the VR controller library to power this VR music video for the band LCD Sound System. You could dance along to the song in VR, and then a recording of your dance would become part of the video itself. So shout out to our collaborators and the real stars of that project, Studio Moniker and Studio Pucky. Look them both up.
I also released Space Rocks, a personal tribute to Atari's 1979 classic Asteroids, but in VR, of course. I took my VR controller library and I added something I called multi-channel haptic feedback. Which made it super easy to add complex haptic commands to your web VR app. Like, if you wanted kickback from firing your laser, but also needed to feel the hum of your plasma engines revving up and down, well, my haptic channels approach made that a breeze. Just a few years later, Oculus upped the game by adding a hand tracking API for web-based VR. I immediately wrote HandyJS. For both recording and recognizing hand poses on the fly. So instead of just pinch gestures to select things, with HandyJS you could easily recognize the whole ASL finger spelling alphabet and then some. Finger guns was most fun, obviously. This library does not require any machine learning whatsoever. Seriously, there's no network inside of Handy, it's some k-means clustering magic. And it is wicked fast.
I've made a lot of work outside of VR, too. I started coding when I was quite young, but I'm educated as a graphic designer and artist. I didn't study computer science. I've worked as a commissioned artist, and I've had artwork exhibited in various galleries and museums. I'm also a lifelong mediocre-to-terrible musician.
2. Stuart Smith's Quantum Computing Journey
And okay, that's all great, right? But what exactly is quantum computing? What even is a quantum computer? This. This is a quantum computer right here. This hanging cylindrical tank that you see. There are different sorts of quantum computer architectures, polarized photons, trapped ions, superconductors. Right now, superconducting quantum computers, like you see here, are the most popular kind.
3. Inside the Quantum Computer
Superconducting quantum computers require extreme cold to function. The actual quantum computation happens on a tiny chip. A quantum computer is like a graphics card, computing graphics. Companies like IBM, Rigetti, Google hook these golden monsters up to the internet to carry out quantum computation tasks.
They're used by companies like IBM, or Getty, Google. Superconducting quantum computers require extreme cold to function, just a hair above absolute zero. What we're looking at here is actually the refrigeration tank that holds the computing parts. Let's look inside that tank.
Here we see someone servicing the parts that would normally be covered by the refrigeration tank during operation. This is what some folks call the golden chandelier. All of this intricate hardware inside the refrigeration tank is for supercooling and gently nudging electron pairs. Using the quantum nature of this internal environment to represent data and perform computations on that data. Here is a glamour shot of a golden chandelier. I'm told that there is some actual gold plating in here for thermal and corrosion prevention purposes, but what we're looking at is mostly copper alloys. It's still pretty though.
The actual quantum computation happens right here on this tiny chip itself. It sits at the very bottom, the coldest part of the chandelier. This is where you actually nudge and measure the state of your electron pairs. And just to be clear, this hardware does not do some kind of magic. Our universe is already quantum in nature. We humans are just too big, and our environment is too noisy to be able to observe quantum effects directly. That's why we have to make really intricate hardware that can make these effects visible and useful to us.
Okay, but you might notice this so-called computer does not seem to have a keyboard or mouse or even a monitor. It's definitely a computer but not in the sense that we commonly use that word. It makes more sense to think about a quantum computer like a graphics card. If you're not familiar with graphics cards, this is one right here, you slot it into your computer's motherboard and it handles all the complex graphic rendering that your machine might need to do. If you're into high-end video games, you've probably been concerned about how powerful your graphics card is. Now, we never use the phrase graphics computer, though that's really what this is. It computes graphics.
So, we have a parallel situation here. A quantum computer is really a computing component. Instead of sliding it into your computer's motherboard like a graphics card, companies like IBM, Rigetti, Google, and so on, they hook these golden monsters up to the internet and you can send them quantum computation tasks to carry out. They'll run your program, and then they'll send you back the finished results. And this paradigm has been around forever, right? Maybe you think of it as cloud computing or time-sharing? When Pixar or Weta are rendering their computer-generated imagery for their next blockbuster film, they don't just render that on a single computer in the office.
4. Quantum Computing and QGS
No way, it's too complex. Instead they'll send that task out to what's called a render farm, racks and racks of raw computing hardware that you can access remotely. Unless you're at a university or a major corporation, you're going to write a quantum program right on your laptop or phone and send that over the internet to be run remotely on real quantum hardware. Let's say this circle represents quantum physics. This is all the knowledge about how the universe actually conducts itself. And over here is quantum computing. This is just pure math and logic. You don't need to know anything about electrons or superconducting or any of it. So all of that quantum hardware that makes up a quantum computer, it's really this intersection right here. That's actual physics and engineering in the service of creating a machine that can compute things. And that is great. It's all great. But this is really where QGS sits. I'm not a physicist. I'm not an engineer. QGS is not hardware. It's just software. So no physics, just computing.
No way, it's too complex. Instead they'll send that task out to what's called a render farm, racks and racks of raw computing hardware that you can access remotely. And that's the commercial model for using quantum computers today.
Unless you're at a university or a major corporation, you know, building this hardware yourself, you're going to write a quantum program right on your laptop or phone and send that over the internet to be run remotely on real quantum hardware like this. And then the results of that quantum execution will be pinged back to you when it's done.
Now, we just talked about quantum hardware, and we'll touch on quantum hardware again in a few minutes. But I want to make something clear. Let's say this circle represents quantum physics. This is all the knowledge about how the universe actually conducts itself. Photons, electrons, locality, tolerances, thermodynamics, packets of light, and so on. And over here is quantum computing. This is just pure math and logic. You don't need to know anything about electrons or superconducting or any of it. This is just computer programming.
Now, that statement might frustrate folks who understand both of these oceans of knowledge, but you don't need to know how electricity works to make a website, right? Same deal here. You don't need to actually know the physics in order to write some code. So all of that quantum hardware that makes up a quantum computer, it's really this intersection right here. That's actual physics and engineering in the service of creating a machine that can compute things. And that is great. It's all great. But this is really where QGS sits. I'm not a physicist. I'm not an engineer. QGS is not hardware. It's just software. So no physics, just computing. If we're being honest, my personal knowledge scape looks a little more like this. Random puddles of knowledge rather than a vast ocean. But also this. Because we humans are beautifully messy and nonsensical creatures.
Learning is a journey and I'm still at the beginning of my quantum journey, I think. If you think this stuff is exciting but worry that you're not a physicist, that you don't understand quantum mechanics, all of QGS has been built so far on these splotchy puddles of knowledge. You're in good company. Hop in the puddles with me.
Like I said, we'll touch on hardware again in a bit. But for now, let's talk about QGS itself. So this is the QGS website, really the hub for the whole Q experience. There are quantum tutorials, API documentation, and it's a playground for experimenting with quantum circuits. They're called circuits in the biz, so that's what I call them here. But it might be more helpful to think of them as programs, just code, just software.
6. Exploring QGS Circuit Interface
We can quickly build a Bell state and edit the circuit to get real output. We can add gates and switch between code and the drag and drop interface. Designing a user interface is about making tasks easier and more efficient for us human beings.
We get a circuit back. Let's make this a little larger. Let's see what that circuit looks like. We can get a diagram of it. It's not very interesting when we have a blank circuit. But here, we can quickly build that Bell state again. And you can see, as I'm editing the circuit, we're getting real output just like that. And here, let me scroll up. So we can actually see that this ASCII diagram looks very similar to what we have right here, doesn't it? And so that is pretty cool. And what's even cooler is we can start to do things like, let's say we want to add one of those H gates. That's a Hadamard gate, and we'll talk about that in a second. Let's add it to moment three on wire three, which should put it right there. Let's see if we can do that. Oh, and there it is. So we can actually jump back and forth between code and the drag and drop interface. So it's not about dumbing something down, not at all. With QGIS, you have access to this quantum circuit both through code and the drag and drop interface. And you can fluidly switch back and forth to whatever has least cognitive overhead in that moment. Let's say I need to get rid of everything here in moment two. I could certainly code that, or I could just select it and throw it away. So I just want to emphasize that designing a user interface and offering pictures to look at and click on is never about dumbing something down. It's about making tasks easier and more efficient for us human beings who require that. And there it is.
7. Introduction to Quantum Concepts
I debated whether to cram a crash course in quantum concepts into a 20-minute talk, but it would take about an hour. Instead, I'll give you a small taste and encourage you to visit the QGIS site and explore the links and references for more information.
Let's see. Now I debated whether or not I should try to cram a crash course in quantum concepts into a 20-minute talk, but I think it would take me about an hour to comfortably walk you through this stuff, and it gets a little mathy. So I'm going to mostly spare you, except for this. I want to give you a small taste of what's going on here, and hopefully that's intriguing enough that you will visit the QGIS site on your own to learn more. And better yet, check out our list of links and references so you can jump straight into some good source materials on your own.
8. Introduction to Qubits
Qubits are just a pair of numbers, representing the probabilities of a bit being 0 or 1. Alpha and beta are the two numbers that make up a qubit, and their sum must always be 100%.
So here we go. This is an actual page from the QGIS website describing qubits and what they are. And it starts out by saying qubits are just a pair of numbers. So a quantum bit, the smallest unit that you will use to do quantum computing, can be represented by a pair of numbers. Now, you might physically represent your qubits using photons or something else. But mathematically, it's just two numbers. That's it. And we can name one alpha, and we can name the other one beta. And the thing that makes this pair of numbers special is their relationship to each other. And here it is. Alpha squared plus beta squared must always equal exactly 1. And the reason is because alpha and beta represent the probabilities of a bit being 0 or 1, on or off. And the sum of those probabilities must always be 100%, right? In the end, there is an outcome.
9. Exploring Qubits and Amazon Bracket
Here we can find more information about qubits, including their names, in-depth descriptions, ket notation, and the block-sphere representation. Superposition is simply a state where outcomes have a mixture of probabilities, not just yes or no. The library has purposeful quirks, such as the use of a dollar sign to indicate mutation of state. Additionally, there's a mention of Amazon bracket, a quantum service that can be accessed through a Jupyter notebook, allowing the building and running of quantum circuits on simulators or actual quantum hardware.
And here we can just scroll down. You can see there's a whole lot more information here, descriptions of why qubits are named certain things, in-depth descriptions of why some are on and some are considered off, ket notation, all sorts of things that I'm just glossing over here. But you can really spend your own time with and get to know.
And this is my favorite right here, is the block-sphere representation of a qubit. So we can see this horizontal qubit, which is considered 0 or off, and the vertical qubit, which is its inverse. So this is considered on. And we also have all these other states. We can just rock around the clock here and see different qubit states. And qubits are really just matrices and vectors. And this will make a lot more sense in context when you look at gates and circuits.
One thing I just wanted to mention really quickly before we jump out of this is superposition. So you've probably heard some things like superposition means something, two things happen at the exact same time or maybe neither happen or something like that. Superposition just means a state where the probability of outcomes are not 100% yes or no, it's some mixture, that's it. I really like to demystify superposition because there's a lot of kind of pop science nonsense around it that just really doesn't translate once you learn the math.
One more thing that I want to touch on here is there are some purposeful quirks to this library. For example, when using the verbose syntax to do things with qubits, you'll notice that some commands have a dollar sign, for instance, at the end. This is a warning sign from the API. If you use the dollar sign, you are mutating your state, you are overwriting the value of that variable. You can see an example here where you add cat and dog and it's destructive, right? Notice that dollar sign suffix as opposed to the non-destructive version which will not change the value of cat. So that's just one example of some of the fun things you might encounter as you explore.
And, oh, right. I said I'd touch on quantum hardware again and here it is. I happen to work at Amazon for a little while in their web services division and Amazon just so happened to be working on a quantum service called Amazon bracket. You can access bracket through a prepared Jupyter notebook. Perhaps some of you might be familiar with Jupyter from doing machine learning. Anyway, here's a little demo video I made a few months before bracket launched using the QGIS interface to drive it. So here I have a Jupyter notebook with Amazon bracket loaded which means that I can use Python code, bracket is Python library, and I can use that to build quantum circuits that I can then run on a simulator in the cloud, or I can run on quantum hardware because Amazon has partnered with different quantum hardware vendors. And so we can do that, we can offer that to our customers and that's pretty exciting. But what's also exciting is this, with just a few lines of HTML, really two lines of HTML, I can inject QJS into this Jupyter notebook, it's now injected, and now I can inject my quantum circuit composer. And this composer, which should look awfully familiar, is writing bracket code.
10. Running Quantum Circuits
This is bracket Python code that can be run on a simulator or actual quantum hardware. It demonstrates a coin flip circuit using Hadamard and CNOT gates. The simulation has been run 100 times, with roughly even results of 00 and 11.
So this is actually bracket Python code, which right now is set to run on the simulator in the cloud so that we can get quicker results. But if you wanted to, you could switch what device we're running on, and you could actually run this on quantum hardware and get true quantum results. So check this out. Down here you can see where it says our QJS circuit equals a new circuit and it has a placeholder identity gate. This is bracket code, and we're about to watch it change as I start to compose stuff. Look at that, look how it put a Hadamard gate and created a CNOT gate. And we can take that and we can run that. What this is, is a coin flip circuit. And we're waiting for the output to come back from the cloud. So Hadamard puts the qubit into a state of superposition. And then this distributes that superposition to the qubit on the second register here. And so our two possible outcomes are 00 and 11. And you can see, we've gotten a result back from the simulator. It's run that simulation 100 times, which is a customizable number. And it's come back roughly even 54 times, it came out 00 and 46 times, it came out 11.
11. Using QJS to Build and Run Quantum Circuits
We can use the QJS drag and drop interface to build circuits and get real-time reports. It can build Amazon bracket code for running on simulators or actual quantum hardware. QJS enables driving actual quantum hardware, making quantum computing accessible to everyone. Get involved in the project and explore the resources available.