[Tutorial] Real-Time Benchmarking for Qubit Selection

[majo-lozano]

This tutorial is meant to update / replace the current Real-Time Benchmarking Qubit Selection Tutorial.

This tutorial shows how to run real-time characterization experiments and update backend properties to improve qubit selection when mapping a circuit to the physical qubits on QPU.

The main goal is to demonstrate the benefits of running real-time characterization experiments before executing a quantum circuit. Users will learn how to:

• Perform basic characterization experiments in Qiskit to determine the
  key properties of a QPU.
• Update QPU error properties with real-time data and use them to
  transpile circuits, enabling the selection of the best-performing qubit
  layouts before execution on actual hardware.

To highlight the benefits of real-time QPU characterization, the tutorial establishes a correlation between predicted and measured hardware performance. This is done by transpiling and running the same circuit across several randomly selected layouts and comparing their outcomes. As a case study, we focus on a modified LUCJ circuit, which is commonly used as an ansatz to estimate the ground-state energy of correlated electronic systems.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[qiskit-bot]

Thanks for contributing to Qiskit documentation!

Before your PR can be merged, it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. Thanks! 🙌

One or more of the following people are relevant to this code:

• @miamico

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ abbycross
❌ Maria Jose Lozano

---

Maria Jose Lozano seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Maria Jose Lozano seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[abbycross]

@miamico @nathanearnestnoble have you already reviewed content? If this is ready for copyediting, I can start going through it. GitHub won't allow me to do in-PR editing because of the size of the diff, unfortunately!

@mjlp123, can you please make sure the email you're using for your commits is matching what GitHub expects? Occasionally we see this problem where the CLA Assistant doesn't recognize an email address, so refer to these instructions to make sure the CLA check passes. Thank you!

[miamico]

@abbycross please hold off the copy edit for a few more days. We want to get another set of eyes on the technical aspects of the tutorial before copy editing

[miamico]

Gave another read and here's some minor feedback:

• when selecting a backend, use the least_busy function. see other tutorials as example
• Let's put this warning in a box so that it is more evident for readers (who will be more interested in real-time characterization to use the updated properties for execution rather than benchmarking) "Please note that in a real application, this should be done right before transpiling your circuit of interest, so the transpiler can use this information to select the best layout to run your circuit on. In this specific case, we have commented out the transpilation block because we already transpiled our circuit of interest on random layouts in the previous step pattern (which we needed to do in order to compare the perfomance of the circuit on different regions of the device).". There is an example of such "warning cell" in the old version of this same notebook

[majo-lozano]

Thanks @miamico, just implemented the changes suggested above.

I also signed the CLA so github recognizes my account.