# What is the Azure Quantum Resource Estimator?

The Azure Quantum Resource Estimator is an open-source tool that allows you to estimate the resources needed to run a quantum program on a fault-tolerant quantum computer.

The Resource Estimator calculates the total number of physical and logical qubits, the runtime, and details of the formulas and values used for each estimate. With the Azure Quantum Resource Estimator, you can compare qubit technologies, quantum error correction schemes, and other hardware characteristics to understand how they impact the resources needed to run a quantum program.

Tip

The Azure Quantum Resource Estimator is **free of charge** and doesn't require an Azure account.

## What features make the Resource Estimator unique?

The Resource Estimator is a powerful tool that involves all levels of quantum computing stack. The quantum computing stack can be divided into three levels: the application level, the quantum programming or compilation level, and the hardware or modeling level.

The Resource Estimator allows you to customize the parameters of each level and analyze how they impact the overall resources needed to run a quantum program.

### Customization

The Resource Estimator has an extensibility API to model any quantum architecture and to modify all assumptions. You can adapt the Resource Estimator and specify the characteristics of your quantum system.

You can use pre-defined qubit parameters and quantum error correction (QEC) schemes or configure unique settings across a wide range of machine characteristics. For more information, see Customize the target parameters of the Resource Estimator.

Target parameters | Describe your system |
---|---|

Physical qubit model | For example, specify the instruction set, the qubit measurement time, error rates, or gate times. |

Quantum error correction scheme | For example, specify the number of physical qubits per logical qubit, the logical cycle time, or the error correction threshold. |

Error budget | For example, specify the error budget to implement logical qubits, T states distillation, and synthesis of the rotation gates. |

Distillation units | For example, specify the number of T states required for the distillation process, number of T states produced as output from the distillation process, or the probability of failure of the distillation process. |

Constraints | For example, specify the maximum number of physical qubits, the maximum runtime, or the maximum number of T factory copies. |

Note

With the Resource Estimator, you can model any quantum architecture. For example, the startup Alice & Bob's uses the Resource Estimator to evaluate their architecture, which uses cat qubits and repetition error correction code. For more information, see this post in the Q# blog

### Flexibility

You can bring your own code and compilation tools to the Resource Estimator. The Resource Estimator supports any language that translates to QIR, for example, Q# and Qiskit. See Different ways to run the Resource Estimator.

### Batch multiple estimates

The Resource Estimator allows you to estimate the resources needed to run the same quantum algorithm for different configurations of target parameters, and compare the results. In this way you can understand how the qubit architecture, QEC scheme, and the rest of the target parameters impact the overall resources.

### Optimization

You can reduce the execution time of the Resource Estimator by incorporating some estimates in the overall cost. For example, if you're working with a large program, you can compute and cache the cost of subroutines, or if you already know estimates for an operation you can pass them to the Resource Estimator.

### Visualization of resources

You can visualize the tradeoffs between the number of physical qubits and the runtime of the algorithm using the space-time diagram, which allows you to find the optimal combination of {number of qubits, runtime} pairs.

You can also inspect the distribution of physical qubits used for the algorithm and the T factories using the space diagram.

## Get started with the Resource Estimator

The Resource Estimator is part of the Azure Quantum Development Kit (QDK). To get started, see Run your first resource estimate.

The following table shows different user scenarios and the recommended articles to start with the Resource Estimator.

User scenario | You want to |
---|---|

I'm developing QEC codes | You can use the Resource Estimator to customize your QEC codes and compare different combinations of parameters. See How to customize your QEC schemes. |

I'm developing quantum algorithms | By analyzing the impact of different configurations of hardware and software profiles on the resource requirements, you can gain insights into how your quantum algorithm might perform under different hardware and error conditions. This information can help you optimize your algorithm for specific quantum hardware or error rates. See Running multiple configurations of target parameters. |

I want to improve the performance of quantum programs | To learn how to harness the power of the Resource Estimator, see Running large programs and Using known estimates. |

I'm interested in large-scale quantum computing | You can use the Resource Estimator to analyze the resources of real-world problems that are expected to be solved by large-scale fault-tolerant quantum computers. See how in Resource estimation for large-scale quantum computing. |

I'm developing quantum-safe cryptography | You can use the Resource Estimator to compare the performance of different encryption algorithms, key strengths, qubit types, and error rates, and their resilience to quantum attacks. See Resource estimation and cryptography. |

Note

If you run into any issue while working with the Resource Estimator, check out the Troubleshooting page.

## Resource estimation for large-scale quantum computing

If you want to develop quantum algorithms for large-scale quantum computers, check out the Estimate the resources of a quantum chemistry problem tutorial.

This tutorial represents a first step to integrate resource estimation of quantum solutions to electronic structure problems. One of the most important applications of scaled quantum computers is solving quantum chemistry problems. The simulation of complex quantum mechanical systems has the potential to unlock breakthroughs in areas such as carbon capture, food insecurity, and designing better fuels and materials.

For example, one of the Hamiltonians used in this tutorial, the *nitrogenase_54orbital*, describes the nitrogenase enzyme. If you could accurately simulate how this enzyme works at a quantum level, it could help us to understand how to produce it at scale. You could replace the highly energy-intensive process which is used to produce enough fertilizer to feed the planet. This has the potential to reduce the global carbon footprint and also to help address concerns regarding food insecurity in a growing population.

## Why is resource estimation important in the development of quantum computing?

Although quantum computers promise to solve important scientific and commercial problems, achieving commercial viability will require large-scale, fault-tolerant quantum computers that have both a large number of qubits in superposition and physical error rates below a certain threshold. Commercial and scientific viability will also require QEC schemes to achieve fault tolerance. QEC is both time and space intensive, requiring increased execution time for algorithm or logical-level operations, as well as additional physical qubits to store and compute information.

Using the Resource Estimator, you can understand the impact of architectural design choices and quantum error correction schemes. The Resource Estimator will help you understand how many qubits are needed to run an application, how long it will take to run, and which qubit technologies are better suited to solving a specific problem. Understanding these requirements will allow you to prepare and refine quantum solutions to run on future, scaled quantum machines.

## Feedback

https://aka.ms/ContentUserFeedback.

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for