Quickstart: Create a quantum-based random number generator in Azure Quantum
Learn how to use Azure Quantum to create a simple quantum-based random number generator.
Prerequisites
To complete this tutorial, you need
- An Azure account with an active subscription. If you don’t have an Azure account, register for free and sign up for a pay-as-you-go subscription.
- Visual Studio Code, which you can download and use for free.
- The Microsoft QDK for VS Code extension.
- The Azure CLI and the quantum CLI extension.
- An Azure Quantum workspace with the IonQ provider enabled. For more information, see Create an Azure Quantum workspace.
Create a Q# project in Visual Studio Code
In VS Code open the View menu, and select Command Palette.
Type Q#: Create New Project.
Select Standalone console application.
Select a directory to hold your project, such as your home directory. Enter QuantumRNG as the project name, then select Create Project.
From the window that appears at the bottom, select Open new project.
You should see two files: QuantumRNG.csproj, the project file, and Program.qs, which contains starter code.
Start by opening the QuantumRNG.csproj file and adding the
ExecutionTargetproperty, which will give you design-time feedback on the compatibility of your program for IonQ's hardware.<Project Sdk="Microsoft.Quantum.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>net6.0</TargetFramework> <ExecutionTarget>ionq.qpu</ExecutionTarget> </PropertyGroup> </Project>Replace the contents of Program.qs with the program:
namespace QuantumRNG { open Microsoft.Quantum.Intrinsic; open Microsoft.Quantum.Measurement; open Microsoft.Quantum.Canon; @EntryPoint() operation GenerateRandomBits() : Result[] { use qubits = Qubit[4]; ApplyToEach(H, qubits); return MultiM(qubits); } }
Note
If you would like to learn more about this program code, see Create your first Q# program by using the Quantum Development Kit.
Prepare the Azure CLI
Next, we'll prepare your environment to run the program against the workspace you created.
From the Visual Studio Code menu, select Terminal > New Terminal.
Log in to Azure using your credentials. You'll get a list of subscriptions associated with your account.
az loginSpecify the subscription you want to use from those associated with your Azure account. You can also find your subscription ID in the overview of your workspace in the Azure portal.
az account set -s MySubscriptionIDUse
quantum workspace setto select the workspace you created above as the default Workspace. Note that you also need to specify the resource group and the location you created it in:az quantum workspace set -g MyResourceGroup -w MyWorkspace -l MyLocation -o tableLocation Name ProvisioningState ResourceGroup StorageAccount Usable ---------- ----------- ------------------- --------------- ------------------ -------- MyLocation MyWorkspace Succeeded MyResourceGroup /subscriptions/... YesNote
The MyLocation parameter in the example above is the Region specified on the Create Quantum Workspace page when following the steps in Create an Azure Quantum workspace. Region and Location are synonymous. The parameter value may be expressed in mixed case surrounded by quotes, for example,
-l "West US 2", or in lower case with no spaces or quotes, such as-l westus2.In your workspace, there are different targets available from the providers that you added when you created the workspace. You can display a list of all the available targets with the command
az quantum target list -o table:az quantum target list -o tableDepending on the provider you selected, you will see:
Provider Target-id Current Availability Average Queue Time (seconds) ------------ --------------------------------------------------- ---------------------- ------------------------------ ionq ionq.qpu Available 38715 ionq ionq.qpu.aria-1 Available 2042052 ionq ionq.simulator Available 2 microsoft-qc microsoft.estimator Available 0 quantinuum quantinuum.hqs-lt-s1 Available 232817 quantinuum quantinuum.hqs-lt-s1-apival Available 331 quantinuum quantinuum.hqs-lt-s2 Unavailable 0 quantinuum quantinuum.hqs-lt-s2-apival Available 7 quantinuum quantinuum.hqs-lt-s1-sim Available 19488 quantinuum quantinuum.hqs-lt-s2-sim Available 1577 quantinuum quantinuum.hqs-lt Available 0 quantinuum quantinuum.qpu.h1-1 Available 232817 quantinuum quantinuum.sim.h1-1sc Available 331 quantinuum quantinuum.qpu.h1-2 Unavailable 0 quantinuum quantinuum.sim.h1-2sc Available 7 quantinuum quantinuum.sim.h1-1e Available 19488 quantinuum quantinuum.sim.h1-2e Available 1577 quantinuum quantinuum.qpu.h1 Unavailable 0 rigetti rigetti.sim.qvm Available 5 rigetti rigetti.qpu.aspen-11 Unavailable 0 rigetti rigetti.qpu.aspen-m-2 Available 5 rigetti rigetti.qpu.aspen-m-3 Available 5 Microsoft microsoft.paralleltempering-parameterfree.cpu Available 0 Microsoft microsoft.paralleltempering.cpu Available 0 Microsoft microsoft.simulatedannealing-parameterfree.cpu Available 0 Microsoft microsoft.simulatedannealing.cpu Available 0 Microsoft microsoft.tabu-parameterfree.cpu Available 0 Microsoft microsoft.tabu.cpu Available 0 Microsoft microsoft.qmc.cpu Available 0 Microsoft microsoft.populationannealing.cpu Available 0 Microsoft microsoft.populationannealing-parameterfree.cpu Available 0 Microsoft microsoft.substochasticmontecarlo.cpu Available 0 Microsoft microsoft.substochasticmontecarlo-parameterfree.cpu Available 0Note
When you submit a job in Azure Quantum it will wait in a queue until the provider is ready to run your program. The Average Queue Time column of the target list command shows you how many seconds recently run jobs waited in the queue. This can give you an idea of how long you might have to wait.
Simulate the program in the IonQ provider
Before you run a program against real hardware, we recommend simulating it first (if possible, based on the number of qubits required) to help ensure that your algorithm is doing what you want. Fortunately, IonQ provides an idealized simulator that you can use.
Note
You can also simulate Q# programs locally using the :::no-loc text="Full state::: simulator.
Run your program with az quantum execute --target-id ionq.simulator -o table. This command will compile your program, submit it to Azure Quantum, and wait until IonQ has finished simulating the program. Once it's done it will output a histogram which should look like the one below:
az quantum execute --target-id ionq.simulator -o table
Result Frequency
--------- ----------- -------------------------
[0,0,0,0] 0.06250000 ▐█ |
[1,0,0,0] 0.06250000 ▐█ |
[0,1,0,0] 0.06250000 ▐█ |
[1,1,0,0] 0.06250000 ▐█ |
[0,0,1,0] 0.06250000 ▐█ |
[1,0,1,0] 0.06250000 ▐█ |
[0,1,1,0] 0.06250000 ▐█ |
[1,1,1,0] 0.06250000 ▐█ |
[0,0,0,1] 0.06250000 ▐█ |
[1,0,0,1] 0.06250000 ▐█ |
[0,1,0,1] 0.06250000 ▐█ |
[1,1,0,1] 0.06250000 ▐█ |
[0,0,1,1] 0.06250000 ▐█ |
[1,0,1,1] 0.06250000 ▐█ |
[0,1,1,1] 0.06250000 ▐█ |
[1,1,1,1] 0.06250000 ▐█ |
This shows an equal frequency for each of the 16 possible states for measuring 4 qubits, which is what we expect from an idealized simulator! This means we're ready to run it on the QPU.
Run the program on hardware
To run the program on hardware, we'll use the asynchronous job submission command az quantum job submit. Like the execute command, this will compile and submit your program, but it won't wait until the execution is complete. We recommend this pattern for running against hardware, because you may need to wait a while for your job to finish. To get an idea of how long that may be, you can run az quantum target list -o table as described earlier.
az quantum job submit --target-id ionq.qpu -o table
Name ID Status Target Submission time
---------- ------------------------------------ -------- -------- ---------------------------------
QuantumRNG 5aa8ce7a-25d2-44db-bbc3-87e48a97249c Waiting ionq.qpu 2020-10-22T22:41:27.8855301+00:00
The table shows that your job has been submitted and is waiting for its turn to run. To check on the status, use the az quantum job show command, being sure to replace the job-id parameter with the ID output by the previous command, for example:
az quantum job show -o table --job-id 5aa8ce7a-25d2-44db-bbc3-87e48a97249c
Name ID Status Target Submission time
---------- ------------------------------------ -------- -------- ---------------------------------
QuantumRNG 5aa8ce7a-25d2-44db-bbc3-87e48a97249c Waiting ionq.qpu 2020-10-22T22:41:27.8855301+00:00
Eventually, you will see the Status in the above table change to Succeeded. Once that's done you can get the results from the job by running az quantum job output:
az quantum job output -o table --job-id 5aa8ce7a-25d2-44db-bbc3-87e48a97249c
Result Frequency
--------- ----------- -------------------------
[0,0,0,0] 0.05200000 ▐█ |
[1,0,0,0] 0.07200000 ▐█ |
[0,1,0,0] 0.05000000 ▐█ |
[1,1,0,0] 0.06800000 ▐█ |
[0,0,1,0] 0.04600000 ▐█ |
[1,0,1,0] 0.06000000 ▐█ |
[0,1,1,0] 0.06400000 ▐█ |
[1,1,1,0] 0.07600000 ▐██ |
[0,0,0,1] 0.04800000 ▐█ |
[1,0,0,1] 0.06200000 ▐█ |
[0,1,0,1] 0.07400000 ▐█ |
[1,1,0,1] 0.08000000 ▐██ |
[0,0,1,1] 0.05800000 ▐█ |
[1,0,1,1] 0.06800000 ▐█ |
[0,1,1,1] 0.05200000 ▐█ |
[1,1,1,1] 0.07000000 ▐█ |
The histogram you receive may be slightly different than the one above, but you should find that the states generally are observed with equal frequency.
Prerequisites
To complete this tutorial, you need
- An Azure account with an active subscription. If you don’t have an Azure account, register for free and sign up for a pay-as-you-go subscription.
- Visual Studio Code, which you can download and use for free.
- The Microsoft QDK for VS Code extension.
- The Azure CLI and the quantum CLI extension.
- An Azure Quantum workspace with the Quantinuum provider enabled. For more information, see Create an Azure Quantum workspace.
Create a Q# project in Visual Studio Code
In VS Code open the View menu, and select Command Palette.
Type Q#: Create New Project.
Select Standalone console application.
Select a directory to hold your project, such as your home directory. Enter QuantumRNG as the project name, then select Create Project.
From the window that appears at the bottom, select Open new project.
You should see two files: QuantumRNG.csproj, the project file, and Program.qs, which contains starter code.
Start by opening the QuantumRNG.csproj file and adding the
ExecutionTargetproperty, which provides design-time feedback on the compatibility of your program for Quantinuum's hardware.<Project Sdk="Microsoft.Quantum.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>net6.0</TargetFramework> <ExecutionTarget>quantinuum.qpu.h1-1</ExecutionTarget> </PropertyGroup> </Project>Replace the contents of Program.qs with the program:
namespace QuantumRNG { open Microsoft.Quantum.Intrinsic; open Microsoft.Quantum.Measurement; open Microsoft.Quantum.Canon; @EntryPoint() operation GenerateRandomBits() : Result[] { use qubits = Qubit[4]; ApplyToEach(H, qubits); return MultiM(qubits); } }
Note
If you would like to learn more about this program code, see Create your first Q# program by using the Quantum Development Kit.
Prepare the Azure CLI
Next, we'll prepare your environment to run the program against the workspace you created.
From the Visual Studio Code menu, select Terminal > New Terminal.
Log in to Azure using your credentials. You'll get a list of subscriptions associated with your account.
az loginSpecify the subscription you want to use from those associated with your Azure account. You can also find your subscription ID in the overview of your workspace in the Azure portal.
az account set -s MySubscriptionIDUse
quantum workspace setto select the workspace you created above as the default Workspace. Note that you also need to specify the resource group and the location you created it in:az quantum workspace set -g MyResourceGroup -w MyWorkspace -l MyLocation -o tableLocation Name ProvisioningState ResourceGroup StorageAccount Usable ---------- ----------- ------------------- --------------- ------------------ -------- MyLocation MyWorkspace Succeeded MyResourceGroup /subscriptions/... YesNote
The MyLocation parameter in the example above is the Region specified on the Create Quantum Workspace page when following the steps in Create an Azure Quantum workspace. Region and Location are synonymous. The parameter value may be expressed in mixed case surrounded by quotes, for example,
-l "West US 2", or in lower case with no spaces or quotes, such as-l westus2.In your workspace, there are different targets available from the providers that you added when you created the workspace. You can display a list of all the available targets with the command
az quantum target list -o table:Note
The target names for the Quantinuum Syntax Checkers, Emulators, and QPUs have recently changed. The updated names are used in this topic. For details, see the Quantinuum provider topic.
az quantum target list -o tablewhich gives you the output
Provider Target-id Current Availability Average Queue Time (seconds) ------------ --------------------------------------------------- ---------------------- ------------------------------ ionq ionq.qpu Available 38715 ionq ionq.qpu.aria-1 Available 2042052 ionq ionq.simulator Available 2 microsoft-qc microsoft.estimator Available 0 quantinuum quantinuum.hqs-lt-s1 Available 232817 quantinuum quantinuum.hqs-lt-s1-apival Available 331 quantinuum quantinuum.hqs-lt-s2 Unavailable 0 quantinuum quantinuum.hqs-lt-s2-apival Available 7 quantinuum quantinuum.hqs-lt-s1-sim Available 19488 quantinuum quantinuum.hqs-lt-s2-sim Available 1577 quantinuum quantinuum.hqs-lt Available 0 quantinuum quantinuum.qpu.h1-1 Available 232817 quantinuum quantinuum.sim.h1-1sc Available 331 quantinuum quantinuum.qpu.h1-2 Unavailable 0 quantinuum quantinuum.sim.h1-2sc Available 7 quantinuum quantinuum.sim.h1-1e Available 19488 quantinuum quantinuum.sim.h1-2e Available 1577 quantinuum quantinuum.qpu.h1 Unavailable 0 rigetti rigetti.sim.qvm Available 5 rigetti rigetti.qpu.aspen-11 Unavailable 0 rigetti rigetti.qpu.aspen-m-2 Available 5 rigetti rigetti.qpu.aspen-m-3 Available 5 Microsoft microsoft.paralleltempering-parameterfree.cpu Available 0 Microsoft microsoft.paralleltempering.cpu Available 0 Microsoft microsoft.simulatedannealing-parameterfree.cpu Available 0 Microsoft microsoft.simulatedannealing.cpu Available 0 Microsoft microsoft.tabu-parameterfree.cpu Available 0 Microsoft microsoft.tabu.cpu Available 0 Microsoft microsoft.qmc.cpu Available 0 Microsoft microsoft.populationannealing.cpu Available 0 Microsoft microsoft.populationannealing-parameterfree.cpu Available 0 Microsoft microsoft.substochasticmontecarlo.cpu Available 0 Microsoft microsoft.substochasticmontecarlo-parameterfree.cpu Available 0Note
When you submit a job in Azure Quantum it will wait in a queue until the provider is ready to run your program. The Average Queue Time column of the target list command shows you how many seconds recently run jobs waited in the queue. This can give you an idea of how long you might have to wait.
Check your program in the Quantinuum syntax checker
Before you run a program against real hardware, we recommend running it against a quantum simulator first (if possible, based on the number of qubits required) to help ensure that your algorithm is doing what you want.
To run your program with the Quantinuum syntax checker, submit the following command:
az quantum execute --target-id quantinuum.sim.h1-1sc -o table
This command compiles your program, submits it to the Quantinuum syntax checker, and waits until it has finished simulating the program. Once it's done, it outputs a histogram similar to this:
Result Frequency
--------- ----------- ----------------------
[0,0,0,0] 1.00000000 |████████████████████|
Looking at the histogram, you may notice that the random number generator returned 0 every time, which isn't very random. This is because that, while the syntax checker ensures that your code will run successfully on Quantinuum hardware, it also returns 0 for every quantum measurement. For a true random number generator, you need to run your circuit on quantum hardware.
Run the program on hardware
To run the program on hardware, we'll use the asynchronous job submission command az quantum job submit. Like the execute command, this will compile and submit your program, but it won't wait until the execution is complete. We recommend this pattern for running against hardware, because you may need to wait a while for your job to finish. To get an idea of how long that may be, you can run az quantum target list -o table as described earlier.
az quantum job submit --target-id quantinuum.qpu.h1-1 -o table
Name ID Status Target Submission time
---------- ------------------------------------ -------- -------- ---------------------------------
QuantumRNG b4d17c63-2119-4d92-91d9-c18d1a07e08f Waiting quantinuum.qpu.h1-1 2020-01-12T22:41:27.8855301+00:00
The table shows that your job has been submitted and is waiting for its turn to run. To check on the status, use the az quantum job show command, being sure to replace the job-id parameter with the Id output by the previous command, for example:
az quantum job show -o table --job-id b4d17c63-2119-4d92-91d9-c18d1a07e08f
Name ID Status Target Submission time
---------- ------------------------------------ -------- -------- ---------------------------------
QuantumRNG b4d17c63-2119-4d92-91d9-c18d1a07e08f Waiting quantinuum.qpu.h1-1 2020-10-22T22:41:27.8855301+00:00
Status in the above table changes to Succeeded. Once that's done you can get the results from the job by running az quantum job output:
az quantum job output -o table --job-id b4d17c63-2119-4d92-91d9-c18d1a07e08f
Result Frequency
--------- ----------- -------------------------
[0,0,0,0] 0.05200000 ▐█ |
[1,0,0,0] 0.07200000 ▐█ |
[0,1,0,0] 0.05000000 ▐█ |
[1,1,0,0] 0.06800000 ▐█ |
[0,0,1,0] 0.04600000 ▐█ |
[1,0,1,0] 0.06000000 ▐█ |
[0,1,1,0] 0.06400000 ▐█ |
[1,1,1,0] 0.07600000 ▐██ |
[0,0,0,1] 0.04800000 ▐█ |
[1,0,0,1] 0.06200000 ▐█ |
[0,1,0,1] 0.07400000 ▐█ |
[1,1,0,1] 0.08000000 ▐██ |
[0,0,1,1] 0.05800000 ▐█ |
[1,0,1,1] 0.06800000 ▐█ |
[0,1,1,1] 0.05200000 ▐█ |
[1,1,1,1] 0.07000000 ▐█ |
The histogram you receive may be slightly different than the one above, but you should find that the states generally are observed with equal frequency.
Prerequisites
To complete this tutorial, you need
- An Azure account with an active subscription. If you don’t have an Azure account, register for free and sign up for a pay-as-you-go subscription.
- Visual Studio Code, which you can download and use for free.
- The Microsoft QDK for VS Code extension.
- The Azure CLI and the quantum CLI extension.
- An Azure Quantum workspace with the Rigetti provider enabled. For more information, see Create an Azure Quantum workspace.
Create a Q# project in Visual Studio Code
In VS Code open the View menu, and select Command Palette.
Type Q#: Create New Project.
Select Standalone console application.
Select a directory to hold your project, such as your home directory. Enter QuantumRNG as the project name, then select Create Project.
From the window that appears at the bottom, select Open new project.
You should see two files: QuantumRNG.csproj, the project file, and Program.qs, which contains starter code.
Start by opening the QuantumRNG.csproj file and adding the
ExecutionTargetproperty, which provides design-time feedback on the compatibility of your program for Rigetti's hardware.<Project Sdk="Microsoft.Quantum.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>net6.0</TargetFramework> <ExecutionTarget>rigetti.qpu.aspen-m-3</ExecutionTarget> </PropertyGroup> </Project>Replace the contents of Program.qs with the program:
namespace QuantumRNG { open Microsoft.Quantum.Intrinsic; open Microsoft.Quantum.Measurement; open Microsoft.Quantum.Canon; @EntryPoint() operation GenerateRandomBits() : Result[] { use qubits = Qubit[4]; for q in qubits { H(q); } return MeasureEachZ(qubits); } }Note
While achieving the same results, the example code for Rigetti differs from the other examples in this Quickstart, using a
forloop to perform the quantumHoperation andMeasureEachZto measure the results. Currently, Rigetti targets do not support mutable arrays, and therefore do not support theApplyToEachorMultiMoperations.
Prepare the Azure CLI
Next, we'll prepare your environment to run the program against the workspace you created.
From the Visual Studio Code menu, select Terminal > New Terminal.
Log in to Azure using your credentials. You'll get a list of subscriptions associated with your account.
az loginSpecify the subscription you want to use from those associated with your Azure account. You can also find your subscription ID in the overview of your workspace in the Azure portal.
az account set -s MySubscriptionIDUse
quantum workspace setto select the workspace you created above as the default Workspace. Note that you also need to specify the resource group and the location you created it in:az quantum workspace set -g MyResourceGroup -w MyWorkspace -l MyLocation -o tableLocation Name ProvisioningState ResourceGroup StorageAccount Usable ---------- ----------- ------------------- --------------- ------------------ -------- MyLocation MyWorkspace Succeeded MyResourceGroup /subscriptions/... YesNote
The MyLocation parameter in the example above is the Region specified on the Create Quantum Workspace page when following the steps in Create an Azure Quantum workspace. Region and Location are synonymous. The parameter value may be expressed in mixed case surrounded by quotes, for example,
-l "West US 2", or in lower case with no spaces or quotes, such as-l westus2.In your workspace, there are different targets available from the providers that you added when you created the workspace. You can display a list of all the available targets with the command
az quantum target list -o table:az quantum target list -o tablewhich gives you the output similar to
Provider Target-id Current Availability Average Queue Time ---------- ------------------------------------------- -------------------- -------------------- ionq ionq.qpu Available 0 ionq ionq.qpu.aria-1 Available 0 ionq ionq.simulator Available 0 microsoft-q c microsoft.estimator quantinuum quantinuum.qpu.h1-1 Available 0 quantinuum quantinuum.qpu.h1-1sc Available 0 quantinuum quantinuum.qpu.h1-1e Available 0 quantinuum quantinuum.qpu.h1-2 Available 0 quantinuum quantinuum.qpu.h1-2sc Available 0 quantinuum quantinuum.qpu.h1-2e Available 0 rigetti rigetti.sim.qvm Available 5 rigetti rigetti.qpu.aspen-11 Unavailable 0 rigetti rigetti.qpu.aspen-m-2 Available 5 rigetti rigetti.qpu.aspen-m-3 Available 5Note
When you submit a job in Azure Quantum it will wait in a queue until the provider is ready to run your program. The Average Queue Time column of the target list command shows you how many seconds recently run jobs waited in the queue. This can give you an idea of how long you might have to wait.
Simulate the program in the Rigetti simulator
Before you run a program against real hardware, we recommend running it against a quantum simulator first (if possible, based on the number of qubits required) to help ensure that your algorithm is doing what you want.
To run your program with the Rigetti QVM simulator, submit the following command:
az quantum execute --target-id rigetti.sim.qvm -o table
This command compiles your program, submits it to the Rigetti QVM simulator, and waits until it has finished simulating the program. Once it's done, it outputs a histogram similar to this:
Result Frequency
------------ ----------- ----------------------[0, 0, 0, 0] 0.06600000 |█ |
[1, 1, 1, 1] 0.05800000 |█ |
[0, 0, 0, 1] 0.06000000 |█ |
[0, 1, 1, 1] 0.07400000 |█ |
[0, 0, 1, 1] 0.05800000 |█ |
[1, 0, 1, 0] 0.06400000 |█ |
[1, 1, 0, 1] 0.07600000 |██ |
[1, 1, 0, 0] 0.04400000 |█ |
[0, 1, 0, 1] 0.06000000 |█ |
[1, 0, 1, 1] 0.07400000 |█ |
[0, 1, 0, 0] 0.05800000 |█ |
[0, 0, 1, 0] 0.07200000 |█ |
[0, 1, 1, 0] 0.06800000 |█ |
[1, 1, 1, 0] 0.05600000 |█ |
[1, 0, 0, 0] 0.05600000 |█ |
[1, 0, 0, 1] 0.05600000 |█ |
Run the program on hardware
To run the program on hardware, we'll use the asynchronous job submission command az quantum job submit. Like the execute command, this will compile and submit your program, but it won't wait until the execution is complete. We recommend this pattern for running against hardware, because you may need to wait a while for your job to finish. To get an idea of how long that may be, you can run az quantum target list -o table as described earlier.
az quantum job submit --target-id rigetti.qpu.aspen-m-3 -o table
Name ID Status Target Submission time
---------- ------------------------------------ -------- -------- ---------------------------------
QuantumRNG b4d17c63-2119-4d92-91d9-c18d1a07e08f Waiting rigetti.qpu.aspen-m-3 2020-01-12T22:41:27.8855301+00:00
The table shows that your job has been submitted and is waiting for its turn to run. To check on the status, use the az quantum job show command, being sure to replace the job-id parameter with the ID output by the previous command, for example:
az quantum job show -o table --job-id b4d17c63-2119-4d92-91d9-c18d1a07e08f
Name ID Status Target Submission time
---------- ------------------------------------ -------- -------- ---------------------------------
QuantumRNG b4d17c63-2119-4d92-91d9-c18d1a07e08f Waiting rigetti.qpu.aspen-m-3 2020-10-22T22:41:27.8855301+00:00
Eventually, you'll see Status in the above table change to Succeeded. Once that's done, you can get the results from the job by running az quantum job output:
az quantum job output -o table --job-id b4d17c63-2119-4d92-91d9-c18d1a07e08f
Result Frequency
--------- ----------- -------------------------
[0,0,0,0] 0.05200000 ▐█ |
[1,0,0,0] 0.07200000 ▐█ |
[0,1,0,0] 0.05000000 ▐█ |
[1,1,0,0] 0.06800000 ▐█ |
[0,0,1,0] 0.04600000 ▐█ |
[1,0,1,0] 0.06000000 ▐█ |
[0,1,1,0] 0.06400000 ▐█ |
[1,1,1,0] 0.07600000 ▐██ |
[0,0,0,1] 0.04800000 ▐█ |
[1,0,0,1] 0.06200000 ▐█ |
[0,1,0,1] 0.07400000 ▐█ |
[1,1,0,1] 0.08000000 ▐██ |
[0,0,1,1] 0.05800000 ▐█ |
[1,0,1,1] 0.06800000 ▐█ |
[0,1,1,1] 0.05200000 ▐█ |
[1,1,1,1] 0.07000000 ▐█ |
The histogram you receive may be slightly different than the one above, but you should find that the states generally are observed with equal frequency.
Note
If you run into an error while working with Azure Quantum, you can check our list of common issues.
Next steps
This quickstart demonstrated how to get started running Q# programs against different quantum computing simulators and QPUs. For more information on the available providers, see the Quantum computing provider overview documentation.
We recommend you continue your journey by learning more about the different types of targets in Azure Quantum, which dictate the types of Q# programs you can run against a given provider. You might also be interested in learning how to submit Q# jobs with Python, Jupyter Notebooks, or the Azure CLI.
Looking for more samples to run? Check out the samples directory for Azure Quantum.
Lastly, if you would like to learn more about writing Q# programs please see the Q# programming language user guide.
Feedback
Submit and view feedback for